Index creation always returns "shards_acknowledged": false AFTER Elasticsearch5.0 upgrade


(purnashree.b) #1

Hi,

I upgraded from elasticsearch 2.4 to v 5.0. After which, index creation always turns the cluster state to red and the response says below
{"acknowledged": true,"shards_acknowledged": false}
I send the below settings during index creation
"settings" : {
"number_of_shards" : 1,
"number_of_replicas" : 0,
"index.write.wait_for_active_shards": "1"
}

I am only trying to start a single node cluster for now. elasticsearch.yml is below

cluster.name: prod_elasticsearch
path.data: /opt/hsdes/data
custom log directory
path.logs: /opt/hsdes/logs/${cluster.name}
network.host: eth0
http.port: 9200
http.host: eth0
script.engine.groovy.inline.aggs: on
script.inline: on
node.name: prod_data_1

Log on cluster start is below

[WARN ][o.e.b.JNANatives ] unable to install syscall filter:
java.lang.UnsupportedOperationException: seccomp unavailable: requires kernel 3.5+ with CONFIG_SECCOMP and CONFIG_SECCOMP_FILTER compiled in
at org.elasticsearch.bootstrap.Seccomp.linuxImpl(Seccomp.java:349) ~[elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.bootstrap.Seccomp.init(Seccomp.java:630) ~[elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.bootstrap.JNANatives.trySeccomp(JNANatives.java:215) [elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.bootstrap.Natives.trySeccomp(Natives.java:99) [elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.bootstrap.Bootstrap.initializeNatives(Bootstrap.java:101) [elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:155) [elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:286) [elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:112) [elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:103) [elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.cli.SettingCommand.execute(SettingCommand.java:54) [elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:96) [elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.cli.Command.main(Command.java:62) [elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:80) [elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:73) [elasticsearch-5.0.0.jar:5.0.0]
[INFO ][o.e.n.Node ] [prod_data_1] initializing ...
[INFO ][o.e.e.NodeEnvironment ] [prod_data_1] using [1] data paths, mounts [[/opt/hsdes/data (/dev/sdb1)]], net usable_space [280gb], net total_space [295.2gb], spins? [possibly], types [ext3]
[INFO ][o.e.e.NodeEnvironment ] [prod_data_1] heap size [29.7gb], compressed ordinary object pointers [true]
[INFO ][o.e.n.Node ] [prod_data_1] version[5.0.0], pid[21272], build[253032b/2016-10-26T04:37:51.531Z], OS[Linux/3.0.101-0.7.29.1.9310.1.PTF-default/amd64], JVM[Oracle Corporation/Java HotSpot(TM) 64-Bit Server VM/1.8.0_92/25.92-b14]

[INFO ][n.u.i.PlatformDependent ] Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability.
[INFO ][o.e.t.TransportService ] [prod_data_1] publish_address {X:Y}, bound_addresses{X:Y}
[INFO ][o.e.b.BootstrapCheck ] [prod_data_1] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks
[INFO ][o.e.c.s.ClusterService ] [prod_data_1] new_master {prod_data_1}{qd5LsAdsQCiIjRbOwxSewg}{BBMHDFS0SoSuQAA1VofILg}{Z}{X:Y}, reason: zen-disco-elected-as-master ([0] nodes joined)
[INFO ][o.e.h.HttpServer ] [prod_data_1] publish_address {X:Y}, bound_addresses {X:Y}
[INFO ][o.e.n.Node ] [prod_data_1] started
[INFO ][o.e.c.s.ClusterSettings ] [prod_data_1] updating [cluster.routing.allocation.enable] from [ALL] to [none]
[INFO ][o.e.g.GatewayService ] [prod_data_1] recovered [1] indices into cluster_state
[INFO ][o.e.c.r.a.AllocationService] [prod_data_1] Cluster health status changed from [YELLOW] to [RED] (reason: [shards started [[apiregression][3], [apiregression][0]] ...]).
[INFO ][o.e.c.m.MetaDataCreateIndexService] [prod_data_1] [apiregression] creating index, cause [api], templates [], shards [1]/[0], mappings [type1]
[INFO ][o.e.c.r.a.AllocationService] [prod_data_1] Cluster health status changed from [YELLOW] to [RED] (reason: [index [apiregression] created]).


Can you please help in fixing this issue?


(purnashree.b) #2

Never mind. I found it to be the issue with the cluster.routing.allocation.enable property which was set to none persistently.

Thanks,


(system) #3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.