You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Kihwal Lee (JIRA)" <ji...@apache.org> on 2014/07/01 19:00:29 UTC

[jira] [Created] (HDFS-6618) Edit log corruption may still happen even after HDFS-6527

Kihwal Lee created HDFS-6618:
--------------------------------

             Summary: Edit log corruption may still happen even after HDFS-6527
                 Key: HDFS-6618
                 URL: https://issues.apache.org/jira/browse/HDFS-6618
             Project: Hadoop HDFS
          Issue Type: Bug
    Affects Versions: 2.5.0
            Reporter: Kihwal Lee
            Priority: Blocker


After HDFS-6527, we have not seen the edit log corruption for weeks on multiple clusters until yesterday. Previously, we would see it within 30 minutes on a cluster.

But the same condition was reproduced even with HDFS-6527.  The only explanation is that the RPC handler thread serving {{addBlock()}} was accessing stale parent value.  Although nulling out parent is done inside the {{FSNamesystem}} and {{FSDirectory}} write lock, there is no memory barrier because there is no "synchronized" block involved in the process.

I suggest making parent volatile.



--
This message was sent by Atlassian JIRA
(v6.2#6252)