You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2013/01/02 17:12:13 UTC
[jira] [Updated] (BOOKKEEPER-409) Integration Test - Perform bookie
rereplication cycle by Auditor-RW processes
[ https://issues.apache.org/jira/browse/BOOKKEEPER-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Kelly updated BOOKKEEPER-409:
----------------------------------
Attachment: BOOKKEEPER-409.diff
When I ran the tests, it gave me a race, which was stopping netty from shutting down. Basically replication worker was killing the bookkeeper client before killing the thread, so the client was being used. I fixed the race in replication worker in the new patch. I'll create another jira for fixing the root issue in 4.3.0.
Also, I changed to used MultiLedgerManager not MultiLedgerManagerMultiDigest. The digest really shouldn't have an affect on this, and running both makes the test last twice as long.
Otherwise it looks good, so when I get a +1 on the ReplicationWorker fix, ill commit.
> Integration Test - Perform bookie rereplication cycle by Auditor-RW processes
> -----------------------------------------------------------------------------
>
> Key: BOOKKEEPER-409
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-409
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-auto-recovery
> Affects Versions: 4.2.0
> Reporter: Rakesh R
> Assignee: Rakesh R
> Labels: test
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-409-1.patch, BOOKKEEPER-409-2.patch, BOOKKEEPER-409-3.patch, BOOKKEEPER-409-4.patch, BOOKKEEPER-409-5.patch, BOOKKEEPER-409.diff, BOOKKEEPER-409.patch
>
>
> The idea is to perform integration testing of entire re-replication module : Auditor-RW processes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira