# Shard Failures

**URL:** <https://discuss.elastic.co/t/shard-failures/4434>\
**Category:** Elasticsearch\
**Created:** [May 19, 2011, 2:34am UTC](https://discuss.elastic.co/t/shard-failures/4434 "2011-05-19T02:34:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![James\_Cook](https://avatars.discourse-cdn.com/v4/letter/j/898d66/32.png) [@James\_Cook](https://discuss.elastic.co/u/James_Cook)\
**Post date:** [May 19, 2011, 2:34am UTC](https://discuss.elastic.co/t/shard-failures/4434/1 "2011-05-19T02:34:38Z")

</div>

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)

---

<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:** [May 19, 2011, 11:37am UTC](https://discuss.elastic.co/t/shard-failures/4434/2 "2011-05-19T11:37:15Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![James\_Cook](https://avatars.discourse-cdn.com/v4/letter/j/898d66/32.png) [@James\_Cook](https://discuss.elastic.co/u/James_Cook)\
**Post date:** [May 19, 2011, 1:12pm UTC](https://discuss.elastic.co/t/shard-failures/4434/3 "2011-05-19T13:12:54Z")

</div>

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](mailto: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)

---

<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:** [May 19, 2011, 1:16pm UTC](https://discuss.elastic.co/t/shard-failures/4434/4 "2011-05-19T13:16:21Z")

</div>

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](mailto: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)

---

<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:05am UTC](https://discuss.elastic.co/t/shard-failures/4434/5 "2017-07-06T04:05:50Z")

</div>


