James Shubin 9aee3f01cd embed: Move the ReadyNotify() call to a better place ...

When using the embed functionality, you can't call the Server.Stop()
function until StartEtcd returns, which can block until there is a call
to Server.Stop() in error situations. Since we have a catch-22, the
ReadyNotify() can be called manually by the user if they wish to wait
for the server startup, or in parallel with a timeout if they wish to
cancel it after some time.

Chzz pointed out that this is also more consistent with the
etcdserver.Start() behaviour too.

purpleidea pointed out that this is actually more correct too, because
we can now register the stop interrupt handler before we block on
startup.

2016-08-29 22:45:41 -04:00

..

config_test.go

etcdmain, embed: export Config and StartEtcd into embed/

2016-07-13 10:40:03 -07:00

config.go

embed: add listen urls to default config

2016-07-25 11:06:03 -07:00

doc.go

embed: Move the ReadyNotify() call to a better place

2016-08-29 22:45:41 -04:00

etcd.go

embed: Move the ReadyNotify() call to a better place

2016-08-29 22:45:41 -04:00

serve.go

embed: change import path to 'grpc-ecosystem'

2016-07-15 12:10:38 -07:00

util.go

embed: only get initial cluster setting if the member is not init

2016-07-13 16:03:27 -07:00