Ken,
On 1/25/07, Ken Burns <[EMAIL PROTECTED]> wrote:
Is someone able to run my test procedure to confirm my findings and decide
if there is an issue that could be handled through JIRA? (Please refer to my
postings on 17/01/2007 and 15/01/2007).
I reproduced the problem with SQL Explorer and your procedure.
In fact the problem only exists when you're in a single controller
configuration with no Distribution element as there is a bug in the
code path when you're not in the distributed case.
It seems that the code path when you're not in distributed mode is
quite broken as I often see problems only in this case.
It's highly recommended to have at least 2 controllers otherwise you
introduce a new single point of failure.
To fix the problem in a quick and dirty way, you can simply add a
<Distribution> element in your virtual database configuration. It
should fix the problem (at least it works here).
<Distribution hederaPropertiesFile="/hedera_jgroups.properties">
<MessageTimeouts/>
</Distribution>
for example (I personnaly use Appia but choose the communication layer
you prefer).
Even with only one controller, this element will force Sequoia to use
the distributed code path which doesn't have this bug.
Can you confirm that it's OK for you when you add this element to your
configuration.
One more time, you should consider adding another controller to your
configuration to avoid the introduction of a new SPOF.
Emmanuel : the problem seems to be that
AbstractRequest.setLazyTransactionStart is only called in the
distributed case (in DistributedRequestManager.lazyTransactionStart).
It prevents the begin from being logged in the recovery log because in
RAIDb1.execWriteRequest (which is the method used in Ken's case),
logLazyTransactionBegin is only executed if
request.isLazyTransactionStart() returns true.
Shouldn't we simply force the users to use a <Distribution> element?
Perhaps it's already the case in Sequoia 3.0 beta? I have really a lot
of weird behaviours when I'm not in distributed mode and it seems that
there is a lot of bugs specific to this code path.
--
Guillaume
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
