[ACCUMULO-1050] Master assumes tserver lost lock when it fails to get lock

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.4.0
• Component/s: master
• Assignee: Eric C. Newton
• Reporter: Keith Turner
• Created: 07/Feb/13 21:52
• Updated: 08/Feb/13 22:15
• Resolved: 08/Feb/13 22:15

Description

There is code in the master like the following.

  if (!lock.isLocked() && !watcher.gotLock && watcher.failureException == null) {
     //assume tserver there
}else{
     //assume tserver lost lock
}

In the else the master assumes it got the tserver lock and therefore the tserver lost its lock. But the else could execute when the master failed to get a lock. This may cause the master to kill tablet server when there is no reason to.

Issue Links

• is superceded by: ACCUMULO-1049 Master does not need to get tserver lock