[
https://issues.apache.org/jira/browse/DERBY-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529834
]
V.Narayanan commented on DERBY-3064:
------------------------------------
>If I understand you correctly, this time interval will only be helpful in the
>"too soon" case, not the >"too late" case.
>When I wrote version 2 of the proof of concept patches (see DERBY-2872), I
>used a Daemon to >read log records at the slave side. I basically had:
>performWork {
> if (messageWaitingForProcess) processMessage();
>}
>The waiting interval between each time performWork was called was way too high
>for this usage >(in the order of 3-10 seconds). This interval is probably too
>high for the log shipper as well, so >my guess is that you'll need something
>similar to an eternal loop with a wait(millis) somewhere in >this package.
Does this mean atleast in the case of log shipper we would be forced to use
threading since the DaemonService interval cannot be varied?
Guess I have a LogShipper specific answer for DaemonService vs Threads if I am
right.
> 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
> Reporter: V.Narayanan
> Assignee: V.Narayanan
> Attachments: LogShipperImpl_v1.diff, LogShipperImpl_v1.stat
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
