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: warn membership change while migration #7441

Merged
merged 1 commit into from
Mar 7, 2017

Conversation

gyuho
Copy link
Contributor

@gyuho gyuho commented Mar 7, 2017

Fix #7429.

@xiang90
Copy link
Contributor

xiang90 commented Mar 7, 2017

LGTM.

defer to @heyitsanthony

@@ -124,5 +124,6 @@ $ ETCDCTL_API=3 etcdctl endpoint health

- etcd < v3.1 does not work properly if built with Go > v1.7. See [Issue 6951](https://github.com/coreos/etcd/issues/6951) for additional information.
- If an error such as `transport: http2Client.notifyError got notified that the client transport was broken unexpected EOF.` shows up in the etcd server logs, be sure etcd is a pre-built release or built with (etcd v3.1+ & go v1.7+) or (etcd <v3.1 & go v1.6.x).
- Adding a v3 node to v2.3 cluster during upgrades is not supported, and could trigger panics. See [Issue 7249](https://github.com/coreos/etcd/issues/7429) for additional information. Mixed versions of etcd members are only allowed during v3 migration. Finish upgrades before making any membership changes.
Copy link
Contributor

Choose a reason for hiding this comment

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

s/, and/ and/

@heyitsanthony
Copy link
Contributor

lgtm after nit fixup. Thanks!

Fix etcd-io#7429.

Signed-off-by: Gyu-Ho Lee <gyuhox@gmail.com>
@@ -124,5 +124,6 @@ $ ETCDCTL_API=3 etcdctl endpoint health

- etcd &lt; v3.1 does not work properly if built with Go &gt; v1.7. See [Issue 6951](https://github.com/coreos/etcd/issues/6951) for additional information.
- If an error such as `transport: http2Client.notifyError got notified that the client transport was broken unexpected EOF.` shows up in the etcd server logs, be sure etcd is a pre-built release or built with (etcd v3.1+ &amp; go v1.7+) or (etcd &lt;v3.1 &amp; go v1.6.x).
Copy link
Member

Choose a reason for hiding this comment

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

for (etcd v3.1+ & go v1.7+), what does + means?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It means 1.7.0, 1.7.1, ...

Copy link
Member

Choose a reason for hiding this comment

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

is it same as 1.7.x?

Copy link
Member

Choose a reason for hiding this comment

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

I saw mix usage of + and v.a.b.x e.g go v1.6.x. I am unsure if they represent same thing.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah semantically they are the same. I think they all make sense.

Copy link
Contributor

Choose a reason for hiding this comment

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

1.7+ is 1.7 and above (e.g., 1.8). 1.7.x is all versions of 1.7 (e.g., 1.7.1 but not 1.8.0)

@gyuho gyuho merged commit 3f515e1 into etcd-io:master Mar 7, 2017
@gyuho gyuho deleted the warning branch March 7, 2017 19:38
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

4 participants