Re: Elasticsearch facing CorruptIndexException exception with GlusterFs 3.10.1

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

 



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.

Alternatively you can give gluster-block + elasticsearch a try, which doesn't require solving all these caching issues.
Here's a blog post on the same - https://pkalever.wordpress.com/2017/03/14/elasticsearch-with-gluster-block/

Adding Prasanna and Pranith who worked on this, in case you need more info on this.

-Krutika

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"

FYI i am using glusterfs 3.10.1 tar.gz

Regards,
Abhijit



On 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.stat-prefetch off
$ gluster volume set <volname> performance.read-ahead off
$ gluster volume set <volname> performance.write-behind off
$ gluster volume set <volname> performance.io-cache off
$ gluster volume set <volname> performance.quick-read off


Regards,
Amar

On 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

_______________________________________________
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