<div dir="ltr"><div><div>On Fri, Jul 17, 2015 at 8:50 AM, Yanbao Cui <span dir="ltr"><<a href="mailto:yygcui@gmail.com" target="_blank">yygcui@gmail.com</a>></span> wrote:<br></div></div><div><br></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">I use the latter one. And we integrade C/R functionality into Docker based on <a href="https://github.com/SaiedKazemi/docker/wiki" target="_blank">https://github.com/SaiedKazemi/docker/wiki</a></div></blockquote><div><br></div><div> So, you rebased Docker 1.5 code to 1.6? Did you see the issue in Docker 1.5?</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>And I found there is another one based on Docker 1.7<br></div></div></blockquote><div><br></div><div>Up until Docker 1.5, the network code was both in libcontainer and in the Docker engine. Now all network logic is in libnetwork, so there's no point spending time on older versions. Unfortunately I haven't had time yet to familiarize myself with the new code. Going forward, I suggest that you use the Docker 1.7. It's a rebase of 1.5 to the head and is under active development by Ross Boucher (<a href="mailto:rboucher@gmail.com">rboucher@gmail.com</a>) and other community members as I am sure you know.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div></div><div>Did you guys test it and focus on the time consumed?<br></div></div></blockquote><div><br></div><div>No my concentration was on getting the network to restore successfully. Didn't make any time measurements.</div><div><br></div><div>--Saied</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><div class="h5"><div class="gmail_extra"><div class="gmail_quote">On Fri, Jul 17, 2015 at 10:45 PM, Saied Kazemi <span dir="ltr"><<a href="mailto:saied@google.com" target="_blank">saied@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Are you doing external checkpoint restore, calling CRIU directly to dump and restore the container, or are you using native "docker checkpoint" and "docker restore" commands? If latter, did you integrate C/R functionality into Docker yourself?<span><font color="#888888"><div><br></div><div>--Saied</div><div><br></div></font></span></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 17, 2015 at 5:56 AM, Yanbao Cui <span dir="ltr"><<a href="mailto:yygcui@gmail.com" target="_blank">yygcui@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">I use docker 1.6.0 and 1.6.2, they all have this problem.<div><br></div><div>the needed files are shared via NFS.</div></div><div class="gmail_extra"><div><div><br><div class="gmail_quote">On Fri, Jul 17, 2015 at 11:15 AM, Saied Kazemi <span dir="ltr"><<a href="mailto:saied@google.com" target="_blank">saied@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Which Docker version are you using to checkpoint and restore your containers? Also, for migration, are you manually copying the container to a target machine?<div><br></div><div>--Saied</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Tue, Jul 14, 2015 at 7:36 AM, Yanbao Cui <span dir="ltr"><<a href="mailto:yygcui@gmail.com" target="_blank">yygcui@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div><p dir="ltr">Correct my reply:</p>
<p dir="ltr">_existing_ migrated connections hang.</p>
<p dir="ltr">New connection (here I mean new socket or a new process, not as like reconnection manually) is OK<br><br></p>
<br><div class="gmail_quote"><div dir="ltr">Yanbao Cui <<a href="mailto:yygcui@gmail.com" target="_blank">yygcui@gmail.com</a>>于2015年7月14日 周二 22:07写道：<br></div><div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><p dir="ltr">_existing_ migrated connections hang.</p>
<p dir="ltr">New connection is OK</p>
<br><div class="gmail_quote"><div dir="ltr">Pavel Emelyanov <<a href="mailto:xemul@parallels.com" target="_blank">xemul@parallels.com</a>>于2015年7月14日 周二 21:59写道：<br></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">On 07/14/2015 04:43 PM, Yanbao Cui wrote:<br>
> Server is working always and waiting. It seems the client, which is in the container, cannot send data out after restored.<br>
><br>
> For TCP, yeah, the client try to reconnect manually.<br>
<br>
You mean that after restore new connect()-s hang for a while? Why do these connect()-s happen?<br>
Or _existing_ migrated connections hang?<br>
<br>
> The delay is happened after restore successful, although the network is recovered<br>
><br>
><br>
> Pavel Emelyanov <<a href="mailto:xemul@parallels.com" target="_blank">xemul@parallels.com</a> <mailto:<a href="mailto:xemul@parallels.com" target="_blank">xemul@parallels.com</a>>>于2015年7月14日 周二 21:31写道：<br>
><br>
> On 07/14/2015 04:15 PM, Yanbao Cui wrote:<br>
> > Sorry for mistake.<br>
> > For UDP, I mean the sever can receive the packet from client again.<br>
><br>
> So where's the 0.5 seconds delay? Server sleeps and doesn't wake up, packets<br>
> do not reach the server or something else?<br>
><br>
> > Actually, I have analysis the tcpdump output, in my case, the client try to reconnect<br>
> > to the server again, but can not receive SYN+ACK, so it re-transmission after 1 second<br>
> > according to the client rule, and then try again.<br>
><br>
> During migration we don't reconnect TCP (with regular SYN, SYNACK, ACK sequence),<br>
> do you reconnect them manually?<br>
><br>
> -- Pavel<br>
><br>
<br>
</blockquote></div></blockquote></div></div></div>
<br></div></div><span>_______________________________________________<br>
CRIU mailing list<br>
<a href="mailto:CRIU@openvz.org" target="_blank">CRIU@openvz.org</a><br>
</span><a href="https://lists.openvz.org/mailman/listinfo/criu" rel="noreferrer" target="_blank">https://lists.openvz.org/mailman/listinfo/criu</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br><br clear="all"><div><br></div></div></div><span>-- <br><div><font color="#3333ff"><div><font color="#3333ff">Best Regards</font></div><div><font color="#3333ff">Cui Yanbao | 崔言宝</font></div><div><font color="#3333ff">--</font></div>龍生玖天，豈能安於凡塵！</font></div>
</span></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><font color="#3333ff"><div><font color="#3333ff">Best Regards</font></div><div><font color="#3333ff">Cui Yanbao | 崔言宝</font></div><div><font color="#3333ff">--</font></div>龍生玖天，豈能安於凡塵！</font></div>
</div>
</div></div></blockquote></div><br></div></div>