# "No active shards" error in 0.9

**URL:** <https://discuss.elastic.co/t/no-active-shards-error-in-0-9/3236>\
**Category:** Elasticsearch\
**Created:** [August 19, 2010, 9:44am UTC](https://discuss.elastic.co/t/no-active-shards-error-in-0-9/3236 "2010-08-19T09:44:55Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lenak](https://avatars.discourse-cdn.com/v4/letter/l/96bed5/32.png) [@Lenak](https://discuss.elastic.co/u/Lenak)\
**Post date:** [August 19, 2010, 9:44am UTC](https://discuss.elastic.co/t/no-active-shards-error-in-0-9/3236/1 "2010-08-19T09:44:55Z")

</div>

Hello, Shay

We are working with 0.9 version and have two nodes in our cluster – one data node and one client node. Cluster discovery zen tcp.  
In the client side we got exception “No active shards”. What is a reason of “No active shards” exception? Is it communication problems? Client restart solved the problem.  
What you recommend to do to solve this problem in runtime?

org.elasticsearch.action.search.SearchPhaseExecutionException: Failed to execute phase [query], total failure; shardFailures {[null][478964696][2]: No active shards}{[null][478964696][1]: No active shards}{[null][478964696][3]: No active shards}{[null][478964696][4]: No active shards}{[null][478964696][0]: No active shards}  
at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize(ServerSerializationStreamWriter.java:610)  
at com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.writeObject(AbstractSerializationStreamWriter.java:129)  
at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter$ValueWriter$8.write(ServerSerializationStreamWriter.java:152)  
at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeValue(ServerSerializationStreamWriter.java:534)  
at com.google.gwt.user.server.rpc.RPC.encodeResponse(RPC.java:609)  
at com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:383)  
at com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:361)  
at com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:329)  
at com.hp.f8upper.server.webapp.guice.GuiceRemoteServiceServlet.handleException(GuiceRemoteServiceServlet.java:69)  
at com.hp.f8upper.server.webapp.guice.GuiceRemoteServiceServlet.processCall(GuiceRemoteServiceServlet.java:52)  
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:224)  
at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)  
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)  
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)  
at com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:216)  
at com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:141)  
at com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:93)  
at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:63)  
at com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:122)  
at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:110)  
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)  
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)  
at com.es.isv.ISVFilter.doFilter(ISVFilter.java:96)  
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)  
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)  
at com.es.relationals.RelationalsEncodingFilter.doFilter(RelationalsEncodingFilter.java:40)  
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)  
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)  
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)  
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)  
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)  
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)  
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)  
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)  
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)  
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)  
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)  
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)  
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)  
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)  
at java.lang.Thread.run(Thread.java:619)

---

<div class="post-metadata">

**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 19, 2010, 11:54am UTC](https://discuss.elastic.co/t/no-active-shards-error-in-0-9/3236/2 "2010-08-19T11:54:02Z")

</div>

This usually happens when no shard is active to perform the operation (an  
active shard is a shard that has been allocated to a node, and is ready for  
work). What type of client are you using?

Another question, why do you have just one node, is it just for testing?

-shay.banon

On Thu, Aug 19, 2010 at 12:44 PM, Lenak [lenakovganov@gmail.com](mailto:lenakovganov@gmail.com) wrote:

> Hello, Shay
> 
> We are working with 0.9 version and have two nodes in our cluster – one  
> data  
> node and one client node. Cluster discovery zen tcp.  
> In the client side we got exception “No active shards”. What is a reason of  
> “No active shards” exception? Is it communication problems? Client restart  
> solved the problem.  
> What you recommend to do to solve this problem in runtime?
> 
> org.elasticsearch.action.search.SearchPhaseExecutionException: Failed to  
> execute phase [query], total failure; shardFailures {[null][478964696][2]:  
> No active shards}{[null][478964696][1]: No active  
> shards}{[null][478964696][3]: No active shards}{[null][478964696][4]: No  
> active shards}{[null][478964696][0]: No active shards}  
> at
> 
> com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize(ServerSerializationStreamWriter.java:610)  
> at
> 
> com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.writeObject(AbstractSerializationStreamWriter.java:129)  
> at
> 
> com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter$ValueWriter$8.write(ServerSerializationStreamWriter.java:152)  
> at
> 
> com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeValue(ServerSerializationStreamWriter.java:534)  
> at com.google.gwt.user.server.rpc.RPC.encodeResponse(RPC.java:609)  
> at  
> com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:383)  
> at  
> com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:361)  
> at  
> com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:329)  
> at
> 
> com.hp.f8upper.server.webapp.guice.GuiceRemoteServiceServlet.handleException(GuiceRemoteServiceServlet.java:69)  
> at
> 
> com.hp.f8upper.server.webapp.guice.GuiceRemoteServiceServlet.processCall(GuiceRemoteServiceServlet.java:52)  
> at
> 
> com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:224)  
> at
> 
> com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)  
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)  
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)  
> at
> 
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:216)  
> at
> 
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:141)  
> at
> 
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:93)  
> at
> 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:63)  
> at
> 
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:122)  
> at  
> com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:110)  
> at
> 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)  
> at
> 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)  
> at com.es.isv.ISVFilter.doFilter(ISVFilter.java:96)  
> at
> 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)  
> at
> 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)  
> at
> 
> com.es.relationals.RelationalsEncodingFilter.doFilter(RelationalsEncodingFilter.java:40)  
> at
> 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)  
> at
> 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)  
> at
> 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)  
> at
> 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)  
> at
> 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)  
> at
> 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)  
> at
> 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)  
> at  
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)  
> at  
> org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)  
> at  
> org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)  
> at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)  
> at
> 
> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)  
> at
> 
> org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)  
> at
> 
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)  
> at java.lang.Thread.run(Thread.java:619)
> 
> --  
> View this message in context:  
> [http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-error-in-0-9-tp1221778p1221778.html](http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-error-in-0-9-tp1221778p1221778.html)  
> Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).

---

<div class="post-metadata">

**Author:** ![Lenak](https://avatars.discourse-cdn.com/v4/letter/l/96bed5/32.png) [@Lenak](https://discuss.elastic.co/u/Lenak)\
**Post date:** [August 19, 2010, 12:15pm UTC](https://discuss.elastic.co/t/no-active-shards-error-in-0-9/3236/3 "2010-08-19T12:15:37Z")

</div>

It is testing environment only and we use Client Node (not TransportClient)  
with configuration "no data".

Additional information: after we got error on client side, we run request  
(\_count) via REST to data node and got good answer with real document  
count.

Lena

On Thu, Aug 19, 2010 at 2:59 PM, kimchy [via Elasticsearch Users] \<  
[ml-node+1223244-1133486945-68658@n3.nabble.com](mailto:ml-node+1223244-1133486945-68658@n3.nabble.com)[ml-node%2B1223244-1133486945-68658@n3.nabble.com](mailto:ml-node%2B1223244-1133486945-68658@n3.nabble.com)

> wrote:

> This usually happens when no shard is active to perform the operation (an  
> active shard is a shard that has been allocated to a node, and is ready for  
> work). What type of client are you using?
> 
> Another question, why do you have just one node, is it just for testing?
> 
> -shay.banon
> 
> On Thu, Aug 19, 2010 at 12:44 PM, Lenak \<[hidden email][http://user/SendEmail.jtp?type=node&node=1223244&i=0](http://user/SendEmail.jtp?type=node&node=1223244&i=0)
> 
> > wrote:
> 
> > Hello, Shay
> > 
> > We are working with 0.9 version and have two nodes in our cluster – one  
> > data  
> > node and one client node. Cluster discovery zen tcp.  
> > In the client side we got exception “No active shards”. What is a reason  
> > of  
> > “No active shards” exception? Is it communication problems? Client restart  
> > solved the problem.  
> > What you recommend to do to solve this problem in runtime?
> > 
> > org.elasticsearch.action.search.SearchPhaseExecutionException: Failed to  
> > execute phase [query], total failure; shardFailures {[null][478964696][2]:  
> > No active shards}{[null][478964696][1]: No active  
> > shards}{[null][478964696][3]: No active shards}{[null][478964696][4]: No  
> > active shards}{[null][478964696][0]: No active shards}  
> > at
> > 
> > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize(ServerSerializationStreamWriter.java:610)  
> > at
> > 
> > com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.writeObject(AbstractSerializationStreamWriter.java:129)  
> > at
> > 
> > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter$ValueWriter$8.write(ServerSerializationStreamWriter.java:152)  
> > at
> > 
> > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeValue(ServerSerializationStreamWriter.java:534)  
> > at com.google.gwt.user.server.rpc.RPC.encodeResponse(RPC.java:609)  
> > at  
> > com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:383)  
> > at  
> > com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:361)  
> > at  
> > com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:329)  
> > at
> > 
> > com.hp.f8upper.server.webapp.guice.GuiceRemoteServiceServlet.handleException(GuiceRemoteServiceServlet.java:69)  
> > at
> > 
> > com.hp.f8upper.server.webapp.guice.GuiceRemoteServiceServlet.processCall(GuiceRemoteServiceServlet.java:52)  
> > at
> > 
> > com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:224)  
> > at
> > 
> > com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)  
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)  
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)  
> > at
> > 
> > com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:216)  
> > at
> > 
> > com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:141)  
> > at
> > 
> > com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:93)  
> > at
> > 
> > com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:63)  
> > at
> > 
> > com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:122)  
> > at  
> > com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:110)  
> > at
> > 
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)  
> > at
> > 
> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)  
> > at com.es.isv.ISVFilter.doFilter(ISVFilter.java:96)  
> > at
> > 
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)  
> > at
> > 
> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)  
> > at
> > 
> > com.es.relationals.RelationalsEncodingFilter.doFilter(RelationalsEncodingFilter.java:40)  
> > at
> > 
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)  
> > at
> > 
> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)  
> > at
> > 
> > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)  
> > at
> > 
> > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)  
> > at
> > 
> > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)  
> > at
> > 
> > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)  
> > at
> > 
> > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)  
> > at
> > 
> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)  
> > at  
> > org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)  
> > at  
> > org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)  
> > at  
> > org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)  
> > at
> > 
> > org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)  
> > at
> > 
> > org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)  
> > at
> > 
> > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)  
> > at java.lang.Thread.run(Thread.java:619)
> > 
> > --  
> > View this message in context:  
> > [http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-error-in-0-9-tp1221778p1221778.html](http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-error-in-0-9-tp1221778p1221778.html)[http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-error-in-0-9-tp1221778p1221778.html?by-user=t](http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-error-in-0-9-tp1221778p1221778.html?by-user=t)  
> > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).
> 
> * * *
> 
> View message @  
> [http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-error-in-0-9-tp1221778p1223244.html](http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-error-in-0-9-tp1221778p1223244.html)  
> To unsubscribe from "No active shards" error in 0.9, click here[http://elasticsearch-users.115913.n3.nabble.com/template/NodeServlet.jtp?tpl=unsubscribe\_by\_code&node=1221778&code=bGVuYWtvdmdhbm92QGdtYWlsLmNvbXwxMjIxNzc4fDEzNzE4Nzg5MDI=](http://elasticsearch-users.115913.n3.nabble.com/template/NodeServlet.jtp?tpl=unsubscribe_by_code&node=1221778&code=bGVuYWtvdmdhbm92QGdtYWlsLmNvbXwxMjIxNzc4fDEzNzE4Nzg5MDI=).

---

<div class="post-metadata">

**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 19, 2010, 2:23pm UTC](https://discuss.elastic.co/t/no-active-shards-error-in-0-9/3236/4 "2010-08-19T14:23:05Z")

</div>

Do you set on the node builder that its a client (and not just disable  
data)? NodeBuilder#client(true) (this also makes it a non data node)?

When do you get the exception, on startup, or over time?

-shay.banon

On Thu, Aug 19, 2010 at 3:16 PM, Lenak [lenakovganov@gmail.com](mailto:lenakovganov@gmail.com) wrote:

> It is testing environment only and we use Client Node (not  
> TransportClient) with configuration "no data".
> 
> Additional information: after we got error on client side, we run request  
> (\_count) via REST to data node and got good answer with real document  
> count.
> 
> Lena
> 
> On Thu, Aug 19, 2010 at 2:59 PM, kimchy [via Elasticsearch Users] \<[hidden  
> email] [http://user/SendEmail.jtp?type=node&node=1223465&i=0](http://user/SendEmail.jtp?type=node&node=1223465&i=0)\> wrote:
> 
> > This usually happens when no shard is active to perform the operation (an  
> > active shard is a shard that has been allocated to a node, and is ready for  
> > work). What type of client are you using?
> > 
> > Another question, why do you have just one node, is it just for testing?
> > 
> > -shay.banon
> > 
> > On Thu, Aug 19, 2010 at 12:44 PM, Lenak \<[hidden email][http://user/SendEmail.jtp?type=node&node=1223244&i=0](http://user/SendEmail.jtp?type=node&node=1223244&i=0)
> > 
> > > wrote:
> > 
> > > Hello, Shay
> > > 
> > > We are working with 0.9 version and have two nodes in our cluster – one  
> > > data  
> > > node and one client node. Cluster discovery zen tcp.  
> > > In the client side we got exception “No active shards”. What is a reason  
> > > of  
> > > “No active shards” exception? Is it communication problems? Client  
> > > restart  
> > > solved the problem.  
> > > What you recommend to do to solve this problem in runtime?
> > > 
> > > org.elasticsearch.action.search.SearchPhaseExecutionException: Failed to  
> > > execute phase [query], total failure; shardFailures  
> > > {[null][478964696][2]:  
> > > No active shards}{[null][478964696][1]: No active  
> > > shards}{[null][478964696][3]: No active shards}{[null][478964696][4]: No  
> > > active shards}{[null][478964696][0]: No active shards}  
> > > at
> > > 
> > > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize(ServerSerializationStreamWriter.java:610)  
> > > at
> > > 
> > > com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.writeObject(AbstractSerializationStreamWriter.java:129)  
> > > at
> > > 
> > > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter$ValueWriter$8.write(ServerSerializationStreamWriter.java:152)  
> > > at
> > > 
> > > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeValue(ServerSerializationStreamWriter.java:534)  
> > > at com.google.gwt.user.server.rpc.RPC.encodeResponse(RPC.java:609)  
> > > at  
> > > com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:383)  
> > > at  
> > > com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:361)  
> > > at  
> > > com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:329)  
> > > at
> > > 
> > > com.hp.f8upper.server.webapp.guice.GuiceRemoteServiceServlet.handleException(GuiceRemoteServiceServlet.java:69)  
> > > at
> > > 
> > > com.hp.f8upper.server.webapp.guice.GuiceRemoteServiceServlet.processCall(GuiceRemoteServiceServlet.java:52)  
> > > at
> > > 
> > > com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:224)  
> > > at
> > > 
> > > com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)  
> > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)  
> > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)  
> > > at
> > > 
> > > com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:216)  
> > > at
> > > 
> > > com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:141)  
> > > at
> > > 
> > > com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:93)  
> > > at
> > > 
> > > com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:63)  
> > > at
> > > 
> > > com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:122)  
> > > at  
> > > com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:110)  
> > > at
> > > 
> > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)  
> > > at
> > > 
> > > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)  
> > > at com.es.isv.ISVFilter.doFilter(ISVFilter.java:96)  
> > > at
> > > 
> > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)  
> > > at
> > > 
> > > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)  
> > > at
> > > 
> > > com.es.relationals.RelationalsEncodingFilter.doFilter(RelationalsEncodingFilter.java:40)  
> > > at
> > > 
> > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)  
> > > at
> > > 
> > > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)  
> > > at
> > > 
> > > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)  
> > > at
> > > 
> > > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)  
> > > at
> > > 
> > > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)  
> > > at
> > > 
> > > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)  
> > > at
> > > 
> > > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)  
> > > at
> > > 
> > > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)  
> > > at  
> > > org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)  
> > > at  
> > > org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)  
> > > at  
> > > org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)  
> > > at
> > > 
> > > org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)  
> > > at
> > > 
> > > org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)  
> > > at
> > > 
> > > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)  
> > > at java.lang.Thread.run(Thread.java:619)
> > > 
> > > --  
> > > View this message in context:  
> > > [http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-error-in-0-9-tp1221778p1221778.html](http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-error-in-0-9-tp1221778p1221778.html)[http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-error-in-0-9-tp1221778p1221778.html?by-user=t&by-user=t](http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-error-in-0-9-tp1221778p1221778.html?by-user=t&by-user=t)  
> > > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).
> > 
> > * * *
> > 
> > View message @  
> > [http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-error-in-0-9-tp1221778p1223244.html](http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-error-in-0-9-tp1221778p1223244.html)[http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-error-in-0-9-tp1221778p1223244.html?by-user=t](http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-error-in-0-9-tp1221778p1223244.html?by-user=t)  
> > To unsubscribe from "No active shards" error in 0.9, click here[http://elasticsearch-users.115913.n3.nabble.com/template/NodeServlet.jtp?tpl=unsubscribe\_by\_code&node=1221778&code=bGVuYWtvdmdhbm92QGdtYWlsLmNvbXwxMjIxNzc4fDEzNzE4Nzg5MDI=&by-user=t](http://elasticsearch-users.115913.n3.nabble.com/template/NodeServlet.jtp?tpl=unsubscribe_by_code&node=1221778&code=bGVuYWtvdmdhbm92QGdtYWlsLmNvbXwxMjIxNzc4fDEzNzE4Nzg5MDI=&by-user=t).
> 
> * * *
> 
> View this message in context: Re: "No active shards" error in 0.9[http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-error-in-0-9-tp1221778p1223465.html](http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-error-in-0-9-tp1221778p1223465.html)
> 
> Sent from the Elasticsearch Users mailing list archive[http://elasticsearch-users.115913.n3.nabble.com/](http://elasticsearch-users.115913.n3.nabble.com/)at [Nabble.com](http://Nabble.com).

---

<div class="post-metadata">

**Author:** ![talsalmona](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/talsalmona/32/3316_2.png) [@talsalmona](https://discuss.elastic.co/u/talsalmona)\
**Post date:** [August 19, 2010, 4:30pm UTC](https://discuss.elastic.co/t/no-active-shards-error-in-0-9/3236/5 "2010-08-19T16:30:21Z")

</div>

Hi Shay,

The node is started using NodeBuilder#client(true).  
The error happened after a run of about 16 hours. After restarting the  
client everything worked as normal.  
I guess that the client somehow got disconnected and could not  
reestablish the connection.  
Is there a way to workaround this by catching some disconnection even  
(or exception when running a query) and restart the client? Better  
yet, this could be done by the client internally.

BTW, this happened only once and we were unable to reproduce this  
since.

Thanks,  
Tal

On Aug 19, 5:23 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote:

> Do you set on the node builder that its a client (and not just disable  
> data)? NodeBuilder#client(true) (this also makes it a non data node)?
> 
> When do you get the exception, on startup, or over time?
> 
> -shay.banon
> 
> On Thu, Aug 19, 2010 at 3:16 PM, Lenak [lenakovga...@gmail.com](mailto:lenakovga...@gmail.com) wrote:
> 
> > It is testing environment only and we use Client Node (not  
> > TransportClient) with configuration "no data".
> 
> > Additional information: after we got error on client side, we run request  
> > (\_count) via REST to data node and got good answer with real document  
> > count.
> 
> > Lena
> 
> > On Thu, Aug 19, 2010 at 2:59 PM, kimchy [via Elasticsearch Users] \<[hidden  
> > email] [http://user/SendEmail.jtp?type=node&node=1223465&i=0](http://user/SendEmail.jtp?type=node&node=1223465&i=0)\> wrote:
> 
> > > This usually happens when no shard is active to perform the operation (an  
> > > active shard is a shard that has been allocated to a node, and is ready for  
> > > work). What type of client are you using?
> 
> > > Another question, why do you have just one node, is it just for testing?
> 
> > > -shay.banon
> 
> > > On Thu, Aug 19, 2010 at 12:44 PM, Lenak \<[hidden email][http://user/SendEmail.jtp?type=node&node=1223244&i=0](http://user/SendEmail.jtp?type=node&node=1223244&i=0)
> > > 
> > > > wrote:
> 
> > > > Hello, Shay
> 
> > > > We are working with 0.9 version and have two nodes in our cluster – one  
> > > > data  
> > > > node and one client node. Cluster discovery zen tcp.  
> > > > In the client side we got exception “No active shards”. What is a reason  
> > > > of  
> > > > “No active shards” exception? Is it communication problems? Client  
> > > > restart  
> > > > solved the problem.  
> > > > What you recommend to do to solve this problem in runtime?
> 
> > > > org.elasticsearch.action.search.SearchPhaseExecutionException: Failed to  
> > > > execute phase [query], total failure; shardFailures  
> > > > {[null][478964696][2]:  
> > > > No active shards}{[null][478964696][1]: No active  
> > > > shards}{[null][478964696][3]: No active shards}{[null][478964696][4]: No  
> > > > active shards}{[null][478964696][0]: No active shards}  
> > > > at
> 
> > > > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize(ServerSerializationStreamWriter.java:610)  
> > > > at
> 
> > > > com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.writeObject(AbstractSerializationStreamWriter.java:129)  
> > > > at
> 
> > > > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter$ValueWriter$8.write(ServerSerializationStreamWriter.java:152)  
> > > > at
> 
> > > > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeValue(ServerSerializationStreamWriter.java:534)  
> > > > at com.google.gwt.user.server.rpc.RPC.encodeResponse(RPC.java:609)  
> > > > at  
> > > > com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:383)  
> > > > at  
> > > > com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:361)  
> > > > at  
> > > > com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:329)  
> > > > at
> 
> > > > com.hp.f8upper.server.webapp.guice.GuiceRemoteServiceServlet.handleException(GuiceRemoteServiceServlet.java:69)  
> > > > at
> 
> > > > com.hp.f8upper.server.webapp.guice.GuiceRemoteServiceServlet.processCall(GuiceRemoteServiceServlet.java:52)  
> > > > at
> 
> > > > com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:224)  
> > > > at
> 
> > > > com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)  
> > > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)  
> > > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)  
> > > > at
> 
> > > > com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:216)  
> > > > at
> 
> > > > com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:141)  
> > > > at
> 
> > > > com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:93)  
> > > > at
> 
> > > > com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:63)  
> > > > at
> 
> > > > com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:122)  
> > > > at  
> > > > com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:110)  
> > > > at
> 
> > > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)  
> > > > at
> 
> > > > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)  
> > > > at com.es.isv.ISVFilter.doFilter(ISVFilter.java:96)  
> > > > at
> 
> > > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)  
> > > > at
> 
> > > > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)  
> > > > at
> 
> > > > com.es.relationals.RelationalsEncodingFilter.doFilter(RelationalsEncodingFilter.java:40)  
> > > > at
> 
> > > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)  
> > > > at
> 
> > > > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)  
> > > > at
> 
> > > > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)  
> > > > at
> 
> > > > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)  
> > > > at
> 
> > > > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)  
> > > > at
> 
> > > > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)  
> > > > at
> 
> > > > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)  
> > > > at
> 
> > > > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)  
> > > > at  
> > > > org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)  
> > > > at  
> > > > org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)  
> > > > at  
> > > > org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)  
> > > > at
> 
> > > > org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)  
> > > > at
> 
> > > > org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)  
> > > > at
> 
> > > > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)  
> > > > at java.lang.Thread.run(Thread.java:619)
> 
> > > > --  
> > > > View this message in context:  
> > > > [http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro](http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro)...[http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro...](http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro...)  
> > > > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).
> 
> > > * * *
> > > 
> > > View message @  
> > > [http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro](http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro)...[http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro...](http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro...)  
> > > To unsubscribe from "No active shards" error in 0.9, click here[http://elasticsearch-users.115913.n3.nabble.com/template/NodeServlet....](http://elasticsearch-users.115913.n3.nabble.com/template/NodeServlet....).
> 
> > * * *
> > 
> > View this message in context: Re: "No active shards" error in 0.9[http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro...](http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro...)
> 
> > Sent from the Elasticsearch Users mailing list archive[http://elasticsearch-users.115913.n3.nabble.com/](http://elasticsearch-users.115913.n3.nabble.com/)at [Nabble.com](http://Nabble.com).

---

<div class="post-metadata">

**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 19, 2010, 5:13pm UTC](https://discuss.elastic.co/t/no-active-shards-error-in-0-9/3236/6 "2010-08-19T17:13:29Z")

</div>

The client is supposed to automatically connect, thats how it works... .  
Strange that you got it... . If you do manage to recreate it, ti would be  
great to see the logs of both the client and the server.

-shay.banon

On Thu, Aug 19, 2010 at 7:30 PM, Tal [talsalmona@gmail.com](mailto:talsalmona@gmail.com) wrote:

> Hi Shay,
> 
> The node is started using NodeBuilder#client(true).  
> The error happened after a run of about 16 hours. After restarting the  
> client everything worked as normal.  
> I guess that the client somehow got disconnected and could not  
> reestablish the connection.  
> Is there a way to workaround this by catching some disconnection even  
> (or exception when running a query) and restart the client? Better  
> yet, this could be done by the client internally.
> 
> BTW, this happened only once and we were unable to reproduce this  
> since.
> 
> Thanks,  
> Tal
> 
> On Aug 19, 5:23 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote:
> 
> > Do you set on the node builder that its a client (and not just disable  
> > data)? NodeBuilder#client(true) (this also makes it a non data node)?
> > 
> > When do you get the exception, on startup, or over time?
> > 
> > -shay.banon
> > 
> > On Thu, Aug 19, 2010 at 3:16 PM, Lenak [lenakovga...@gmail.com](mailto:lenakovga...@gmail.com) wrote:
> > 
> > > It is testing environment only and we use Client Node (not  
> > > TransportClient) with configuration "no data".
> > 
> > > Additional information: after we got error on client side, we run  
> > > request  
> > > (\_count) via REST to data node and got good answer with real document  
> > > count.
> > 
> > > Lena
> > 
> > > On Thu, Aug 19, 2010 at 2:59 PM, kimchy [via Elasticsearch Users]  
> > > \<[hidden  
> > > email] [http://user/SendEmail.jtp?type=node&node=1223465&i=0](http://user/SendEmail.jtp?type=node&node=1223465&i=0)\> wrote:
> > 
> > > > This usually happens when no shard is active to perform the operation  
> > > > (an  
> > > > active shard is a shard that has been allocated to a node, and is  
> > > > ready for  
> > > > work). What type of client are you using?
> > 
> > > > Another question, why do you have just one node, is it just for  
> > > > testing?
> > 
> > > > -shay.banon
> > 
> > > > On Thu, Aug 19, 2010 at 12:44 PM, Lenak \<[hidden email]\<  
> > > > [http://user/SendEmail.jtp?type=node&node=1223244&i=0](http://user/SendEmail.jtp?type=node&node=1223244&i=0)\>
> > > > 
> > > > > wrote:
> > 
> > > > > Hello, Shay
> > 
> > > > > We are working with 0.9 version and have two nodes in our cluster –  
> > > > > one  
> > > > > data  
> > > > > node and one client node. Cluster discovery zen tcp.  
> > > > > In the client side we got exception “No active shards”. What is a  
> > > > > reason  
> > > > > of  
> > > > > “No active shards” exception? Is it communication problems? Client  
> > > > > restart  
> > > > > solved the problem.  
> > > > > What you recommend to do to solve this problem in runtime?
> > 
> > > > > org.elasticsearch.action.search.SearchPhaseExecutionException: Failed  
> > > > > to  
> > > > > execute phase [query], total failure; shardFailures  
> > > > > {[null][478964696][2]:  
> > > > > No active shards}{[null][478964696][1]: No active  
> > > > > shards}{[null][478964696][3]: No active shards}{[null][478964696][4]:  
> > > > > No  
> > > > > active shards}{[null][478964696][0]: No active shards}  
> > > > > at
> > 
> > > > >
> 
> com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize(ServerSerializationStreamWriter.java:610)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.writeObject(AbstractSerializationStreamWriter.java:129)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter$ValueWriter$8.write(ServerSerializationStreamWriter.java:152)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeValue(ServerSerializationStreamWriter.java:534)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> 
> com.google.gwt.user.server.rpc.RPC.encodeResponse(RPC.java:609)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> 
> com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:383)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> 
> com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:361)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> 
> com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:329)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> com.hp.f8upper.server.webapp.guice.GuiceRemoteServiceServlet.handleException(GuiceRemoteServiceServlet.java:69)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> com.hp.f8upper.server.webapp.guice.GuiceRemoteServiceServlet.processCall(GuiceRemoteServiceServlet.java:52)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:224)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> 
> javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> 
> javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:216)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:141)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:93)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:63)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:122)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > > > > 
> > > > > com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:110)  
> > > > > at
> > 
> > > > >
> 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> 
> > > > > ```
> > > > > at com.es.isv.ISVFilter.doFilter(ISVFilter.java:96)
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> com.es.relationals.RelationalsEncodingFilter.doFilter(RelationalsEncodingFilter.java:40)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > > > > 
> > > > > org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)  
> > > > > at  
> > > > > org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)  
> > > > > at  
> > > > > org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)  
> > > > > at
> > 
> > > > >
> 
> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
> 
> > > > > ```
> > > > > at
> > > > > 
> > > > > ```
> > 
> > > > >
> 
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
> 
> > > > > ```
> > > > > at java.lang.Thread.run(Thread.java:619)
> > > > > 
> > > > > ```
> > 
> > > > > --  
> > > > > View this message in context:
> 
> [http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro](http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro)...\<  
> [http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro](http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro)...\>
> 
> > > > > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).
> > 
> > > > * * *
> > > > 
> > > > View message @
> 
> [http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro](http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro)...\<  
> [http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro](http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro)...\>
> 
> > > > To unsubscribe from "No active shards" error in 0.9, click here\<  
> > > > [http://elasticsearch-users.115913.n3.nabble.com/template/NodeServlet](http://elasticsearch-users.115913.n3.nabble.com/template/NodeServlet)....\>.
> > 
> > > * * *
> > > 
> > > View this message in context: Re: "No active shards" error in 0.9\<  
> > > [http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro](http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro)...\>
> > 
> > > Sent from the Elasticsearch Users mailing list archive\<  
> > > [http://elasticsearch-users.115913.n3.nabble.com/](http://elasticsearch-users.115913.n3.nabble.com/)\>at [Nabble.com](http://Nabble.com).

---

<div class="post-metadata">

**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, 4:20am UTC](https://discuss.elastic.co/t/no-active-shards-error-in-0-9/3236/7 "2017-07-06T04:20:33Z")

</div>


