You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by "Hao Chen (JIRA)" <ji...@apache.org> on 2016/06/12 14:57:20 UTC

[jira] [Commented] (EAGLE-337) Generic Service being alive or not feeder

    [ https://issues.apache.org/jira/browse/EAGLE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326478#comment-15326478 ] 

Hao Chen commented on EAGLE-337:
--------------------------------

Sounds like sensible requirements for hadoop cluster monitoring

> Generic Service being alive or not feeder
> -----------------------------------------
>
>                 Key: EAGLE-337
>                 URL: https://issues.apache.org/jira/browse/EAGLE-337
>             Project: Eagle
>          Issue Type: New Feature
>            Reporter: Jing Ge
>              Labels: Hadoop-Daemon-Monitoring
>             Fix For: v0.6.0
>
>
> As a Hadoop cluster administrator, I want to monitoring if the Hadoop daemon services (maybe same host with different ports) are alive or not, i.e.:
> - NameNode
> - DataNode
> - ResourceManager
> - NodeManager
> - HBase region server
> - etc.
> and many more services depending on which daemon will be installed and used. 
> The solution should be HA, generic, and dynamic configurable. The alive checking should be at a more reliable level beyond just getting a response without looking into the content.



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