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

Eli Collins commented on HDFS-2554:
-----------------------------------

Looks like we need another rev:
{noformat}
2012-08-18 22:38:58,132 FATAL blockmanagement.BlockManager 
(BlockManager.java:run(3047)) - ReplicationMonitor thread received Runtime 
exception. 
java.lang.NullPointerException
        at 
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.updateCorruptMissingCounts(BlockManager.java:1090)
        at 
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.updateState(BlockManager.java:1107)
        at 
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.computeDatanodeWork(BlockManager.java:3083)
        at 
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager$ReplicationMonitor.run(BlockManager.java:3040)
        at java.lang.Thread.run(Thread.java:662)
{noformat}
                
> Add separate metrics for missing blocks with desired replication level 1
> ------------------------------------------------------------------------
>
>                 Key: HDFS-2554
>                 URL: https://issues.apache.org/jira/browse/HDFS-2554
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>    Affects Versions: 2.0.0-alpha
>            Reporter: Todd Lipcon
>            Assignee: Andy Isaacson
>            Priority: Minor
>         Attachments: hdfs-2554.txt
>
>
> Some users use replication level set to 1 for datasets which are unimportant 
> and can be lost with no worry (eg the output of terasort tests). But other 
> data on the cluster is important and should not be lost. It would be useful 
> to separate the metric for missing blocks by the desired replication level of 
> those blocks, so that one could ignore missing blocks at repl 1 while still 
> alerting on missing blocks with higher desired replication.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to