You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2012/09/07 05:24:07 UTC
[jira] [Created] (HDFS-3899) QJM: Writer-side metrics
Todd Lipcon created HDFS-3899:
---------------------------------
Summary: QJM: Writer-side metrics
Key: HDFS-3899
URL: https://issues.apache.org/jira/browse/HDFS-3899
Project: Hadoop HDFS
Issue Type: Sub-task
Affects Versions: QuorumJournalManager (HDFS-3077)
Reporter: Todd Lipcon
Assignee: Todd Lipcon
We already have some metrics on the server side (JournalNode) but it's useful to also gather metrics from the client side (NameNode). This is important in order to monitor that the client is seeing good performance from the individual JNs, and so that administrators can set up alerts if any of the JNs has become inaccessible to the NN.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HDFS-3899) QJM: Writer-side metrics
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon resolved HDFS-3899.
-------------------------------
Resolution: Fixed
Fix Version/s: QuorumJournalManager (HDFS-3077)
Committed to branch, thx.
> QJM: Writer-side metrics
> ------------------------
>
> Key: HDFS-3899
> URL: https://issues.apache.org/jira/browse/HDFS-3899
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Affects Versions: QuorumJournalManager (HDFS-3077)
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: QuorumJournalManager (HDFS-3077)
>
> Attachments: hdfs-3899.txt, hdfs-3899.txt
>
>
> We already have some metrics on the server side (JournalNode) but it's useful to also gather metrics from the client side (NameNode). This is important in order to monitor that the client is seeing good performance from the individual JNs, and so that administrators can set up alerts if any of the JNs has become inaccessible to the NN.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira