# New to Elastic Search, I get this exception: org.elasticsearch.action.UnavailableShardsException **URL:** \ **Category:** Elasticsearch\ **Created:** [August 11, 2011, 12:25am UTC](https://discuss.elastic.co/t/new-to-elastic-search-i-get-this-exception-org-elasticsearch-action-unavailableshardsexception/5120 "2011-08-11T00:25:27Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![ogregras](https://avatars.discourse-cdn.com/v4/letter/o/cdc98d/32.png) [@ogregras](https://discuss.elastic.co/u/ogregras)\ **Post date:** [August 11, 2011, 12:25am UTC](https://discuss.elastic.co/t/new-to-elastic-search-i-get-this-exception-org-elasticsearch-action-unavailableshardsexception/5120/1 "2011-08-11T00:25:27Z")
I'm new to Elastic search, the project is fantastic! In fact it works very well most of the time. But once in a while (not sure when exactly) I get this exception: ======================= org.elasticsearch.action.UnavailableShardsException: [autopage][0] [2] shardIt, [0] active : Timeout waiting for [1m], request: index {[XXX][YYY][4], source[{"title":"A title","body":"A body"}]} at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$3.onTimeout(TransportShardReplicationOperationAction.java:419) at org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:305) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) ======================= Things to know: 1. I use Elastic Search as an embeded search server in a Java web application (using the Play framework, but not using the Play Elastic module written by Felipe Oliveira ). 2. I currently don't really need replication. My web application is not critical and I have a way to reindex eveything easily if a problem occures. 3. I want something simple: I start my Java application, it starts the Elastic Search server. No external Elastic server. 4. I would prefere not to use any external .yml configuration file. I'd prefere to set all settings using Java directly. 5. Here's the way I currently start Elastic in my application (thanks to Felipe Oliveira of the Play Elastic Module, I learned a lot from his code): * * * ImmutableSettings.Builder settings = ImmutableSettings.settingsBuilder(); settings.put("client.transport.sniff", true); settings.put("path.home", "/path/to/elastic/home"); // test settings.put("index.number\_of\_replicas", 1); settings.put("action.write\_consistency", "one"); settings.build(); NodeBuilder nb = new NodeBuilder().settings(settings) .local(true) .client(false) .clusterName(clusterName) .data(true); Node node = nb.node(); ## Client client = node.client(); I'm not sure about the "index.number\_of\_replicas" and "action.write\_consistency" settings. I think they may have something to do with my problem (ie: [http://elasticsearch-users.115913.n3.nabble.com/org-elasticsearch-action-UnavailableShardsException-td2210314.html](http://elasticsearch-users.115913.n3.nabble.com/org-elasticsearch-action-UnavailableShardsException-td2210314.html) ) but I don't know what I need to use for those settings. I still have UnavailableShardsExceptions with those current settings (I had the exceptions without them too!). Again, I'm a newbie and I'm still not sure to understand the differences between indices, shards, nodes, etc. What settings would you recommend for my application? Thanks a lot for any help! ---
**Author:** ![OlgaT](https://avatars.discourse-cdn.com/v4/letter/o/fbc32d/32.png) [@OlgaT](https://discuss.elastic.co/u/OlgaT)\ **Post date:** [August 11, 2011, 4:43am UTC](https://discuss.elastic.co/t/new-to-elastic-search-i-get-this-exception-org-elasticsearch-action-unavailableshardsexception/5120/2 "2011-08-11T04:43:11Z")
I have the same problem starting from 0.17.3 version - 0.17.2 it doesn't happen. On Aug 11, 3:25 am, ogregras [ogreg...@gmail.com](mailto:ogreg...@gmail.com) wrote: > I'm new to Elastic search, the project is fantastic! In fact it works very > well most of the time. But once in a while (not sure when exactly) I get > this exception: > > ======================= > > org.elasticsearch.action.UnavailableShardsException: [autopage][0] [2] > shardIt, [0] active : Timeout waiting for [1m], request: index > {[XXX][YYY][4], source[{"title":"A title","body":"A body"}]} > at > org.elasticsearch.action.support.replication.TransportShardReplicationOpera tionAction$AsyncShardOperationAction$3.onTimeout(TransportShardReplicationO perationAction.java:419) > at > org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run( InternalClusterService.java:305) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown > Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) > > ======================= > > Things to know: > > 1. I use Elastic Search as an embeded search server in a Java web > application (using the Play framework, but not using the Play Elastic module > written by Felipe Oliveira ). > > 2. I currently don't really need replication. My web application is not > critical and I have a way to reindex eveything easily if a problem occures. > > 3. I want something simple: I start my Java application, it starts the > Elastic Search server. No external Elastic server. > > 4. I would prefere not to use any external .yml configuration file. I'd > prefere to set all settings using Java directly. > > 5. Here's the way I currently start Elastic in my application (thanks to > Felipe Oliveira of the Play Elastic Module, I learned a lot from his code): > > * * * > > ImmutableSettings.Builder settings = ImmutableSettings.settingsBuilder(); > settings.put("client.transport.sniff", true); > settings.put("path.home", "/path/to/elastic/home"); > > // test > settings.put("index.number\_of\_replicas", 1); > settings.put("action.write\_consistency", "one"); > > settings.build(); > > NodeBuilder nb = new NodeBuilder().settings(settings) > .local(true) > .client(false) > .clusterName(clusterName) > .data(true); > Node node = nb.node(); > > ## Client client = node.client(); > > I'm not sure about the "index.number\_of\_replicas" and > "action.write\_consistency" settings. I think they may have something to do > with my problem (ie:[http://elasticsearch-users.115913.n3.nabble.com/org-elasticsearch-act](http://elasticsearch-users.115913.n3.nabble.com/org-elasticsearch-act)... > ) but I don't know what I need to use for those settings. I still have > UnavailableShardsExceptions with those current settings (I had the > exceptions without them too!). > > Again, I'm a newbie and I'm still not sure to understand the differences > between indices, shards, nodes, etc. > > What settings would you recommend for my application? > > Thanks a lot for any help! ---
**Author:** ![OlgaT](https://avatars.discourse-cdn.com/v4/letter/o/fbc32d/32.png) [@OlgaT](https://discuss.elastic.co/u/OlgaT)\ **Post date:** [August 11, 2011, 7:12am UTC](https://discuss.elastic.co/t/new-to-elastic-search-i-get-this-exception-org-elasticsearch-action-unavailableshardsexception/5120/3 "2011-08-11T07:12:20Z")
Sorry, it happens also in 0.17.2 On Aug 11, 7:43 am, OlgaT [tubm...@gmail.com](mailto:tubm...@gmail.com) wrote: > I have the same problem starting from 0.17.3 version - 0.17.2 it > doesn't happen. > > On Aug 11, 3:25 am, ogregras [ogreg...@gmail.com](mailto:ogreg...@gmail.com) wrote: > > > I'm new to Elastic search, the project is fantastic! In fact it works very > > well most of the time. But once in a while (not sure when exactly) I get > > this exception: > > > ======================= > > > org.elasticsearch.action.UnavailableShardsException: [autopage][0] [2] > > shardIt, [0] active : Timeout waiting for [1m], request: index > > {[XXX][YYY][4], source[{"title":"A title","body":"A body"}]} > > at > > org.elasticsearch.action.support.replication.TransportShardReplicationOpera tionAction$AsyncShardOperationAction$3.onTimeout(TransportShardReplicationO perationAction.java:419) > > at > > org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run( InternalClusterService.java:305) > > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown > > Source) > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > > at java.lang.Thread.run(Unknown Source) > > > ======================= > > > Things to know: > > > 1. I use Elastic Search as an embeded search server in a Java web > > application (using the Play framework, but not using the Play Elastic module > > written by Felipe Oliveira ). > > > 1. I currently don't really need replication. My web application is not > > critical and I have a way to reindex eveything easily if a problem occures. > > > 1. I want something simple: I start my Java application, it starts the > > Elastic Search server. No external Elastic server. > > > 1. I would prefere not to use any external .yml configuration file. I'd > > prefere to set all settings using Java directly. > > > 1. Here's the way I currently start Elastic in my application (thanks to > > Felipe Oliveira of the Play Elastic Module, I learned a lot from his code): > > > * * * > > > > ImmutableSettings.Builder settings = ImmutableSettings.settingsBuilder(); > > settings.put("client.transport.sniff", true); > > settings.put("path.home", "/path/to/elastic/home"); > > > // test > > settings.put("index.number\_of\_replicas", 1); > > settings.put("action.write\_consistency", "one"); > > > settings.build(); > > > NodeBuilder nb = new NodeBuilder().settings(settings) > > .local(true) > > .client(false) > > .clusterName(clusterName) > > .data(true); > > Node node = nb.node(); > > > ## Client client = node.client(); > > > I'm not sure about the "index.number\_of\_replicas" and > > "action.write\_consistency" settings. I think they may have something to do > > with my problem (ie:[http://elasticsearch-users.115913.n3.nabble.com/org-elasticsearch-act](http://elasticsearch-users.115913.n3.nabble.com/org-elasticsearch-act)... > > ) but I don't know what I need to use for those settings. I still have > > UnavailableShardsExceptions with those current settings (I had the > > exceptions without them too!). > > > Again, I'm a newbie and I'm still not sure to understand the differences > > between indices, shards, nodes, etc. > > > What settings would you recommend for my application? > > > Thanks a lot for any help! ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [August 11, 2011, 9:32am UTC](https://discuss.elastic.co/t/new-to-elastic-search-i-get-this-exception-org-elasticsearch-action-unavailableshardsexception/5120/4 "2011-08-11T09:32:26Z")
You don't need to set the write consistency, also, the number of replicas should be 0 since you start just a single node. I would even set the node to be local (no discovery). You don't need to set the path.home setting, you can have it embedded in your app (jar files) and thats it. Regarding the failure, do you get it on startup? I suggest waiting for green health after starting the node, just to wait for it to recover itself if needed. Note, a green health means all shards are allocated, so in your case, make sure to set the number of replicas to 0. Also, if its a single node, you probably don't need the default 5 shards for an index. Here is how you wait for green health: client.admin().cluster().prepareHealth().setWaitForGreenStatus().execute().actionGet(). On Thu, Aug 11, 2011 at 3:25 AM, ogregras [ogregras@gmail.com](mailto:ogregras@gmail.com) wrote: > I'm new to Elastic search, the project is fantastic! In fact it works very > well most of the time. But once in a while (not sure when exactly) I get > this exception: > > ======================= > > org.elasticsearch.action.UnavailableShardsException: [autopage][0] [2] > shardIt, [0] active : Timeout waiting for [1m], request: index > {[XXX][YYY][4], source[{"title":"A title","body":"A body"}]} > at > org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$3.onTimeout(TransportShardReplicationOperationAction.java:419) > at > org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:305) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown > Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) > > ======================= > > Things to know: > > 1. I use Elastic Search as an embeded search server in a Java web > application (using the Play framework, but not using the Play Elastic module > written by Felipe Oliveira ). > > 2. I currently don't really need replication. My web application is not > critical and I have a way to reindex eveything easily if a problem occures. > > 3. I want something simple: I start my Java application, it starts the > Elastic Search server. No external Elastic server. > > 4. I would prefere not to use any external .yml configuration file. I'd > prefere to set all settings using Java directly. > > 5. Here's the way I currently start Elastic in my application (thanks to > Felipe Oliveira of the Play Elastic Module, I learned a lot from his code): > > * * * > > ImmutableSettings.Builder settings = ImmutableSettings.settingsBuilder(); > settings.put("client.transport.sniff", true); > settings.put("path.home", "/path/to/elastic/home"); > > // test > settings.put("index.number\_of\_replicas", 1); > settings.put("action.write\_consistency", "one"); > > settings.build(); > > NodeBuilder nb = new NodeBuilder().settings(settings) > .local(true) > .client(false) > .clusterName(clusterName) > .data(true); > Node node = nb.node(); > > ## Client client = node.client(); > > I'm not sure about the "index.number\_of\_replicas" and > "action.write\_consistency" settings. I think they may have something to do > with my problem (ie: > [http://elasticsearch-users.115913.n3.nabble.com/org-elasticsearch-action-UnavailableShardsException-td2210314.html](http://elasticsearch-users.115913.n3.nabble.com/org-elasticsearch-action-UnavailableShardsException-td2210314.html)) but I don't know what I need to use for those settings. I still have > UnavailableShardsExceptions with those current settings (I had the > exceptions without them too!). > > Again, I'm a newbie and I'm still not sure to understand the differences > between indices, shards, nodes, etc. > > What settings would you recommend for my application? > > Thanks a lot for any help! ---
**Author:** ![ogregras](https://avatars.discourse-cdn.com/v4/letter/o/cdc98d/32.png) [@ogregras](https://discuss.elastic.co/u/ogregras)\ **Post date:** [August 11, 2011, 12:13pm UTC](https://discuss.elastic.co/t/new-to-elastic-search-i-get-this-exception-org-elasticsearch-action-unavailableshardsexception/5120/5 "2011-08-11T12:13:39Z")
OlgaT, Are you then using a version prior to 0.17.2 because of this? Can you confirm this error doesn't occures in prior versions? ---
**Author:** ![ogregras](https://avatars.discourse-cdn.com/v4/letter/o/cdc98d/32.png) [@ogregras](https://discuss.elastic.co/u/ogregras)\ **Post date:** [August 11, 2011, 12:18pm UTC](https://discuss.elastic.co/t/new-to-elastic-search-i-get-this-exception-org-elasticsearch-action-unavailableshardsexception/5120/6 "2011-08-11T12:18:44Z")
Thanks for the help kimchy. So here are my new settings : * * * ## settings.put("index.number\_of\_replicas", 0); settings.put("index.number\_of\_shards", 1); Is that what you suggest? > Here is how you wait for green health: > client.admin().cluster(). > prepareHealth().setWaitForGreenStatus().execute().actionGet(). I'll try that. You way be right and I wasn't waiting enough before using the Node. Weird thing though... I try: * * * ## ClusterHealthResponse healthResponse = client.admin().cluster().prepareHealth().setWaitForGreenStatus().execute().actionGet(); ClusterHealthStatus healthStatus = healthResponse.status(); It returns but the healthStatus is YELLOW, not GREEN. Is that normal? Even if I used setWaitForGreenStatus()? Thanks again for the help. ---
**Author:** ![ogregras](https://avatars.discourse-cdn.com/v4/letter/o/cdc98d/32.png) [@ogregras](https://discuss.elastic.co/u/ogregras)\ **Post date:** [August 11, 2011, 12:36pm UTC](https://discuss.elastic.co/t/new-to-elastic-search-i-get-this-exception-org-elasticsearch-action-unavailableshardsexception/5120/7 "2011-08-11T12:36:54Z")
> It returns but the healthStatus is YELLOW, not GREEN. Is that normal? Even > if I used setWaitForGreenStatus()? Hummm, now it returns GREEN as expected. Maybe I had an hallucination! Anyway, since I deleted all the "data" folder and started from scratch, it seems to be working well now. I just wait for the healthStatus before running any query. I'll let you know if the exception still occures. ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [August 11, 2011, 8:39pm UTC](https://discuss.elastic.co/t/new-to-elastic-search-i-get-this-exception-org-elasticsearch-action-unavailableshardsexception/5120/8 "2011-08-11T20:39:28Z")
Its yellow possibly because the setting for number of replicas was not applied? yellow means all primary shards are allocated, but replicas are not (possibly yet...). On Thu, Aug 11, 2011 at 3:18 PM, ogregras [ogregras@gmail.com](mailto:ogregras@gmail.com) wrote: > Thanks for the help kimchy. > > So here are my new settings : > > * * * > > ## settings.put("index.number\_of\_replicas", 0); settings.put("index.number\_of\_shards", 1); > > Is that what you suggest? > > > Here is how you wait for green health: > > > client.admin().cluster(). > > \*\*\> prepareHealth().\*\*setWaitForGreenStatus().\*\*execute().actionGet(). > > I'll try that. You way be right and I wasn't waiting enough before using > the Node. > > Weird thing though... I try: > > * * * > > ## ClusterHealthResponse healthResponse = client.admin().cluster().prepareHealth().setWaitForGreenStatus().execute().actionGet(); ClusterHealthStatus healthStatus = healthResponse.status(); > > It returns but the healthStatus is YELLOW, not GREEN. Is that normal? Even > if I used setWaitForGreenStatus()? > > Thanks again for the help. ---
**Author:** ![ogregras](https://avatars.discourse-cdn.com/v4/letter/o/cdc98d/32.png) [@ogregras](https://discuss.elastic.co/u/ogregras)\ **Post date:** [August 11, 2011, 9:03pm UTC](https://discuss.elastic.co/t/new-to-elastic-search-i-get-this-exception-org-elasticsearch-action-unavailableshardsexception/5120/9 "2011-08-11T21:03:22Z")
You know better than me! It's just a little bit odd that setWaitFor_Green_Status() returns and the status is not green! ๐Ÿ™‚ But currently everything seems to be running well. So thanks again for the help! ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [August 11, 2011, 9:27pm UTC](https://discuss.elastic.co/t/new-to-elastic-search-i-get-this-exception-org-elasticsearch-action-unavailableshardsexception/5120/10 "2011-08-11T21:27:20Z")
It waits for green status for a timeout, and then returns. It returns what the status is now, and a flag indicating if it timed out. We don't want to block forever ๐Ÿ™‚ On Fri, Aug 12, 2011 at 12:03 AM, ogregras [ogregras@gmail.com](mailto:ogregras@gmail.com) wrote: > You know better than me! > > It's just a little bit odd that setWaitFor_Green_Status() returns and the > status is not green! ๐Ÿ™‚ > > But currently everything seems to be running well. So thanks again for the > help! ---
**Author:** ![Jamshid](https://avatars.discourse-cdn.com/v4/letter/j/ecd19e/32.png) [@Jamshid](https://discuss.elastic.co/u/Jamshid)\ **Post date:** [August 12, 2011, 12:07am UTC](https://discuss.elastic.co/t/new-to-elastic-search-i-get-this-exception-org-elasticsearch-action-unavailableshardsexception/5120/11 "2011-08-12T00:07:13Z")
FYI I'm also seeing UnavailableShardsException with 0.17.4. I did not see it with 0.16.5. I started a test with a clean data directory, single node, created a couple of indexes (one with five shards and another with ten) and verified elasticsearch-head showed all was Yellow (since no replicas). Then I tried adding a document but got that exception: curl -XPUT [http://localhost:9200/five/named/1234](http://localhost:9200/five/named/1234) -d '{"named": {"context": "Domain001/Bucket0001", "name": "File612606243717652", "size": "90803308" }}' {"error":"UnavailableShardsException[[five][3] [3] shardIt, [1] active : Timeout waiting for [1m], request: index {[five][named] [1234], source[{.... So I killed java and restarted, this is all that got logged: ... [2011-08-11 18:48:46,383][INFO][node] [Mantra] {elasticsearch/0.17.4}[14437]: started [2011-08-11 18:48:46,399][INFO][gateway] [Mantra] recovered [2] indices into cluster\_state And now cluster health is stuck in red: curl -XGET '[http://localhost:9200/\_cluster/health](http://localhost:9200/_cluster/health)' {"cluster\_name":"mytest","status":"red","timed\_out":false,"number\_of\_nodes": 1,"number\_of\_data\_nodes":1,"active\_primary\_shards":0,"active\_shards": 0,"relocating\_shards":0,"initializing\_shards":0,"unassigned\_shards": 45} Same problem after another restart. Btw elasticsearch-head shows 3 (why not 2?) replicas, all Unassigned. Any ideas? --Jamshid On Aug 11, 4:27 pm, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > It waits for green status for a timeout, and then returns. It returns what > the status is now, and a flag indicating if it timed out. We don't want to > block forever ๐Ÿ™‚ > > On Fri, Aug 12, 2011 at 12:03 AM, ogregras [ogreg...@gmail.com](mailto:ogreg...@gmail.com) wrote: > > > You know better than me! > > > It's just a little bit odd that setWaitFor_Green_Status() returns and the > > status is not green! ๐Ÿ™‚ > > > But currently everything seems to be running well. So thanks again for the > > help! ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [August 12, 2011, 2:35pm UTC](https://discuss.elastic.co/t/new-to-elastic-search-i-get-this-exception-org-elasticsearch-action-unavailableshardsexception/5120/12 "2011-08-12T14:35:47Z")
Can you post a curl recreation from "clean data" and notes when to stop the server and start it? On Fri, Aug 12, 2011 at 3:07 AM, Jamshid [jamshid69@gmail.com](mailto:jamshid69@gmail.com) wrote: > FYI I'm also seeing UnavailableShardsException with 0.17.4. I did not > see it with 0.16.5. > > I started a test with a clean data directory, single node, created a > couple of indexes (one with five shards and another with ten) and > verified elasticsearch-head showed all was Yellow (since no replicas). > > Then I tried adding a document but got that exception: > > curl -XPUT [http://localhost:9200/five/named/1234](http://localhost:9200/five/named/1234) -d '{"named": > {"context": "Domain001/Bucket0001", "name": "File612606243717652", > "size": "90803308" }}' > > {"error":"UnavailableShardsException[[five][3] [3] shardIt, [1] > active : Timeout waiting for [1m], request: index {[five][named] > [1234], source[{.... > > So I killed java and restarted, this is all that got logged: > > ... > [2011-08-11 18:48:46,383][INFO][node] [Mantra] > {elasticsearch/0.17.4}[14437]: > started > [2011-08-11 18:48:46,399][INFO][gateway] [Mantra] > recovered [2] indices into > cluster\_state > > And now cluster health is stuck in red: > > curl -XGET '[http://localhost:9200/\_cluster/health](http://localhost:9200/_cluster/health)' > > {"cluster\_name":"mytest","status":"red","timed\_out":false,"number\_of\_nodes": > 1,"number\_of\_data\_nodes":1,"active\_primary\_shards":0,"active\_shards": > 0,"relocating\_shards":0,"initializing\_shards":0,"unassigned\_shards": > 45} > > Same problem after another restart. > > Btw elasticsearch-head shows 3 (why not 2?) replicas, all Unassigned. > > Any ideas? > > --Jamshid > > On Aug 11, 4:27 pm, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > It waits for green status for a timeout, and then returns. It returns > > what > > the status is now, and a flag indicating if it timed out. We don't want > > to > > block forever ๐Ÿ™‚ > > > > On Fri, Aug 12, 2011 at 12:03 AM, ogregras [ogreg...@gmail.com](mailto:ogreg...@gmail.com) wrote: > > > > > You know better than me! > > > > > It's just a little bit odd that setWaitFor_Green_Status() returns and > > > the > > > status is not green! ๐Ÿ™‚ > > > > > But currently everything seems to be running well. So thanks again for > > > the > > > help! ---
**Author:** ![Jamshid](https://avatars.discourse-cdn.com/v4/letter/j/ecd19e/32.png) [@Jamshid](https://discuss.elastic.co/u/Jamshid)\ **Post date:** [August 15, 2011, 3:48am UTC](https://discuss.elastic.co/t/new-to-elastic-search-i-get-this-exception-org-elasticsearch-action-unavailableshardsexception/5120/13 "2011-08-15T03:48:07Z")
I tried reproducing on 0.17.4 and was not able to. I'll upgrade to 0.17.6 and try to get more information if I see it again. Thanks, Jamshid On Aug 12, 9:35 am, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > Can you post a curl recreation from "clean data" and notes when to stop the > server and start it? > > On Fri, Aug 12, 2011 at 3:07 AM, Jamshid [jamshi...@gmail.com](mailto:jamshi...@gmail.com) wrote: > > > FYI I'm also seeing UnavailableShardsException with 0.17.4. I did not > > see it with 0.16.5. > > > I started a test with a clean data directory, single node, created a > > couple of indexes (one with five shards and another with ten) and > > verified elasticsearch-head showed all was Yellow (since no replicas). > > > Then I tried adding a document but got that exception: > > > curl -XPUThttp://localhost:9200/five/named/1234-d '{"named": > > {"context": "Domain001/Bucket0001", "name": "File612606243717652", > > "size": "90803308" }}' > > > {"error":"UnavailableShardsException[[five][3] [3] shardIt, [1] > > active : Timeout waiting for [1m], request: index {[five][named] > > [1234], source[{.... > > > So I killed java and restarted, this is all that got logged: > > > ... > > [2011-08-11 18:48:46,383][INFO][node] [Mantra] > > {elasticsearch/0.17.4}[14437]: > > started > > [2011-08-11 18:48:46,399][INFO][gateway] [Mantra] > > recovered [2] indices into > > cluster\_state > > > And now cluster health is stuck in red: > > > curl -XGET '[http://localhost:9200/\_cluster/health](http://localhost:9200/_cluster/health)' > > > {"cluster\_name":"mytest","status":"red","timed\_out":false,"number\_of\_nodes" : > > 1,"number\_of\_data\_nodes":1,"active\_primary\_shards":0,"active\_shards": > > 0,"relocating\_shards":0,"initializing\_shards":0,"unassigned\_shards": > > 45} > > > Same problem after another restart. > > > Btw elasticsearch-head shows 3 (why not 2?) replicas, all Unassigned. > > > Any ideas? > > > --Jamshid > > > On Aug 11, 4:27 pm, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > > > It waits for green status for a timeout, and then returns. It returns > > > what > > > the status is now, and a flag indicating if it timed out. We don't want > > > to > > > block forever ๐Ÿ™‚ > > > > On Fri, Aug 12, 2011 at 12:03 AM, ogregras [ogreg...@gmail.com](mailto:ogreg...@gmail.com) wrote: > > > > > > > You know better than me! > > > > > It's just a little bit odd that setWaitFor_Green_Status() returns and > > > > the > > > > status is not green! ๐Ÿ™‚ > > > > > But currently everything seems to be running well. So thanks again for > > > > the > > > > help! ---
**Author:** ![lecochien](https://avatars.discourse-cdn.com/v4/letter/l/48db29/32.png) [@lecochien](https://discuss.elastic.co/u/lecochien)\ **Post date:** [August 17, 2011, 3:19pm UTC](https://discuss.elastic.co/t/new-to-elastic-search-i-get-this-exception-org-elasticsearch-action-unavailableshardsexception/5120/14 "2011-08-17T15:19:29Z")
Hello, I've receive the same error (UnavailableShardsException) when i'm trying to create an index with 0.17.6 and a s3 gateway. the first time my index settings was : "settings" : { "index" : { "number\_of\_shards" : 3, "number\_of\_replicas" : 2, And it doesn't work. the second time i've changed the settings to : "settings" : { "index" : { "number\_of\_shards" : 3, "number\_of\_replicas" : 1, and it's worked. Maybe it could help you.. bye. (sorry for my bad english... ๐Ÿ˜‰ On 15 aoรปt, 05:48, Jamshid [jamshi...@gmail.com](mailto:jamshi...@gmail.com) wrote: > I tried reproducing on 0.17.4 and was not able to. I'll upgrade to > 0.17.6 and try to get more information if I see it again. > > Thanks, > Jamshid > > On Aug 12, 9:35 am, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > Can you post a curl recreation from "clean data" and notes when to stop the > > server and start it? > > > On Fri, Aug 12, 2011 at 3:07 AM, Jamshid [jamshi...@gmail.com](mailto:jamshi...@gmail.com) wrote: > > > > > FYI I'm also seeingUnavailableShardsExceptionwith 0.17.4. I did not > > > see it with 0.16.5. > > > > I started a test with a clean data directory, single node, created a > > > couple of indexes (one with five shards and another with ten) and > > > verified elasticsearch-head showed all was Yellow (since no replicas). > > > > Then I tried adding a document but got that exception: > > > > curl -XPUThttp://localhost:9200/five/named/1234-d'{"named": > > > {"context": "Domain001/Bucket0001", "name": "File612606243717652", > > > "size": "90803308" }}' > > > > {"error":"UnavailableShardsException[[five][3] [3] shardIt, [1] > > > active : Timeout waiting for [1m], request: index {[five][named] > > > [1234], source[{.... > > > > So I killed java and restarted, this is all that got logged: > > > > ... > > > [2011-08-11 18:48:46,383][INFO][node] [Mantra] > > > {elasticsearch/0.17.4}[14437]: > > > started > > > [2011-08-11 18:48:46,399][INFO][gateway] [Mantra] > > > recovered [2] indices into > > > cluster\_state > > > > And now cluster health is stuck in red: > > > > curl -XGET '[http://localhost:9200/\_cluster/health](http://localhost:9200/_cluster/health)' > > > > {"cluster\_name":"mytest","status":"red","timed\_out":false,"number\_of\_nodes" : > > > 1,"number\_of\_data\_nodes":1,"active\_primary\_shards":0,"active\_shards": > > > 0,"relocating\_shards":0,"initializing\_shards":0,"unassigned\_shards": > > > 45} > > > > Same problem after another restart. > > > > Btw elasticsearch-head shows 3 (why not 2?) replicas, all Unassigned. > > > > Any ideas? > > > > --Jamshid > > > > On Aug 11, 4:27 pm, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > > > > > It waits for green status for a timeout, and then returns. It returns > > > > what > > > > the status is now, and a flag indicating if it timed out. We don't want > > > > to > > > > block forever ๐Ÿ™‚ > > > > > On Fri, Aug 12, 2011 at 12:03 AM, ogregras [ogreg...@gmail.com](mailto:ogreg...@gmail.com) wrote: > > > > > > > > > You know better than me! > > > > > > It's just a little bit odd that setWaitFor_Green_Status() returns and > > > > > the > > > > > status is not green! ๐Ÿ™‚ > > > > > > But currently everything seems to be running well. So thanks again for > > > > > the > > > > > help! ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [August 18, 2011, 12:08pm UTC](https://discuss.elastic.co/t/new-to-elastic-search-i-get-this-exception-org-elasticsearch-action-unavailableshardsexception/5120/15 "2011-08-18T12:08:58Z")
How many nodes did you have allocated? By default, elasticsearch expects a quorum of shard and replicas to be allocated in order to allow for writes. In your first example, it expects 2 to be allocated per replication group / partition. Check write consistency here: [Elasticsearch Platform โ€” Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/index_.html). On Wed, Aug 17, 2011 at 6:19 PM, lecochien [rgarcon@voisins-super.fr](mailto:rgarcon@voisins-super.fr) wrote: > Hello, > I've receive the same error (UnavailableShardsException) when i'm > trying to create an index with 0.17.6 and a s3 gateway. > the first time my index settings was : > "settings" : { > "index" : { > "number\_of\_shards" : 3, > "number\_of\_replicas" : 2, > And it doesn't work. > the second time i've changed the settings to : > "settings" : { > "index" : { > "number\_of\_shards" : 3, > "number\_of\_replicas" : 1, > and it's worked. > Maybe it could help you.. > bye. > (sorry for my bad english... ๐Ÿ˜‰ > > On 15 aoรปt, 05:48, Jamshid [jamshi...@gmail.com](mailto:jamshi...@gmail.com) wrote: > > > I tried reproducing on 0.17.4 and was not able to. I'll upgrade to > > 0.17.6 and try to get more information if I see it again. > > > > Thanks, > > Jamshid > > > > On Aug 12, 9:35 am, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > > > Can you post a curl recreation from "clean data" and notes when to stop > > > the > > > server and start it? > > > > > On Fri, Aug 12, 2011 at 3:07 AM, Jamshid [jamshi...@gmail.com](mailto:jamshi...@gmail.com) wrote: > > > > > > > FYI I'm also seeingUnavailableShardsExceptionwith 0.17.4. I did not > > > > see it with 0.16.5. > > > > > > I started a test with a clean data directory, single node, created a > > > > couple of indexes (one with five shards and another with ten) and > > > > verified elasticsearch-head showed all was Yellow (since no > > > > replicas). > > > > > > Then I tried adding a document but got that exception: > > > > > > curl -XPUThttp://localhost:9200/five/named/1234-d'{"named": > > > > {"context": "Domain001/Bucket0001", "name": "File612606243717652", > > > > "size": "90803308" }}' > > > > > > {"error":"UnavailableShardsException[[five][3] [3] shardIt, [1] > > > > active : Timeout waiting for [1m], request: index {[five][named] > > > > [1234], source[{.... > > > > > > So I killed java and restarted, this is all that got logged: > > > > > > ... > > > > [2011-08-11 18:48:46,383][INFO][node] [Mantra] > > > > {elasticsearch/0.17.4}[14437]: > > > > started > > > > [2011-08-11 18:48:46,399][INFO][gateway] [Mantra] > > > > recovered [2] indices into > > > > cluster\_state > > > > > > And now cluster health is stuck in red: > > > > > > curl -XGET '[http://localhost:9200/\_cluster/health](http://localhost:9200/_cluster/health)' > > > > > > > > {"cluster\_name":"mytest","status":"red","timed\_out":false,"number\_of\_nodes" > : > > > > > 1,"number\_of\_data\_nodes":1,"active\_primary\_shards":0,"active\_shards": > > > > 0,"relocating\_shards":0,"initializing\_shards":0,"unassigned\_shards": > > > > 45} > > > > > > Same problem after another restart. > > > > > > Btw elasticsearch-head shows 3 (why not 2?) replicas, all Unassigned. > > > > > > Any ideas? > > > > > > --Jamshid > > > > > > On Aug 11, 4:27 pm, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > > > > > > > It waits for green status for a timeout, and then returns. It > > > > > returns > > > > > what > > > > > the status is now, and a flag indicating if it timed out. We don't > > > > > want > > > > > to > > > > > block forever ๐Ÿ™‚ > > > > > > > On Fri, Aug 12, 2011 at 12:03 AM, ogregras [ogreg...@gmail.com](mailto:ogreg...@gmail.com) > > > > > wrote: > > > > > > > > > > > You know better than me! > > > > > > > > It's just a little bit odd that setWaitFor_Green_Status() returns > > > > > > and > > > > > > the > > > > > > status is not green! ๐Ÿ™‚ > > > > > > > > But currently everything seems to be running well. So thanks > > > > > > again for > > > > > > the > > > > > > help! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:56am UTC](https://discuss.elastic.co/t/new-to-elastic-search-i-get-this-exception-org-elasticsearch-action-unavailableshardsexception/5120/16 "2017-07-06T03:56:42Z")