[sheepdog] [PATCH v3] sheep: remove master node

Liu Yuan namei.unix at gmail.com
Wed Jul 24 11:17:23 CEST 2013


在 2013-7-24 PM5:13,"Kai Zhang" <kyle at zelin.io>写道:
>
>
> On Jul 24, 2013, at 2:53 PM, MORITA Kazutaka <
morita.kazutaka at lab.ntt.co.jp> wrote:
>
> > At Tue, 23 Jul 2013 17:30:03 +0800,
> > Kai Zhang wrote:
> >>
> >> On Jul 23, 2013, at 4:44 PM, MORITA Kazutaka <
morita.kazutaka at lab.ntt.co.jp> wrote:
> >>
> >>> Ah, sorry.  The node A doesn't start until the nodes B, C, and D come
> >>> back.  It is because the latest epoch in the node A includes B, C, and
> >>> D.
> >>
> >> Well, it seems I didn't fully understand the current implementation of
cluster driver.
> >>
> >> A very silly question: if B, C come back but D does not, what is the
status of
> >> the cluster? It can work or just wait for D?
> >
> > The cluster status will be SD_STATUS_WAIT.  It will wait for the node
> > D to join Sheepdog if you don't run "collie cluster recover force".
> >
>
> Does this mean that sheepdog is not self-healing?
> Any persistent failure of sheep will be handled by administrator?

sd is indeed self-healing, only corner case we need manaul recovery.

> If so, I think there is no need for auto-recover.
> Recover should happen when administrator call "collie cluster recover
force".
>
> Thanks,
> Kyle
>
> --
> sheepdog mailing list
> sheepdog at lists.wpkg.org
> http://lists.wpkg.org/mailman/listinfo/sheepdog
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/sheepdog/attachments/20130724/1e60a5ce/attachment-0004.html>


More information about the sheepdog mailing list