Re: [Gluster-devel] Disperse volume : Sequential Writes

2017-07-05 Thread Pranith Kumar Karampuri
>> >> *From: *"Pranith Kumar Karampuri" > <mailto:pkara...@redhat.com>> >> *To: *"Xavier Hernandez" > <mailto:xhernan...@datalab.es>> >> *Cc: *"Ashish Pandey" > <ma

Re: [Gluster-devel] Disperse volume : Sequential Writes

2017-07-04 Thread Xavier Hernandez
quot; mailto:xhernan...@datalab.es>> *Cc: *"Ashish Pandey" mailto:aspan...@redhat.com>>, "Gluster Devel" mailto:gluster-devel@gluster.org>> *Sent: *Friday, June 16, 2017 3:50:09 PM *Subject: *Re: [Gluster-devel] Disperse volume : Sequential Writes

Re: [Gluster-devel] Disperse volume : Sequential Writes

2017-07-03 Thread Ashish Pandey
ay, July 3, 2017 9:05:54 AM Subject: Re: [Gluster-devel] Disperse volume : Sequential Writes Ashish, Xavi, I think it is better to implement this change as a separate read-after-write caching xlator which we can load between EC and client xlator. That way EC will not get a lot more functionality than

Re: [Gluster-devel] Disperse volume : Sequential Writes

2017-07-02 Thread Pranith Kumar Karampuri
ot; , "Gluster Devel" < > gluster-devel@gluster.org> > *Sent: *Friday, June 16, 2017 3:50:09 PM > *Subject: *Re: [Gluster-devel] Disperse volume : Sequential Writes > > > > > On Fri, Jun 16, 2017 at 3:12 PM, Xavier Hernandez > wrote: > >> On

Re: [Gluster-devel] Disperse volume : Sequential Writes

2017-06-16 Thread Ashish Pandey
I think it should be done as we have agreement on basic design. - Original Message - From: "Pranith Kumar Karampuri" To: "Xavier Hernandez" Cc: "Ashish Pandey" , "Gluster Devel" Sent: Friday, June 16, 2017 3:50:09 PM Subject: Re: [Glu

Re: [Gluster-devel] Disperse volume : Sequential Writes

2017-06-16 Thread Pranith Kumar Karampuri
On Fri, Jun 16, 2017 at 3:12 PM, Xavier Hernandez wrote: > On 16/06/17 10:51, Pranith Kumar Karampuri wrote: > >> >> >> On Fri, Jun 16, 2017 at 12:02 PM, Xavier Hernandez >> mailto:xhernan...@datalab.es>> wrote: >> >> On 15/06/17 11:50, Pranith Kumar Karampuri wrote: >> >> >> >> On Th

Re: [Gluster-devel] Disperse volume : Sequential Writes

2017-06-16 Thread Xavier Hernandez
On 16/06/17 10:51, Pranith Kumar Karampuri wrote: On Fri, Jun 16, 2017 at 12:02 PM, Xavier Hernandez mailto:xhernan...@datalab.es>> wrote: On 15/06/17 11:50, Pranith Kumar Karampuri wrote: On Thu, Jun 15, 2017 at 11:51 AM, Ashish Pandey mailto:aspan...@redhat.com>

Re: [Gluster-devel] Disperse volume : Sequential Writes

2017-06-16 Thread Pranith Kumar Karampuri
On Fri, Jun 16, 2017 at 12:02 PM, Xavier Hernandez wrote: > On 15/06/17 11:50, Pranith Kumar Karampuri wrote: > >> >> >> On Thu, Jun 15, 2017 at 11:51 AM, Ashish Pandey > > wrote: >> >> Hi All, >> >> We have been facing some issues in disperse (EC) volume. >>

Re: [Gluster-devel] Disperse volume : Sequential Writes

2017-06-15 Thread Xavier Hernandez
On 15/06/17 11:50, Pranith Kumar Karampuri wrote: On Thu, Jun 15, 2017 at 11:51 AM, Ashish Pandey mailto:aspan...@redhat.com>> wrote: Hi All, We have been facing some issues in disperse (EC) volume. We know that currently EC is not good for random IO as it requires READ-MODIFY

Re: [Gluster-devel] Disperse volume : Sequential Writes

2017-06-15 Thread Pranith Kumar Karampuri
On Thu, Jun 15, 2017 at 11:51 AM, Ashish Pandey wrote: > Hi All, > > We have been facing some issues in disperse (EC) volume. > We know that currently EC is not good for random IO as it requires > READ-MODIFY-WRITE fop > cycle if an offset and offset+length falls in the middle of strip size. > >

[Gluster-devel] Disperse volume : Sequential Writes

2017-06-14 Thread Ashish Pandey
Hi All, We have been facing some issues in disperse (EC) volume. We know that currently EC is not good for random IO as it requires READ-MODIFY-WRITE fop cycle if an offset and offset+length falls in the middle of strip size. Unfortunately, it could also happen with sequential writes. Consi