db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jørgen Løland (JIRA) <j...@apache.org>
Subject [jira] Updated: (DERBY-2926) Replication: Add a log buffer for log records that should be shipped to the slave
Date Thu, 23 Aug 2007 09:36:31 GMT

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

Jørgen Løland updated DERBY-2926:

    Attachment: bytebuffer_resizefix_1.diff

I agree - the change you suggest would both make the code easier to read and be more effective.
The attached patch, resizefix_1, addresses this issue.

> Replication: Add a log buffer for log records that should be shipped to the slave
> ---------------------------------------------------------------------------------
>                 Key: DERBY-2926
>                 URL: https://issues.apache.org/jira/browse/DERBY-2926
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Services
>    Affects Versions:
>            Reporter: Jørgen Løland
>            Assignee: Jørgen Løland
>             Fix For:
>         Attachments: bytebuffer_resizefix_1.diff, bytebuffer_resizefix_1.stat, bytebuffer_v1-fixheader.diff,
bytebuffer_v1-fixheader.stat, bytebuffer_v1.diff, bytebuffer_v1.stat, bytebuffer_v1a.diff,
bytebuffer_v1a.stat, bytebuffer_v2.diff, bytebuffer_v2.stat, bytebuffer_v2b.diff, bytebuffer_v2b.stat
> When a Derby instance has the master role for a database, log records are shipped to
the slave to keep it up to date. A buffer is needed because the log records should not be
shipped one at a time. Also, writing the log records to a buffer instead of sending them immediately
removes the network communication from the critical path for the transaction.

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

View raw message