[Pacemaker] Migration atomicity

[Andreas Kurz]

On 03/14/2012 08:40 AM, Vladislav Bogdanov wrote:
> Hi,
> 
> I'm observing a little bit unintuitive behavior of migration logic when
> transition is aborted (due to CIB change) in the middle of the resource
> migration.
> 
> That is:
> 1. nodea: migrate_to nodeb
> 2. transition abort
> 3. nodeb: stop
> 4. nodea: migrate_to nodec
> 5. nodec: migrate_from nodea
> (note: no stop on nodea)
> 
> While I expect migration operation pair to be "more atomic":
> 1. nodea: migrate_to nodeb
> 2. transition abort
> 3. nodeb: migrate_from nodea
> 4. nodea: stop
> 5. nodeb: migrate_to nodec
> 6. nodec: migrate_from nodeb
> 7. nodeb: stop
> 
> Is the current behavior intended?

You mean that a migration is rolled-back due to a transition abort --
depending on its progress? I think that is the defined (and intended)
behavior since quite a long time ... maybe Andrew likes to comment on that?

Regards,
Andreas

-- 
Need help with Pacemaker?
http://www.hastexo.com/now

> 
> hb_report is available.
> 
> Best regards,
> Vladislav
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 222 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120314/90b3d83d/attachment-0004.sig>