Hi,
I had a look at the bt:
(gdb) bt
#0 0x7f8a40d4c175 in dict_unserialize (orig_buf=0x243e840 "", size=504,
fill=0x7fffe8386aa8) at
/home/jenkins/root/workspace/rackspace-regression-2GB-triggered/libglusterfs/src/dict.c:2692
#1 0x7f8a2f580f73 in server_setvolume (req=0x7f8a2efeeb58)
All,
It would be really helpful to hear some feedback on this proposal. It is
important
that we solve Glusterd's configuration replication problem at scale. Getting
this
right would help us be better prepared for the kind of changes planned for
GlusterFS 4.0.
thanks,
kp
- Original Message
Hi Siva,
On 11/22/2014 08:44 AM, Rudra Siva wrote:
Thanks for the response. In my case, I am trying to avoid doing the
network level lookup - since I use the same resolve only pass a null
for the attribute structure - essentially in my case, it is an atomic
multiple object read/write so I only w
