> On 24 Feb 2015, at 4:35 pm, Vladislav Bogdanov wrote:
>
> 24.02.2015 01:58, Andrew Beekhof wrote:
>>
>>> On 21 Jan 2015, at 5:08 pm, Vladislav Bogdanov wrote:
>>>
>>> 21.01.2015 03:51, Andrew Beekhof wrote:
> On 20 Jan 2015, at 4:13 pm, Vladislav Bogdanov
> wrote:
>
>>>
24.02.2015 01:58, Andrew Beekhof wrote:
On 21 Jan 2015, at 5:08 pm, Vladislav Bogdanov wrote:
21.01.2015 03:51, Andrew Beekhof wrote:
On 20 Jan 2015, at 4:13 pm, Vladislav Bogdanov wrote:
20.01.2015 02:47, Andrew Beekhof wrote:
On 17 Jan 2015, at 1:25 am, Vladislav Bogdanov
wrote:
H
> On 21 Jan 2015, at 5:08 pm, Vladislav Bogdanov wrote:
>
> 21.01.2015 03:51, Andrew Beekhof wrote:
>>
>>> On 20 Jan 2015, at 4:13 pm, Vladislav Bogdanov wrote:
>>>
>>> 20.01.2015 02:47, Andrew Beekhof wrote:
> On 17 Jan 2015, at 1:25 am, Vladislav Bogdanov
> wrote:
>
21.01.2015 03:51, Andrew Beekhof wrote:
On 20 Jan 2015, at 4:13 pm, Vladislav Bogdanov wrote:
20.01.2015 02:47, Andrew Beekhof wrote:
On 17 Jan 2015, at 1:25 am, Vladislav Bogdanov
wrote:
Hi all,
Trying to reproduce problem with early stop of globally-unique
clone instances during move
> On 20 Jan 2015, at 4:13 pm, Vladislav Bogdanov wrote:
>
> 20.01.2015 02:47, Andrew Beekhof wrote:
>>
>>> On 17 Jan 2015, at 1:25 am, Vladislav Bogdanov
>>> wrote:
>>>
>>> Hi all,
>>>
>>> Trying to reproduce problem with early stop of globally-unique
>>> clone instances during move to anoth
20.01.2015 02:47, Andrew Beekhof wrote:
On 17 Jan 2015, at 1:25 am, Vladislav Bogdanov
wrote:
Hi all,
Trying to reproduce problem with early stop of globally-unique
clone instances during move to another node I found one more
"interesting" problem.
Due to the different order of resources in
> On 17 Jan 2015, at 1:25 am, Vladislav Bogdanov wrote:
>
> Hi all,
>
> Trying to reproduce problem with early stop of globally-unique clone
> instances during move to another node I found one more "interesting" problem.
>
> Due to the different order of resources in the CIB and extensive use