-
Notifications
You must be signed in to change notification settings - Fork 25.6k
No longer require logs@settings component template to enable logsdb by default. #114501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No longer require logs@settings component template to enable logsdb by default. #114501
Conversation
|
Pinging @elastic/es-storage-engine (Team:StorageEngine) |
| template: | ||
| settings: | ||
| codec: best_compression | ||
| mode: standard |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is required to opt-out right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirming my understanding here, this means that logsdb will be disabled for APM and we will have same behaviour as before - is this right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that is correct.
otherwise we enable logsdb all nodes are upgraded.
...-upgrade/src/javaRestTest/java/org/elasticsearch/upgrades/LogsIndexModeRollingUpgradeIT.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
APM-data bit LGTM!
…ult disabled and after upgrade turn it on.
| } | ||
| }"""; | ||
|
|
||
| private static final String LOGS_TEMPLATE = """ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@salvatore-campagna fyi, this test both used cluster.logsdb.enabled=true and template with index.mode set to logsdb. With this change because cluster.logsdb.enabled was set to true, the data stream was in logsdb mode from the start. So I slightly changed this test, so that we still test rolling upgrade from standard mode and after upgrade update to logsdb.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that the setting is dynamic we can do that...before it was static...
💚 Backport successful
|
…y default. (elastic#114501) This change also opts out apm logs from logsdb.
…y default. (elastic#114501) This change also opts out apm logs from logsdb.
…y default. (elastic#114501) This change also opts out apm logs from logsdb.
Restore standard mode after LogsDB took precedence. Related: #114501
Restore standard mode after LogsDB took precedence. Related: #114501
Restore standard mode after LogsDB took precedence. Related: elastic#114501 (cherry picked from commit 2b1dc5a)
Restore standard mode after LogsDB took precedence. Related: elastic#114501
Restore standard mode after LogsDB took precedence. Related: elastic#114501
This change also opts out apm logs from logsdb.