Has anyone observed a problem when upgrading from ElasticSearch 1.0.3 to 
1.1.2 regarding the cat shards (or cat indices)?  We recently rolled this 
out in one of our environments and experienced a NullPointerException (NPE) 
for some of the cat API calls (for instance: cat/shards or cat/indices). 
 The good news is that this went away once all nodes were on the same 
version.

My question: is it correct to assume that this is expected behavior?  Also, 
is there anything that I could do to mitigate this (upgrade faster ;)?

Problems experienced were with:

*cat/shards*
*cat/indices*
*cat/nodes*

Oddly, *cat/indices/my-index?H* did return the expected values (or at least 
when I tested it did).


-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/906da92f-0072-43af-84cb-bc394728544a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to