Hello Guys,
I have been trying to set a geo replication in our glusterfs test
environment and got a problem with a message invalid slave name
So first things first...
I have 3 nodes configured in a cluster. Those nodes are configured as
replica. On this cluster I have a volume created with
On 15/07/14 15:08, Stefan Moravcik wrote:
Hello Guys,
I have been trying to set a geo replication in our glusterfs test
environment and got a problem with a message invalid slave name
So first things first...
I have 3 nodes configured in a cluster. Those nodes are configured as
replica. On
Hi,
Yesterday I was gonna to replicate the error, but I didnt managed to do
it, so I started to wonder whether it wasnt bad call..
I read the following links, so I would like to ask :D Does it mean, that
this bug is caused by very fast recovery of connection? Or are there
other things that
On 07/15/2014 05:47 PM, Milos Kozak wrote:
Hi,
Yesterday I was gonna to replicate the error, but I didnt managed to
do it, so I started to wonder whether it wasnt bad call..
I read the following links, so I would like to ask :D Does it mean,
that this bug is caused by very fast recovery of
Hello Vishwanath
thank you for your quick reply but i have a follow up question if it is
ok... Maybe a different issue and i should open a new thread, but i will
try to continue to use this one...
So I followed the new documentation... let me show you what i have done
and what is the final
I read your answer, but I dont know how how to create my RPM files,
because I dont want to install it right to the system.. Is there any manual?
On 7/15/2014 8:34 AM, Ravishankar N wrote:
On 07/15/2014 05:47 PM, Milos Kozak wrote:
Hi,
Yesterday I was gonna to replicate the error, but I didnt
On 07/15/2014 06:39 PM, Milos Kozak wrote:
I read your answer, but I dont know how how to create my RPM files,
because I dont want to install it right to the system.. Is there any
manual?
http://www.gluster.org/community/documentation/index.php/CompilingRPMS
Compile the release-3.5 branch.
The latency is quite high for synchronous replication. For
geo-replication, this latency value is sustainable.
-Vijay
Hi Vijay,
Do you think 15-20ms is OK for synchronous?
Thanks.
Hello,
I would love to have that answer too... I'm now on a link with a latency
below 9ms.
On 15/07/14 18:13, Stefan Moravcik wrote:
Hello Vishwanath
thank you for your quick reply but i have a follow up question if it
is ok... Maybe a different issue and i should open a new thread, but i
will try to continue to use this one...
So I followed the new documentation... let me show
On 07/15/2014 06:24 AM, Franco Broi wrote:
I think the option I need is noac.
noac is no-attribute-caching in NFS. By default, NFS client would cache
the meta-data/attributes of FILEs for 3 seconds and directory for 30
seconds (default value). NFS client revalidates the attr cache by
On Wed, 2014-07-16 at 08:32 +0530, Santosh Pradhan wrote:
On 07/15/2014 06:24 AM, Franco Broi wrote:
I think the option I need is noac.
noac is no-attribute-caching in NFS. By default, NFS client would cache
the meta-data/attributes of FILEs for 3 seconds and directory for 30
seconds
On 07/16/2014 08:41 AM, Franco Broi wrote:
On Wed, 2014-07-16 at 08:32 +0530, Santosh Pradhan wrote:
On 07/15/2014 06:24 AM, Franco Broi wrote:
I think the option I need is noac.
noac is no-attribute-caching in NFS. By default, NFS client would cache
the meta-data/attributes of FILEs for 3
On Tuesday 15 July 2014 01:57 PM, David Raffelt wrote:
Hi Raghavendra,
Thanks for looking into this. Attached are the log files from the 3
peers. The glusterfs server is running on Beauty. All 3 peers mount
the native gluster client on /home. Each peer has a direct connection
to each other,
13 matches
Mail list logo
