-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Act on version 8 related asserts #38556
Comments
Tracking elastic#38556
Pinging @elastic/es-core-infra |
@DaveCTurner Can you clean up the last remaining version 8 assertion in the code base? It's currently commented out: elasticsearch/server/src/main/java/org/elasticsearch/gateway/MetaStateService.java Lines 120 to 125 in a051321
so there's some dead code there that theoretically can be cleaned up and removed. |
There's an assertion in this block of code too: elasticsearch/server/src/main/java/org/elasticsearch/gateway/MetaStateService.java Lines 130 to 153 in a051321
|
7.x nodes permit the on-disk cluster metadata to omit the manifest file in order to support upgrades from 6.x. We are similarly lenient in `master`, i.e. 8.x, but there is no need to be since we must be upgrading from a 7.x node which ensures that the manifest file is written. This commit removes the lenient loading of a manifest-free cluster metadata from `master`. Relates elastic#38556
Sure, I opened #52412. |
7.x nodes permit the on-disk cluster metadata to omit the manifest file in order to support upgrades from 6.x. We are similarly lenient in `master`, i.e. 8.x, but there is no need to be since we must be upgrading from a 7.x node which ensures that the manifest file is written. We prefer to keep this lenience (see elastic#52412) so this commit removes the commented-out indications that it should be removed. The new metadata format introduced in elastic#50907 means that this whole subsystem will be removed in v9 anyway. Relates elastic#38556
7.x nodes permit the on-disk cluster metadata to omit the manifest file in order to support upgrades from 6.x. We are similarly lenient in `master`, i.e. 8.x, but there is no need to be since we must be upgrading from a 7.x node which ensures that the manifest file is written. We prefer to keep this lenience (see #52412) so this commit removes the commented-out indications that it should be removed. The new metadata format introduced in #50907 means that this whole subsystem will be removed in v9 anyway. Relates #38556
@jasontedor I merged #52646. Since you say that this was the last remaining assertions here, should we close this issue now? |
We have a number of assertions for checking that we did not pump to version 8 yet.
I am in the process of muting them thus this issue to track them.
This is necessary so we can merge #38514 and get builds going.
ResyncReplicationRequest
,MetaDataCreateIndexService
,RemoteClusterAware
andRemoteClusterAware
added by @jasontedorMetaStateService
added by @andrershovThe text was updated successfully, but these errors were encountered: