Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 18 Jun 2017 05:35:00 +0000 (UTC)
From: "Rakesh R (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13078941.1497184799000.42546.1497764100104@Atlassian.JIRA>
In-Reply-To: <JIRA.13078941.1497184799000@Atlassian.JIRA>
References: <JIRA.13078941.1497184799000@Atlassian.JIRA> <JIRA.13078941.1497184799358@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HDFS-11966) [SPS] Correct the log in
 BlockStorageMovementAttemptedItems#blockStorageMovementResultCheck
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 18 Jun 2017 05:35:04 -0000


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

Rakesh R updated HDFS-11966:
----------------------------
       Resolution: Fixed
    Fix Version/s: HDFS-10285
           Status: Resolved  (was: Patch Available)

Thank you [~surendrasingh] for the contribution. Committed to the branch.

> [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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org