On 12/7/13, 9:00 AM, 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.
OK, yes, I understand and that all makes sense.
We some files that are not active (such as periodic MySQL "archive"
dumps), so on those we can pull from the brick.
For others, that may be active, we will continue to use the client mount.
Thank You
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users