[DOCS] Add transient settings migration guide#80091
[DOCS] Add transient settings migration guide#80091jrodewig merged 9 commits intoelastic:7.16from jrodewig:docs__transient-to-persistent-settings
Conversation
|
Pinging @elastic/es-docs (Team:Docs) |
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
docs/reference/migration/transient-settings-migration-guide.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/migration/transient-settings-migration-guide.asciidoc
Outdated
Show resolved
Hide resolved
…ciidoc Co-authored-by: Jake Landis <jake.landis@elastic.co>
jakelandis
left a comment
There was a problem hiding this comment.
@jrodewig - This looks really nice. Thanks for picking this up so fast !
I wonder if there should be a blurb about "Some Elastic products may make use of transient settings and those should not be changed" similar to #79953 (comment)
The hard part for the user will be to know which settings they set vs. the Elastic products, so maybe there be some deliberate wording around setting they or their workflow toolings may have set ?
Thanks for pointing this out. I added a related admon in c4f67aa. However, I raise some concerns below.
Maybe @grcevski can help us out here. AFAIK there's no way to differentiate Elastic- vs user-managed cluster settings. In that case, the user won't know which transient settings are okay to reset vs. not. If we include the above admon or something like it, I feel we also need to include this step too. |
docs/reference/migration/transient-settings-migration-guide.asciidoc
Outdated
Show resolved
Hide resolved
grcevski
left a comment
There was a problem hiding this comment.
LGTM! Thanks for this great write-up.
Yes, that's right @jrodewig. There's no way to tell which settings are being set by our infrastructure vs. the end user. We don't do any detection on client type for these settings. |
jakelandis
left a comment
There was a problem hiding this comment.
LGTM. Thanks for putting this together so quickly!
Changes:
Closes #80055
Relates to #79167.
Forwardports
This deprecation is currently in the 7.16 docs only. However, I plan to forwardport to 8.0 and main based on the discussion in #79953.
In the 8.0 and main forwardports, I plan to add the guide and deprecation notice to the 8.0 migration docs. Let me know if there are any objections.
Previews