Unassigned shards after node close

android · April 14, 2012, 10:17pm

I have 6 indices, running 3 clusters. each index has 1 shard. there are total of 10k documents, and total of 20mb.

I index those documents using JAVA API in a process, and during indexing and querying everything works fine. But if I terminate that process after all the indexing and searching is done, some nodes go unassigned and cluster health goes red.
If I let the process keep up and running, nodes are all assigned and cluster health is green.

What could be the reason for that?

Rafal_Kuc_3 · April 14, 2012, 10:22pm

Hi,

It seems like you are creating a new node with the Java API and then after
you close that node (terminate the process) your cluster can't locate the
shards. Could you please try initializing Elasticsearch client by using:

Node node = nodeBuilder().client(true).node();

Or you can also use the TransportClient.

--
Regards,
Rafał Kuć
Sematext :: http://sematext.com/

W dniu niedziela, 15 kwietnia 2012 00:17:20 UTC+2 użytkownik Orcun Simsek
napisał:

I have 6 indices, running 3 clusters. each index has 1 shard. there are
total
of 10k documents, and total of 20mb.

I index those documents using JAVA API in a process, and during indexing
and
querying everything works fine. But if I terminate that process after all
the indexing and searching is done, some nodes go unassigned and cluster
health goes red.
If I let the process keep up and running, nodes are all assigned and
cluster
health is green.

What could be the reason for that?

--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/unassigned-shards-after-node-close-tp3910996p3910996.html
Sent from the Elasticsearch Users mailing list archive at Nabble.com.

android · April 14, 2012, 11:57pm

Initializing with client set to true worked! Thanks!

android · April 15, 2012, 3:40pm

Now, if i set the node using client = true, i get failed to find analyzer exception in an analyze, which is not being thrown if i dont set client true.

gist.github.com

https://gist.github.com/ortschun/2393383

builder.java

BufferedReader reader = new BufferedReader(new FileReader("ESSettings"));
StringBuilder builder = new StringBuilder();
String line;
while((line = reader.readLine()) != null){
    builder.append(line);
}
settings = ImmutableSettings.settingsBuilder().loadFromSource(builder.toString()).put(settingsMap).build();
n = NodeBuilder.nodeBuilder().settings(settings).client(true).build().start();
c = n.client();
AnalyzeResponse rsvp = c.admin().indices().prepareAnalyze("THIS IS A123 45 t-0 133[orcun] TEST").setIndex("c").setField("store").execute().actionGet();

essettings.json

"index":{
        "number_of_shards":1,
        "number_of_replicas":0,
        "analysis":{
            "tokenizer":{
                "standard":{
                    "type":"standard"
                },
                "whitespace":{
                    "type":"whitespace"

This file has been truncated. show original

kimchy · April 17, 2012, 10:32am

Are you sure the client gets connected to the cluster?

On Sun, Apr 15, 2012 at 6:40 PM, android orcunsimsek@gmail.com wrote:

Now, if i set the node using client = true, i get failed to find analyzer
exception in an analyze, which is not being thrown if i dont set client
true.

builder.java · GitHub

--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/unassigned-shards-after-node-close-tp3910996p3912124.html
Sent from the Elasticsearch Users mailing list archive at Nabble.com.