Skip to content

docs: fix up incorrect upgrade advice for 3.5 -> 3.6 upgrade #1117

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.

Sign up for GitHub

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

Open
alam0rt wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: fix up incorrect upgrade advice for 3.5 -> 3.6 upgrade #1117

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions content/en/docs/v3.6/upgrades/upgrade_3_6.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,19 +21,19 @@ Before upgrading to 3.6, make sure that [all of your 3.5 members are updated to

#### V2 Store

**NOTE:** If the `--enable-v2` flag is not configured or is set to false, no further action is required.

If `--enable-v2` or the environment variable `ETCD_ENABLE_V2="true"` **is** configured, additional steps are required to handle the v2store data:
{{% alert title="Important" color="warning" %}}
Is it possible that custom data exists in v2store despite v2store not being enabled. Before upgrading to 3.6, make sure that you run the `etcdutl check v2store` utility as it prevent 3.6 running.
Copy link
Copy Markdown
Author

@alam0rt alam0rt Feb 4, 2026

Choose a reason for hiding this comment

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

I know this is true because I am experiencing it as we speak haha. Stuck on 3.5 with v2store data. Compounded by not being able to tolerate downtime + v2 API not being accessible etcd-io/etcd#21249

Copy link
Copy Markdown
Contributor

@jberkus jberkus Apr 8, 2026

Choose a reason for hiding this comment

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

I think we need to understand the issue you're hitting better, because all of the v2store data issues were supposed to be fixed.

{{% /alert %}}

1. If there is data in the v2store that needs to be migrated to the v3store, follow the [v2 migration guide](../../../v3.4/op-guide/v2-migration/) to migrate the data.
Copy link
Copy Markdown
Author

@alam0rt alam0rt Feb 4, 2026

Choose a reason for hiding this comment

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

Not sure if this is recommended since we'd need to downgrade to 3.4 right?


2. Remove the `--enable-v2` flag and the `ETCD_ENABLE_V2="true"` environment variable.
2. Remove the `--enable-v2` flag and the `ETCD_ENABLE_V2="true"` environment variable if present.

3. Run the command `etcdutl check v2store` to verify whether the v2store contains any non-membership (custom) data. If no custom data is present, no further action is required.

4. If custom data is detected in the v2store, apply the following workaround to remove the legacy data:

- Add the flag `--snapshot-count=1` to each etcd instnace that contains custom data in the v2store.
- Add the flag `--snapshot-count=1` to each etcd instance that contains custom data in the v2store.
- Restart the etcd instances.
- Remove the `--snapshot-count=1` flag from (or restore to its original value, if applicable) from all etcd instances.
- Restart the etcd instances again.
Expand Down