[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gluster-devel
Subject:    [Gluster-devel] Evergrowing distributed volume question
From:       nux () li ! nux ! ro
Date:       2021-03-19 15:32:51
Message-ID: 6d84e82a46dd0e57c8844c12e06d5a95 () li ! nux ! ro
[Download RAW message or body]

Hello,

A while ago I attempted and failed to maintain an "evergrowing" storage 
solution based on GlusterFS.
I was relying on a distributed non-replicated volume to host backups and 
so on, in the idea that when it was close to full I would just add 
another brick (server) and keep it going like that.
In reality what happened was that many of the writes were distributed to 
the brick that was (in time) full, ending up with "out of space" errors, 
despite having one or more bricks with plenty of space.

Can anyone advise whether current Glusterfs behaviour has improved in 
this regard, ie does it check if a brick is full and redirect the 
"write" to one that is not?

Regards,
Lucian
-------

Community Meeting Calendar:
Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://meet.google.com/cpu-eiue-hvk

Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel

[prev in list] [next in list] [prev in thread] [next in thread]