[
https://issues.apache.org/jira/browse/HDFS-11840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039767#comment-16039767
]
Hudson commented on HDFS-11840:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11834 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11834/])
HDFS-11840. Log HDFS Mover exception message of exit to its own log. (wang: rev
c31cb879a3595f76d01408e6d066a0bde20be043)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/mover/Mover.java
> 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: 2.9.0, 3.0.0-alpha4
>
> Attachments: HDFS-11840.patch, HDFS-11840.update.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: [email protected]
For additional commands, e-mail: [email protected]
