[
https://issues.apache.org/jira/browse/BOOKKEEPER-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Kelly updated BOOKKEEPER-776:
----------------------------------
Attachment: TEST-org.apache.bookkeeper.client.BookieRecoveryTest.xml.fail2
TEST-org.apache.bookkeeper.client.BookieRecoveryTest.xml.fail1
TEST-org.apache.bookkeeper.client.BookieRecoveryTest.xml
This is super weird. Basically, it can fail in many of the tests, but the mode
of failing is all the same. Recovery occurs, but then when it tries to verify
it cannot connect to the replaced bookie. But the bookie is there. It fails on
the PerChannelBookieClient connect, with a ClosedChannelException even though,
noone has a reference to the channel to close it before this point (triggers in
the channel future from the connect).
> Flaky test BookieRecoveryTest
> -----------------------------
>
> Key: BOOKKEEPER-776
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-776
> Project: Bookkeeper
> Issue Type: Test
> Components: bookkeeper-client
> Reporter: Sijie Guo
> Assignee: Ivan Kelly
> Labels: test
> Fix For: 4.3.0
>
> Attachments:
> TEST-org.apache.bookkeeper.client.BookieRecoveryTest.xml,
> TEST-org.apache.bookkeeper.client.BookieRecoveryTest.xml.fail1,
> TEST-org.apache.bookkeeper.client.BookieRecoveryTest.xml.fail2
>
>
> testMetadataConflictWithRecovery[0](org.apache.bookkeeper.client.BookieRecoveryTest):
> Not fully replicated
--
This message was sent by Atlassian JIRA
(v6.2#6252)
