[
https://issues.apache.org/jira/browse/DERBY-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
V.Narayanan updated DERBY-3359:
-------------------------------
Attachment: DynamicLogShipping_v1.stat
DynamicLogShipping_v1.diff
Pls find attached the patch for the implementation of dynamic log shipping. I
have to test this code
for various cases but did not see that as stopping a review of this patch since
the design,
and the subsequent changes required have been described in detail in previous
comments on this patch.
I thought that the workToDo() method can be used in the place of the
forceFlush() method. When a
LogBufferFullException occurs in the MasterController the FI > 80 so this
method would automatically
result in shipALogChunk() being called. The only difference from calling
forceFlush() being that we do an
additional checking of FI before shipping. I am not sure this should be a
deterrent to using this method.
Consequently,
- Removed the use of forceFlush() when a LogBufferFullException is thrown
and replaced it with workToDo().
- Removed the forceFlush() method from the LogBuffer interface and its
AsynchronousLogShipper implementation
as it will not be used anymore.
- workToDo() will now be called both when a log buffer element becomes full
and when the log buffer becomes
full
> The log shipper needs to be modified to vary the shipping intervals
> dynamically (based on load)
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-3359
> URL: https://issues.apache.org/jira/browse/DERBY-3359
> Project: Derby
> Issue Type: Sub-task
> Reporter: V.Narayanan
> Assignee: V.Narayanan
> Attachments: DynamicLogShipping_v1.diff, DynamicLogShipping_v1.stat
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
