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] Updated: (DERBY-3064) Implement the LogShipper that will enable the shipping of Log records from the master to the slave
Date Fri, 07 Dec 2007 12:29:43 GMT

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

V.Narayanan updated DERBY-3064:
-------------------------------

    Attachment: LogShipperIntegration_v5.stat
                LogShipperIntegration_v5.diff

>9. a) Will a timeout at this level work? As far as I can tell you
>      have not set any timeout on the socket. Is there a default
>      timeout, or do you risk that getting the connection may hang for
>      much longer than the desired timeout?

>   b) Don't you risk that the same error message may be written to
>      derby.log very many times before the timeout occurs? An
>      alternative could be to link the last received IOExcpetion to
>      the exception thrown when it times out.

I have changed the patch to use socket timeout. I have removed the earlier timeouts used at
this level. IOExceptions are now being thrown, since overshooting the time interval would
now
throw a SocketTimeoutException rather than a IOException.

>MasterFactory: Is SLAVE_DB a good name here? It seems to me that we
>are talking about the database at the master here.

Changed it to MASTER_DB

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


Mime
View raw message