Hi Avati,
Sounds like i'll hold off until it's ready... There was sadly no
debugging information that I could see in the log file, got any times
to get better debugging on this?
Here are my config files:
#### server.vol ##### (the ip's change accoringly for each 4 servers)
volume brick
type storage/posix
option directory /GlusterFS
end-volume
volume brick-afr
type storage/posix
option directory /GlusterFS-AFR
end-volume
volume server
type protocol/server
option transport-type tcp/server
option bind-address 10.175.175.134
option listen-port 6996
subvolumes brick brick-afr
option auth.ip.brick.allow 10.175.175.*
option auth.ip.brick-afr.allow 10.175.175.*
end-volume
#### client.vol ####
volume brick1
type protocol/client
option transport-type tcp/client
option remote-host 10.175.175.134
option remote-port 6996
option remote-subvolume brick
end-volume
volume brick1-afr
type protocol/client
option transport-type tcp/client
option remote-host 10.175.175.135
option remote-port 6996
option remote-subvolume brick-afr
end-volume
volume brick2
type protocol/client
option transport-type tcp/client
option remote-host 10.175.175.135
option remote-port 6996
option remote-subvolume brick
end-volume
volume brick2-afr
type protocol/client
option transport-type tcp/client
option remote-host 10.175.175.136
option remote-port 6996
option remote-subvolume brick-afr
end-volume
volume brick3
type protocol/client
option transport-type tcp/client
option remote-host 10.175.175.136
option remote-port 6996
option remote-subvolume brick
end-volume
volume brick3-afr
type protocol/client
option transport-type tcp/client
option remote-host 10.175.175.137
option remote-port 6996
option remote-subvolume brick-afr
end-volume
volume brick4
type protocol/client
option transport-type tcp/client
option remote-host 10.175.175.137
option remote-port 6996
option remote-subvolume brick
end-volume
volume brick4-afr
type protocol/client
option transport-type tcp/client
option remote-host 10.175.175.134
option remote-port 6996
option remote-subvolume brick-afr
end-volume
volume afr1
type cluster/afr
subvolumes brick1 brick1-afr
option replicate *:2
end-volume
volume afr2
type cluster/afr
subvolumes brick2 brick2-afr
option replicate *:2
end-volume
volume afr3
type cluster/afr
subvolumes brick3 brick3-afr
option replicate *:2
end-volume
volume afr4
type cluster/afr
subvolumes brick4 brick4-afr
option replicate *:2
end-volume
volume unify1
type cluster/unify
subvolumes afr1 afr2 afr3 afr4
option readdir-force-success on
option scheduler rr
option rr.limits.min-free-disk 10GB
end-volume
Pooya
On Apr 24, 2007, at 3:25 AM, Anand Avati wrote:
I might be able to guess at locking issues - PHP locks session files
during access, and removes the lock once the request has finished.
How
well does gluster handle locking ?
posix-locks are not officially *in*. the tla version of posix-locks is
under development and we will make an annuuncement when it is
complete.
my guess too is locking as the io-thread hanging was a known bug.
please use the latest tla for the fix.
avati
--
ultimate_answer_t
deep_thought (void)
{
sleep (years2secs (7500000));
return 42;
}
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx
http://lists.nongnu.org/mailman/listinfo/gluster-devel
