Hello Nuno,

Nuno Carvalho wrote:
> On Mar 29, 2007, at 1:57 , Ingo Kampe wrote:
> 
>>
>> May be you can give an example howto set the suspect_sweep and
>> suspect_time
>> param in xml? I can't find that.
>>
>> Is this a hederachannel parameter like this:
>> <chsession name="hederalayer">
>>   <parameter name="suspect_sweep">2000</parameter>
>>   <parameter name="suspect_time">6000</parameter>
>>   ...
>> </chsession>
>> ??
>>
> 
> Each layer is configured separately, so in the channel that you are
> using you should add something like this:
> <chsession name="suspectl">
> <parameter name="suspect_sweep">2000</parameter>
> <parameter name="suspect_time">6000</parameter>
> </chsession>
> 
> where "suspectl" is the name of the corresponding layer in the
> corresponding template.
> 
>> I have done some further testing with the base view default setup and
>> debian
>> sarge, jvm 1.5. If I push the load (just CPU load!) to values around 6
>> the group
>> communication breaks. Even if I set the nice level of sequoia JVM to -20 !
>> I'm really surprised how CPU load can break a communication of a
>> process with
>> highest available priority.
>>
> 
> The ping messages of the failure detector between the members era FIFO
> ordered with the other messages (in this case, sequoia messages). If
> this messages are not received in time, the membership is suspected. Are
> you also loading the sequoia controllers?

No, thats it. Absolutly no load on sequoia. There are just some SELECTS without
transaction from maintainance threads once in 2 minutes. May be the FIFO is
blocked by somebody waiting for CPU.


>> Does anybody have an idea what to fix here? BTW the same test with jgroups
>> passes without problems. Jgroups communication is stable (tested up to
>> a load of
>> 20).
>>
> 
> You can increase the suspect timers. This should help.

Thanx for your help. I will play with timeouts and repeat my tests tomorrow.

)ngo

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia

Reply via email to