9260066fa3
If you don't give your two host cluster enough time to "feel healthy", it will generate an error if you do operations within five seconds. This is a regression and the five seconds is also quite arbitrary. This is detailed at: https://github.com/coreos/etcd/issues/6305 This seems to be a bit of a race condition, even with a 10s timer, so this also disables the StrictReconfigCheck. Re-enable this as soon as possible.
23 lines
656 B
Bash
Executable File
23 lines
656 B
Bash
Executable File
#!/bin/bash -e
|
|
|
|
# run empty graphs, we're just testing etcd clustering
|
|
timeout --kill-after=120s 90s ./mgmt run --hostname h1 --tmp-prefix &
|
|
pid1=$!
|
|
sleep 10s # let it startup
|
|
|
|
timeout --kill-after=120s 90s ./mgmt run --hostname h2 --seeds http://127.0.0.1:2379 --client-urls http://127.0.0.1:2381 --server-urls http://127.0.0.1:2382 --tmp-prefix &
|
|
pid2=$!
|
|
sleep 10s
|
|
|
|
$(sleep 10s && kill -SIGINT $pid2)& # send ^C to exit 2nd mgmt
|
|
wait $pid2
|
|
e=$?
|
|
if [ $e -ne 0 ]; then
|
|
exit $e
|
|
fi
|
|
|
|
$(sleep 10s && kill -SIGINT $pid1)& # send ^C to exit 1st mgmt
|
|
wait $pid1 # get exit status
|
|
# if pid1 exits because of a timeout, then it blocked, and this is a bug!
|
|
exit $?
|