search

Norconex / committer-elasticsearch

Implementation of Norconex Committer for Elasticsearch.
https://opensource.norconex.com/committers/elasticsearch/
Apache License 2.0
11 stars 6 forks source link

Issues after revert to elasticsearch 2.4 #13

Closed danizen closed 7 years ago

danizen commented 7 years ago

Having naively made my crawl work with elasticsearch 5.3.1 and norconex-commiter-elasticsearch 3.0.0, I am told that our server is running elasticsearch 2.4.x

I have attempted to back-down to norconex-commiter-elasticsearch 2.1.0, and to override the elasticsearch version to 2.4.5 to get the latest in that vein. However, I'm still using norconex-collector-http version 2.7.0

At the end of the artificially short crawl, I see the exception below.

[2]: index [medlineplus], type [page], id [6c56fd8b-872a-43c7-af54-c60c90f184fd], message 
[RemoteTransportException[[Rebel][127.0.0.1:9300][indices:data/write/bulk[s]]]; nested: 
RemoteTransportException[[Rebel][127.0.0.1:9300][indices:data/write/bulk[s][p]]]; nested: 
UnavailableShardsException[[medlineplus][1] Not enough active copies to meet write consistency of 
[QUORUM] (have 1, needed 2). Timeout: [1m], request: [BulkShardRequest to [medlineplus] containing [3] requests]];]
        at com.norconex.committer.elasticsearch.ElasticsearchCommitter.sendBulkToES(ElasticsearchCommitter.java:335)
...

I appreciate any help you can provide in addressing this issue.

danizen commented 7 years ago

I'm going to close this. I believe this has to do with elasticsearch configuration. After setting up a second node on the same host, cluster status is green. I just have to get the index status to be green, and then I'm fine.