[jira] [Moved] (HDFS-9218) BlockPlacementPolicy related logs should contain the details about the filename and blockid

["J.Andreina (JIRA)" <ji...@apache.org>]

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

J.Andreina moved YARN-4244 to HDFS-9218:
----------------------------------------

        Key: HDFS-9218  (was: YARN-4244)
    Project: Hadoop HDFS  (was: Hadoop YARN)

> BlockPlacementPolicy related logs should contain the details about the filename and blockid
> -------------------------------------------------------------------------------------------
>
>                 Key: HDFS-9218
>                 URL: https://issues.apache.org/jira/browse/HDFS-9218
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: J.Andreina
>            Assignee: J.Andreina
>
> Currently the user will not get the details about which file/block , the BlockPlacementPolicy is not able to find a replica node , if there is a huge client write operation is going on.
> For example consider below failure message , which does'nt have details about file/block , which will be difficult to track later.
> {noformat}
>       final String message =
>           "Failed to place enough replicas, still in need of "
>               + (totalReplicasExpected - results.size()) + " to reach " + totalReplicasExpected
>               + " (unavailableStorages=" + unavailableStorages + ", storagePolicy="
>               + storagePolicy + ", newBlock=" + newBlock + ")";
>         String msg = "All required storage types are unavailable: "
>             + " unavailableStorages=" + unavailableStorages
>             + ", storagePolicy=" + storagePolicy.getName();
> {noformat}
> It  is better to provide the file/block information in the logs for better debugability .



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