Is there any update on this ?
Regards
Rafi KC
On 12/24/2016 03:53 PM, yonex wrote:
> Rafi,
>
> Thanks again. I will try that and get back to you.
>
> Regards.
>
>
> 2016-12-23 18:03 GMT+09:00 Mohammed Rafi K C :
>> Hi Yonex,
>>
>> As we discussed in irc #gluster-devel , I
Hi Andreas,
By checking the code IMO currently this is limitation with in
FSAL_GLUSTER. It tries to
establish connection with glusterfs servers only using "tcp". It is easy
to fix as well.
You can raise a bug in
https://bugzilla.redhat.com/enter_bug.cgi?product=nfs-ganesha
under
Hi Kevin
Thanks for this. I did some more testing and found that adding a third,
brick-less node didn't really help. I think I need to upgrade to 3.8.x to
get this functionality.
I'll upgrade my test gluster environment and try again.
Thanks
On Fri, Jan 6, 2017 at 6:21 AM, Kevin Lemonnier
Thanks Vijay, good to know.
On 9 January 2017 at 09:59, Vijay Bellur wrote:
>
>
> On Sun, Jan 8, 2017 at 5:29 PM, Lindsay Mathieson
> wrote:
>>
>> On 8/01/2017 10:38 AM, Lindsay Mathieson wrote:
>>>
>>> Option: performance.flush-behind
>>>
On Sun, Jan 8, 2017 at 5:29 PM, Lindsay Mathieson <
lindsay.mathie...@gmail.com> wrote:
> On 8/01/2017 10:38 AM, Lindsay Mathieson wrote:
>
>> Option: performance.flush-behind
>> Default Value: on
>> Description: If this option is set ON, instructs write-behind translator
>> to perform flush in
On 8/01/2017 10:38 AM, Lindsay Mathieson wrote:
Option: performance.flush-behind
Default Value: on
Description: If this option is set ON, instructs write-behind
translator to perform flush in background, by returning success (or
any errors, if any of previous writes were failed) to