[
https://issues.apache.org/jira/browse/HDFS-11326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876798#comment-15876798
]
Wei-Chiu Chuang edited comment on HDFS-11326 at 2/21/17 9:55 PM:
-----------------------------------------------------------------
Hello [~piaoyu zhang] thanks for reporting this jira.
Do you have more information regarding this finding? For instance, stack trace
that shows a thread is stuck in this call?
Without more information it would be hard to tell what happened here exactly.
If I were to guess, was the file being closed in a snapshottable directory?
Also, your reported environment is on Hadoop 2.2. A lot have changed since
Hadoop 2.2, do you think the issue still applies to more recent versions?
was (Author: jojochuang):
Hello [~piaoyu zhang] thanks for reporting this jira.
Do you have more information regarding this finding? For instance, stack trace
that shows a thread is stuck in this call?
Without more information it would be hard to tell what happened here exactly.
If I were to guess, was the file being closed in a snapshottable directory?
> FSNamesystem closeFileCommitBlocks block FSNamesystem Ops
> ---------------------------------------------------------
>
> Key: HDFS-11326
> URL: https://issues.apache.org/jira/browse/HDFS-11326
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.2.0
> Environment: CentOS 6.5 Hadoop-2.2.0
> Reporter: zhangyubiao
> Priority: Critical
>
> Seems like String src = leaseManager.findPath(pendingFile); cause to much
> time hold the write lock.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
