[
https://issues.apache.org/jira/browse/DERBY-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529808
]
Øystein Grøvlen commented on DERBY-3064:
----------------------------------------
Thanks for the desgin overview, Narayanan. I have a few questions
around the scheduling of the shipping:
1. If I understand you correctly, log records will be shipped either
when the log buffer is full or when a timeout occur. If the traffic
is high so that the time it takes to fill the log buffer is
normally less than the timeout, this means that log will only be
sent when the log buffer is full. Would it not be better to try to
keep the log shipping ahead so that it never goes full?
2. It seems like you suggest that the shipping thread will continously
check to see whether the timeout has expired. Generally, such
busy-waits should be avoided. I think you should introduce a timer
or something so that the thread can be suspended until it is time
to ship log records.
3. You mention a ShippingDeamon, but it is not described what it is or
how it works. Is this a new thread that you will introduce or will
the LogShipper be run in the existing background thread?
> 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.
