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

Add validation of restored persistent settings #9051

Merged
merged 1 commit into from
Jan 18, 2015

Conversation

imotov
Copy link
Contributor

@imotov imotov commented Dec 24, 2014

Closes #8830

@imotov imotov added :Distributed/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs >bug review v1.5.0 v2.0.0-beta1 labels Dec 24, 2014
.put("discovery.type", "zen")
.put("discovery.zen.ping_timeout", "200ms")
.put("discovery.initial_state_timeout", "500ms")
.put("gateway.type", "local")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Duplicate "gateway.type"

Note that gateway.local will be removed in #9128

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. Removing.

@tlrx
Copy link
Member

tlrx commented Jan 6, 2015

LGTM left two minor comments

@imotov imotov force-pushed the issue-8830-validate-restored-settings branch from 86715ae to a4c92eb Compare January 18, 2015 02:10
@imotov imotov merged commit a4c92eb into elastic:master Jan 18, 2015
@clintongormley clintongormley changed the title Snapshot/Restore: add validation of restored persistent settings Add validation of restored persistent settings Jun 8, 2015
@imotov imotov deleted the issue-8830-validate-restored-settings branch May 1, 2020 22:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :Distributed/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs resiliency v1.5.0 v2.0.0-beta1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Restore process can restore incompatible minimum_master_nodes setting
3 participants