Abhijit we just started making the efforts to get all of this stable.
On Fri, May 5, 2017 at 4:45 PM, Abhijit Paul <er.abhijitpaul@xxxxxxxxx> wrote:
I yet to try gluster-block with elasticsearch...but carious to know does this combination plays well in kubernetes environment?On Fri, May 5, 2017 at 12:14 PM, Abhijit Paul <er.abhijitpaul@xxxxxxxxx> wrote:thanks Krutika for the alternative.@Prasanna @PranithI was going thorough the mentioned blog post and saw that used tested environment was Fedora ,but i am using RHEL based Oracle linux so does gluster-block compatible with RHEL as well?On Fri, May 5, 2017 at 12:03 PM, Krutika Dhananjay <kdhananj@xxxxxxxxxx> wrote:-KrutikaAdding Prasanna and Pranith who worked on this, in case you need more info on this.Here's a blog post on the same - https://pkalever.wordpress.comAlternatively you can give gluster-block + elasticsearch a try, which doesn't require solving all these caching issues.Yeah, there are a couple of cache consistency issues with performance translators that are causing these exceptions.Some of them were fixed by 3.10.1. Some still remain./2017/03/14/elasticsearch-with -gluster-block/ On Fri, May 5, 2017 at 12:15 AM, Abhijit Paul <er.abhijitpaul@xxxxxxxxx> wrote:Thanks for the reply, i will try it out but i am also facing one more issue "i.e. replicated volumes returning different timestamps"so is this because of Bug 1426548 - Openshift Logging ElasticSearch FSLocks when using GlusterFS storage backend ?FYI i am using glusterfs 3.10.1 tar.gzRegards,AbhijitOn Thu, May 4, 2017 at 10:58 PM, Amar Tumballi <atumball@xxxxxxxxxx> wrote:On Thu, May 4, 2017 at 10:41 PM, Abhijit Paul <er.abhijitpaul@xxxxxxxxx> wrote:Since i am new to gluster, can please provide how to turn off/disable "perf xlator options"?$ gluster volume set <volname> performance.quick-read off$ gluster volume set <volname> performance.stat-prefetch off$ gluster volume set <volname> performance.io-cache off
$ gluster volume set <volname> performance.read-ahead off
$ gluster volume set <volname> performance.write-behind offRegards,AmarOn Wed, May 3, 2017 at 8:51 PM, Atin Mukherjee <amukherj@xxxxxxxxxx> wrote:I think there is still some pending stuffs in some of the gluster perf xlators to make that work complete. Cced the relevant folks for more information. Can you please turn off all the perf xlator options as a work around to move forward?On Wed, May 3, 2017 at 8:04 PM, Abhijit Paul <er.abhijitpaul@xxxxxxxxx> wrote:______________________________Dear folks,I setup Glusterfs(3.10.1) NFS type as persistence volume for Elasticsearch(5.1.2) but currently facing issue with "CorruptIndexException" with Elasticseach logs and due to that index health trued RED in Elasticsearch.Later found that there was an issue with gluster < 3.10 (https://bugzilla.redhat.com/show_bug.cgi?id=1390050 ) but even after upgrading to 3.10.1 issue is still there.So curios to know what would be the root cause to fix this issue.Regards,Abhijit_________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
--Amar Tumballi (amarts)
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
--
Pranith
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
