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
Added short comment on snapshotting closed indices #10579
Conversation
I think it should be "If the |
I might be missing something but I think we can also improve on the error message in this case? If the error message was clear like "can't snapshot closed indices" ,we could just say that only open yellow indices can be snapshotted. @imotov , what do you think? |
+1 on @bleskes 's idea on improving the reason message |
To include Java 8 and recommendation to install the same version of Java to all nodes in the cluster.
Currently the error message is the same when index is closed and when it is missing shards. This commit will generate a specific failure message when a user tries to create a snapshot of a closed index. Related to elastic#10579
Currently the error message is the same when index is closed and when it is missing shards. This commit will generate a specific failure message when a user tries to create a snapshot of a closed index. Related to elastic#10579
Currently the error message is the same when index is closed and when it is missing shards. This commit will generate a specific failure message when a user tries to create a snapshot of a closed index. Related to #10579
Hi @ppf2 It looks like you've mixed two different changes into this PR: one for Java versions and one for snapshot/restore. The latter is no longer accurate since #10608 was pushed. I'm going to close this PR - please feel free to open a new one with just the Java changes (or just push those changes directly) thanks |
Trying again, didn't pick up changed file last time.