Jörg Prante

You can not run the Knapsack plugin at transport client side. It must run at server side in a node being part of the cluster.

You are using a wrong Elasticsearch / Knapsack version combination.

Knapsack uses indexed data from cluster nodes, it is an internal export/import cluster service. Because TransportClient does not hold any cluster service, this combination is not possible.

The correct ones from the README of course. Example: Elasticsearch 1.5.2 with Knapsack 1.5.2.0

Shield is not supported, sorry. It is not open source.

Sure, you have to disable Shield or ask Shield support for a solution.

You seem to have an error in your node setup, maybe you initialized twice. The `getClient()` method makes no sense, there is a node created (and not started) for each...

Version 2.1.0.0 which is compatible to Elasticsearch 2.1.0 just released.

ES 1.x has many bugs regarding shard initialization and the pick up of correct mappings. Please update to ES 2.x+ and post your index settings and mappings (`GET /indexname/_settings` and...

You can set `max_bulk_actions_per_request` knapsack import parameter, default is `1000`, or `max_bulk_concurrency`, default is 2 \* number of CPU cores. The `bytes` is only a counter for statistical purpose.