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-3064) Implement the LogShipper that will enable the shipping of Log records from the master to the slave
Date Mon, 10 Dec 2007 11:04:43 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550015

V.Narayanan commented on DERBY-3064:

1) when you attempt the first connect
2) when a connection failure occurs

1) I believe that if an IOException occurs here we should log the exception and exit. 
   User can handle the cause of the exception here and can restart replication after 
   correcting the problem. We do not know the severity of the cause of the IOException. 
   So it is very difficult to distinguish between when we should stop and re-try based
   on the cause. So I believe here we should exit when a timeout occurs.

2) Here we should re-try if a timeout or a IOException occurs. This would take care of
   the case for example when the network connection goes down and comes back again. Also
   if the log buffer is full and the network is down we fail aborting reconnect attempts.

Does this sound OK to you?

> Implement the LogShipper that will enable the shipping of Log records from the master
to the slave
> --------------------------------------------------------------------------------------------------
>                 Key: DERBY-3064
>                 URL: https://issues.apache.org/jira/browse/DERBY-3064
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Miscellaneous
>            Reporter: V.Narayanan
>            Assignee: V.Narayanan
>         Attachments: LogShipperImpl_v1.diff, LogShipperImpl_v1.stat, LogShipperImpl_v2.diff,
LogShipperImpl_v2.stat, LogShipperImpl_v3.diff, LogShipperImpl_v3.stat, LogShipperImpl_v4.diff,
LogShipperImpl_v4.stat, LogShipperImpl_v5.diff, LogShipperImpl_v5.stat, LogShipperIntegration_v1.diff,
LogShipperIntegration_v1.stat, LogShipperIntegration_v2.diff, LogShipperIntegration_v2.stat,
LogShipperIntegration_v3.diff, LogShipperIntegration_v3.stat, LogShipperIntegration_v4.diff,
LogShipperIntegration_v4.stat, LogShipperIntegration_v5.diff, LogShipperIntegration_v5.stat

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

View raw message