<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 1, 2016 at 2:59 PM, Atin Mukherjee <span dir="ltr"><<a href="mailto:amukherj@redhat.com" target="_blank">amukherj@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
On 04/01/2016 02:55 PM, ABHISHEK PALIWAL wrote:<br>
> Hi Atin,<br>
><br>
> Thanks for reply.<br>
><br>
> Could you please help me to identify the error log in the respective<br>
> brick log file. I tried but not able to identified where the problem is<br>
> occuring.<br>
><br>
> I am attaching the brick log file which is not coming online even after<br>
> waiting for 1 minute.<br>
</span>What time did you reboot B? Could you also attach glusterd log file<br>
(complete log) for board B?<br>
<span class="">><br></span></blockquote><div>it is hard to say at what time we rebooted the B board because we are continuously rebooting the board B.<br><br></div><div>Here I am attaching the glusterd and glsuterfs log for board B. <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
> Regards,<br>
> Abhishek<br>
><br>
> On Fri, Apr 1, 2016 at 1:04 PM, Atin Mukherjee <<a href="mailto:amukherj@redhat.com">amukherj@redhat.com</a><br>
</span><div><div class="h5">> <mailto:<a href="mailto:amukherj@redhat.com">amukherj@redhat.com</a>>> wrote:<br>
><br>
><br>
><br>
> On 04/01/2016 12:10 PM, ABHISHEK PALIWAL wrote:<br>
> > Hi,<br>
> ><br>
> ><br>
> > I have the setup of two boards A and B with two bricks in replica mode.<br>
> ><br>
> > There is one test scenario<br>
> ><br>
> > 1. A acts as an active board and having the glusterfs mount point on it.<br>
> > 2. B acts as Passive board.<br>
> > 3. We are repetitively rebooting the B board (In this time period peer<br>
> > status on A board will be "peer in cluster (Disconnected)" and brick is<br>
> > not present in "gluster volume status") and when Board B comes up,<br>
> > starts the gluster daemon.<br>
> > 4. if Gluster daemon starts successfully it will make "peer in<br>
> > cluster(Connected)"<br>
> > 5. At the same with the immediate effect "gluster volume status" command<br>
> > should show the brick is available in online.<br>
> ><br>
> ><br>
> > But in my case sometime step 5 takes immediate reflection sometime 10-15<br>
> > second and sometime doesn't show brick is online even after the 1minute.<br>
> ><br>
> > Could you please confirm why this type of unpredictable behavior is<br>
> > occuring. It should be reflect with immediate effect in "gluster volume<br>
> > status" command.<br>
> When glusterd restarts bricks processes are brought up asynchronously<br>
> and hence you may not see the brick processes reflecting in gluster<br>
> volume status output immediately after restart. 5-10 seconds is an<br>
> accepted time frame. However if it doesn't come back online post that<br>
> then probably brick fails to start in that case.<br>
><br>
> Please check the respective brick log file and if you can find any error<br>
> logs in it.<br>
> ><br>
> ><br>
> > --<br>
> > Regards<br>
> > Abhishek Paliwal<br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Gluster-devel mailing list<br>
</div></div>> > <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a> <mailto:<a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a>><br>
<div class="HOEnZb"><div class="h5">> > <a href="http://www.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
> ><br>
><br>
><br>
><br>
><br>
> --<br>
><br>
><br>
><br>
><br>
> Regards<br>
> Abhishek Paliwal<br>
</div></div></blockquote></div><br></div></div>