We've decided to delay GCS 0.5 release and postpone by few days (new date :
1st week of Jan) considering (a) most of the team members are out on
holidays (b) some of the critical issues/PRs are yet to be addressed from
[1] .
Regards,
GCS team
[1] https://waffle.io/gluster/gcs?label=GCS%2F0.5
On Mon, Dec 24, 2018 at 3:40 PM Sankarshan Mukhopadhyay <
sankarshan.mukhopadh...@gmail.com> wrote:
> [pulling the conclusions up to enable better in-line]
>
> > Conclusions:
> >
> > We should never have a volume with caching-related xlators disabled. The
> price we pay for it is too high. We
On 12/21/18 6:56 PM, Sankarshan Mukhopadhyay wrote:
On Fri, Dec 21, 2018 at 6:30 PM RAFI KC wrote:
Hi All,
What is the problem?
As of now self-heal client is running as one daemon per node, this means
even if there are multiple volumes, there will only be one self-heal
daemon. So to take
[...truncated 6 lines...]
https://bugzilla.redhat.com/1654778 / build: Please update GlusterFS
documentation to describe how to do a non-root install
https://bugzilla.redhat.com/1660404 / core: Conditional freeing of string after
returning from dict_set_dynstr function
On Fri, Dec 21, 2018 at 6:30 PM RAFI KC wrote:
>
> Hi All,
>
> What is the problem?
> As of now self-heal client is running as one daemon per node, this means
> even if there are multiple volumes, there will only be one self-heal
> daemon. So to take effect of each configuration changes in the
[pulling the conclusions up to enable better in-line]
> Conclusions:
>
> We should never have a volume with caching-related xlators disabled. The
> price we pay for it is too high. We need to make them work consistently and
> aggressively to avoid as many requests as we can.
Are there current
