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 "David Mollitor (Jira)" <ji...@apache.org> on 2019/09/20 19:15:00 UTC

[jira] [Created] (HDFS-14866) NameNode stopRequested is Marked volatile

David Mollitor created HDFS-14866:
-------------------------------------

             Summary: NameNode stopRequested is Marked volatile
                 Key: HDFS-14866
                 URL: https://issues.apache.org/jira/browse/HDFS-14866
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: namenode
    Affects Versions: 3.2.0
            Reporter: David Mollitor
            Assignee: David Mollitor


https://github.com/apache/hadoop/blob/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java#L405

"Used for testing" so not a big deal, but it's a bit odd that it's scoped as 'protected' and is not 'volatile'.  It could be accessed outside of a lock and getting a bad value.  Tighten that up a little.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org