I suspect this is because of the RPC portmap reconnection delay. Can you check with the latest git head which has review.gluster.com/3994?
Avati On Tue, Sep 25, 2012 at 9:05 PM, Bharata B Rao <[email protected]>wrote: > Hi, > > With recent git tree, glusterd takes a long time to start. > > Earlier: > [root@bharata glusterfs]# time glusterd > > real 0m0.007s > user 0m0.001s > sys 0m0.006s > > Now: > [root@bharata glusterfs]# time glusterd > > real 0m4.152s > user 0m0.003s > sys 0m0.009s > > git bisect points to this commit: > > [root@bharata glusterfs]# git bisect bad > 373b25827f0250d11461fbe76dd6a0e295069171 is the first bad commit > commit 373b25827f0250d11461fbe76dd6a0e295069171 > Author: Anand Avati <[email protected]> > Date: Mon Aug 20 10:48:16 2012 -0700 > > core: enable process to return the appropriate error code > > Setup a pipe() in glusterfs_ctx_t to communicate with the fork'ed > child the exit status and return it to the shell. > > Change-Id: Ibbaa581d45acb24d5141e43ae848cae29312d95f > BUG: 762935 > Signed-off-by: Anand Avati <[email protected]> > Reviewed-on: http://review.gluster.org/3836 > Tested-by: Gluster Build System <[email protected]> > Reviewed-by: Amar Tumballi <[email protected]> > > Regards, > Bharata. > -- > http://bharata.sulekha.com/blog/posts.htm, > http://raobharata.wordpress.com/ > > _______________________________________________ > Gluster-devel mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/gluster-devel >
_______________________________________________ Gluster-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/gluster-devel
