search for: 104255

...inet addr:x.x.x.x Bcast:x.x.x.x Mask:x.x.x.x UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1166 errors:0 dropped:0 overruns:0 frame:0 TX packets:268 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:104255 (101.8 Kb) TX bytes:19936 (19.4 Kb) Interrupt:5 Base address:0x2000 I wounder about RX bytes and TX bytes, what does it mean, how does it collect its data How often does it zero the counters, every boot, hour or somethings else?. Is the information reliable Thanks Tronn -----------...

...c in syncenv_task () from /usr/lib64/libglusterfs.so.0 #2 0x00007f414634d9f0 in syncenv_processor () from /usr/lib64/libglusterfs.so.0 #3 0x0000003d99c07aa1 in start_thread () from /lib64/libpthread.so.0 #4 0x0000003d998e8bbd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f413aa48700 (LWP 104255)): #0 0x0000003d99c0b68c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f413befb99b in hooks_worker () from /usr/lib64/glusterfs/3.10.5/xlator/mgmt/glusterd.so #2 0x0000003d99c07aa1 in start_thread () from /lib64/libpthread.so.0 #3 0x0000003d998e8bbd in clone () from...

.../usr/lib64/libglusterfs.so.0 > #2 0x00007f414634d9f0 in syncenv_processor () from > /usr/lib64/libglusterfs.so.0 > #3 0x0000003d99c07aa1 in start_thread () from /lib64/libpthread.so.0 > #4 0x0000003d998e8bbd in clone () from /lib64/libc.so.6 > Thread 3 (Thread 0x7f413aa48700 (LWP 104255)): > #0 0x0000003d99c0b68c in pthread_cond_wait@@GLIBC_2.3.2 () from > /lib64/libpthread.so.0 > #1 0x00007f413befb99b in hooks_worker () from > /usr/lib64/glusterfs/3.10.5/xlator/mgmt/glusterd.so > #2 0x0000003d99c07aa1 in start_thread () from /lib64/libpthread.so.0 > #3 0x000...

On Mon, 4 Sep 2017 at 20:04, Serkan ?oban <cobanserkan at gmail.com> wrote: > I have been using a 60 server 1560 brick 3.7.11 cluster without > problems for 1 years. I did not see this problem with it. > Note that this problem does not happen when I install packages & start > glusterd & peer probe and create the volumes. But after glusterd > restart. > > Also

Help please- I am running 3.3.1 on Centos using a 10GB network. I get reasonable write speeds, although I think they could be faster. But my read speeds are REALLY slow. Executive summary: On gluster client- Writes average about 700-800MB/s Reads average about 70-80MB/s On server- Writes average about 1-1.5GB/s Reads average about 2-3GB/s Any thoughts? Here are some additional details: