There is a publish node as down and wait method that just waits until then
down states show up in the cluster state. But waiting won't do any good
until down is actually published and it still is not. I'm pretty down has
never been published on startup despite appearances. I've seen two
ramifications from this. One is that it's much easier for replicas to get
out of sync when restarting a cluster while updates are coming in. I say
easier, because that's notnair tight regardless, but it does make it much
easier to happen. The second is that cores that are not ready can
participate in leader elections, receiving updates and queries. And if a
core fails to load, it will participate indefinitely. Retries and fault
tolerance will plaster over a good chunk of that though, less so for leader
election when a core fails to load
