<div dir="ltr">So this change of the Gluster Volume Plugin will make it into K8s 1.7 or 1.8. Unfortunately too late for me.<br></div><div dir="ltr"><br></div><div dir="ltr">Does anyone know how to disable performance translators by default?</div><div dir="ltr"><br></div><span>
</span><br><div class="gmail_quote"><div dir="ltr">Raghavendra Talur <<a href="mailto:rtalur@redhat.com">rtalur@redhat.com</a>> schrieb am Mi., 24. Mai 2017, 19:30:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, May 24, 2017 at 4:08 PM, Christopher Schmidt <<a href="mailto:fakod666@gmail.com" target="_blank">fakod666@gmail.com</a>> wrote:<br>
><br>
><br>
> Vijay Bellur <<a href="mailto:vbellur@redhat.com" target="_blank">vbellur@redhat.com</a>> schrieb am Mi., 24. Mai 2017 um 05:53 Uhr:<br>
>><br>
>> On Tue, May 23, 2017 at 1:39 AM, Christopher Schmidt <<a href="mailto:fakod666@gmail.com" target="_blank">fakod666@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>> OK, seems that this works now.<br>
>>><br>
>>> A couple of questions:<br>
>>> - What do you think, are all these options necessary for Kafka?<br>
>><br>
>><br>
>> I am not entirely certain what subset of options will make it work as I do<br>
>> not understand the nature of failure with Kafka and the default gluster<br>
>> configuration. It certainly needs further analysis to identify the list of<br>
>> options necessary. Would it be possible for you to enable one option after<br>
>> the other and determine the configuration that ?<br>
>><br>
>><br>
>>><br>
>>> - You wrote that there have to be kind of application profiles. So to<br>
>>> find out, which set of options work is currently a matter of testing (and<br>
>>> hope)? Or are there any experiences for MongoDB / ProstgreSQL / Zookeeper<br>
>>> etc.?<br>
>><br>
>><br>
>> Application profiles are work in progress. We have a few that are focused<br>
>> on use cases like VM storage, block storage etc. at the moment.<br>
>><br>
>>><br>
>>> - I am using Heketi and Dynamik Storage Provisioning together with<br>
>>> Kubernetes. Can I set this volume options somehow by default or by volume<br>
>>> plugin?<br>
>><br>
>><br>
>><br>
>> Adding Raghavendra and Michael to help address this query.<br>
><br>
><br>
> For me it would be sufficient to disable some (or all) translators, for all<br>
> volumes that'll be created, somewhere here:<br>
> <a href="https://github.com/gluster/gluster-containers/tree/master/CentOS" rel="noreferrer" target="_blank">https://github.com/gluster/gluster-containers/tree/master/CentOS</a><br>
> This is the container used by the GlusterFS DaemonSet for Kubernetes.<br>
<br>
Work is in progress to give such option at volume plugin level. We<br>
currently have a patch[1] in review for Heketi that allows users to<br>
set Gluster options using heketi-cli instead of going into a Gluster<br>
pod. Once this is in, we can add options in storage-class of<br>
Kubernetes that pass down Gluster options for every volume created in<br>
that storage-class.<br>
<br>
[1] <a href="https://github.com/heketi/heketi/pull/751" rel="noreferrer" target="_blank">https://github.com/heketi/heketi/pull/751</a><br>
<br>
Thanks,<br>
Raghavendra Talur<br>
<br>
><br>
>><br>
>><br>
>> -Vijay<br>
>><br>
>><br>
>><br>
>>><br>
>>><br>
>>> Thanks for you help... really appreciated.. Christopher<br>
>>><br>
>>> Vijay Bellur <<a href="mailto:vbellur@redhat.com" target="_blank">vbellur@redhat.com</a>> schrieb am Mo., 22. Mai 2017 um 16:41<br>
>>> Uhr:<br>
>>>><br>
>>>> Looks like a problem with caching. Can you please try by disabling all<br>
>>>> performance translators? The following configuration commands would disable<br>
>>>> performance translators in the gluster client stack:<br>
>>>><br>
>>>> gluster volume set <volname> performance.quick-read off<br>
>>>> gluster volume set <volname> performance.io-cache off<br>
>>>> gluster volume set <volname> performance.write-behind off<br>
>>>> gluster volume set <volname> performance.stat-prefetch off<br>
>>>> gluster volume set <volname> performance.read-ahead off<br>
>>>> gluster volume set <volname> performance.readdir-ahead off<br>
>>>> gluster volume set <volname> performance.open-behind off<br>
>>>> gluster volume set <volname> performance.client-io-threads off<br>
>>>><br>
>>>> Thanks,<br>
>>>> Vijay<br>
>>>><br>
>>>><br>
>>>><br>
>>>> On Mon, May 22, 2017 at 9:46 AM, Christopher Schmidt<br>
>>>> <<a href="mailto:fakod666@gmail.com" target="_blank">fakod666@gmail.com</a>> wrote:<br>
>>>>><br>
>>>>> Hi all,<br>
>>>>><br>
>>>>> has anyone ever successfully deployed a Kafka (Cluster) on GlusterFS<br>
>>>>> volumes?<br>
>>>>><br>
>>>>> I my case it's a Kafka Kubernetes-StatefulSet and a Heketi GlusterFS.<br>
>>>>> Needless to say that I am getting a lot of filesystem related<br>
>>>>> exceptions like this one:<br>
>>>>><br>
>>>>> Failed to read `log header` from file channel<br>
>>>>> `sun.nio.ch.FileChannelImpl@67afa54a`. Expected to read 12 bytes, but<br>
>>>>> reached end of file after reading 0 bytes. Started read from position<br>
>>>>> 123065680.<br>
>>>>><br>
>>>>> I limited the amount of exceptions with the<br>
>>>>> log.flush.interval.messages=1 option, but not all...<br>
>>>>><br>
>>>>> best Christopher<br>
>>>>><br>
>>>>><br>
>>>>> _______________________________________________<br>
>>>>> Gluster-users mailing list<br>
>>>>> <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
>>>>> <a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
>>>><br>
>>>><br>
><br>
</blockquote></div>