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.

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

Jump to bottom

cluster wide configuration #2038

Closed
yichengq opened this issue Jan 5, 2015 · 4 comments
Closed

cluster wide configuration #2038

yichengq opened this issue Jan 5, 2015 · 4 comments
Labels
area/performance

Comments

@yichengq
Copy link
Contributor

yichengq commented Jan 5, 2015

from #1551
The thoughts is to expose HTTP endpoint for it and make the timeout cluster-wide configurable.
@yichengq yichengq added this to the v3.0.0-alpha.1 milestone Jan 5, 2015
@yichengq yichengq mentioned this issue Jan 5, 2015
Closed
@damm
Copy link

damm commented Jun 25, 2015

This would be rather helpful for my team as we use etcd in most regions (asia pacific, england, us, soon india)

also a command line argument would work no?

P.S. if help will bump this milestone up please add the label.

@xiang90
Copy link
Contributor

xiang90 commented Aug 25, 2015

@yichengq Any update on this one?

@xiang90 xiang90 changed the title make server timeout configurable cluster wide configuration Apr 25, 2016
@xiang90
Copy link
Contributor

xiang90 commented Apr 25, 2016

This is a configuration issue. It is not urgent since most users can actually ensure the configuration are consistent across their cluster members and do not really need to do runtime configuration changes.

@xiang90 xiang90 modified the milestones: unplanned, v3.0.0-alpha0 Apr 25, 2016
@xiang90 xiang90 modified the milestones: v3.2.0, unplanned Jul 11, 2016
@bogdando bogdando mentioned this issue Aug 3, 2016
Closed
@xiang90 xiang90 modified the milestones: v3.2.0-maybe, v3.2.0 Aug 15, 2016
@xiang90 xiang90 modified the milestones: v3.3.0, v3.2.0-maybe Mar 31, 2017
@xiang90 xiang90 modified the milestones: unplanned, v3.3.0 Jul 15, 2017
@xiang90
Copy link
Contributor

xiang90 commented Oct 24, 2017

this is unlikely to happen anytime soon. we rarely see people have configuration issues due to the incompatible flags provided to different etcd members in the cluster.

@xiang90 xiang90 closed this as completed Oct 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/performance
Milestone
No milestone
Development

No branches or pull requests
3 participants
@damm @yichengq @xiang90