[
https://issues.apache.org/jira/browse/HDFS-17327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
huangzhaobo updated HDFS-17327:
-------------------------------
Description:
1. If it is a null value, after reconfig, the current system value will take
effect and not necessarily the default value.
2. {{ReconfigurableBase#reconfigureProperty}} judges the condition incorrectly,
When the effectValue is not null, the system value needs to be changed.
3. In other words, certain variables actually have effected, but the current
configuration of the system is refreshed to null.
was:
1. If it is a null value, after reconfig, the current system value will take
effect and not necessarily the default value.
2. {{ReconfigurableBase#reconfigureProperty}} judges the condition incorrectly,
When the effectValue is not null, the system value needs to be changed.
> Fix the judgment logic of the ReconfigurableBase class method
> reconfigureProperty.
> ----------------------------------------------------------------------------------
>
> Key: HDFS-17327
> URL: https://issues.apache.org/jira/browse/HDFS-17327
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: huangzhaobo
> Assignee: huangzhaobo
> Priority: Blocker
> Labels: pull-request-available
>
> 1. If it is a null value, after reconfig, the current system value will take
> effect and not necessarily the default value.
> 2. {{ReconfigurableBase#reconfigureProperty}} judges the condition
> incorrectly, When the effectValue is not null, the system value needs to be
> changed.
> 3. In other words, certain variables actually have effected, but the current
> configuration of the system is refreshed to null.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
