[ https://issues.apache.org/jira/browse/DERBY-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564650#action_12564650 ] 

V.Narayanan commented on DERBY-3359:
------------------------------------

>Based on this, I think workToDo case b) could simply be reduced 
>to on b.3, i.e. notify the log shipper thread that it has to wake up 
>no matter what. By doing that, we would still need the forceFlush 
>method, but the client thread would not be involved in log shipping
>until the buffer is 100% full.

makes sense to notify the log shipper thread and let it handle the log shipping.
I agree with your comments Jorgen! I will remove b.1 and b.2 and shall retain
forceFlush.

> 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
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.