-
Notifications
You must be signed in to change notification settings - Fork 22
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
docs: add info about etcd snapshot #129
base: version/2.1
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
Signed-off-by: anupriya0703 <anupriya.gupta@mayadata.io>
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,7 +2,18 @@ | |
|
||
A legacy installation of Mayastor (1.0.5 and below) cannot be seamlessly upgraded and needs manual intervention. | ||
Follow the below steps if you wish to upgrade from Mayastor 1.0.x to Mayastor 2.1.0 and above. | ||
Mayastor uses etcd as a persistent datastore for its configuration. As a first step, take a snapshot of the etcd. The detailed steps for taking a snapshot can be found in the etcd [documentation](https://etcd.io/docs/v3.3/op-guide/recovery/). | ||
Mayastor uses etcd as a persistent datastore for its configuration. As a first step, take a snapshot of the etcd. To do so, execute: | ||
{% tab title="Commands" %} | ||
```text | ||
kubectl exec -it mayastor-etcd-0 -n mayastor -- bash | ||
kubectl cp -n mayastor mayastor-etcd-0:/tmp/snapshot.db ./snapshot.db | ||
ls -lrt snapshot.db | ||
kubectl exec -it mayastor-etcd-0 -n mayastor -- bash | ||
kubectl cp -n mayastor mayastor-etcd-0:/tmp/snapshot.db ./snapshot.db | ||
ls -lrt snapshot.db | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What is the user supposed to be doing with this snapshot? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we need to provide more explanation on this. Why should a user take a etcd snapshot? Where should it be stored (if needed)? How to recover from the snapshot in case of an irrecoverable failure? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @datacore-tilangovan Could you please help me with the above information There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @avishnu It can be stored in the local, let me draft some new steps for snapshot restore. |
||
``` | ||
{% endtab %} | ||
The detailed steps for taking a snapshot can be found in the etcd [documentation](https://etcd.io/docs/v3.3/op-guide/recovery/). | ||
|
||
|
||
{% hint style="warning" %} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are the steps repeated here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to take the snapshot on every pod of etcd? or only on the master pod?
cc @datacore-tilangovan
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Vishnu, taking snapshot from one pod is enough.