[CRIU] [Users] socket will take at least 0.5 seconds to recovery after docker restore done

Pavel Emelyanov xemul at parallels.com
Mon Jul 13 05:12:14 PDT 2015


On 07/12/2015 11:57 AM, Vasily Averin wrote:
> Re-addressed to criu mailing list
> 
> On 12.07.2015 10:48, Yanbao Cui wrote:
>> Hi,
>>
>> I am working on the docker checkpoint/restore use CRIU, and the time consuming is the key point we concerned.
>>
>> I found a strange phenomenon that the created socket need additional at least 0.5 seconds to reconnect after
>> the docker restore done.

Can you shed more light on this -- is there any particular system call that hangs for 0.5
seconds or is it just a "criu restore" time you observe?

>>
>> But if I create a new socket after restoring the docker , it will connect to the peer immediately.
>>
>> No matter the connection uses TCP or UDP.
>>
>> From the CRIU source code, I found that it will create a new socket with SO_REUSEADDR, and change the original fd to this new one. but I have no idea that why it need more time to recovery.
>>
>> Could someone help me to explain it or give me some points?
>>
>> Thanks very much!
>>
>> -- 
>> Best Regards
>> Cui Yanbao | 崔言宝
>> --
>> 龍生玖天,豈能安於凡塵!
> _______________________________________________
> CRIU mailing list
> CRIU at openvz.org
> https://lists.openvz.org/mailman/listinfo/criu
> 



More information about the CRIU mailing list