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

etcdmain: start on unsupported arch when ETCD_UNSUPPORTED_ARCH is set #5028

Merged

Conversation

heyitsanthony
Copy link
Contributor

No description provided.

@heyitsanthony
Copy link
Contributor Author

/cc @xiang90 @luxas

@@ -141,8 +141,9 @@ The `v2` API responses should not change after the 2.0.0 release but new feature

etcd has known issues on 32-bit systems due to a bug in the Go runtime. See #[358][358] for more information.

To avoid inadvertantly producing an unstable etcd server, 32-bit builds emit an `etcd` that prints
a warning message and immediately exits.
To avoid inadvertantly running a possibly unstable etcd server, `etcd` on unsupported architectures will print
Copy link
Contributor

Choose a reason for hiding this comment

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

shall we mention that the only supported arch is amd64 right now?

@heyitsanthony heyitsanthony force-pushed the etcdmain-unsupported-envvar branch 2 times, most recently from 4962d4d to c4caa65 Compare April 11, 2016 02:35
@heyitsanthony
Copy link
Contributor Author

all fixed /cc @xiang90

@xiang90
Copy link
Contributor

xiang90 commented Apr 11, 2016

LGTM

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

2 participants