[
https://issues.apache.org/jira/browse/HDFS-11840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
LiXin Ge updated HDFS-11840:
----------------------------
Attachment: HDFS-11840.update.patch
Thanks for review, [~liuml07].
I have updated the patch to log only the IOException message now. In my
opinion, exception informations should keep in log in case people want to
digging out what happened in they cluster someday.
> 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, 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]
