search for: hekaf

...s is sufficient to cause the corruption problem. The good news is that we think both of these problems got fixed in 3.4.1. So why are we leaving? In trying to figure out what was going on with our GlusterFS system after the disastrous rebalance, we ran across two posts. The first one was http://hekafs.org/index.php/2012/03/glusterfs-algorithms-distribution/. If we understand it correctly, anytime you add new storage servers to your cluster, you have to do a rebalance and that rebalance will require a minimum of 50% of the data in the cluster to be moved to make the hashing algorithms work. Th...

Hello, Thanks to "partner" on IRC who told me about this (quite big) problem. Apparently in a distributed setup once a brick fills up you start getting write failures. Is there a way to work around this? I would have thought gluster would check for free space before writing to a brick. It's very easy to test, I created a distributed volume from 2 uneven bricks and started to

Hi all, I am having problems with painfully slow directory listings on a freshly created replicated volume. The configuration is as follows: 2 nodes with 3 replicated drives each. The total volume capacity is 5.6T. We would like to expand the storage capacity much more, but first we need to figure this problem out. Soon after loading up about 100 MB of small files (about 300kb each), the

Hi, We have a cluster with 130 compute nodes with an NAS-type central storage under gluster (3 bricks, ~50TB). When we run large number of ocean models we can run into bottlenecks with many jobs trying to write to our central storage. It was suggested to us that we could also used gluster to unite the disks on the compute nodes into a single "disk" in which files would be written

Hi everyone, I have seen in (GlusterFS 3.3) the gluster cli a eager locking option (cluster.eager-lock) and there is no reference to this option in the documentation. Is it in relation with this post http://hekafs.org/index.php/2012/03/glusterfs-algorithms-replication-future/ ? Enabling this option seems to boost write performance but is it without danger ? Thx Anthony Garnier -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/...

...s you can create. If you?ve ever wondered what the difference between replicated and distributed volumes is in GlusterFS, or how they?re related, you?ll like this recent post<http://community.gluster.org/p/how-are-distribution-and-replication-related/> by Jeff Darcy<http://pl.atyp.us/>, HekaFS<http://cloudfs.org/> creator * TheStraightTech: GlusterFS Over NFS, Virtual IP Migration, and Replication<http://www.gluster.com/2011/09/26/thestraighttech-glusterfs-over-nfs-virtual-ip-migration-and-replication/> Monday, September 26th, 2011 Community linchpin Jjulian<http://com...

Hi there, This is a hypothetical problem, not one that describes specific hardware at the moment. As we all know, gluster currently usually works best when each brick is the same size, and each host has the same number of bricks. Let's call this a "homogeneous" configuration. Suppose you buy the hardware to build such a pool. Two years go by, and you want to grow the pool. Changes

Hi! I just gave GlusterFS a try and experienced two problems. First some background: - I want to set up a file server with synchronous replication between branch offices, similar to Windows DFS-Replication. The goal is _not_ high-availability or cluster-scaleout, but just having all files locally available at each branch office. - To test GlusterFS, I installed two virtual machines