On 05/23/2017 11:15 AM, Joe Julian wrote:
If this was multiple clients I could see that possibility, but the
single fuse client by which this file is being accessed should have a
consistent state to the single application regardless of the state of
the servers. How (and be specific, please, so I
On Tue, May 23, 2017 at 1:39 AM, Christopher Schmidt
wrote:
> OK, seems that this works now.
>
> A couple of questions:
> - What do you think, are all these options necessary for Kafka?
>
I am not entirely certain what subset of options will make it work as I do
not understand the nature of fail
If this happens again I will try to run the profiling of gluster and post back.
Fortunately it does not happen often but I need then to be in front so that I
can start/stop the profiling. By the way on that server I just have two clients
connected with FUSE.
Original Message
S
If this was multiple clients I could see that possibility, but the single fuse
client by which this file is being accessed should have a consistent state to
the single application regardless of the state of the servers. How (and be
specific, please, so I can understand the actual mechanism and e
I'm getting Transport endpoint is not connected on two client nodes, but I
don't see any errors on the server, any idea where to look next?
I'm using gluster 3.10 from the ppa for ubuntu-server, any idea if this
version is known to be broken?
I'm mounting the file systems using fuse, is that supp
Hi Kotresh,
As we know this problem occurs when BitRot start versioning of file of big
size.
Is there any possibility to disable this feature totally means remove the
BitRot feature so that it will not do this even when it is disabled.
Regards,
Abhishek
On Tue, Apr 25, 2017 at 12:47 PM, ABHISHE
