You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2021/06/21 08:59:00 UTC
[jira] [Updated] (HDFS-16082) Avoid non-atomic operations on
exceptionsSinceLastBalance and failedTimesSinceLastSuccessfulBalance in
Balancer
[ https://issues.apache.org/jira/browse/HDFS-16082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Viraj Jasani updated HDFS-16082:
--------------------------------
Target Version/s: 3.4.0, 3.3.2
> Avoid non-atomic operations on exceptionsSinceLastBalance and failedTimesSinceLastSuccessfulBalance in Balancer
> ---------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-16082
> URL: https://issues.apache.org/jira/browse/HDFS-16082
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
>
> Balancer has introduced 2 volatile int as part of HDFS-13783 namely: exceptionsSinceLastBalance and failedTimesSinceLastSuccessfulBalance. However, we are performing non-atomic operations on it. Since non-atomic operations done here mostly depend on their previous values, we should use AtomicInteger for both.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org