Hi Steven,

Graylog2 0.91.1 simply isn't compatible with newer Elasticsearch versions.

You have to upgrade Graylog first. 
See 
http://docs.graylog.org/en/2.1/pages/configuration/elasticsearch.html#elasticsearch-versions
 
for a compatibility table of Elasticsearch versions.

Cheers,
Jochen

On Friday, 4 November 2016 17:00:31 UTC+1, Steven Cherry wrote:
>
> Hi All,
>
> Some background first. 
>
> We're using currently using Graylog 0.91.1 in our production environments. 
> A while back (over a year ago) I tested later versions of Graylog in our 
> non-production environments. This required me to upgrade ES from 1.3.4 to 
> 1.7.2 in the non-production environments. As it turned out the testing 
> didn't go well so we decided to stay at Graylog version 0.91.1. I didn't 
> downgrade ES in the non-production environments as it seemed to be working 
> well at the later version plus, doing so would have caused data loss since 
> indexes created in ES version 1.7.2 are not compatible with 1.3.4. The 
> upgraded ES continued to perform well in non production environments so I 
> decided to upgrade production ES to version 1.7.2. It all went well and ES 
> is performing as expected. Now for the problem, I need to introduce a new 
> Graylog server cluster node into our production cluster. From what I can 
> conclude, the Graylog cluster node registers with ES upon it's first 
> connection as an ES client node. The new Grayloy server node is refusing to 
> do this as it's insisting on ES version 1.3.4 where as we are using 1.7.2. 
> Where as Graylog nodes introduced pre ES upgrade are fine. I'm unable to 
> downgrade ES without data loss. Any suggestions?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/3162d896-0356-44f7-b223-40af8bb8dd7b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to