On Fri, Sep 6, 2013 at 1:46 AM, Xavier Hernandez wrote:
> Al 04/09/13 18:10, En/na Anand Avati ha escrit:
>
> On Wed, Sep 4, 2013 at 6:37 AM, Xavier Hernandez wrote:
>
>> Al 04/09/13 14:05, En/na Jeff Darcy ha escrit:
>>
>> On 09/04/2013 04:27 AM, Xavier Hernandez wrote:
>>>
I would also li
Good point Amar.. Noted.
Avati
On Fri, Sep 6, 2013 at 1:40 AM, Amar Tumballi wrote:
> One of the other things we missed in this thread is how to handle bugs in
> bugzilla, and who should own the triage for high/urgent priority bugs.
>
> -Amar
>
>
> On Fri, Jul 26, 2013 at 10:56 PM, Anand Avati
On 09/02/2013 10:24 AM, Xavier Hernandez wrote:
* Implement dict_foreach() as a macro (similar to kernel's list_for_each()).
FWIW, a version of dict_foreach_inline is included as part of
http://review.gluster.org/#/c/5846/
I'm certainly not volunteering to convert existing uses of dic
Thanks for the announcement steve ! FYI ~ for those interested, there
are alot of different areas of expertise which can be useful in this
project. I've added a list here:
https://forge.gluster.org/hadoop/pages/HackIdeas . In my view, people from
the Gluster, DevOps, Linux , and MapReduce comm
Al 04/09/13 18:10, En/na Anand Avati ha escrit:
On Wed, Sep 4, 2013 at 6:37 AM, Xavier Hernandez
mailto:xhernan...@datalab.es>> wrote:
Al 04/09/13 14:05, En/na Jeff Darcy ha escrit:
On 09/04/2013 04:27 AM, Xavier Hernandez wrote:
I would also like to note that each nod
One of the other things we missed in this thread is how to handle bugs in
bugzilla, and who should own the triage for high/urgent priority bugs.
-Amar
On Fri, Jul 26, 2013 at 10:56 PM, Anand Avati wrote:
> Hello everyone,
>
> We are in the process of formalizing the governance model of the
>
+1
On Thu, Sep 5, 2013 at 4:18 PM, Anand Avati wrote:
>
> On Thu, Sep 5, 2013 at 2:53 PM, Stephen Watt wrote:
>
>> Hi Folks
>>
>> We are pleased to announce a major update to the glusterfs-hadoop project
>> with the release of version 2.1. The glusterfs-hadoop project, available at
>> The glus
> > >
> > > Introduce a key in xdata "force-open" in open fop and if that
> > > key is set, make open-behind to not to delay open.
> > >
> > > But the problem is syncop_open () does not send any dictionary (it
> > > will be NULL). We can make open-behind
> > > check whet
It is cleaner to implement it as a separate fop. The complexity of
overloading writev() is unnecessary. There would be a whole bunch of new
if/else condititions to be introduced in existing code, and modules like
write-behind, stripe etc. where special action is taken in multiple places
based on si
