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 2017/03/29 23:18:42 UTC
[jira] [Updated] (ACCUMULO-4615) ThreadPool timeout when checking
tserver stats is confusing
[ https://issues.apache.org/jira/browse/ACCUMULO-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher Tubbs updated ACCUMULO-4615:
----------------------------------------
Fix Version/s: 2.0.0
1.8.2
> ThreadPool timeout when checking tserver stats is confusing
> -----------------------------------------------------------
>
> Key: ACCUMULO-4615
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4615
> Project: Accumulo
> Issue Type: Bug
> Components: master
> Affects Versions: 1.8.1
> Reporter: Michael Wall
> Priority: Minor
> Fix For: 1.8.2, 2.0.0
>
>
> 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.
> [~dlmarion@comcast.net] please add more info if needed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)