On 07/12/13 18:00, Vijay Bellur wrote:
If there is no write activity (either application driven or gluster's
maintenance operations like self-heal, rebalance), then reading from
the bricks might be fine. Since these operations are asynchronous in
nature and since most applications are not written to be aware of the
implications of loose consistency, the recommended method is to
perform all reads through a gluster client stack.
This seems very reasonable. But what about the case where a new
installation of gluster is supposed to "incorporate" files already
present at the mount points, how to "bring them in" under gluster?
Regards,
/jon
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
