[ https://issues.apache.org/jira/browse/BOOKKEEPER-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15858579#comment-15858579 ]
Robert Joseph Evans commented on BOOKKEEPER-1000: ------------------------------------------------- It looks like this is a bug in BOOKKEEPER-873 and BOOKKEEPER-553. Not sure how this test ever passed for them. Essentially because the layout of the files changed for 2-4-4- to 3-4-4-4-4 it is not able to see the older ledgers. It just ignores them. It seems like we should be able to make it so that for IDs < max int we go with 2-4-4 and for > max int we go with 3-4-4-4-4. Or we just disable this particular test because it will never work. I would prefer to do the former because it provides a path towards a rolling upgrade. [~knusbaum] said he was already looking at this so I think I will just hand it off to him. > BookieRecoveryTest.ensurePasswordUsedForOldLedgers failing > ---------------------------------------------------------- > > Key: BOOKKEEPER-1000 > URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1000 > Project: Bookkeeper > Issue Type: Bug > Reporter: Robert Joseph Evans > Assignee: Robert Joseph Evans > > Tests in error: > BookieRecoveryTest.ensurePasswordUsedForOldLedgers[4] » BKNoSuchLedgerExists > BookieRecoveryTest.ensurePasswordUsedForOldLedgers[5] » BKNoSuchLedgerExists > This has been happening in master recently both in Jenkins and on my Mac. > I'll try to take a look at it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)