elastic / elasticsearch Public
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
Taking a snapshot of an index closed prior to 7.2.0 fails with a NPE in 7.11.2 #70676
Comments
Pinging @elastic/es-distributed (Team:Distributed) |
We agreed to fix this by marking such shards as The test I suggested above only works for BWC versions <7.2.0 because of that change, because more recent versions can successfully snapshot a closed index. |
@DaveCTurner i am newbie to open source contributions, would like to pick this issue. |
Sure, go ahead @SivaTharun |
First timer here, can I get started with this issue? |
@SivaTharun are you still working on this? |
No reply, so I think this issue is up for grabs again. |
@DaveCTurner sorry for late reply, missed the conversation in my inbox, can i start to work on this issue |
Yes, sure, I thought you'd already started :) |
@DaveCTurner can i work on this? I'm new to contributing. |
Elasticsearch version (
bin/elasticsearch --version
):master
, various7.x
versionsPlugins installed: N/A
JVM version (
java -version
): N/AOS version (
uname -a
if on a Unix-like system): N/ADescription of the problem including expected versus actual behavior:
In
SnapshotsService#shards
we assume that if an index has metadata in the cluster state then it has a routing table entry, but this isn't true if the index was closed prior to 7.2. As a workaround, you can open and close any such indices.Steps to reproduce:
Introduce a closed index in, say, 7.1.1 and then try and take a snapshot in
master
. For instance, apply these changes to b65992e ...... and then run
./gradlew :qa:full-cluster-restart:v7.1.1#bwcTest -Dtests.class=org.elasticsearch.upgrades.FullClusterRestartIT -Dtests.method=testSnapshotRestore
.Provide logs (if relevant):
In tests one of the nodes fails with an
AssertionError
:In production it's a NPE instead:
The text was updated successfully, but these errors were encountered: