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

Documentation/op-guide: discourage "--force-new-cluster" in recovery #9279

Merged
merged 1 commit into from
Feb 26, 2018

Conversation

gyuho
Copy link
Contributor

@gyuho gyuho commented Feb 5, 2018

Highlight the discussions from #9177.

@gyuho gyuho requested a review from xiang90 February 5, 2018 22:08
@gyuho gyuho force-pushed the force-new-cluster branch 2 times, most recently from aae4566 to e383b93 Compare February 5, 2018 22:34
@codecov-io
Copy link

Codecov Report

❗ No coverage uploaded for pull request base (master@4e662b2). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##             master    #9279   +/-   ##
=========================================
  Coverage          ?   76.14%           
=========================================
  Files             ?      364           
  Lines             ?    30231           
  Branches          ?        0           
=========================================
  Hits              ?    23020           
  Misses            ?     5627           
  Partials          ?     1584

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4e662b2...99e1bd2. Read the comment docs.

@gyuho gyuho merged commit d6b46ac into etcd-io:master Feb 26, 2018
@gyuho gyuho deleted the force-new-cluster branch February 26, 2018 23:52
@@ -61,3 +61,9 @@ $ etcd \
```

Now the restored etcd cluster should be available and serving the keyspace given by the snapshot.

## Restoring a cluster from membership mis-reconfiguration with wrong URLs
Copy link
Contributor

Choose a reason for hiding this comment

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

This section should be made more generic: restoring a cluster from membership misconfiguration. also the content should focus on how to restore the mis-configured cluster i believe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants