TransportClient and its limited libraries

Elastic Stack Elasticsearch
1

Hi there,

as current elasticsearch allows one to use plugins in the transport client,
i just tried with the fst plugin, but failed somewhat.

I am getting tons of guice errors for missing implementations, among them

  • ClusterService
  • NodeService
  • IndicesService
  • FsProbe
  • NetworkProbe
  • ProcessProbe

When looking at the initialization of the TransportClient it looks to me,
that it is simply more lightweight than a node and does not start tons of
services.

What is the proposed solution for this? Should I split my fst suggester
package in some client/serveer manner? Or am I doing something stupid when
initializing my actions?
The initializaton can be seen here
https://github.com/spinscale/elasticsearch-suggest-plugin/blob/master/src/main/java/org/elasticsearch/module/suggest/SuggestModule.java

Thanks for any help!

Regards, Alexander

--

2

Hi Alexander,

TransportClient is now dependent on the Lucene jar(s) - I stumbled upon
this before CompressorFactory forces inclusion of lucene jars to TransportClient applications · Issue #2091 · elastic/elasticsearch · GitHub
This might be the cause for the injection errors, but I'm not sure.
Hopefully including the Lucene jars will fix the injection issues.

Best regards,

Jörg

On Tuesday, August 21, 2012 9:31:27 AM UTC+2, Alexander Reelsen wrote:

Hi there,

as current elasticsearch allows one to use plugins in the transport
client, i just tried with the fst plugin, but failed somewhat.

I am getting tons of guice errors for missing implementations, among them

  • ClusterService
  • NodeService
  • IndicesService
  • FsProbe
  • NetworkProbe
  • ProcessProbe

When looking at the initialization of the TransportClient it looks to me,
that it is simply more lightweight than a node and does not start tons of
services.

What is the proposed solution for this? Should I split my fst suggester
package in some client/serveer manner? Or am I doing something stupid when
initializing my actions?
The initializaton can be seen here
https://github.com/spinscale/elasticsearch-suggest-plugin/blob/master/src/main/java/org/elasticsearch/module/suggest/SuggestModule.java

Thanks for any help!

Regards, Alexander

--

3

Hey Jörg,

On Tue, Aug 21, 2012 at 4:18 PM, Jörg Prante joergprante@gmail.com wrote:

TransportClient is now dependent on the Lucene jar(s) - I stumbled upon
this before CompressorFactory forces inclusion of lucene jars to TransportClient applications · Issue #2091 · elastic/elasticsearch · GitHub
This might be the cause for the injection errors, but I'm not sure.
Hopefully including the Lucene jars will fix the injection issues.

Nope, they were already included. Because of the Exception due to missing
Probes I was thinking the sigar libs were missing, but as this happens when
I try to add the (suggest) actions to the client (which of course does not
need them as it is a client not a server) the problem occurs.

--Alexander

--