On Tue, Nov 8, 2016 at 8:10 AM, Ravishankar N wrote:
> So there is a class of bugs* in exposed in replicate volumes where if the
> only good copy of the file is down, we still end up serving stale data to
> the application because of caching
> in various layers outside
On 11/08/2016 06:30 AM, Shyam wrote:
> On 11/08/2016 08:10 AM, Ravishankar N wrote:
>> So there is a class of bugs* in exposed in replicate volumes where if
>> the only good copy of the file is down, we still end up serving stale
>> data to the application because of caching
>> in various layers
On 11/08/2016 08:10 AM, Ravishankar N wrote:
So there is a class of bugs* in exposed in replicate volumes where if
the only good copy of the file is down, we still end up serving stale
data to the application because of caching
in various layers outside gluster. In fuse, this can be mitigated by
So there is a class of bugs* in exposed in replicate volumes where if
the only good copy of the file is down, we still end up serving stale
data to the application because of caching
in various layers outside gluster. In fuse, this can be mitigated by
setting attribute and entry-timeout to zero