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

Surendra Singh Lilhore commented on HDFS-11966:
-----------------------------------------------

Thanks [~rakeshr] for review and commit...

> [SPS] Correct the log in 
> BlockStorageMovementAttemptedItems#blockStorageMovementResultCheck
> -------------------------------------------------------------------------------------------
>
>                 Key: HDFS-11966
>                 URL: https://issues.apache.org/jira/browse/HDFS-11966
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>    Affects Versions: HDFS-10285
>            Reporter: Surendra Singh Lilhore
>            Assignee: Surendra Singh Lilhore
>            Priority: Minor
>             Fix For: HDFS-10285
>
>         Attachments: HDFS-11966-HDFS-10285-001.patch, 
> HDFS-11966-HDFS-10285-002.patch
>
>
> {{BlockStorageMovementAttemptedItems#blockStorageMovementResultCheck}} print 
> confusing log when block movement is success.
> Logs
> ====
> 2017-06-10 17:33:20,690 INFO 
> org.apache.hadoop.hdfs.server.namenode.BlockStorageMovementAttemptedItems: 
> Blocks storage movement is SUCCESS for the track id: 16386 reported from 
> co-ordinating datanode.{color:red} But the trackID doesn't exists in 
> storageMovementAttemptedItems list{color}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to