db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3567) AsynchronousLogShipper#forceFlush should time out
Date Wed, 02 Apr 2008 10:18:24 GMT

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

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

The patch looks complete and very good,

Work has been done to remove the dependency of the forceFlush function on the client
thread and instead make the log shipper thread do the work.

I request the patch attached to this issue to be pls considered for a commit.

> AsynchronousLogShipper#forceFlush should time out
> -------------------------------------------------
>
>                 Key: DERBY-3567
>                 URL: https://issues.apache.org/jira/browse/DERBY-3567
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.4.0.0, 10.5.0.0
>            Reporter: Jørgen Løland
>         Attachments: derby-3567-1a.diff, derby-3567-1a.stat
>
>
> If the network connection to the slave is lost, ObjectOutputStream#writeObject may be
blocked for 2 minutes before failing (not configurable TCP property). 
> Currently, ALS#forceFlush sends a chunk of log to the slave using the client thread.
The client thread cannot be blocked for 2 minutes before giving up. Rather, it should notify
the log shipper that it has to send log immediately, and then wait for a short while (until
notified or e.g. maximum 5 seconds). If the log shipper has not been able to empty some space
in the log buffer by then, replication should be stopped.

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


Mime
View raw message