Re: Elasticsearch facing CorruptIndexException exception with GlusterFs 3.10.1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux