Transient settings were deprecated via #78794 in 7.16. As a result users will see the deprecation message in the deprecation logs and upgrade assistant. [1] This particular deprecation warning is special in that we can not differentiate a user setting these and the automation of systems/processes that can set any transient setting for any reason they needed. For example, our Cloud system will set some of these transient setting while performing automated changes to the system. Efforts are underway to ensure all uses are removed for systems/process, but in order to raise visibility of this deprecation as soon as possible there will be some overlap between users and systems causing these warnings.
We should tweak the wording if this deprecation such that a user aware that settings are deprecated, but this could caused by some automated system/process including our Cloud provider.
This issue is specifically for deprecated transient settings, however, this pattern may be repeated in other exceptional cases.
[1]
Log / Header:
[deprecation.elasticsearch][WARN] [transient settings removal] Updating cluster settings through transientSettings is deprecated. Use persistent settings instead.
Deprecation info / Upgrade Assistant
message: Transient cluster settings are deprecated
details: Use persistent settings to configure your cluster.
Transient settings were deprecated via #78794 in 7.16. As a result users will see the deprecation message in the deprecation logs and upgrade assistant. [1] This particular deprecation warning is special in that we can not differentiate a user setting these and the automation of systems/processes that can set any transient setting for any reason they needed. For example, our Cloud system will set some of these transient setting while performing automated changes to the system. Efforts are underway to ensure all uses are removed for systems/process, but in order to raise visibility of this deprecation as soon as possible there will be some overlap between users and systems causing these warnings.
We should tweak the wording if this deprecation such that a user aware that settings are deprecated, but this could caused by some automated system/process including our Cloud provider.
This issue is specifically for deprecated transient settings, however, this pattern may be repeated in other exceptional cases.
[1]
Log / Header:
Deprecation info / Upgrade Assistant