<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Nov 24, 2013 at 8:42 PM, Muralidhar Balcha <span dir="ltr"><<a href="mailto:muralidharb@gmail.com" target="_blank">muralidharb@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div>I have couple of questions on rebalance functionality</div><div>1. When I ran rebalancing command, the gluster daemon that is responsible for migrating data is terminating itself in the middle of the data migration. I may be missing something. How do I make the daemon wait until the data migration is complete.</div>
</div></blockquote><div><br></div><div>Under normal circumstances, the rebalance daemon terminates when it believes it has completed transferring all files it is supposed to. Do you have any logs with more details?</div><div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">
<div>2. This question may not be related to rebalance adding or removing a brick from a volume. If I add a new brick to a volume that is in use, how do existing clients realize the new brick? Is there a notification mechanism that each client refreshes their client volinfo?</div>
<div><br></div></div></blockquote><div><br></div><div><br></div><div>Yes, clients are polling w/ glusterd waiting for config changes, and will swap to a new xlator graph at run time if necessary.</div><div><br></div><div>
Avati</div><div><br></div></div></div></div>