<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 8, 2017 at 1:46 PM, Abhijit Paul <span dir="ltr"><<a href="mailto:er.abhijitpaul@gmail.com" target="_blank">er.abhijitpaul@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><b>@Prasanna & @Pranith & @Keithley </b>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. <div><br></div><div>My hole intention to use this gluster-block solution is to <b>avoid Elasticsearch index health turn RED issue due to CorruptIndex</b> issue by using GlusterFS & FUSE, <b>on this regard if any further pointer or forwards are there will relay appreciate.</b><div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="m_7970649228871898602HOEnZb"><div class="m_7970649228871898602h5"><span class=""><br><br></span></div></div></blockquote></div></div></div></div></div>
<br></blockquote><div><br></div><div>We expect gluster's block interface to not have the same problem as encountered by the file system interface with Elasticsearch. Our limited testing validates that expectation as outlined in Prasanna's blog post.</div><div><br></div><div>Feedback from your testing would be very welcome! Please feel free to let us know if you require any help in getting the deployment working.</div><div><br></div><div>Thanks!</div><div>Vijay</div><div> </div></div><br></div></div>