[ https://forge.continuent.org/jira/browse/SEQUOIA-1106?page=comments#action_14640 ]
Robert Hodges commented on SEQUOIA-1106: ---------------------------------------- Interesting indeed. The obvious problem is that while each BackendTaskQueues implementation offers deterministic execution of SQL, there's no guarantee that the actual order is the same. Once you pick an implementation you have to stick with it *or* discard the recovery log if you change. This is not as bad as doing an init; however, it's possible to foresee some ugly corner cases if you can't shut down the VDB on all controllers at once. For now we should advise users to pick one implementation and stick with it. > RecoverThread should use the right backend request scheduler, as defined in > config file > --------------------------------------------------------------------------------------- > > Key: SEQUOIA-1106 > URL: https://forge.continuent.org/jira/browse/SEQUOIA-1106 > Project: Sequoia > Type: Bug > Components: Core > Versions: sequoia 2.10.11 > Reporter: Stephane Giron > Assignee: Stephane Giron > Fix For: sequoia 2.10.11 > > > For now, whatever the configured request scheduler is, RecoverThread is using > BackendTaskQueues request scheduler. -- 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
