Re: [Gluster-users] Elasticsearch facing CorruptIndexException exception with GlusterFs 3.10.1

On Mon, May 8, 2017 at 1:46 PM, Abhijit Paul wrote: > *@Prasanna & @Pranith & @Keithley *Thank you very much for this update, > let me try out this with build frm src and then use with Elasticsearch in > kubernetes environment, i will let you know the update. > > My

Re: [Gluster-users] Elasticsearch facing CorruptIndexException exception with GlusterFs 3.10.1

On 05/08/2017 05:32 AM, Pranith Kumar Karampuri wrote: Abhijit, We released gluster-block v0.2 just this Friday for which RHEL packages are yet to be built. +Kaleb, Could you help with this please? Prasanna, Could you let Abhijit know the rpm versions for tcmu-runner

Re: [Gluster-users] Elasticsearch facing CorruptIndexException exception with GlusterFs 3.10.1

Abhijit, We released gluster-block v0.2 just this Friday for which RHEL packages are yet to be built. +Kaleb, Could you help with this please? Prasanna, Could you let Abhijit know the rpm versions for tcmu-runner and other packages so that this feature can be used? On Mon,

Re: [Gluster-users] Elasticsearch facing CorruptIndexException exception with GlusterFs 3.10.1

Wait, wait we are discussing this issue only. Expect a reply in some time :-) On Mon, May 8, 2017 at 2:19 PM, Abhijit Paul wrote: > poking for previous mail reply > > On Sun, May 7, 2017 at 1:06 AM, Abhijit Paul > wrote: > >>

Re: [Gluster-users] Elasticsearch facing CorruptIndexException exception with GlusterFs 3.10.1

poking for previous mail reply On Sun, May 7, 2017 at 1:06 AM, Abhijit Paul wrote: > https://pkalever.wordpress.com/2017/03/14/elasticsearch-wit > h-gluster-block/ > here used tested environment is Fedora , > but i am using RHEL based Oracle linux so does

Re: [Gluster-users] Elasticsearch facing CorruptIndexException exception with GlusterFs 3.10.1

https://pkalever.wordpress.com/2017/03/14/elasticsearch-with-gluster-block/ here used tested environment is Fedora , but i am using RHEL based Oracle linux so does gluster-block compatible with RHEL as well? What i needs to change & make it work? On Fri, May 5, 2017 at 5:42 PM, Pranith Kumar

Re: [Gluster-users] Elasticsearch facing CorruptIndexException exception with GlusterFs 3.10.1

On Fri, May 5, 2017 at 5:40 PM, Pranith Kumar Karampuri wrote: > > > On Fri, May 5, 2017 at 5:36 PM, Abhijit Paul > wrote: > >> So should i start using gluster-block with elasticsearch in kubernetes >> environment? >> >> My expectation from

Re: [Gluster-users] Elasticsearch facing CorruptIndexException exception with GlusterFs 3.10.1

On Fri, May 5, 2017 at 5:36 PM, Abhijit Paul wrote: > So should i start using gluster-block with elasticsearch in kubernetes > environment? > > My expectation from gluster-block is, it should not CorruptIndex > of elasticsearch...and issue facing in previous mails. > >

Re: [Gluster-users] Elasticsearch facing CorruptIndexException exception with GlusterFs 3.10.1

So should i start using gluster-block with elasticsearch in kubernetes environment? My expectation from gluster-block is, it should not CorruptIndex of elasticsearch...and issue facing in previous mails. Please let me know whether should i processed with above mentioned combination. On Fri, May

Re: [Gluster-users] Elasticsearch facing CorruptIndexException exception with GlusterFs 3.10.1

thanks Krutika for the alternative. @*Prasanna @**Pranith* I 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

Re: [Gluster-users] Elasticsearch facing CorruptIndexException exception with GlusterFs 3.10.1

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

Re: [Gluster-users] Elasticsearch facing CorruptIndexException exception with GlusterFs 3.10.1

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

Re: [Gluster-users] Elasticsearch facing CorruptIndexException exception with GlusterFs 3.10.1

On Thu, May 4, 2017 at 10:41 PM, Abhijit Paul wrote: > Since i am new to gluster, can please provide how to turn off/disable "perf > xlator options"? > > $ gluster volume set performance.stat-prefetch off $ gluster volume set performance.read-ahead off $ gluster

Re: [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 > wrote: > >> I think there is still some pending stuffs in some of the gluster perf >> xlators to make that work complete. Cced the

Re: [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 wrote: > I think there is still some pending stuffs in some of the gluster perf > xlators to make that work complete. Cced the

Re: [Gluster-users] Elasticsearch facing CorruptIndexException exception with GlusterFs 3.10.1

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

[Gluster-users] Elasticsearch facing CorruptIndexException exception with GlusterFs 3.10.1

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 (