[ https://forge.continuent.org/jira/browse/SEQUOIA-737?page=comments#action_13837 ]
Marc Herbert commented on SEQUOIA-737: -------------------------------------- Is it so much harder to solve the general case ? (only the last VDB part stopped has the right to be started first) > Allow un-ordered vdb restart in case of global vdb shutdown with no write load > ------------------------------------------------------------------------------ > > Key: SEQUOIA-737 > URL: https://forge.continuent.org/jira/browse/SEQUOIA-737 > Project: Sequoia > Type: Improvement > Components: Core > Versions: Sequoia 2.9 > Reporter: Olivier Fambon > Assignee: Olivier Fambon > > > In the general 'complete vdb shutdown' scenario, i.e. when there is (write) > load on the system, > the boot up sequence should be carried out in reverse order from the shutdown > sequence. > That is: > - shutdown vdb on controller 1 > - shutdown vdb on controller 2 > - load vdb on controller 2 > - load vdb on controller 1 > However, in the special - although likely - case of a complete system shutdown > that would happen NOT under load, e.g. no clients performing writes on the > system, > or no clients at all, there is technically no good reason to force this > reverse order sequence, > since shutdown checkpoints on both vdb members refer to exactly the same > point in the recoverylog time. > It could be nice to allow un-ordered boot up in this case. -- 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 Sequoia@lists.forge.continuent.org https://forge.continuent.org/mailman/listinfo/sequoia
