[ https://forge.continuent.org/jira/browse/SEQUOIA-905?page=all ]
Emmanuel Cecchet resolved SEQUOIA-905:
--------------------------------------
Resolution: Fixed
Fix Version: (was: Sequoia 2.10.5)
Fixed in CVS HEAD. Needs to be tested before being backported to 2.10 branch
> Transaction begin not logged in recovery log in single controller
> configuration
> -------------------------------------------------------------------------------
>
> Key: SEQUOIA-905
> URL: https://forge.continuent.org/jira/browse/SEQUOIA-905
> Project: Sequoia
> Type: Bug
> Components: Recovery Log, Core
> Versions: Sequoia 3.0 beta2, Sequoia 2.10.4, Sequoia 2.10.3, Sequoia
> 2.10.2
> Environment: Single controller configuration / RAIDb-1
> Reporter: Emmanuel Cecchet
> Assignee: Emmanuel Cecchet
> Priority: Blocker
> Fix For: Sequoia 3.0
>
>
> Problem reported by Ken Burns on the Sequoia mailing list and investigated by
> Guillaume Smet:
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
