[
https://issues.apache.org/jira/browse/ACCUMULO-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Newton updated ACCUMULO-236:
---------------------------------
Description:
After all tablets are unloaded (as reported in the monitor web pages) and all
tablet servers appear to be down, the shutdown command hangs. The master log
messages show something like
{noformat}
... Unable to halt server 10.1.2.3:9997[abc123456789]:
org.apache.thrift.transport.TTransportException
{noformat}
One error for every server, making this problem much worse on a large cluster.
Thought we fixed this for 1.3.5, but it was reported again after the release.
was:
After all tablets are unloaded (as reported in the monitor web pages) and all
tablet servers appear to be down, the shutdown command hangs. The master log
messages show something like
{{{
... Unable to halt server 10.1.2.3:9997[abc123456789]:
org.apache.thrift.transport.TTransportException
}}}
One error for every server, making this problem much worse on a large cluster.
Thought we fixed this for 1.3.5, but it was reported again after the release.
> shutdown is very slow after all tservers are down
> -------------------------------------------------
>
> Key: ACCUMULO-236
> URL: https://issues.apache.org/jira/browse/ACCUMULO-236
> Project: Accumulo
> Issue Type: Bug
> Components: master
> Affects Versions: 1.3.5
> Environment: on a larger cluster shutdown takes a long time
> Reporter: Eric Newton
> Assignee: Eric Newton
>
> After all tablets are unloaded (as reported in the monitor web pages) and all
> tablet servers appear to be down, the shutdown command hangs. The master log
> messages show something like
> {noformat}
> ... Unable to halt server 10.1.2.3:9997[abc123456789]:
> org.apache.thrift.transport.TTransportException
> {noformat}
> One error for every server, making this problem much worse on a large
> cluster. Thought we fixed this for 1.3.5, but it was reported again after
> the release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
