You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2018/12/01 07:16:00 UTC

[jira] [Commented] (ACCUMULO-4410) Master didn't not resume balancing after administrative tserver shutdown

    [ https://issues.apache.org/jira/browse/ACCUMULO-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16705689#comment-16705689 ] 

Christopher Tubbs commented on ACCUMULO-4410:
---------------------------------------------

This was fixed in 1.9.3, but as of 1.9.0 and 2.0.0, we're no longer tracking versions in JIRA. We're using GitHub as our primary issue tracker. No new versions are being created in JIRA.  2.0.0 is an exception because lots of issues were tracked for it in JIRA before we switched to GitHub.

I've added the 1.9.3 label and the 2.0.0 label to the GitHub Pull Request, so there's no longer any reason to update this issue in JIRA.

> Master didn't not resume balancing after administrative tserver shutdown
> ------------------------------------------------------------------------
>
>                 Key: ACCUMULO-4410
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4410
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 1.8.0, 1.9.0, 2.0.0
>            Reporter: Josh Elser
>            Assignee: Ivan Bella
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 2.0.0
>
>          Time Spent: 3h 50m
>  Remaining Estimate: 0h
>
> I realized that I misconfigured a property, so, I started manually stopping each tabletserver (using {{accumulo admin stop <host:port>}}).
> This worked as intended, the tablets were migrated and the tserver was stopped:
> {noformat}
> 2016-08-17 15:24:20,871 [master.EventCoordinator] INFO : Tablet Server shutdown requested for jelser-accumulo-180-4.openstacklocal:59540[1568579a4b4004c]
> 2016-08-17 15:24:20,991 [master.Master] DEBUG: FATE op shutting down jelser-accumulo-180-4.openstacklocal:59540[1568579a4b4004c] finished
> {noformat}
> However, after this point, the master did not resume balancing:
> {noformat}
> 2016-08-17 15:24:31,024 [master.Master] DEBUG: Finished gathering information from 4 servers in 0.02 seconds
> 2016-08-17 15:24:31,024 [master.Master] DEBUG: not balancing while shutting down servers [jelser-accumulo-180-4.openstacklocal:59540[1568579a4b4004c]]
> 2016-08-17 15:24:36,831 [replication.WorkDriver] DEBUG: Sleeping 30000 ms before next work assignment
> 2016-08-17 15:24:41,074 [master.Master] DEBUG: Finished gathering information from 4 servers in 0.05 seconds
> 2016-08-17 15:24:41,083 [master.Master] DEBUG: not balancing while shutting down servers [jelser-accumulo-180-4.openstacklocal:59540[1568579a4b4004c]]
> 2016-08-17 15:24:51,134 [master.Master] DEBUG: Finished gathering information from 4 servers in 0.05 seconds
> 2016-08-17 15:24:51,135 [master.Master] DEBUG: not balancing while shutting down servers [jelser-accumulo-180-4.openstacklocal:59540[1568579a4b4004c]]
> {noformat}
> Even after I brought a new tserver online on that host, the master still did not resume balancing:
> {noformat}
> 2016-08-17 15:25:53,015 [master.Master] INFO : New servers: [jelser-accumulo-180-4.openstacklocal:54722[2568579a5c3006e]]
> 2016-08-17 15:25:53,026 [master.EventCoordinator] INFO : There are now 5 tablet servers
> 2016-08-17 15:25:53,096 [master.Master] DEBUG: Finished gathering information from 5 servers in 0.06 seconds
> 2016-08-17 15:25:53,109 [master.Master] DEBUG: not balancing while shutting down servers [jelser-accumulo-180-4.openstacklocal:59540[1568579a4b4004c]]
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)