On Tue, Nov 6, 2018 at 9:58 AM Vijay Bellur wrote:
>
>
> On Mon, Nov 5, 2018 at 7:56 PM Raghavendra Gowdappa
> wrote:
>
>> All,
>>
>> There is a patch [1] from Kotresh, which makes ctime generator as default
>> in stack. Currently ctime generator is being recommended only for usecases
>> where c
On Mon, Nov 5, 2018 at 7:56 PM Raghavendra Gowdappa
wrote:
> All,
>
> There is a patch [1] from Kotresh, which makes ctime generator as default
> in stack. Currently ctime generator is being recommended only for usecases
> where ctime is important (like for Elasticsearch). However, a reliable
> (
All,
There is a patch [1] from Kotresh, which makes ctime generator as default
in stack. Currently ctime generator is being recommended only for usecases
where ctime is important (like for Elasticsearch). However, a reliable
(c)(m)time can fix many consistency issues within glusterfs stack too.
Th
On 11/05/2018 08:29 AM, Vijay Bellur wrote:
> Hi All,
>
> I am triaging the open RFEs in bugzilla [1]. Since our new(er) workflow
> involves managing RFEs as github issues, I am considering migrating
> relevant open RFEs from bugzilla to github. Once migrated, a RFE in
> bugzilla would be closed w
Hi All,
I am triaging the open RFEs in bugzilla [1]. Since our new(er) workflow
involves managing RFEs as github issues, I am considering migrating
relevant open RFEs from bugzilla to github. Once migrated, a RFE in
bugzilla would be closed with an appropriate comment. I can also update the
extern
On Mon, Nov 5, 2018 at 8:43 AM Sankarshan Mukhopadhyay <
sankarshan.mukhopadh...@gmail.com> wrote:
> On Mon, Nov 5, 2018 at 8:35 AM Atin Mukherjee wrote:
> >
> > Thank you Rahul for the report. This does help to keep community up to
> date on the effort being put up here and understand where the
Hello folks,
Going to restart gerrit on review.gluster.org for a quick config change in
the next 15 mins. Estimate outage of 5 mins. I'll update this thread when
we're back online
--
nigelb
___
Gluster-devel mailing list
Gluster-devel@gluster.org
https
