Hi,
On Mar 26, 2007, at 5:00 , Sylvain Coutant wrote:
Ingo Kampe a écrit :
Hi,
Schnabl, Sebastian wrote:
Detail : version is 2.10.6.
Hm, I remembered on a similar issue short time ago - but this was
with
3.0beta. Look here:
https://forge.continuent.org/pipermail/sequoia/2007-February/
004791.html
There was a problem of loosing connection between controllers while
dump-operation (heavy load if controller == db-server). But no
solution
so far.
Possible a problem with appia and high cpu-utilization ?
We had problems with sequoia in high load too. It's not as robust
as I would
like it to. We are using sequoia 2.10.6 with appia from source for
the new base
view configuration.
Maybe there are some timing problems in the appia.xml SEQ channel
definitions. I
could imagine that some timeout frames are not big enough if whole
system is
slow and "cluster pings" takes too long.
Possibly. Our sequoia test controllers are slow (DB backends are
not on the same servers).
But the controller never resync and we have to put down both
controllers and restart everything to have them back online. A
timing issue would declare one controller dead at some point, but I
think some resync mechanism should take the hand at some point to
make them work together again later.
Yes, you are wright. You can increase the timers in the suspect
protocol. Check this:\
http://appia.di.fc.ul.pt/docs/javadoc/org/continuent/appia/protocols/
group/suspect/SuspectSession.html#init
(org.continuent.appia.xml.utils.SessionProperties)
But in the case of a real failure (not only because the system is
loaded) the resync will be needed anyway.
Cheers,
--
Nuno Carvalho
University of Lisbon, Portugal
http://dialnp.di.fc.ul.pt
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
