Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 19 Oct 2015 14:44:05 +0000 (UTC)
From: "Eric Newton (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12864345.1442346084000.74719.1445265845064@Atlassian.JIRA>
In-Reply-To: <JIRA.12864345.1442346084000@Atlassian.JIRA>
References: <JIRA.12864345.1442346084000@Atlassian.JIRA>
 <JIRA.12864345.1442346084625@arcas>
Subject: [jira] [Resolved] (ACCUMULO-3999) monitor status collection should
 be done in parallel
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ACCUMULO-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Newton resolved ACCUMULO-3999.
-----------------------------------
    Resolution: Fixed

> monitor status collection should be done in parallel
> ----------------------------------------------------
>
>                 Key: ACCUMULO-3999
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3999
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: master
>         Environment: very large cluster
>            Reporter: Eric Newton
>            Assignee: Eric Newton
>             Fix For: 1.8.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The master collects statistics every few seconds from all the tservers so that it has up-to-date statistics to hand to the balancer.  It does this one server at a time.  On a very large cluster, the status collection can take a long time, causing the monitor to show "blocky" statistics in the graphs, and long "last contact" times in the tablet server lists.
> A small thread pool could be used to speed up this simple work.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)