Skip to content
This repository has been archived by the owner on Nov 14, 2019. It is now read-only.

RiverWeb-2.4.0-snapshot connectivity issue #131

Open
mykola-shulba opened this issue Sep 5, 2017 · 1 comment
Open

RiverWeb-2.4.0-snapshot connectivity issue #131

mykola-shulba opened this issue Sep 5, 2017 · 1 comment
Labels

Comments

@mykola-shulba
Copy link

I'm trying to connect RiverWeb2.4.0-snapshot (master version) to Elasticsearch >= 2.4.1
and getting this error: riverweb.log

INFO [Asylum] failed to get node info for {#transport#-1}{10.0.2.16}{10.0.2.16:9300}, disconnecting...
RemoteTransportException[[Failed to deserialize response of type [org.elasticsearch.action.admin.cluster.node.liveness.LivenessResponse]]]; nested: TransportSerializationException[Failed to deserialize response
of type [org.elasticsearch.action.admin.cluster.node.liveness.LivenessResponse]]; nested: NoClassDefFoundError[org/apache/lucene/search/suggest/Lookup]; nested: ClassNotFoundException[org.apache.lucene.search.su
ggest.Lookup];
Caused by: TransportSerializationException[Failed to deserialize response of type [org.elasticsearch.action.admin.cluster.node.liveness.LivenessResponse]]; nested: NoClassDefFoundError[org/apache/lucene/search/s
uggest/Lookup]; nested: ClassNotFoundException[org.apache.lucene.search.suggest.Lookup];

With the same configuration and ES 2.4.0 river-Web works perfectly

What the most recent Elasticsearch version River-Web supports?

@marevol
Copy link
Contributor

marevol commented Sep 5, 2017

We have no plan to upgrade riverweb and recommend to use Fess.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants