[
https://issues.apache.org/jira/browse/ACCUMULO-2717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Newton reopened ACCUMULO-2717:
-----------------------------------
Timed out again last night. Was waiting for the master to die during clean-up.
The master logs were empty, which is strange because the tablet server logs
clearly show the master was alive and coordinating.
> multiTableTest is timing out
> ----------------------------
>
> Key: ACCUMULO-2717
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2717
> Project: Accumulo
> Issue Type: Bug
> Components: test
> Environment: nightly test runs
> Reporter: Eric Newton
> Assignee: Eric Newton
> Priority: Minor
> Fix For: 1.6.0, 1.6.1
>
>
> {noformat}
> java.lang.Exception: test timed out after 120000 milliseconds
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at java.lang.UNIXProcess.waitFor(UNIXProcess.java:181)
> at
> org.apache.accumulo.minicluster.impl.MiniAccumuloClusterImpl.stop(MiniAccumuloClusterImpl.java:619)
> at
> org.apache.accumulo.test.functional.AbstractMacIT.cleanUp(AbstractMacIT.java:51)
> at
> org.apache.accumulo.test.functional.ConfigurableMacIT.tearDown(ConfigurableMacIT.java:71)
> 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:622)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
> at
> org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
> {noformat}
> This looks like it's waiting for the gc to die, but there's no output in the
> gc logs.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
