Yes, we have two nodes set up in our cluster and I've confirmed that both of them are running 1.1.0.
However, the error that I'm getting seems to suggest that for some reason the BigArrays class from 1.0.1 is still being used somewhere. Could that be caused by an incomplete migration? -- Robert On Tuesday, April 8, 2014 4:43:03 AM UTC-5, Alexander Reelsen wrote: > > Hey, > > are you sure that every node has been upgraded to 1.1.0? Looks as if there > is still a 1.0 node running from the outside... > > > --Alex > > > On Mon, Apr 7, 2014 at 9:35 PM, Robert Douglas <[email protected]<javascript:> > > wrote: > >> Hi All, >> >> I recently upgraded my ElasticSearch cluster to 1.1.0 in order to utilize >> the built in cardinality aggregation. However, whenever I try to run any >> sort of cardinality aggregation, I get back: >> >> { >> >> - error: SearchPhaseExecutionException[Failed to execute phase >> [query_fetch], all shards failed; shardFailures >> {[QOCVDBG8QrCX8arlUl6gGg][w2o_tweet][0]: >> >> RemoteTransportException[[customsearch-elastic-dev-2][inet[/10.146.214.50:9300]][search/phase/query+fetch]]; >> >> nested: >> >> ElasticsearchException[org.elasticsearch.common.util.BigArrays.newObjectArray(JLorg/elasticsearch/cache/recycler/PageCacheRecycler;)Lorg/elasticsearch/common/util/ObjectArray;]; >> >> nested: >> >> NoSuchMethodError[org.elasticsearch.common.util.BigArrays.newObjectArray(JLorg/elasticsearch/cache/recycler/PageCacheRecycler;)Lorg/elasticsearch/common/util/ObjectArray;]; >> >> }] >> - status: 500 >> >> } >> >> My query looks like this: >> >> { >> "size": 0, >> "query": { >> "filtered": { >> "query": { >> "match_all": {} >> }, >> "filter": { >> "and": { >> "filters": [ >> { >> "range": { >> "tweet.created_at": { >> "from": 1392613200000, >> "to": 1396843199999, >> "include_lower": true, >> "include_upper": true >> }, >> "_cache": true >> } >> } >> ] >> } >> } >> } >> }, >> "aggs": { >> "congress_unique": { >> "filter": { >> "term": { >> "user.screen_name": "CongPalazzo" >> } >> }, >> "aggs": { >> "unique": { >> "cardinality": { >> "field": "entities.hashtags.text" >> } >> } >> } >> } >> } >> } >> >> I've checked my mappings and everything looks like it should be good to >> go. Any ideas? >> >> Thanks, >> Robert >> >> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/3f6d4148-ede7-48ab-a213-3bde272b515b%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/3f6d4148-ede7-48ab-a213-3bde272b515b%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/752a65a1-8f0c-4297-8b16-3e63c7a22fc2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
