3.6 and bootstrap-defrag-threshold-megabytes

[morete]

Hi, on the upgrade guide it is stated "bootstrap-defrag-threshold-megabytes" is no longer an experimental feature.
https://etcd.io/docs/v3.6/upgrades/upgrade_3_6/#flags-deprecated

But on the 3.6 operations section it is documented as an experimental feature...
https://etcd.io/docs/v3.6/op-guide/configuration/#experimental-features

Could someone verify/confirm this? I'm interested on using auto-defrag.
Could this feature be enabled during upgrade from 3.5 to 3.6?

Thanks in advance

[jmhbnz]

Hi @morete - Thanks for your question.

In v3.6.0 the flag --experimental-bootstrap-defrag-threshold-megabytes has been marked as deprecated with the new flag --bootstrap-defrag-threshold-megabytes to take its place, as outlined in our 3.6 upgrade guide https://etcd.io/docs/v3.6/upgrades/upgrade_3_6/#flags-deprecated.

However, as mentioned in #19141 (comment) this does not "graduate" the feature itself. The feature is still experimental. We are only changing the way experimental features are provided so that moving forward when a feature does graduate it does not need to be a breaking change to users in terms of the flags/configuration they supply.

For v3.6.x releases, when you launch etcd, you can supply either the deprecated --experimental-bootstrap-defrag-threshold-megabytes flag, or the newer --bootstrap-defrag-threshold-megabytes (but not both at the same time). They both relate to the same, still experimental feature.

It does look like we need to update the documentation in https://etcd.io/docs/v3.6/op-guide/configuration/#experimental-features so that the new flag name is listed. I've opened etcd-io/website#1036 to address this.

[morete]

Hi @jmhbnz . Thanks a lot for your support!