hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elek, Marton (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDDS-240) Implement metrics for EventQueue
Date Mon, 09 Jul 2018 09:28:00 GMT

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

Elek, Marton updated HDDS-240:
    Attachment: HDDS-240.001.patch

> Implement metrics for EventQueue
> --------------------------------
>                 Key: HDDS-240
>                 URL: https://issues.apache.org/jira/browse/HDDS-240
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: SCM
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>             Fix For: 0.2.1
>         Attachments: HDDS-240.001.patch
> The heart of the SCM is the lightweight EventQueue which is implemented in HDDS-25.
> The main advantage to use a centralized EventQueue API is that all the thread handling
could be implemented in one central place (with unified the monitoring, thread naming, lifecycle
> In this jira I propose to create basic metrics for EventQueue. As (in the current implementation)
each handler has an own executor which has already some metrics (for check when the unit tests
could be stoped), it's quite easy to convert the atomic counters to real hadoop metrics.
> For the sake of simplicity I also propose to remove the addHandlerGroup. The method supported
the case when the Executor was shared between multiple handlers. It's a special case, it's
more harder to monitor (we need tricky naming convention) and can't see real demand. We can
restore it when we will see the requirements.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message