The general advice is to just have your applications crash loop on whatever
invariant you are waiting on.

Does that now work for some reason?

On Thu, Jan 18, 2018 at 3:41 PM Karthik <kart...@yugabyte.com> wrote:

> Hi all,
>
> I created a StatefulSet service (yb-master) with 3 pods (yb-master-0,1,2).
> The cname of the headless service seems to list the pods that are currently
> running, so right when my processes start, they are not able to resolve the
> addresses of the others (I am using podManagementPolicy: "Parallel"). But
> to establish quorum, I need to wait for all the pods to come up before
> trying to leader elect.
>
> In the above scenario, is there some mechanism to wait for all the pods to
> come up before starting any of the processes?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Kubernetes user discussion and Q&A" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to kubernetes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to kubernetes-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/kubernetes-users.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
CTO, CoreOS, Inc
Tectonic is enterprise Kubernetes
https://coreos.com/tectonic

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to