[
https://issues.apache.org/jira/browse/BOOKKEEPER-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239888#comment-15239888
]
Matteo Merli commented on BOOKKEEPER-919:
-----------------------------------------
Extract from the failed test logs :
{noformat}
2016-04-07 19:50:12,979 - INFO -
[AuditorElector-10.208.165.209:15051:Auditor@195] - I'm starting as Auditor
Bookie. ID: 10.208.165.209:15051
2016-04-07 19:50:12,980 - INFO -
[AuditorElector-10.208.165.209:15051:Auditor@206] - Auditor periodic ledger
checking enabled 'auditorPeriodicCheckInterval' 604800 seconds
2016-04-07 19:50:12,985 - INFO -
[AuditorElector-10.208.165.209:15051:Auditor@252] - Auditor periodic bookie
checking enabled 'auditorPeriodicBookieCheckInterval' 86400 seconds
2016-04-07 19:50:12,995 - INFO - [Time-limited test:Bookie@945] -
Transitioning Bookie to ReadOnly mode, and will serve only read requests from
clients!
2016-04-07 19:50:12,998 - INFO - [Time-limited test:Bookie@849] - Registered
myself in ZooKeeper at /ledgers/available/readonly/10.208.165.209:15053.
2016-04-07 19:50:12,999 - INFO -
[AuditorBookie-10.208.165.209:15051:Auditor@330] - Following are the failed
bookies: [10.208.165.209:15053] and searching its ledgers for re-replication
2016-04-07 19:50:13,003 - INFO - [main-EventThread:NetworkTopology@463] -
Removing a node: /default-rack/10.208.165.209:15053
2016-04-07 19:50:13,003 - INFO -
[AuditorBookie-10.208.165.209:15051:Auditor@348] - Following ledgers: [0] of
bookie: 10.208.165.209:15053 are identified as underreplicated
{noformat}
> Auditor is sometimes marking as failed a bookie switching from available to
> read-only mode
> ------------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-919
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-919
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Matteo Merli
> Assignee: Matteo Merli
> Priority: Minor
> Fix For: 4.4.0
>
>
> AuditorLedgerCheckerTest.testReadOnlyBookieExclusionFromURLedgersCheck
> intermittently failing
> This test too, I've seen it failing in different occasions.
> https://builds.apache.org/job/bookkeeper-master-git-pullrequest/59/testReport/junit/org.apache.bookkeeper.replication/AuditorLedgerCheckerTest/testReadOnlyBookieExclusionFromURLedgersCheck_2_/
> {noformat}
> Error Message
> latch should not have completed
> Stacktrace
> java.lang.AssertionError: latch should not have completed
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at
> org.apache.bookkeeper.replication.AuditorLedgerCheckerTest.testReadOnlyBookieExclusionFromURLedgersCheck(AuditorLedgerCheckerTest.java:279)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
