Gluster users - Feb 2009 - cloud config with multiple internal drives

Hi,
I'm trying to come up with a working configuration for some machines as
follows:
- each is a client and a server and can see all the other nodes' storage and
its own
- each has 4 identical hard drives
- replication (one or possibly two replicas)
- high availability (continues to function if one replicated node of a pair goes
down)

It's something like the example configuration with NUFA/unify, but with
replication across nodes and HA too.

Any suggested configuration? Just a general explanation of the setup is fine.
All my efforts so far have resulted in error messages about dht anomalies with
"holes=1, overlaps=1" in the logs. I'm using 2.0.0rc1.

thanks!
Craig
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20090205/23b936f3/attachment.html>

Hi Craig,

please find the comments inlined.

On Fri, Feb 6, 2009 at 8:15 AM, Craig Flockhart
<craig.flockhart at yahoo.com>wrote:
> Hi,
> I'm trying to come up with a working configuration for some machines as
> follows:
> - each is a client and a server and can see all the other nodes'
storage
> and its own
> - each has 4 identical hard drives
> - replication (one or possibly two replicas)
> - high availability (continues to function if one replicated node of a pair
> goes down)
>
Replication implicitly also provides High availability. High availability
may be needed in the presence of replication in any of the following cases:
1. replication is being provided on server side instead of having replicate
on client.
2. each server has multiple network links. High availability is useful in
this scenario if there are any problems in the network, but the server
process keeps running without any problems.

>
> It's something like the example configuration with NUFA/unify, but with
> replication across nodes and HA too.
>
> Any suggested configuration? Just a general explanation of the setup is
> fine.
> All my efforts so far have resulted in error messages about dht anomalies
> with "holes=1, overlaps=1" in the logs. I'm using 2.0.0rc1.
>
An example configuration might be (nufa/unify)->afr->(optional
HA)->client
<->  server

>
> thanks!
> Craig
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
>
>
regards,
-- 
Raghavendra G
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20090209/49365b24/attachment.html>

> I'm trying to come up with a working configuration for some machines as
> follows:
> - each is a client and a server and can see all the other nodes'
storage and
> its own
> - each has 4 identical hard drives
> - replication (one or possibly two replicas)
> - high availability (continues to function if one replicated node of a pair
> goes down)
>
> It's something like the example configuration with NUFA/unify, but with
> replication across nodes and HA too.
>
> Any suggested configuration? Just a general explanation of the setup is
> fine.
> All my efforts so far have resulted in error messages about dht anomalies
> with "holes=1, overlaps=1" in the logs. I'm using 2.0.0rc1.
Is it possible that you were re-using a backend directory which was
once used with another configuration of distribute? Please retry by
using a freshly mkdir'ed export directory in posix.

Avati