Skip to content
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

Closed
wants to merge 2 commits into from

Conversation

ppf2
Copy link
Member

@ppf2 ppf2 commented Apr 13, 2015

Trying again, didn't pick up changed file last time.

@ppf2 ppf2 added >docs General docs changes :Distributed/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs labels Apr 13, 2015
@imotov
Copy link
Contributor

imotov commented Apr 14, 2015

I think it should be "If the indices parameter specified includes any closed indices....". Otherwise LGTM.

@bleskes
Copy link
Contributor

bleskes commented Apr 14, 2015

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?

@ppf2
Copy link
Member Author

ppf2 commented Apr 14, 2015

+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.
imotov added a commit to imotov/elasticsearch that referenced this pull request Apr 15, 2015
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
@imotov
Copy link
Contributor

imotov commented Apr 15, 2015

@bleskes, @ppf2 I think you are right. I opened PR, which makes the message more clear.

imotov added a commit to imotov/elasticsearch that referenced this pull request Apr 20, 2015
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
imotov added a commit that referenced this pull request Apr 20, 2015
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
@clintongormley
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs >docs General docs changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants