[
https://issues.apache.org/jira/browse/HDFS-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049683#comment-14049683
]
Hadoop QA commented on HDFS-6618:
-
{color:red}-1 overall{color}. Here are the results of
[
https://issues.apache.org/jira/browse/HDFS-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050242#comment-14050242
]
Hadoop QA commented on HDFS-6618:
-
{color:red}-1 overall{color}. Here are the results of
[
https://issues.apache.org/jira/browse/HDFS-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049122#comment-14049122
]
Jing Zhao commented on HDFS-6618:
-
If the corruption is caused by the same issue, can we
[
https://issues.apache.org/jira/browse/HDFS-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049195#comment-14049195
]
Kihwal Lee commented on HDFS-6618:
--
bq. can we move the following code into the writelock
[
https://issues.apache.org/jira/browse/HDFS-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049259#comment-14049259
]
Hadoop QA commented on HDFS-6618:
-
{color:red}-1 overall{color}. Here are the results of
[
https://issues.apache.org/jira/browse/HDFS-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049309#comment-14049309
]
Kihwal Lee commented on HDFS-6618:
--
I guess we can move it inside the first lock, since it
