milleruntime commented on issue #1534: GarbageCollectorIT.gcLotsOfCandidatesIT 
failure
URL: https://github.com/apache/accumulo/issues/1534#issuecomment-594054633
 
 
   @jzgithub1 thanks for looking at this.
   
   I have seen that ```TestTimedOutException``` but I am not sure how useful 
that is.  The same goes with the similar client exception I have seen:
   ```
   java.lang.IllegalStateException: No lock is held at 
/accumulo/1d1562ff-4b75-47e1-b7d0-edf08778bd96/gc/lock
        at 
org.apache.accumulo.fate.zookeeper.ZooLock.deleteLock(ZooLock.java:499) 
~[accumulo-core-2.1.0-SNAPSHOT.jar:2.1.0-SNAPSHOT]
        at 
org.apache.accumulo.test.functional.GarbageCollectorIT.killMacGc(GarbageCollectorIT.java:106)
 [classes/:?]
        at 
org.apache.accumulo.test.functional.GarbageCollectorIT.gcLotsOfCandidatesIT(GarbageCollectorIT.java:145)
 [classes/:?]
        at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
~[?:?]
        at 
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 ~[?:?]
        at 
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 ~[?:?]
        at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
        at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
 [junit-4.12.jar:4.12]
        at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
 [junit-4.12.jar:4.12]
        at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
 [junit-4.12.jar:4.12]
        at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
 [junit-4.12.jar:4.12]
        at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) 
[junit-4.12.jar:4.12]
        at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) 
[junit-4.12.jar:4.12]
        at 
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
 [junit-4.12.jar:4.12]
        at 
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
 [junit-4.12.jar:4.12]
        at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
        at java.lang.Thread.run(Thread.java:834) [?:?]
   ```
   
   We need to figure out what is happening on the server side that is causing 
the timeout.  Try doing a ```jstack``` on the pid of one of the IT processes.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to