Hi Markus,
You may have a problem in your group communication setup if the
fragmentation layer is not working in JGroups.
Where could the problem in the fragmentation layer? We just use the
default sequencer jgroups file shipped with sequoia.
Can you point me to a good documentation source, since we are not firm
with jgroups.
The reference documentation on JGroups is
http://www.jgroups.org/javagroupsnew/docs/manual/html/index.html
The default JGroups config in 2.10.10 seems to have the FRAG2 protocol
commented, you might want to uncomment that line (on both controllers)
and give it a try. I would not rely on a UDP configuration anyway for
production this has proven to be too unreliable in terms of performance
under high load (see http://jmob.objectweb.org/JGroups.html or the paper
at http://jmob.objectweb.org/jgroups/JGroups-middleware-2004.pdf).
You may also have to check your recovery log configuration to make
sure that the columns storing the SQL are large enough to contain the
whole statement. Otherwise there is no limit on the statement size
in Sequoia, we do insert Blobs of several MB so few KB should not be
a problem
This should be no problem, since if we use only one controller all does
work well. Even larger blobs.
Since you have a single backend attached to that controller, I am not
sure that still guarantees you that the recovery log is working 100% ok.
Note that also Hedera should bypass the communication layer if the
messages have only to be delivered locally (common optimization).
Keep us posted with your findings,
Emmanuel
--
Emmanuel Cecchet
FTO @ Frog Thinker
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: [EMAIL PROTECTED]
Skype: emmanuel_cecchet
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
