[Apiman-user] Elastic search upgrade

[Balu S]

Ok, So option 3) is not straightforward. The build fails as there is bunch
of API incompatibility between 1.7 and 2.4 versions. Unless one wiling to
refactor the apiman-es source to use 2.4 API or may be latest 5.2.

I have gone ahead with option 1 and used a separate ES instance running
with 2.4.4 (cannot go higher than this version due to incompatibility with
bundled ES API in apiman) version and it seems fine. Since I'm not worried
about the old indices, this looks like straightforward option.

But if someone want to use old indices, then you may need to dig deeper to
re-index may be (?).

regards
Balu

On Thu, Mar 16, 2017 at 10:06 AM, Balu S <sbalu27 at gmail.com> wrote:

> Hello,
> I'm trying to gather metrics (using Kibana tool) from the ES instance that
> is being used by apiman. But what I found is the ES instance that is
> bundled inside the apiman is 1.7.x version which seems to be too old for
> current trending tools to index upon. Of course we can use old versions of
> those tools, for ex. Kibana 4.1.x version to index and gather metrics. But
> the older version are limited in functionality and I would like to use the
> latest if possible.
>
> Hence I have following options.
>
>   1) Use separate ElasticSearch instance with latest versions and update
> apiman.properties to point to this instance. And with this new version
> instance, I can use the latest tools.
>
>    Question : Do you think the ES API 1.7.x is compatible and write
> indices to ES database running in latest version ?
>
>  2) Migrate the ES indices to new versions. But the below article, clearly
> says that the ES version must be at least 2.4.x for smooth migration using
> their migration tool.
>
> https://www.elastic.co/guide/en/elasticsearch/reference/
> current/reindex-upgrade.html
>
> 3) Upgrade bundled ES API 1.7.x to 5.2.x (latest version) or at least
> 2.4.x version
>
>
> I think it is practical to upgrade bundled ES version to 2.4.x at least
> (if not for latest 5.2.x) just to make it compatible for migrating indices
> easily.
>
> What are your thoughts? I'm happy to see any alternative options other
> than mentioned above. Thanks.
>
> regards
> Balu
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170317/c4c8bd02/attachment.html