[ejabberd] safe recovery from inconsistent_database/running_partitioned_network error

Zbyszek Żółkiewski zbyszek at toliman.pl
Thu Nov 8 17:29:26 MSK 2007


oh, ok i know this issue, it was reported few month ago on mailing list, but
with no futhure actions :/

On 11/8/07, Igor Goryachev <igor at goryachev.org> wrote:
>
> "Zbyszek Żółkiewski" <zbyszek at toliman.pl> writes:
>
> >>      I am thinking on implementing a safe recovery routine against
> >>      inconsistent_database/running_partitioned_network errors which
> >>      occur
> >>      sometimes in our network environment. Any suggestions?
> >
> >    can you explain more? we're running cluster also so we can exchange
> >    experiences
>
> This behaviour occurs while network failures, even the short ones. The
> nodes begin to live as they are standalone, not connected in cluster.
> The only one solution (for now) is to reboot all nodes except one in
> order they could sync mnesia once again.
>
>
> --
>     Igor Goryachev              E-Mail/Jabber: igor at goryachev.org
> _______________________________________________
> ejabberd mailing list
> ejabberd at jabber.ru
> http://lists.jabber.ru/mailman/listinfo/ejabberd
>



-- 
pozdrawiam,
Zbyszek Żółkiewski
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jabber.ru/pipermail/ejabberd/attachments/20071108/217b1b41/attachment.htm 


More information about the ejabberd mailing list