On 10/07/2013 06:26, Greg Scott wrote:
Bummer. Looks like I'm on my own with this one.
I'm afraid this is the problem with gluster: everything works great on
the happy path, but as soon as anything goes wrong, you're stuffed.
There is neither recovery procedure documentation, nor detailled
internals documentation (so you could work out for yourself what is
going on and fix it). In my opinion, gluster is unsupportable in its
current form.
For this reason I have recently stripped gluster out of a production
network. We're back to using simple NFSv4 at the moment. At some point I
will be evaluating ceph and maybe swift.
As you've observed, there's little point in having "resilient" copies of
data if they are not retrievable in error scenarios.
Regards,
Brian.
_______________________________________________
Gluster-users mailing list
[email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-users
