On Tue, Mar 20, 2012 at 9:26 PM, Lars Marowsky-Bree wrote:
> On 2012-03-20T11:42:08, Andrew Beekhof wrote:
>
>> > 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:
On 2012-03-20T11:42:08, Andrew Beekhof wrote:
> > 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
On Wed, Mar 14, 2012 at 6:40 PM, 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. n
16.03.2012 05:46, Andrew Beekhof wrote:
> On Thu, Mar 15, 2012 at 3:22 PM, Vladislav Bogdanov
> wrote:
>> 15.03.2012 01:49, Andreas Kurz wrote:
>>> On 03/14/2012 08:40 AM, Vladislav Bogdanov wrote:
Hi,
I'm observing a little bit unintuitive behavior of migration logic when
tran
On Thu, Mar 15, 2012 at 3:22 PM, Vladislav Bogdanov
wrote:
> 15.03.2012 01:49, Andreas Kurz wrote:
>> 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 middl
On Thu, Mar 15, 2012 at 9:53 AM, Lars Marowsky-Bree wrote:
> On 2012-03-14T23:49:26, Andreas Kurz wrote:
>
>> > 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)
>> be
On Thu, Mar 15, 2012 at 6:55 PM, Andreas Kurz wrote:
> On 03/15/2012 05:22 AM, Vladislav Bogdanov wrote:
>> 15.03.2012 01:49, Andreas Kurz wrote:
>>> On 03/14/2012 08:40 AM, Vladislav Bogdanov wrote:
Hi,
I'm observing a little bit unintuitive behavior of migration logic when
tr
15.03.2012 10:55, Andreas Kurz wrote:
> On 03/15/2012 05:22 AM, Vladislav Bogdanov wrote:
>> 15.03.2012 01:49, Andreas Kurz wrote:
>>> 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 abor
On 03/15/2012 05:22 AM, Vladislav Bogdanov wrote:
> 15.03.2012 01:49, Andreas Kurz wrote:
>> 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 r
15.03.2012 01:49, Andreas Kurz wrote:
> 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
On 2012-03-14T23:49:26, Andreas Kurz wrote:
> > 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
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: st
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 s
13 matches
Mail list logo