Hi Niels,
We have tested the patch for some days. It works well when the gluster peer
status
change to disconnected. However, if we retore the network just before the
peer
status change to disconnected status, we found out that glusterfsd will
still
open a new fd, and leave the old one not
It seems that this email was sent twice? Just in case you missed my
response to the other one, here it is:
- http://supercolony.gluster.org/pipermail/gluster-devel/2014-August/041972.html
Niels
On Wed, Aug 20, 2014 at 07:13:21PM +0800, Jaden Liang wrote:
Hi gluster-devel team,
We are running
Yes, that is another copy.
We are testing and reviewing the patch codes, will try some other scenarios at
the same time. The result will inform out when solution confirmed.
Thanks again for your reply.
Jaden Liang
在 2014年8月21日，17:00，Niels de Vos nde...@redhat.com 写道：
It seems that this
Hi gluster-devel team,
We are running a 2 replica volume in 2 servers. One of our service daemon
open a file with 'flock' in the volume. We can see every glusterfsd daemon
open the replica files in its own server(in /proc/pid/fd). When we pull off
the cable of one server about 10 minutes then
On Wed, Aug 20, 2014 at 07:16:16PM +0800, Jaden Liang wrote:
Hi gluster-devel team,
We are running a 2 replica volume in 2 servers. One of our service daemon
open a file with 'flock' in the volume. We can see every glusterfsd daemon
open the replica files in its own server(in /proc/pid/fd).
