hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "LiXin Ge (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-11840) Log HDFS Mover exception message of exit to its own log
Date Wed, 17 May 2017 08:56:04 GMT

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

LiXin Ge updated HDFS-11840:
----------------------------
    Description: 
Currently, the exception message of why mover exit is logged to stderr. 
It is hard to figure out why Mover was aborted as we may lose the console message,but it would
be much better if we also log this to Mover log.

  was:
Currently, the exception message of why mover exit is logged to stderr. 
It is hard to figure out why Mover was aborted as we may lose the console message,
but it would be much better if we also log this to Mover log.


> Log HDFS Mover exception message of exit to its own log
> -------------------------------------------------------
>
>                 Key: HDFS-11840
>                 URL: https://issues.apache.org/jira/browse/HDFS-11840
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: balancer & mover
>    Affects Versions: 3.0.0-alpha2
>            Reporter: LiXin Ge
>            Assignee: LiXin Ge
>            Priority: Minor
>             Fix For: 3.0.0-alpha2
>
>         Attachments: HDFS-11840.patch
>
>
> Currently, the exception message of why mover exit is logged to stderr. 
> It is hard to figure out why Mover was aborted as we may lose the console message,but
it would be much better if we also log this to Mover log.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message