Abhijit Paul
2017-May-04 08:59 UTC
[Gluster-users] Elasticsearch facing CorruptIndexException exception with GlusterFs 3.10.1
Since i am new to gluster, can please provide how to turn off/disable "perf xlator options"? On Wed, May 3, 2017 at 8:51 PM, Atin Mukherjee <amukherj at redhat.com> 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 at gmail.com> > 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 at gluster.org >> http://lists.gluster.org/mailman/listinfo/gluster-users >> > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20170504/abe52c41/attachment.html>
Abhijit Paul
2017-May-04 17:11 UTC
[Gluster-users] Elasticsearch facing CorruptIndexException exception with GlusterFs 3.10.1
Since i am new to gluster, can please provide how to turn off/disable "perf xlator options"?> On Wed, May 3, 2017 at 8:51 PM, Atin Mukherjee <amukherj at redhat.com> > 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 at gmail.com> >> 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 at gluster.org >>> http://lists.gluster.org/mailman/listinfo/gluster-users >>> >> >> >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20170504/fc713681/attachment.html>