[ACCUMULO-4615] ThreadPool timeout when checking tserver stats is confusing

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Not A Problem
• Affects Version/s: 1.8.1
• Component/s: master
• Labels: pull-request-available
• Assignee: Jeff Schmidt
• Reporter: Michael Wall
• Created: 28/Mar/17 19:38
• Updated: 05/Jan/19 22:56
• Resolved: 05/Jan/19 22:56

Description

If it takes longer than the configured time to gather information from all the tablet servers, the thread pool stops and processing continues with whatever has been collected. Code is https://github.com/apache/accumulo/blob/1.8/server/master/src/main/java/org/apache/accumulo/master/Master.java#L1120, default timeout is 6s. Does not appear to be an issue prior to 1.8.

Best case, this was really confusing. The monitor page would have 30 tservers, then 5 tservers. Didn't really see any other negative effects, no migrations and no balancing appeared to be affected. Worse case though, I missed something and the master is making decisions based on incomplete information.

[e-mail] please add more info if needed.

Issue Links

• is related to: ACCUMULO-3999 monitor status collection should be done in parallel
• links to: GitHub Pull Request #402