Hi Anand, I am enclosing the log. I added few log messages in dht_migrate_file. As you can see the daemon terminates before files are migrated.
This is a small volume. When I added sleep(100) statement in gf_defrag_done() routine then the migration of files work. All my bricks are on a single node. I created a volume with two bricks, created few files and added a new brick. I started the rebalance task. Thanks, Murali Balcha On Sun, Nov 24, 2013 at 11:53 PM, Anand Avati <av...@gluster.org> wrote: > > > > On Sun, Nov 24, 2013 at 8:42 PM, Muralidhar Balcha > <muralidh...@gmail.com>wrote: > >> Hi, >> I have couple of questions on rebalance functionality >> 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. >> > > 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? > > >> 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? >> >> > > Yes, clients are polling w/ glusterd waiting for config changes, and will > swap to a new xlator graph at run time if necessary. > > Avati > > -- Muralidhar Balcha 508 494 5007
vault-rebalance.log
Description: Binary data
_______________________________________________ Gluster-devel mailing list Gluster-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/gluster-devel