# Index creation always returns "shards\_acknowledged": false AFTER Elasticsearch5.0 upgrade **URL:** \ **Category:** Elasticsearch\ **Created:** [November 15, 2016, 2:24am UTC](https://discuss.elastic.co/t/index-creation-always-returns-shards-acknowledged-false-after-elasticsearch5-0-upgrade/66041 "2016-11-15T02:24:32Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![purnashree.b](https://avatars.discourse-cdn.com/v4/letter/p/ed8c4c/32.png) [@purnashree.b](https://discuss.elastic.co/u/purnashree.b)\ **Post date:** [November 15, 2016, 2:24am UTC](https://discuss.elastic.co/t/index-creation-always-returns-shards-acknowledged-false-after-elasticsearch5-0-upgrade/66041/1 "2016-11-15T02:24:32Z")
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](http://cluster.name): prod\_elasticsearch path.data: /opt/hsdes/data custom log directory path.logs: /opt/hsdes/logs/${[cluster.name](http://cluster.name)} network.host: _eth0_ http.port: 9200 http.host: _eth0_ script.engine.groovy.inline.aggs: on script.inline: on [node.name](http://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? ---
**Author:** ![purnashree.b](https://avatars.discourse-cdn.com/v4/letter/p/ed8c4c/32.png) [@purnashree.b](https://discuss.elastic.co/u/purnashree.b)\ **Post date:** [November 15, 2016, 2:54am UTC](https://discuss.elastic.co/t/index-creation-always-returns-shards-acknowledged-false-after-elasticsearch5-0-upgrade/66041/2 "2016-11-15T02:54:50Z")
Never mind. I found it to be the issue with the cluster.routing.allocation.enable property which was set to none persistently. Thanks, ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 13, 2016, 2:54am UTC](https://discuss.elastic.co/t/index-creation-always-returns-shards-acknowledged-false-after-elasticsearch5-0-upgrade/66041/3 "2016-12-13T02:54:53Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.