"No active shards" error in 0.9

Lenak · August 19, 2010, 9:44am

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)

kimchy · August 19, 2010, 11:54am

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 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
Sent from the Elasticsearch Users mailing list archive at Nabble.com.

Lenak · August 19, 2010, 12:15pm

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 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

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?by-user=t
Sent from the Elasticsearch Users mailing list archive at Nabble.com.

View message @
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 herehttp://elasticsearch-users.115913.n3.nabble.com/template/NodeServlet.jtp?tpl=unsubscribe_by_code&node=1221778&code=bGVuYWtvdmdhbm92QGdtYWlsLmNvbXwxMjIxNzc4fDEzNzE4Nzg5MDI=.

kimchy · August 19, 2010, 2:23pm

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 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> 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

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?by-user=t&by-user=t
Sent from the Elasticsearch Users mailing list archive at 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?by-user=t
To unsubscribe from "No active shards" error in 0.9, click herehttp://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.9http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-error-in-0-9-tp1221778p1223465.html

Sent from the Elasticsearch Users mailing list archivehttp://elasticsearch-users.115913.n3.nabble.com/at Nabble.com.

talsalmona · August 19, 2010, 4:30pm

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 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 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> 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

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...
Sent from the Elasticsearch Users mailing list archive at 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...
To unsubscribe from "No active shards" error in 0.9, click herehttp://elasticsearch-users.115913.n3.nabble.com/template/NodeServlet.....

View this message in context: Re: "No active shards" error in 0.9http://elasticsearch-users.115913.n3.nabble.com/No-active-shards-erro...

Sent from the Elasticsearch Users mailing list archivehttp://elasticsearch-users.115913.n3.nabble.com/at Nabble.com.

kimchy · August 19, 2010, 5:13pm

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 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 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 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> 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>

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...>

Sent from the Elasticsearch Users mailing list archive at 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...>

To unsubscribe from "No active shards" error in 0.9, click here<
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...>

Sent from the Elasticsearch Users mailing list archive<
http://elasticsearch-users.115913.n3.nabble.com/>at Nabble.com.