[
https://issues.apache.org/jira/browse/BOOKKEEPER-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Kelly updated BOOKKEEPER-718:
----------------------------------
Attachment: 0001-BOOKKEEPER-718-AuditorLedgerCheckerTest-is-flakey.patch
Problem was that BookKeeperAdmin was taking ownership of a bookkeeper and
zookeeper handle that was being passed in. This meant that when it was closed,
it would clean up both. In the test in question, multiple bookkeeperadmin
instances eventually shared the same zookeeper instance via auditor electors,
so when one auditor elector was shut down, it would kill the zookeeper session
of the other auditor electors and they weren't able to mark the unreplicated
ledgers.
> AuditorLedgerCheckerTest is flakey
> ----------------------------------
>
> Key: BOOKKEEPER-718
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-718
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-auto-recovery
> Reporter: Ivan Kelly
> Assignee: Ivan Kelly
> Fix For: 4.3.0
>
> Attachments:
> 0001-BOOKKEEPER-718-AuditorLedgerCheckerTest-is-flakey.patch, error505.txt,
> error509.txt
>
>
> See:
> https://builds.apache.org/job/bookkeeper-trunk/505/
> &
> https://builds.apache.org/job/bookkeeper-trunk/509
> Relevant errors attached.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
