Re: replace-brick failing - transport.address-family not specified

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 12/08/2013 07:06 PM, Nguyen Viet Cuong wrote:
Thanks for sharing.

Btw, I do believe that GlusterFS 3.2.x is much more stable than 3.4.x in
production.


This is quite contrary to what we have seen in the community. From a development perspective too, we feel much better about 3.4.1. Are there specific instances that worked well with 3.2.x which does not work fine for you in 3.4.x?

Cheers,
Vijay






_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users




[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux