[jira] [Updated] (ACCUMULO-4637) Master should rip out locks of servers with bad system credentials
[ https://issues.apache.org/jira/browse/ACCUMULO-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Tubbs updated ACCUMULO-4637: Fix Version/s: (was: 1.7.4) > Master should rip out locks of servers with bad system credentials > -- > > Key: ACCUMULO-4637 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4637 > Project: Accumulo > Issue Type: Bug >Affects Versions: 1.7.2 >Reporter: John Vines >Priority: Major > Fix For: 1.9.0, 2.0.0 > > > Saw at a customer where one of their servers had not been properly synced. > Specifically, one of the instance values was mismatched, which means the > system password was mismatched. Server logs show a lot of bad auth failures > for the system user (as expected). > Meanwhile, the master is spinning, trying to get all the tablets online, > constantly attempting to assign them to this one server (because it has 0 > assigned, so it's a prime contender). Instead of this behavior, the master > should rip out the servers zk lock because it's not a member of the cluster > anymore (not until it's accumulo-site is fixed). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ACCUMULO-4637) Master should rip out locks of servers with bad system credentials
[ https://issues.apache.org/jira/browse/ACCUMULO-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Tubbs updated ACCUMULO-4637: Fix Version/s: 1.8.2 1.7.4 > Master should rip out locks of servers with bad system credentials > -- > > Key: ACCUMULO-4637 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4637 > Project: Accumulo > Issue Type: Bug >Affects Versions: 1.7.2 >Reporter: John Vines > Fix For: 1.7.4, 1.8.2, 2.0.0 > > > Saw at a customer where one of their servers had not been properly synced. > Specifically, one of the instance values was mismatched, which means the > system password was mismatched. Server logs show a lot of bad auth failures > for the system user (as expected). > Meanwhile, the master is spinning, trying to get all the tablets online, > constantly attempting to assign them to this one server (because it has 0 > assigned, so it's a prime contender). Instead of this behavior, the master > should rip out the servers zk lock because it's not a member of the cluster > anymore (not until it's accumulo-site is fixed). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ACCUMULO-4637) Master should rip out locks of servers with bad system credentials
[ https://issues.apache.org/jira/browse/ACCUMULO-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Tubbs updated ACCUMULO-4637: Fix Version/s: 2.0.0 > Master should rip out locks of servers with bad system credentials > -- > > Key: ACCUMULO-4637 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4637 > Project: Accumulo > Issue Type: Bug >Affects Versions: 1.7.2 >Reporter: John Vines > Fix For: 2.0.0 > > > Saw at a customer where one of their servers had not been properly synced. > Specifically, one of the instance values was mismatched, which means the > system password was mismatched. Server logs show a lot of bad auth failures > for the system user (as expected). > Meanwhile, the master is spinning, trying to get all the tablets online, > constantly attempting to assign them to this one server (because it has 0 > assigned, so it's a prime contender). Instead of this behavior, the master > should rip out the servers zk lock because it's not a member of the cluster > anymore (not until it's accumulo-site is fixed). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
