[Gluster-users] Limit of Glusterfs help

eagleeyes eagleeyes at 126.com
Wed Jun 24 07:10:25 UTC 2009


HI:
    Was there  a limit of servers which was used as storage in Gluster ?


2009-06-24 



eagleeyes 



发件人: gluster-users-request 
发送时间: 2009-06-24  03:00:42 
收件人: gluster-users 
抄送: 
主题: Gluster-users Digest, Vol 14, Issue 34 
Send Gluster-users mailing list submissions to
gluster-users at gluster.org
To subscribe or unsubscribe via the World Wide Web, visit
http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
or, via email, send a message with subject or body 'help' to
gluster-users-request at gluster.org
You can reach the person managing the list at
gluster-users-owner at gluster.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gluster-users digest..."
Today's Topics:
   1. Re: bailout after period of inactivity (mki-glusterfs at mozone.net)
   2. AFR problem (maurizio oggiano)
----------------------------------------------------------------------
Message: 1
Date: Tue, 23 Jun 2009 05:48:11 -0700
From: mki-glusterfs at mozone.net
Subject: Re: [Gluster-users] bailout after period of inactivity
To: Vikas Gorur <vikas at gluster.com>
Cc: gluster-users at gluster.org
Message-ID: <20090623124811.GL3330 at cyclonus.mozone.net>
Content-Type: text/plain; charset=us-ascii
On Tue, Jun 23, 2009 at 07:22:31AM -0500, Vikas Gorur wrote:
> > So there is a timeout, but whatever the cause is, it's triggered by
> > long term inactivity. We never had any network problems.
> > 
> > Other machines that access the filesystem on a regular basis do not
> > show this problem. It's only the machine that get's used once in a while.
> > The problem is reproducable, not a one time event.
>  
> Thanks everyone for the reports. We will try to reproduce this and resolve
> the issue.
Perhaps adding SO_KEEPALIVE may help maintain the socket connection in the
event that there's some form of tcp session timeout happening on the
network and/or router (such as in the case of NAT)?
Just a thought.
Mohan
------------------------------
Message: 2
Date: Tue, 23 Jun 2009 16:50:10 +0200
From: maurizio oggiano <oggiano.maurizio at gmail.com>
Subject: [Gluster-users] AFR problem
To: gluster-users at gluster.org
Message-ID:
<b251017f0906230750m747c8f0er9bc4e7968dd98f11 at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
I all,
I have some problem with automatic file translator ( afr). I have two server
A e B. Both servers have afr client configured.
If I stop one server, for example B, The file system managed from AFR is not
available for 30 sec in the server A.
 Below there is the gluster-client.vol of one of the server.
  volume TSU-1.localdomain-disk
          type protocol/client
          option transport-type tcp/client
          option remote-host 127.0.0.1
          option remote-subvolume disk
  end-volume
  volume TSU-2.localdomain-disk
          type protocol/client
          option transport-type tcp/client
          option remote-host 10.1.48.51
          option remote-subvolume disk
          option transport-timeout 5
  end-volume
  volume disk-afr
          type cluster/afr
          subvolumes TSU-1.localdomain-disk TSU-2.localdomain-disk
          option favorite-child TSU-1.localdomain-disk
  end-volume
  volume writeback-disk
          type performance/write-behind
          option aggregate-size 131072
          subvolumes disk-afr
  end-volume
  volume readahead-disk
          type performance/read-ahead
          option page-size 65536
          option page-count 16
          subvolumes writeback-disk
  end-volume
the server has the following configuration:
##### Volume #####
  volume local-disk
          type storage/posix
          option directory /glusterfs/shared
  end-volume
  volume disk
          type features/posix-locks
          subvolumes local-disk
  end-volume
##### Access Control #####
  volume server
          type protocol/server
          option transport-type tcp/server
          subvolumes disk
          option auth.ip.disk.allow *
  end-volume
Is there a way to avoid this behaviour?
Thanks
Maurizio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://zresearch.com/pipermail/gluster-users/attachments/20090623/23246bef/attachment.html>
------------------------------
_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org
http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
End of Gluster-users Digest, Vol 14, Issue 34
*********************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20090624/537f491a/attachment.html>


More information about the Gluster-users mailing list