[
https://issues.apache.org/jira/browse/HDFS-14680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen Zhang updated HDFS-14680:
------------------------------
Description:
StorageInfoDefragmenter is responsible for FoldedTreeSet compaction, but it
terminates NameNode on any exception, is it too radical?
I mean, even the critical threads like HeartbeatManager don't terminates
NameNode once they encounter exceptions, StorageInfoDefragmenter should not do
that either.
was:
StorageInfoDefragmenter is responsible for FoldedTreeSet compaction, but it
terminates NameNode on any exception, is it too radical?
I mean, even the critical threads like HeartbeatManager don't terminates
NameNode once they encounter exceptions, StorageInfoDefragmenter should not do
this either.
> StorageInfoDefragmenter should handle exceptions gently
> -------------------------------------------------------
>
> Key: HDFS-14680
> URL: https://issues.apache.org/jira/browse/HDFS-14680
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Chen Zhang
> Priority: Major
>
> StorageInfoDefragmenter is responsible for FoldedTreeSet compaction, but it
> terminates NameNode on any exception, is it too radical?
> I mean, even the critical threads like HeartbeatManager don't terminates
> NameNode once they encounter exceptions, StorageInfoDefragmenter should not
> do that either.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
