[Gluster-devel] requesting review available gluster* plugins in sos

is (as might just be widely known) an extensible, portable, support data collection tool primarily aimed at Linux distributions and other UNIX-like operating systems. At present there are 2 plugins

Re: [Gluster-devel] GlusterFS development Environment-Debug

Hello Rajib, On Mon, Mar 18, 2019 at 1:29 PM Rajib Hossen wrote: > Hello All, > I am new to development of GlusterFS and have some experience in > competitive programming in C. I want to implement systematic code for > erasure coding in glusterfs. I would like to setup debugging environment. I

Re: [Gluster-devel] Different glusterfs clients's data not consistent.

On Mon, Mar 18, 2019 at 1:21 PM 快乐 <994506...@qq.com> wrote: > Three node： node1， node2, node3 > > Steps: > > 1. gluster volume create volume_test node1:/brick1 > 2. gluster volume set volume_test cluster.server-quorum-ratio 51 > 3. gluster volume set volume_test cluster.server-quorum-type

Re: [Gluster-devel] [Gluster-users] "rpc_clnt_ping_timer_expired" errors

Hi Raghavendra, Yes, server.event-thread has been changed from 4 to 8. During last days, I noticed that the error events are still here although they have been considerably reduced. So, I used grep command against the log files in order to provide you a global vision about the warning, error

Re: [Gluster-devel] [Gluster-users] "rpc_clnt_ping_timer_expired" errors

Hi Raghavendra, I just changed the client option value to 8. I will check the volume behaviour during the next hours. The GlusterFS version is 3.12.14. I will provide you the logs as soon as the activity load will be high. Thank you, Mauro > On 14 Mar 2019, at 04:57, Raghavendra Gowdappa

[Gluster-devel] GlusterFS development Environment-Debug

Hello All, I am new to development of GlusterFS and have some experience in competitive programming in C. I want to implement systematic code for erasure coding in glusterfs. I would like to setup debugging environment. I can use gdb or any IDE. So far, I tried with CLion and Visual Studio Code

Re: [Gluster-devel] [Gluster-users] Experiences with FUSE in real world - Presentationat Vault 2019

Thanks, I have nothing in mind - but I know from experience that live sessions are much more interesting and going in deep. Best Regards, Strahil Nikolov On Mar 7, 2019 08:54, Raghavendra Gowdappa wrote: > > Unfortunately, there is no recording. However, we are willing to discuss our >

Re: [Gluster-devel] [Gluster-users] Bitrot: Time of signing depending on the file size???

Hi David, Once after file write completes (fd closed) bitrot process will wait for 120 seconds and if there no fd is opened for the file it will trigger the signer process. considering the signer, process start and end time file read speed was < 250KB/s. To increase bitrot signer read speed

Re: [Gluster-devel] [Gluster-users] Gluster : Improvements on "heal info" command

Hi , This sounds nice. I would like to ask if the order is starting from the local node's bricks first ? (I am talking about --brick=one) Best Regards, Strahil NikolovOn Mar 5, 2019 10:51, Ashish Pandey wrote: > > Hi All, > > We have observed and heard from gluster users about the long time

Re: [Gluster-devel] [Gluster-users] Bitrot: Time of signing depending on the file size???

Hi David, I have also tested the bitrot signature process by default it takes < 250 KB/s. regards Amudhan P On Fri, Mar 1, 2019 at 1:19 PM David Spisla wrote: > Hello folks, > > I did some observations concerning the bitrot daemon. It seems to be that > the bitrot signer is signing files

Re: [Gluster-devel] [Gluster-users] Version uplift query

Hi Poornima, Instead of killing process stopping volume followed by stopping service in nodes and update glusterfs. can't we follow the above step? regards Amudhan On Thu, Feb 28, 2019 at 8:16 AM Poornima Gurusiddaiah wrote: > > > On Wed, Feb 27, 2019, 11:52 PM Ingo Fischer wrote: > >> Hi

[Gluster-devel] Different glusterfs clients's data not consistent.

Three node?? node1?? node2, node3 Steps: 1. gluster volume create volume_test node1:/brick1 2. gluster volume set volume_test cluster.server-quorum-ratio 51 3. gluster volume set volume_test cluster.server-quorum-type server 4. On node1, mount -t glusterfs node1:/volume_test /mnt. 5. On