Skip to content

Conversation

@martijnvg
Copy link
Member

@martijnvg martijnvg commented Oct 10, 2024

This change also opts out apm logs from logsdb.

@martijnvg martijnvg marked this pull request as ready for review October 10, 2024 13:39
@martijnvg martijnvg requested a review from a team as a code owner October 10, 2024 13:39
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-storage-engine (Team:StorageEngine)

@martijnvg martijnvg changed the title No longer require logs@settings component template to enable logsdb. No longer require logs@settings component template to enable logsdb by default. Oct 10, 2024
template:
settings:
codec: best_compression
mode: standard
Copy link
Contributor

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?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes

Copy link
Contributor

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?

Copy link
Member Author

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.
Copy link
Contributor

@lahsivjar lahsivjar left a 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!

}
}""";

private static final String LOGS_TEMPLATE = """
Copy link
Member Author

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.

Copy link
Contributor

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...

@martijnvg martijnvg added the auto-backport Automatically create backport pull requests when merged label Oct 10, 2024
@martijnvg martijnvg enabled auto-merge (squash) October 10, 2024 17:08
@martijnvg martijnvg merged commit 8e3b3aa into elastic:main Oct 10, 2024
16 checks passed
@elasticsearchmachine
Copy link
Collaborator

💚 Backport successful

Status Branch Result
8.x

martijnvg added a commit to martijnvg/elasticsearch that referenced this pull request Oct 10, 2024
…y default. (elastic#114501)

This change also opts out apm logs from logsdb.
matthewabbott pushed a commit to matthewabbott/elasticsearch that referenced this pull request Oct 10, 2024
…y default. (elastic#114501)

This change also opts out apm logs from logsdb.
elasticsearchmachine pushed a commit that referenced this pull request Oct 11, 2024
…y default. (#114501) (#114525)

This change also opts out apm logs from logsdb.

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
davidkyle pushed a commit to davidkyle/elasticsearch that referenced this pull request Oct 13, 2024
…y default. (elastic#114501)

This change also opts out apm logs from logsdb.
inge4pres added a commit that referenced this pull request Oct 28, 2024
Restore standard mode after LogsDB took precedence.
Related: #114501
inge4pres added a commit that referenced this pull request Oct 28, 2024
Restore standard mode after LogsDB took precedence.
Related: #114501
inge4pres added a commit to inge4pres/elasticsearch that referenced this pull request Oct 30, 2024
Restore standard mode after LogsDB took precedence.
Related: elastic#114501

(cherry picked from commit 2b1dc5a)
inge4pres added a commit that referenced this pull request Oct 30, 2024
Restore standard mode after LogsDB took precedence.
Related: #114501

(cherry picked from commit 2b1dc5a)
ioanatia pushed a commit to ioanatia/elasticsearch that referenced this pull request Nov 4, 2024
Restore standard mode after LogsDB took precedence.
Related: elastic#114501
jfreden pushed a commit to jfreden/elasticsearch that referenced this pull request Nov 4, 2024
Restore standard mode after LogsDB took precedence.
Related: elastic#114501
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-backport Automatically create backport pull requests when merged >non-issue :StorageEngine/Logs You know, for Logs Team:StorageEngine v8.16.0 v9.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants