db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "ReplicationWriteup" by narayanan
Date Mon, 10 Mar 2008 09:58:42 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by narayanan:
http://wiki.apache.org/db-derby/ReplicationWriteup

------------------------------------------------------------------------------
  
  == Basic Design ==
  
- A simple block diagram for the replication implementation can be found here
+ A simple block diagram for the replication implementation can be found below
  
- [http://issues.apache.org/jira/browse/Derby-2872 Derby-2872]
- 
- in the attachment ReplicationDesign.pdf
+ attachment:ReplicationDesign.gif
  
  The solid arrows indicate the flow of the log records through the system.
  
@@ -120, +118 @@

  is needed for the following reasons
  
  1) A buffer is needed because the log records should not be shipped one at a time.
+ 
  2) Writing to the log buffer instead of transmitting them immediately removes the network
communitcation from the
     critical path of the transaction.
+ 
  
  Related JIRA Issue(s)
  
@@ -136, +136 @@

  shipping in the following three-fold scenarios
  
  1) Periodically (i.e.) at regular intervals of time.
+ 
  2) when a request is sent from the master controller (force flushing of the log buffer).
+ 
  3) when a notification is received from the log shipper about a log buffer element becoming
full and the load on 
     the log buffer so warrants a ship.
+ 
  
  Related JIRA Issue(s)
  

Mime
View raw message