Shard Failures

Elastic Stack Elasticsearch
1

I have a non-data node executing a simple query against an index, and I am
receiving the following exception. Can someone shed some light on what the
"[na]" means in the trace? My cluster health is checked prior to the query
and is in Yellow state. Thanks!

01:46:05,465 DEBUG p-8080-3 elastic.search: ? - Performing
searchRequest of indices: {ppkc}, types: (["profiles"]), source:
{"query":{"field":{"username":"matt"}},"size":32767}
01:46:05,484 ERROR p-8080-3 rest.rest: ? - Error while
processing request: /api/profiles JavaException:
org.elasticsearch.action.search.SearchPhaseExecutionException: Failed to
execute phase [query], total failure; shardFailures {[na][ppkc][0]: No
active shards}{[na][ppkc][1]: No active shards}{[na][ppkc][2]: No active
shards}{[na][ppkc][3]: No active shards}{[na][ppkc][4]: No active
shards} (elastic/search.js#221)
Script stack:
at elastic/search.js:221 (search)
at store/map.js:180 (anonymous)
at store/map.js:104 (anonymous)
at api/profiles.js:1365 (anonymous)
at api/profiles.js:388 (anonymous)
at rest/rest.js:101 (handleRequest)
at middleware/method.js:33 (anonymous)
at middleware/headers.js:7 (anonymous)
at middleware/snoop.js:72 (anonymous)
at ringo/jsgi.js:41 (handleRequest)

2

na means that a "printable" view of the search request could not be generated (probably because it uses Smile format and not Json). You should not get this failure when the cluster is yellow.
On Thursday, May 19, 2011 at 5:34 AM, James Cook wrote:

I have a non-data node executing a simple query against an index, and I am receiving the following exception. Can someone shed some light on what the "[na]" means in the trace? My cluster health is checked prior to the query and is in Yellow state. Thanks!

01:46:05,465 DEBUG p-8080-3 elastic.search: ? - Performing searchRequest of indices: {ppkc}, types: (["profiles"]), source: {"query":{"field":{"username":"matt"}},"size":32767}
01:46:05,484 ERROR p-8080-3 rest.rest: ? - Error while processing request: /api/profiles JavaException: org.elasticsearch.action.search.SearchPhaseExecutionException: Failed to execute phase [query], total failure; shardFailures {[na][ppkc][0]: No active shards}{[na][ppkc][1]: No active shards}{[na][ppkc][2]: No active shards}{[na][ppkc][3]: No active shards}{[na][ppkc][4]: No active shards} (elastic/search.js#221)
Script stack:
at elastic/search.js:221 (search)
at store/map.js:180 (anonymous)
at store/map.js:104 (anonymous)
at api/profiles.js:1365 (anonymous)
at api/profiles.js:388 (anonymous)
at rest/rest.js:101 (handleRequest)
at middleware/method.js:33 (anonymous)
at middleware/headers.js:7 (anonymous)
at middleware/snoop.js:72 (anonymous)
at ringo/jsgi.js:41 (handleRequest)

3

The JSON search query is shown in the first log statement. The exception
seems to occur only when I execute the query using a TransportClient. Using
a node client, the query executes properly. Does that offer any more clues?

-- jim

On Thu, May 19, 2011 at 7:37 AM, Shay Banon shay.banon@elasticsearch.comwrote:

na means that a "printable" view of the search request could not be
generated (probably because it uses Smile format and not Json). You should
not get this failure when the cluster is yellow.

On Thursday, May 19, 2011 at 5:34 AM, James Cook wrote:

I have a non-data node executing a simple query against an index, and I am
receiving the following exception. Can someone shed some light on what the
"[na]" means in the trace? My cluster health is checked prior to the query
and is in Yellow state. Thanks!

01:46:05,465 DEBUG p-8080-3 elastic.search: ? - Performing
searchRequest of indices: {ppkc}, types: (["profiles"]), source:
{"query":{"field":{"username":"matt"}},"size":32767}
01:46:05,484 ERROR p-8080-3 rest.rest: ? - Error while
processing request: /api/profiles JavaException:
org.elasticsearch.action.search.SearchPhaseExecutionException: Failed to
execute phase [query], total failure; shardFailures {[na][ppkc][0]: No
active shards}{[na][ppkc][1]: No active shards}{[na][ppkc][2]: No active
shards}{[na][ppkc][3]: No active shards}{[na][ppkc][4]: No active
shards} (elastic/search.js#221)
Script stack:
at elastic/search.js:221 (search)
at store/map.js:180 (anonymous)
at store/map.js:104 (anonymous)
at api/profiles.js:1365 (anonymous)
at api/profiles.js:388 (anonymous)
at rest/rest.js:101 (handleRequest)
at middleware/method.js:33 (anonymous)
at middleware/headers.js:7 (anonymous)
at middleware/snoop.js:72 (anonymous)
at ringo/jsgi.js:41 (handleRequest)

4

Are you sure the TransportClient is connected to the cluster?
On Thursday, May 19, 2011 at 4:12 PM, James Cook wrote:

The JSON search query is shown in the first log statement. The exception seems to occur only when I execute the query using a TransportClient. Using a node client, the query executes properly. Does that offer any more clues?

-- jim

On Thu, May 19, 2011 at 7:37 AM, Shay Banon shay.banon@elasticsearch.com wrote:

na means that a "printable" view of the search request could not be generated (probably because it uses Smile format and not Json). You should not get this failure when the cluster is yellow.
On Thursday, May 19, 2011 at 5:34 AM, James Cook wrote:

I have a non-data node executing a simple query against an index, and I am receiving the following exception. Can someone shed some light on what the "[na]" means in the trace? My cluster health is checked prior to the query and is in Yellow state. Thanks!

01:46:05,465 DEBUG p-8080-3 elastic.search: ? - Performing searchRequest of indices: {ppkc}, types: (["profiles"]), source: {"query":{"field":{"username":"matt"}},"size":32767}
01:46:05,484 ERROR p-8080-3 rest.rest: ? - Error while processing request: /api/profiles JavaException: org.elasticsearch.action.search.SearchPhaseExecutionException: Failed to execute phase [query], total failure; shardFailures {[na][ppkc][0]: No active shards}{[na][ppkc][1]: No active shards}{[na][ppkc][2]: No active shards}{[na][ppkc][3]: No active shards}{[na][ppkc][4]: No active shards} (elastic/search.js#221)
Script stack:
at elastic/search.js:221 (search)
at store/map.js:180 (anonymous)
at store/map.js:104 (anonymous)
at api/profiles.js:1365 (anonymous)
at api/profiles.js:388 (anonymous)
at rest/rest.js:101 (handleRequest)
at middleware/method.js:33 (anonymous)
at middleware/headers.js:7 (anonymous)
at middleware/snoop.js:72 (anonymous)
at ringo/jsgi.js:41 (handleRequest)