accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3957) Consider moving off getContentSummary in the monitor
Date Tue, 11 Aug 2015 21:11:47 GMT


Christopher Tubbs commented on ACCUMULO-3957:

This probably shouldn't happen in 1.5/1.6, since I'd hate to make any changes which could
affect their compatibility with any Hadoop 1 versions which they may currently work with (and
I wouldn't want to go back and check all those older versions of Hadoop. 1.7 and later supports
only relatively modern versions of Hadoop, so it's less an issue there). Plus, I don't see
this as a critical issue for 1.5.

I'm +1 for dropping it from the monitor in 1.8.0.

> Consider moving off getContentSummary in the monitor
> ----------------------------------------------------
>                 Key: ACCUMULO-3957
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: monitor
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Critical
>             Fix For: 1.6.4, 1.7.1, 1.8.0, 1.5.4
> Recently heard about an issue where a large Hadoop installation which had Accumulo running
was experiencing long pauses in the Namenode. Inspecting NN audit logs, it was found that
the user running Accumulo issues a {{getContentSummary("/")}} call just before the NN pauses
were experienced.
> In {{}}, we use this call to compute the total HDFS disk usage and
present a ratio of space that Accumulo uses relative to the total available space.
> It's still unclear why this was causing issues in this case (as this operation should
only be acquiring a read-lock in the namenode), it was recommended to me that Accumulo use
the JMX metrics for the NN instead of making this call.

This message was sent by Atlassian JIRA

View raw message