mirror of
https://github.com/featurebasedb/featurebase.git
synced 2026-08-28 10:54:59 +00:00
98a7129464
We had this fail in CI once, and failing took 30 minutes because we didn't have a timeout on this. This shouldn't ever fail, but the fact that it did indicates that the fabled etcd failures we've seen a couple of times were still capable of happening. This will make that failure happen sooner and more clearly. Also, log the cluster states (and possibly node states) while waiting. But add a delay -- otherwise we can do this quite a few times per millisecond. We use Logf so that, if you didn't use -v, you see these reported only if the test fails, but if the test fails, we'll say what happened. It would probably be better to have a passive thing that can wait for updates, because we're waiting on heartbeats. Missing: A way to detect what's actually happening in the failure cases, which we see only quite rarely. |
||
|---|---|---|
| .. | ||
| config_gen.go | ||
| embed.go | ||
| embed_test.go | ||
| enterprise_cluster.go | ||
| external.go | ||
| external_test.go | ||
| fake_test.go | ||
| leasedkv.go | ||
| leasedkv_test.go | ||
| plg_cluster.go | ||