[
https://issues.apache.org/jira/browse/HDFS-11087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669056#comment-15669056
]
Brahma Reddy Battula commented on HDFS-11087:
---------------------------------------------
That will be good idea .Everybody will aware of it before committing to
branch-2.7 and we might not miss any entry.
bq.Should we consider adding a pre-commit hook?
can we do this..?
Even I sent [mail in
common-dev|http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/201609.mbox/browser]
(sub: Updation of Change.txt in branch-2.7 on Sept-30),but I did not hear any
thoughts there.
If we need any discussion in mailing list ,may be we can use this..?
> NamenodeFsck should check if the output writer is still writable.
> -----------------------------------------------------------------
>
> Key: HDFS-11087
> URL: https://issues.apache.org/jira/browse/HDFS-11087
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.6.5
> Reporter: Konstantin Shvachko
> Assignee: Erik Krogen
> Fix For: 2.8.0, 2.9.0, 2.7.4
>
> Attachments: HDFS-11087-branch-2.000.patch,
> HDFS-11087-branch-2.001.patch, HDFS-11087.branch-2.000.patch
>
>
> {{NamenodeFsck}} keeps running even after the client was interrupted. So if
> you start {{fsck /}} on a large namespace and kill the client, the NameNode
> will keep traversing the tree for hours although there is nobody to receive
> the result.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
