search for: glusterd_store_retrieve_volumes

Hi,we have use glusterfs for two years. After upgraded to 3.2.5,we discover that when one of replicate node reboot and startup the glusterd daemon,the gluster will crash cause by the other replicate node cpu usage reach 100%. Our gluster info: Type: Distributed-Replicate Status: Started Number of Bricks: 5 x 2 = 10 Transport-type: tcp Options Reconfigured: performance.cache-size: 3GB

Hello all. I have a working replica 2 cluster (4 nodes) up and running happily over Amazon EC2. My end goal is to create AMIs of each machine and then quickly reproduce the same, but new, cluster from those AMIs. Essentially, I'd like a cluster "template". -Assigned original instances' Elastic IPs to new machines to reduce resolution issues. -Passwordless SSH works on initial

...store_update_volinfo] 0-management: Failed to get next store iter [2017-05-06 03:33:39.827563] E [MSGID: 106207] [glusterd-store.c:2844:glusterd_store_retrieve_volume] 0-management: Failed to update volinfo for c_glusterfs volume [2017-05-06 03:33:39.827625] E [MSGID: 106201] [glusterd-store.c:3042:glusterd_store_retrieve_volumes] 0-management: Unable to restore volume: c_glusterfs [2017-05-06 03:33:39.827722] E [MSGID: 101019] [xlator.c:428:xlator_init] 0-management: Initialization of volume 'management' failed, review your volfile again [2017-05-06 03:33:39.827762] E [graph.c:322:glusterfs_graph_init] 0-management...

I am trying to run GlusterFS on only my internal interfaces. I have setup two bricks and have a replicated volume that is started. Everything works fine when I run with no transport.socket.bind-address defined in the /etc/glusterfs/glusterd.vol file, but when I add it I get: Transport endpoint is not connected My configuration looks like this: volume management type mgmt/glusterd

...c:2844:glusterd_store_retrieve_volume] > > >>>>>>>> 0-management: Failed to update volinfo for c_glusterfs volume > > >>>>>>>> [2017-05-06 03:33:39.827625] E [MSGID: 106201] > > >>>>>>>> [glusterd-store.c:3042:glusterd_store_retrieve_volumes] > > >>>>>>>> 0-management: Unable to restore volume: c_glusterfs > > >>>>>>>> [2017-05-06 03:33:39.827722] E [MSGID: 101019] > > >>>>>>>> [xlator.c:428:xlator_init] 0-management: Initialization of > volume...

..._store_retrieve_volume] > > > >>>>>>>> 0-management: Failed to update volinfo for c_glusterfs volume > > > >>>>>>>> [2017-05-06 03:33:39.827625] E [MSGID: 106201] > > > >>>>>>>> [glusterd-store.c:3042:glusterd_store_retrieve_volumes] > > > >>>>>>>> 0-management: Unable to restore volume: c_glusterfs > > > >>>>>>>> [2017-05-06 03:33:39.827722] E [MSGID: 101019] > > > >>>>>>>> [xlator.c:428:xlator_init] 0-management: Initialization...

I'm hoping that someone here can point me the right direction to help me solve a problem I am having. I've got 3 gluster peers and for some reason glusterd sill not start on one of them. All are running glusterfs version 3.4.0-8.el6 on Centos 6.4 (2.6.32-358.el6.x86_64). In /var/log/glusterfs/etc-glusterfs-glusterd.vol.log I see this error repeated 36 times (alternating between brick-0

I've run into a problem with Gluster stability with the RDMA transport. Below is a description of the environment, a simple script that can replicate the problem, and log files from my test system. I can work around the problem by using the TCP transport over IPoIB but would like some input onto what may be making the RDMA transport fail in this case. ===== Symptoms ===== - Error from test