You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Siddhant Sangwan (Jira)" <ji...@apache.org> on 2024/08/29 11:05:00 UTC
[jira] [Updated] (HDDS-11387) Put the changes introduced in HDDS-11120 behind a feature flag
[ https://issues.apache.org/jira/browse/HDDS-11387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddhant Sangwan updated HDDS-11387:
------------------------------------
Description:
The goal here is to protect existing users of the Container Balancer Status command from bugs introduced in HDDS-11120. We can have a verbose flag in the command `{{ozone admin containerbalancer status}}` to return the new output, and without the flag it returns the old output. Once the new feature is more reliable and well tested, we can make it the default.
On the other hand, if every useful feature is put behind a flag, it'll be hard to discover new and useful information. We need to decide whether we want a verbose flag, a new command for the new code and output, or just fix bugs in the new code.
was:The goal here is to protect existing users of the Container Balancer Status command from bugs or new output introduced in HDDS-11120. We should at least ensure that the command `{{ozone admin containerbalancer status}}` has a flag that can be used to return the new output, and without the flag it returns the old output. Once the new feature is more reliable and well tested, we can make it the default.
> Put the changes introduced in HDDS-11120 behind a feature flag
> --------------------------------------------------------------
>
> Key: HDDS-11387
> URL: https://issues.apache.org/jira/browse/HDDS-11387
> Project: Apache Ozone
> Issue Type: Bug
> Components: Balancer, Ozone CLI, SCM
> Affects Versions: 1.5.0
> Reporter: Siddhant Sangwan
> Priority: Major
>
> The goal here is to protect existing users of the Container Balancer Status command from bugs introduced in HDDS-11120. We can have a verbose flag in the command `{{ozone admin containerbalancer status}}` to return the new output, and without the flag it returns the old output. Once the new feature is more reliable and well tested, we can make it the default.
> On the other hand, if every useful feature is put behind a flag, it'll be hard to discover new and useful information. We need to decide whether we want a verbose flag, a new command for the new code and output, or just fix bugs in the new code.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org