search for: krutika

...sharded volume. This is unfortunately likely with sharding because the optimizations eager-locking and delayed post-op will now only be applicable on a per-shard basis. Larger the shard size, the better, to work around this issue. Meanwhile, let me think about how we can get this fixed in code. -Krutika On Mon, Jul 10, 2017 at 7:59 PM, <gencer at gencgiyen.com> wrote: > Hi Krutika, > > > > May I kindly ping to you and ask that If you have any idea yet or figured > out whats the issue may? > > > > I am awaiting your reply with four eyes :) > > > >...

Hi Krutika, I also did one more test. I re-created another volume (single volume. Old one destroyed-deleted) then do 2 dd tests. One for 1GB other for 2GB. Both are 32MB shard and eager-lock off. Samples: sr:~# gluster volume profile testvol start Starting volume profile on testvol has been succe...

Hi Krutika, May I kindly ping to you and ask that If you have any idea yet or figured out whats the issue may? I am awaiting your reply with four eyes :) Apologies for the ping :) -Gencer. From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of...

Ki Krutika, After that setting: $ dd if=/dev/zero of=/mnt/ddfile bs=1G count=1 1+0 records in 1+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 11.7351 s, 91.5 MB/s $ dd if=/dev/zero of=/mnt/ddfile2 bs=2G count=1 0+1 records in 0+1 records out 2147479552 bytes (2.1 GB, 2.0 GiB) copi...

Thanks. I think reusing the same volume was the cause of lack of IO distribution. The latest profile output looks much more realistic and in line with i would expect. Let me analyse the numbers a bit and get back. -Krutika On Tue, Jul 4, 2017 at 12:55 PM, <gencer at gencgiyen.com> wrote: > Hi Krutika, > > > > Thank you so much for myour reply. Let me answer all: > > > > 1. I have no idea why it did not get distributed over all bricks. > 2. Hm.. This is really weird. > &g...

Krutika, I?m sorry I forgot to add logs. I attached them now. Thanks, Gencer. From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of gencer at gencgiyen.com Sent: Thursday, July 6, 2017 10:27 AM To: 'Krutika Dhananjay' <kdhananj at re...

What if you disabled eager lock and run your test again on the sharded configuration along with the profile output? # gluster volume set <VOL> cluster.eager-lock off -Krutika On Tue, Jul 4, 2017 at 9:03 PM, Krutika Dhananjay <kdhananj at redhat.com> wrote: > Thanks. I think reusing the same volume was the cause of lack of IO > distribution. > The latest profile output looks much more realistic and in line with i > would expect. > > Let me analy...

Great news. Is this planned to be published in next release? Il 29 mag 2017 3:27 PM, "Krutika Dhananjay" <kdhananj at redhat.com> ha scritto: > Thanks for that update. Very happy to hear it ran fine without any issues. > :) > > Yeah so you can ignore those 'No such file or directory' errors. They > represent a transient state where DHT in the client proces...

Great, thanks! Il 5 giu 2017 6:49 AM, "Krutika Dhananjay" <kdhananj at redhat.com> ha scritto: > The fixes are already available in 3.10.2, 3.8.12 and 3.11.0 > > -Krutika > > On Sun, Jun 4, 2017 at 5:30 PM, Gandalf Corvotempesta < > gandalf.corvotempesta at gmail.com> wrote: > >> Great news. >>...

The fixes are already available in 3.10.2, 3.8.12 and 3.11.0 -Krutika On Sun, Jun 4, 2017 at 5:30 PM, Gandalf Corvotempesta < gandalf.corvotempesta at gmail.com> wrote: > Great news. > Is this planned to be published in next release? > > Il 29 mag 2017 3:27 PM, "Krutika Dhananjay" <kdhananj at redhat.com> ha > scritto: > >...

Great to hear! ----- Original Message ----- > From: "Abi Askushi" <rightkicktech at gmail.com> > To: "Krutika Dhananjay" <kdhananj at redhat.com> > Cc: "gluster-user" <gluster-users at gluster.org> > Sent: Friday, September 8, 2017 7:01:00 PM > Subject: Re: [Gluster-users] Slow performance of gluster volume > > Following changes resolved the perf issue: > >...

----- Original Message ----- > From: "Abi Askushi" <rightkicktech at gmail.com> > To: "Ben Turner" <bturner at redhat.com> > Cc: "Krutika Dhananjay" <kdhananj at redhat.com>, "gluster-user" <gluster-users at gluster.org> > Sent: Monday, September 11, 2017 1:40:42 AM > Subject: Re: [Gluster-users] Slow performance of gluster volume > > Did not upgrade yet gluster. I am still using 3.8.12. Only...

...er: invalid argument: client [Invalid argument] Do I need to upgrade all nodes before I attempt to start the gluster services? I reverted the first node back to 3.8 at the moment and all restored. Also tests with eager lock disabled did not make any difference. On Wed, Sep 6, 2017 at 11:15 AM, Krutika Dhananjay <kdhananj at redhat.com> wrote: > Do you see any improvement with 3.11.1 as that has a patch that improves > perf for this kind of a workload > > Also, could you disable eager-lock and check if that helps? I see that max > time is being spent in acquiring locks. >...

...olume info` outputs to eliminate any confusion? * If there's just one volume, are you taking care to remove all data from the mount point of this volume before converting it? * What is the size the test file grew to? * These attached profiles are against dd runs? Or the file download test? -Krutika On Mon, Jul 3, 2017 at 8:42 PM, <gencer at gencgiyen.com> wrote: > Hi Krutika, > > > > Have you be able to look out my profiles? Do you have any clue, idea or > suggestion? > > > > Thanks, > > -Gencer > > > > *From:* Krutika Dhananjay [mailt...

Hi Krutika, Is it anything in the profile indicating what is causing this bottleneck? In case i can collect any other info let me know. Thanx On Sep 5, 2017 13:27, "Abi Askushi" <rightkicktech at gmail.com> wrote: Hi Krutika, Attached the profile stats. I enabled profiling then ran some d...

...gt;> Any update about multiple bugs regarding data corruptions with >> sharding enabled ? >> >> Is 3.12.1 ready to be used in production? >> > > Most issues have been fixed but there appears to be one more race for > which the patch is being worked on. > > @Krutika, is that correct? > > > That is my understanding too, yes, in light of the discussion that happened at https://bugzilla.redhat.com/show_bug.cgi?id=1465123 -Krutika > Thanks, > Nithya > > > > >> _______________________________________________ >> Gluster-user...

...d you see such performance boost? I will try to upgrade and check difference also. On Sep 11, 2017 2:45 AM, "Ben Turner" <bturner at redhat.com> wrote: Great to hear! ----- Original Message ----- > From: "Abi Askushi" <rightkicktech at gmail.com> > To: "Krutika Dhananjay" <kdhananj at redhat.com> > Cc: "gluster-user" <gluster-users at gluster.org> > Sent: Friday, September 8, 2017 7:01:00 PM > Subject: Re: [Gluster-users] Slow performance of gluster volume > > Following changes resolved the perf issue: > > A...

Do you see any improvement with 3.11.1 as that has a patch that improves perf for this kind of a workload Also, could you disable eager-lock and check if that helps? I see that max time is being spent in acquiring locks. -Krutika On Wed, Sep 6, 2017 at 1:38 PM, Abi Askushi <rightkicktech at gmail.com> wrote: > Hi Krutika, > > Is it anything in the profile indicating what is causing this bottleneck? > In case i can collect any other info let me know. > > Thanx > > On Sep 5, 2017 13:27, "A...

...change? Thank you. On Mon, Sep 11, 2017 at 9:55 AM, Ben Turner <bturner at redhat.com> wrote: > ----- Original Message ----- > > From: "Abi Askushi" <rightkicktech at gmail.com> > > To: "Ben Turner" <bturner at redhat.com> > > Cc: "Krutika Dhananjay" <kdhananj at redhat.com>, "gluster-user" < > gluster-users at gluster.org> > > Sent: Monday, September 11, 2017 1:40:42 AM > > Subject: Re: [Gluster-users] Slow performance of gluster volume > > > > Did not upgrade yet gluster. I am s...

Hi Krutika, Thank you so much for myour reply. Let me answer all: 1. I have no idea why it did not get distributed over all bricks. 2. Hm.. This is really weird. And others; No. I use only one volume. When I tested sharded and striped volumes, I manually stopped volume, deleted volume, purged...