Re: [ClusterLabs] Is "Process pause detected" triggered too easily?

2017-10-04 Thread Jean-Marc Saffroy
On Wed, 4 Oct 2017, Jan Friesse wrote: > > Could you clarify the formula for me? I don't see how "- 2" and "650" > > map to this configuration. > > Since Corosync 2.3.4 when nodelist is used, totem.token is used only as > a basis for calculating real token timeout. You can check corosync.conf

Re: [ClusterLabs] Is "Process pause detected" triggered too easily?

2017-10-04 Thread Jan Friesse
Jean, Hi Jan, On Tue, 3 Oct 2017, Jan Friesse wrote: I hope this makes sense! :) I would still have some questions :) but that is really not related to the problem you have. Questions are welcome! I am new to this stack, so there is certainly room for learning and for improvement. My pe

Re: [ClusterLabs] Is "Process pause detected" triggered too easily?

2017-10-03 Thread Jean-Marc Saffroy
Hi Jan, On Tue, 3 Oct 2017, Jan Friesse wrote: > > I hope this makes sense! :) > > I would still have some questions :) but that is really not related to > the problem you have. Questions are welcome! I am new to this stack, so there is certainly room for learning and for improvement. > My p

Re: [ClusterLabs] Is "Process pause detected" triggered too easily?

2017-10-03 Thread Jan Friesse
Jean, On Mon, 2 Oct 2017, Jan Friesse wrote: We had one problem on a real deployment of DLM+corosync (5 voters and 20 non-voters, with dlm on those 20, for a specific application that uses What you mean by voters and non-voters? There is 25 nodes in total and each of them is running corosync

Re: [ClusterLabs] Is "Process pause detected" triggered too easily?

2017-10-02 Thread Jean-Marc Saffroy
On Mon, 2 Oct 2017, Jan Friesse wrote: > > We had one problem on a real deployment of DLM+corosync (5 voters and 20 > > non-voters, with dlm on those 20, for a specific application that uses > > What you mean by voters and non-voters? There is 25 nodes in total and > each of them is running coro

Re: [ClusterLabs] Is "Process pause detected" triggered too easily?

2017-10-02 Thread Jan Friesse
On Wed, 27 Sep 2017, Jan Friesse wrote: I don't think scheduling is the case. If scheduler would be the case other message (Corosync main process was not scheduled for ...) would kick in. This looks more like a something is blocked in totemsrp. Ah, interesting! Also, it looks like the side e

Re: [ClusterLabs] Is "Process pause detected" triggered too easily?

2017-09-27 Thread Jean-Marc Saffroy
On Wed, 27 Sep 2017, Jan Friesse wrote: > I don't think scheduling is the case. If scheduler would be the case > other message (Corosync main process was not scheduled for ...) would > kick in. This looks more like a something is blocked in totemsrp. Ah, interesting! > > Also, it looks like th

Re: [ClusterLabs] Is "Process pause detected" triggered too easily?

2017-09-27 Thread Jan Friesse
Jean, Hello, As the subject line suggests, I am wondering why I see so many of these log lines (many means about 10 times per minute, usually several in the same second): Sep 26 19:56:24 [950] vm0 corosync notice [TOTEM ] Process pause detected for 2555 ms, flushing membership messages. Sep 2