Hello Vikas, thanks for your reply.>> On each Webserver is a local brick used as a type of cache. > > Can you explain a bit more about how the local brick is used > and why it's needed?It is just used as another copy of data. I feel like using such a local brick optimizes the performance very much.>> Now when we change a file on a Fileserver. > > Are you changing the file directly on the backend on a fileserver?No, we change file in the mounted directory. So the new files is immediately replicated to the second fileserver.> Vikas > -- > Engineer - http://gluster.com/ >Thanks for your help! Christian
----- "Christian Schab" <christian.schab at me.com> wrote:> It is just used as another copy of data. > I feel like using such a local brick optimizes the performance very > much.In that case you should set the option read-subvolume to "brick", so that reads go to the local brick.> No, we change file in the mounted directory. > So the new files is immediately replicated to the second fileserver.Ok. Can you explain in more detail where you're doing the modification from, and when self-heal is triggered? Vikas -- Engineer - http://gluster.com/