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 "Haiyang Hu (Jira)" <ji...@apache.org> on 2023/01/12 06:31:00 UTC

[jira] [Created] (HDFS-16888) BlockManager#maxReplicationStreams, replicationStreamsHardLimit, blocksReplWorkMultiplier and PendingReconstructionBlocks#timeout should be volatile

Haiyang Hu created HDFS-16888:
---------------------------------

             Summary: BlockManager#maxReplicationStreams, replicationStreamsHardLimit, blocksReplWorkMultiplier and PendingReconstructionBlocks#timeout should be volatile
                 Key: HDFS-16888
                 URL: https://issues.apache.org/jira/browse/HDFS-16888
             Project: Hadoop HDFS
          Issue Type: Improvement
            Reporter: Haiyang Hu


BlockManager#maxReplicationStreams, replicationStreamsHardLimit, blocksReplWorkMultiplier and PendingReconstructionBlocks#timeout these variables may be  writen by NameNode#reconfReplicationParameters then while read by the other threads. 
Thus they should be declared as volatile to make sure the "happens-before" consistency.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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