Re: Upgrading to Elasticsearch 5.6
We do not have support for ES 6.x yet. Metron's current supported/tested
version is 5.6.2. Some users have reported success with 5.6.8 as well,
though the reason we're specific about the patch version at this point is
because we are still relying on the TransportClient for connecting to ES.
There is some work underway to move towards the newer REST client and I'll
likely be testing against 6.x to kick the tires there as well. In
the meantime, the challenge of the dependency on the TC for connections is
that ES also uses this for their internal process communications. And
they've basically said that minor/patch versions will likely have breaking
changes in them. So the client we bundle for 5.6.2 might not work on other
5.x installations due to the variability of the API. Once the shift to REST
occurs, there should be more stable support for incremental ES versions in
Metron.
On Fri, Oct 5, 2018 at 11:05 AM Farrukh Naveed Anjum <
anjum.farr...@gmail.com> wrote:
> I am trying to upgrade to 0.6, hope it support ES 6 ? Documentation is
> still older on 0.4.1
>
> Can you please confirm is 0.6 Release has updated drivers ? for
> Elasticsearch or its still using legacy 2.4 ?
>
> On Wed, Oct 3, 2018 at 7:46 PM Vets, Laurens wrote:
>
>> Did you upgrade Metron?
>>
>> On 02-Oct-18 23:50, Farrukh Naveed Anjum wrote:
>> > I upgraded Elasticsearch to 5.6, I also made upgrade in templates.
>> >
>> > But My Elasticsearch logs keeps sayings.
>> >
>> > java.lang.IllegalStateException: Received message from unsupported
>> > version: [2.0.0] minimal compatible version is: [5.0.0]
>> >
>> >
>> >
>> > and Storm Indexing Topology Says
>> >
>> > NoNodeAvailableException[None of the configured nodes are available:
>> > [{#transport#-1}{127.0.0.1}{cogito/127.0.0.1:9300}]] at
>> >
>> org.elasticsearch.client.transport.TransportClientNodesService.ensureNodes
>> >
>> >
>> >
>> >
>> > Any idea how to resolve this ?
>> >
>> > --
>> > With Regards
>> > Farrukh Naveed Anjum
>>
>
>
> --
> With Regards
> Farrukh Naveed Anjum
>
Re: Upgrading to Elasticsearch 5.6
Hi Farrukh,
I can only confirm that ES 5.6 works with Metron 0.6.0 as that's what
I'm currently using.
Hopefully someone else on the list can confirm whether ES 6 works...
Kind regards,
Laurens
On 2018-10-05 10:05, Farrukh Naveed Anjum wrote:
> I am trying to upgrade to 0.6, hope it support ES 6 ? Documentation is still
> older on 0.4.1
>
> Can you please confirm is 0.6 Release has updated drivers ? for Elasticsearch
> or its still using legacy 2.4 ?
>
> On Wed, Oct 3, 2018 at 7:46 PM Vets, Laurens wrote:
>
>> Did you upgrade Metron?
>>
>> On 02-Oct-18 23:50, Farrukh Naveed Anjum wrote:
>>> I upgraded Elasticsearch to 5.6, I also made upgrade in templates.
>>>
>>> But My Elasticsearch logs keeps sayings.
>>>
>>> java.lang.IllegalStateException: Received message from unsupported
>>> version: [2.0.0] minimal compatible version is: [5.0.0]
>>>
>>>
>>>
>>> and Storm Indexing Topology Says
>>>
>>> NoNodeAvailableException[None of the configured nodes are available:
>>> [{#transport#-1}{127.0.0.1}{cogito/127.0.0.1:9300}]] at
>>> org.elasticsearch.client.transport.TransportClientNodesService.ensureNodes
>>>
>>>
>>>
>>>
>>> Any idea how to resolve this ?
>>>
>>> --
>>> With Regards
>>> Farrukh Naveed Anjum
>
> --
> With Regards
> Farrukh Naveed Anjum
Re: Upgrading to Elasticsearch 5.6
I am trying to upgrade to 0.6, hope it support ES 6 ? Documentation is
still older on 0.4.1
Can you please confirm is 0.6 Release has updated drivers ? for
Elasticsearch or its still using legacy 2.4 ?
On Wed, Oct 3, 2018 at 7:46 PM Vets, Laurens wrote:
> Did you upgrade Metron?
>
> On 02-Oct-18 23:50, Farrukh Naveed Anjum wrote:
> > I upgraded Elasticsearch to 5.6, I also made upgrade in templates.
> >
> > But My Elasticsearch logs keeps sayings.
> >
> > java.lang.IllegalStateException: Received message from unsupported
> > version: [2.0.0] minimal compatible version is: [5.0.0]
> >
> >
> >
> > and Storm Indexing Topology Says
> >
> > NoNodeAvailableException[None of the configured nodes are available:
> > [{#transport#-1}{127.0.0.1}{cogito/127.0.0.1:9300}]] at
> >
> org.elasticsearch.client.transport.TransportClientNodesService.ensureNodes
> >
> >
> >
> >
> > Any idea how to resolve this ?
> >
> > --
> > With Regards
> > Farrukh Naveed Anjum
>
--
With Regards
Farrukh Naveed Anjum
