On 12/19/2018 10:11 PM, Markus Armbruster wrote:
Fei Li writes:
On 12/13/2018 02:17 PM, Markus Armbruster wrote:
Fei Li writes:
In our current code, when multifd is used during migration, if there
is an error before the destination receives all new channels, the
source keeps running,
Fei Li writes:
> On 12/13/2018 02:17 PM, Markus Armbruster wrote:
>> Fei Li writes:
>>
>>> In our current code, when multifd is used during migration, if there
>>> is an error before the destination receives all new channels, the
>>> source keeps running, however the destination does not exit
On 12/13/2018 02:17 PM, Markus Armbruster wrote:
Fei Li writes:
In our current code, when multifd is used during migration, if there
is an error before the destination receives all new channels, the
source keeps running, however the destination does not exit but keeps
waiting until the
Fei Li writes:
> In our current code, when multifd is used during migration, if there
> is an error before the destination receives all new channels, the
> source keeps running, however the destination does not exit but keeps
> waiting until the source is killed deliberately.
>
> Fix this by
In our current code, when multifd is used during migration, if there
is an error before the destination receives all new channels, the
source keeps running, however the destination does not exit but keeps
waiting until the source is killed deliberately.
Fix this by dumping the specific error and
