Skip to content

Conversation

williamrandolph
Copy link
Contributor

Now that cluster state has minimum system index mappings versions (#99307), the system index mappings upgrade service needs to use them to determine when to update mappings for system indices.

Closes #98504

@williamrandolph williamrandolph added :Core/Infra/Core Core issues without another label >non-issue labels Sep 20, 2023
@williamrandolph williamrandolph marked this pull request as ready for review September 20, 2023 03:29
@elasticsearchmachine elasticsearchmachine added the Team:Core/Infra Meta label for core/infra team label Sep 20, 2023
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (Team:Core/Infra)

@williamrandolph williamrandolph merged commit 1e5f4a3 into elastic:main Sep 20, 2023
@williamrandolph williamrandolph deleted the sysindex/mappings-versions-in-mappings-upgrade-service branch September 20, 2023 18:28
williamrandolph added a commit to williamrandolph/elasticsearch that referenced this pull request Nov 3, 2023
elastic#99668 seems to have introduced a bug where
SystemIndexMappingUpdateService updates system index mappings
even in mixed clusters. This PR restores the old version-based
check in order to be sure that there's no update until the
cluster is fully upgraded.

Fixes elastic#99778, elastic#101331
williamrandolph added a commit that referenced this pull request Nov 3, 2023
* Don't update system index mappings in mixed clusters

#99668 seems to have introduced a bug where
SystemIndexMappingUpdateService updates system index mappings
even in mixed clusters. This PR restores the old version-based
check in order to be sure that there's no update until the
cluster is fully upgraded.

The timing of the mapping update seems to be causing worse
problems, corrupting persisted cluster state.

Fixes #99778, #101331

* Remove broken assertion

The compatibility versions objects are not showing up
correctly, so we shouldn't assert on them.
williamrandolph added a commit to williamrandolph/elasticsearch that referenced this pull request Nov 3, 2023
* Don't update system index mappings in mixed clusters

elastic#99668 seems to have introduced a bug where
SystemIndexMappingUpdateService updates system index mappings
even in mixed clusters. This PR restores the old version-based
check in order to be sure that there's no update until the
cluster is fully upgraded.

The timing of the mapping update seems to be causing worse
problems, corrupting persisted cluster state.

Fixes elastic#99778, elastic#101331

* Remove broken assertion

The compatibility versions objects are not showing up
correctly, so we shouldn't assert on them.
elasticsearchmachine pushed a commit that referenced this pull request Nov 3, 2023
* Don't update system index mappings in mixed clusters

#99668 seems to have introduced a bug where
SystemIndexMappingUpdateService updates system index mappings
even in mixed clusters. This PR restores the old version-based
check in order to be sure that there's no update until the
cluster is fully upgraded.

The timing of the mapping update seems to be causing worse
problems, corrupting persisted cluster state.

Fixes #99778, #101331

* Remove broken assertion

The compatibility versions objects are not showing up
correctly, so we shouldn't assert on them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Core Core issues without another label >non-issue Team:Core/Infra Meta label for core/infra team v8.11.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use system index mappings version number in SystemIndexMappingUpdateService
3 participants