[Bugs] [Bug 1390050] Elasticsearch get CorruptIndexException errors when running with GlusterFS persistent storage

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1390050

kcao22003 at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|needinfo?(kcao22003 at gmail.c |
                   |om)                         |



--- Comment #40 from kcao22003 at gmail.com ---
(In reply to Raghavendra G from comment #38)
> (In reply to kcao22003 from comment #37)
> > Hello,
> > 
> > According to this bug report, this issue was already fixed in Gluster
> > version glusterfs-3.11.0. However, we are currently using version Gluster
> > 4.1.0 and still having the same issue. 
> > 
> > Does anyone run into this same problem with Gluster version above 3.11.0?
> 
> We found some new issues later wrt to this use-case. Currently we are
> working on fixes. Is it possible to share your testcase (with complete
> instructions to setup elasticsearch and the test case that fails) so that
> it'll help us to validate our fixes wrt your usecase?

We are using GlusterFS as a storage service for our Kubernetes cluster:
https://github.com/gluster/gluster-kubernetes. For Elasticsearch, we are
launching ES cluster as a Kubernetes StatefulSet and deploying using a Helm
chart: https://github.com/clockworksoul/helm-elasticsearch.  We still run into
this issue with the latest version for glusterfs: (4.1.4) and ElasticSearch
(v6.2.3).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=EfrNoImb7K&a=cc_unsubscribe