Actually, no. It is because glusterd (which is just a different incarnation glusterfsd) now returns proper error code by waiting long enough (completion of init()). The init() in glusterd actually can take some time since it starts all the brick processes. Previously all this would happen in the background after starting glusterd (i.,e return of glusterd to shell wouldn't truly have "completed the startup") and now it just waits and returns the right exit status to the shell.<div>
<br></div><div>Avati<br><br><div class="gmail_quote">On Tue, Sep 25, 2012 at 9:15 PM, Anand Avati <span dir="ltr"><<a href="mailto:anand.avati@gmail.com" target="_blank">anand.avati@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I suspect this is because of the RPC portmap reconnection delay. Can you check with the latest git head which has <a href="http://review.gluster.com/3994" target="_blank">review.gluster.com/3994</a>?<span class="HOEnZb"><font color="#888888"><div>
<br></div></font></span><div><span class="HOEnZb"><font color="#888888">Avati</font></span><div><div class="h5"><br><br><div class="gmail_quote">
On Tue, Sep 25, 2012 at 9:05 PM, Bharata B Rao <span dir="ltr"><<a href="mailto:bharata.rao@gmail.com" target="_blank">bharata.rao@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
With recent git tree, glusterd takes a long time to start.<br>
<br>
Earlier:<br>
[root@bharata glusterfs]# time glusterd<br>
<br>
real 0m0.007s<br>
user 0m0.001s<br>
sys 0m0.006s<br>
<br>
Now:<br>
[root@bharata glusterfs]# time glusterd<br>
<br>
real 0m4.152s<br>
user 0m0.003s<br>
sys 0m0.009s<br>
<br>
git bisect points to this commit:<br>
<br>
[root@bharata glusterfs]# git bisect bad<br>
373b25827f0250d11461fbe76dd6a0e295069171 is the first bad commit<br>
commit 373b25827f0250d11461fbe76dd6a0e295069171<br>
Author: Anand Avati <<a href="mailto:avati@redhat.com" target="_blank">avati@redhat.com</a>><br>
Date: Mon Aug 20 10:48:16 2012 -0700<br>
<br>
core: enable process to return the appropriate error code<br>
<br>
Setup a pipe() in glusterfs_ctx_t to communicate with the fork'ed<br>
child the exit status and return it to the shell.<br>
<br>
Change-Id: Ibbaa581d45acb24d5141e43ae848cae29312d95f<br>
BUG: 762935<br>
Signed-off-by: Anand Avati <<a href="mailto:avati@redhat.com" target="_blank">avati@redhat.com</a>><br>
Reviewed-on: <a href="http://review.gluster.org/3836" target="_blank">http://review.gluster.org/3836</a><br>
Tested-by: Gluster Build System <<a href="mailto:jenkins@build.gluster.com" target="_blank">jenkins@build.gluster.com</a>><br>
Reviewed-by: Amar Tumballi <<a href="mailto:amarts@redhat.com" target="_blank">amarts@redhat.com</a>><br>
<br>
Regards,<br>
Bharata.<br>
<span><font color="#888888">--<br>
<a href="http://bharata.sulekha.com/blog/posts.htm" target="_blank">http://bharata.sulekha.com/blog/posts.htm</a>, <a href="http://raobharata.wordpress.com/" target="_blank">http://raobharata.wordpress.com/</a><br>
<br>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@nongnu.org" target="_blank">Gluster-devel@nongnu.org</a><br>
<a href="https://lists.nongnu.org/mailman/listinfo/gluster-devel" target="_blank">https://lists.nongnu.org/mailman/listinfo/gluster-devel</a><br>
</font></span></blockquote></div><br></div></div></div>
</blockquote></div><br></div>