[DERBY-3051] Replication: Modify logging subsystem to append log records to the replication buffer when in replication master mode

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.4.1.3
• Fix Version/s: 10.4.1.3
• Component/s: Services, Store
• Assignee: Jorgen Loland
• Reporter: Jorgen Loland
• Created: 05/Sep/07 11:29
• Updated: 02/May/13 02:29
• Resolved: 18/Sep/07 11:38

Description

When Derby has the replication master role for a database 'x', it should ship all log records generated for this database to the Derby with the slave role. A replication buffer was added to Derby in DERBY-2926. This issue is for modifying the logging subsystem to append log records to this buffer every time a log records is appended to the disk buffer (LogAccessFile). This will, of course, only be done if it has the master role.

Currently, I have identified two modifications that will be required in LogToFile:

• LogToFile#appendLogRecord needs to append to the replication buffer after appending to the disk buffer
• LogToFile#flush (i.e., the method used to force buffered log records to disk) must notify the Master Controller (DERBY-2977) that a flush has taken place. The MasterController will decide if any action is required because of this.

Issue Links

• depends upon: DERBY-2926 Replication: Add a log buffer for log records that should be shipped to the slave
• depends upon: DERBY-2977 Replication: Add a ReplicationMaster controller that will manage replication on the master side