[
https://issues.apache.org/jira/browse/HDFS-16099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoqiao He resolved HDFS-16099.
--------------------------------
Fix Version/s: 3.4.0
Hadoop Flags: Reviewed
Resolution: Fixed
Committed to trunk. Thanks [~zhangshuyan] for your report and contribution!
> Make bpServiceToActive to be volatile
> -------------------------------------
>
> Key: HDFS-16099
> URL: https://issues.apache.org/jira/browse/HDFS-16099
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode
> Reporter: Shuyan Zhang
> Assignee: Shuyan Zhang
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> BPOfferService#bpServiceToActive is not volatile, which may cause
> _CommandProcessingThread_ to get the out-of-date active namenode.
> When a failover occurs, the old ANN's _CommandProcessingThread_ may read the
> outdated BPOfferService#bpServiceToActive and execute the NN's command. At
> this time, if the new ANN's _CommandProcessingThread_ reads the new value of
> bpServiceToActive, split brain will occur; otherwise, the new ANN's commands
> cannot be executed normally, which is also unacceptable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
