Unconfigured Ad Widget

Collapse

Announcement

Collapse
No announcement yet.

High Availability Roundup

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • High Availability Roundup

    ** This thread discusses the article: High Availability Roundup **
    ** This thread discusses the Content article: High Availability Roundup **
    0

  • #2
    High Availability Roundup

    ** This thread discusses the article: High Availability Roundup **
    This from a friend at LakeView: MIMIX simulates Commitment Control on the target side. We do not actually use it. We "temporarily apply" changes inside a commit cycle until we get the commit or rollback. The apply session is smart enough to make things come out right. Note on the DB DB status screen, there is an indication of open commit cycles. Note also that the apply session does not take credit for applying changes within a commit cycle until it gets the commit or rollback. Customers have complained that the apply session appears to be "just sitting there". Actually, it is temporarily applying CC changes, but will not permanently apply them until the commit comes through.

    Comment


    • #3
      High Availability Roundup

      ** This thread discusses the article: High Availability Roundup **
      Thanks for that Mike, but I'm still a little puzzled - do you use some form of temporary storage to hold the pending changes which is then processed to write the records to the database (in the case of a commit), or scrapped (if a rollback) ?. I can see how that would work for relatively small commit charges, but must become a real overhead once the number of pending changes gets large, or is it done another way ?

      Comment

      Working...
      X