[Gluster-users] One big vs. many small

[Tobias Wilken]

Hey all,
at our office we've justed discussed the question: Should we use one big
glusterfs share or makes it more sense to use multilpe small shares.

We are going to use glusterfs on multiple virtual instances which hosts
multiple web applications. So we are thinking of providing for every web
application an own glustershare.
Not every web application is on every virtual instance so the glusterfs will
stay small in number of nodes and data to store.

The problem or question are
 - Does the glusterfs overhead eat my bandwith or the number of started
glusterfs processes eat my memory?
 - How is the performance of write duration and read delay compared in the
two situations?
 - Where are the limitations? (Size of glusterfs GB-TB-PB, number of
mounted/started glusterfs's)

I think it depens heavily on the values:
I think with 5 virtual instances, 5 web applications and 100 MB per
application, you'll say: "Boy, take one "big" share and come back, if you
have real problems" :-)
But whats about 500 virtual instaces, 1500 web applications and 500 GB per
application, or the whole thing multiplied by 10 as often you want.

Does someone has experience with similar "problems" or can give hints, why
to use which configuration?!

Best regards
Tobias Wilken
___
Gluster-users mailing list
Gluster-users@gluster.org
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users

[Gluster-users] Worrying

[Hiren Joshi]

Hello all,
 
I have a 2 servers each exporting 6 bricks. The client mirrors the 2
servers and AFRs the 6 mirrors it creates.
 
Running bonnie, the servers kept dropping (according to gluster logs
they stopped responding to pings in 10 seconds) so I set the ping
timeout to 30 second, now although bonnie runs I still see dropouts in
the log.
 
The worrying thing is that one of the servers is localhost! What's
happening here? I'm frustratingly close to putting this system on our
live network.
 
The log:
[2009-09-03 02:10:01] E
[client-protocol.c:437:client_ping_timer_expired] glust1a_1: Server
127.0.0.1:6996 has not responded in the last 30 seconds, disconnecting.
[2009-09-03 01:10:01] E
[client-protocol.c:437:client_ping_timer_expired] glust1b_1: Server
192.168.4.51:6996 has not responded in the last 30 seconds,
disconnecting.
[2009-09-03 01:10:01] E [saved-frames.c:165:saved_frames_unwind]
glust1a_1: forced unwinding frame type(2) op(PING)
[2009-09-03 01:10:01] E
[client-protocol.c:437:client_ping_timer_expired] glust1a_2: Server
127.0.0.1:6996 has not responded in the last 30 seconds, disconnecting.
[2009-09-03 01:10:01] E
[client-protocol.c:437:client_ping_timer_expired] glust1b_2: Server
192.168.4.51:6996 has not responded in the last 30 seconds,
disconnecting.
[2009-09-03 01:10:01] E
[client-protocol.c:437:client_ping_timer_expired] glust1a_3: Server
127.0.0.1:6996 has not responded in the last 30 seconds, disconnecting.
[2009-09-03 01:10:01] E
[client-protocol.c:437:client_ping_timer_expired] glust1b_3: Server
192.168.4.51:6996 has not responded in the last 30 seconds,
disconnecting.
[2009-09-03 01:10:01] E
[client-protocol.c:437:client_ping_timer_expired] glust1a_5: Server
127.0.0.1:6996 has not responded in the last 30 seconds, disconnecting.
[2009-09-03 01:10:01] E
[client-protocol.c:437:client_ping_timer_expired] glust1b_5: Server
192.168.4.51:6996 has not responded in the last 30 seconds,
disconnecting.
[2009-09-03 01:10:01] E
[client-protocol.c:437:client_ping_timer_expired] glust1a_6: Server
127.0.0.1:6996 has not responded in the last 30 seconds, disconnecting.
[2009-09-03 01:10:01] E
[client-protocol.c:437:client_ping_timer_expired] glust1b_6: Server
192.168.4.51:6996 has not responded in the last 30 seconds,
disconnecting.
[2009-09-03 01:10:01] N [client-protocol.c:6246:notify] glust1a_1:
disconnected
[2009-09-03 01:10:01] E [saved-frames.c:165:saved_frames_unwind]
glust1b_6: forced unwinding frame type(2) op(PING)
[2009-09-03 01:10:01] N [client-protocol.c:6246:notify] glust1b_6:
disconnected
[2009-09-03 01:10:01] E [saved-frames.c:165:saved_frames_unwind]
glust1a_6: forced unwinding frame type(2) op(PING)
[2009-09-03 01:10:01] N [client-protocol.c:6246:notify] glust1a_6:
disconnected
[2009-09-03 01:10:01] E [afr.c:2228:notify] mirror1_6: All subvolumes
are down. Going offline until atleast one of them comes back up.
[2009-09-03 01:10:01] E [saved-frames.c:165:saved_frames_unwind]
glust1b_5: forced unwinding frame type(2) op(PING)
[2009-09-03 01:10:01] N [client-protocol.c:6246:notify] glust1b_5:
disconnected
[2009-09-03 01:10:01] E [saved-frames.c:165:saved_frames_unwind]
glust1a_5: forced unwinding frame type(2) op(PING)
[2009-09-03 01:10:01] N [client-protocol.c:6246:notify] glust1a_5:
disconnected
[2009-09-03 01:10:01] E [afr.c:2228:notify] mirror1_5: All subvolumes
are down. Going offline until atleast one of them comes back up.
[2009-09-03 01:10:01] E [saved-frames.c:165:saved_frames_unwind]
glust1b_3: forced unwinding frame type(2) op(PING)
[2009-09-03 01:10:01] N [client-protocol.c:6246:notify] glust1b_3:
disconnected
[2009-09-03 01:10:01] E [saved-frames.c:165:saved_frames_unwind]
glust1a_3: forced unwinding frame type(2) op(PING)
[2009-09-03 01:10:01] N [client-protocol.c:6246:notify] glust1a_3:
disconnected
[2009-09-03 01:10:01] E [afr.c:2228:notify] mirror1_3: All subvolumes
are down. Going offline until atleast one of them comes back up.
[2009-09-03 01:10:01] E [saved-frames.c:165:saved_frames_unwind]
glust1b_2: forced unwinding frame type(2) op(PING)
[2009-09-03 01:10:01] N [client-protocol.c:6246:notify] glust1b_2:
disconnected
[2009-09-03 01:10:01] E [saved-frames.c:165:saved_frames_unwind]
glust1a_2: forced unwinding frame type(2) op(PING)
[2009-09-03 01:10:01] N [client-protocol.c:6246:notify] glust1a_2:
disconnected
[2009-09-03 01:10:01] E [afr.c:2228:notify] mirror1_2: All subvolumes
are down. Going offline until atleast one of them comes back up.
[2009-09-03 01:10:01] E [saved-frames.c:165:saved_frames_unwind]
glust1b_1: forced unwinding frame type(2) op(PING)
[2009-09-03 01:10:02] N [client-protocol.c:6246:notify] glust1b_1:
disconnected
[2009-09-03 01:10:02] E [afr.c:2228:notify] mirror1_1: All subvolumes
are down. Going offline until atleast one of them comes back up.
[2009-09-03 01:10:31] E
[client-protocol.c:437:client_ping_timer_expired] glust1a_4: Server
127.0.0.1:6996 has not responded in the last 30 seconds, disconnecting.
[2009-09-03 01:10:31] E
[client-protoco