On Tue, 4 Aug 2009, Anton wrote:
Hello friends, I have sucessully installed Gluster 2.0.4 in the configuration of 3 nodes with 2x bricks per node with replication and distribution. While adding an extra brick, which had to became a replicated copy of another brick I have noticed that gluster is doing replication wile accessing a non-replicated data in the rel-time - so listing the contents of the non-replicated directory with large-size files became unacceptably slow, since replication of 10GB data takes time over 1GB network - so the question, is there any way (options) to have the given replication in the backround, so not-affecting the user work? Or this is just is not implemented?
Not yet, but you can fix the ls problme with: unalias ls
<>
Nathan Stratton CTO, BlinkMind, Inc. nathan at robotics.net nathan at blinkmind.com http://www.robotics.net http://www.blinkmind.com
