[Gluster-users] GlusterFS Storage Interruption at Node Loss

[Nic Seltzer]

Good evening,

Are you familiar with a way to short circuit this intended behavior?

Nic
On Jul 8, 2016 10:16 PM, "Alastair Neil" <ajneil.tech at gmail.com> wrote:

> Nic
>  I believe this is normal expected behaviour.  The network timeout is
> there because it is expensive to tear down the sockets etc. so you only
> want to do it if a node has really failed and not for some transitory
> network blip.
>
> On 8 July 2016 at 20:29, Nic Seltzer <nseltzer at riotgames.com> wrote:
>
>> Hello list!
>>
>> I am experiencing an issue whereby mounted Gluster volumes are being made
>> read-only until the network timeout interval has passed or the node comes
>> back online. I  have reduced the network timeout to one second and was able
>> to reduce the size of the outage window to two seconds. I am curious if
>> anyone else has seen this issue and how they went about resolving it for
>> their implementation. We are using a distributed-replicated volume, but
>> have also tested _just_ replicated volume with the same results. I can
>> provide the gluster volume info if it's helpful, but suffice to say that it
>> is a pretty simple setup.
>>
>> Thanks!
>>
>> --
>> Nic Seltzer
>> Esports Ops Tech | Riot Games
>> Cell: +1.402.431.2642 | NA Summoner: Riot Dankeboop
>> http://www.riotgames.com
>> http://www.leagueoflegends.com
>>
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://www.gluster.org/mailman/listinfo/gluster-users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160708/36924838/attachment.html>