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;];
}]
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;];
}]
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 <robe...@gmail.com<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;];
}]
do you use a client node somewhere, which might be the wrong version? Is
this triggered by a HTTP query? What does curl
'10.146.214.50:9200/_cat/nodes?v&jvm'
return?
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 robe...@gmail.com 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:
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 elasticsearc...@googlegroups.com.
How do you mean client node? There are only two nodes currently in this
cluster, a single master and a single worker node. This error is being
triggered by an HTTP query that I'm executing via the head plugin (in the
'Any Request' tab). The results of that curl command are:
On Tuesday, April 8, 2014 10:01:19 AM UTC-5, Alexander Reelsen wrote:
Hey,
do you use a client node somewhere, which might be the wrong version? Is
this triggered by a HTTP query? What does curl '10.146.214.50:9200/_cat/nodes?v&jvm'
return?
--Alex
On Tue, Apr 8, 2014 at 4:26 PM, Robert Douglas <robe...@gmail.com<javascript:>
wrote:
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 robe...@gmail.comwrote:
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:
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 elasticsearc...@googlegroups.com.
How do you mean client node? There are only two nodes currently in this
cluster, a single master and a single worker node. This error is being
triggered by an HTTP query that I'm executing via the head plugin (in the
'Any Request' tab). The results of that curl command are:
On Tuesday, April 8, 2014 10:01:19 AM UTC-5, Alexander Reelsen wrote:
Hey,
do you use a client node somewhere, which might be the wrong version? Is
this triggered by a HTTP query? What does curl '10.146.214.50:9200/_cat/nodes?v&jvm'
return?
--Alex
On Tue, Apr 8, 2014 at 4:26 PM, Robert Douglas robe...@gmail.com wrote:
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 robe...@gmail.comwrote:
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:
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 elasticsearc...@googlegroups.com.
On Tue, Apr 8, 2014 at 5:07 PM, Robert Douglas <robe...@gmail.com<javascript:>
wrote:
How do you mean client node? There are only two nodes currently in this
cluster, a single master and a single worker node. This error is being
triggered by an HTTP query that I'm executing via the head plugin (in the
'Any Request' tab). The results of that curl command are:
On Tuesday, April 8, 2014 10:01:19 AM UTC-5, Alexander Reelsen wrote:
Hey,
do you use a client node somewhere, which might be the wrong version? Is
this triggered by a HTTP query? What does curl '10.146.214.50:9200/_cat/nodes?v&jvm'
return?
--Alex
On Tue, Apr 8, 2014 at 4:26 PM, Robert Douglas robe...@gmail.comwrote:
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 robe...@gmail.comwrote:
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:
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 elasticsearc...@googlegroups.com.
On Tue, Apr 8, 2014 at 5:07 PM, Robert Douglas <robe...@gmail.com<javascript:>
wrote:
How do you mean client node? There are only two nodes currently in this
cluster, a single master and a single worker node. This error is being
triggered by an HTTP query that I'm executing via the head plugin (in the
'Any Request' tab). The results of that curl command are:
On Tuesday, April 8, 2014 10:01:19 AM UTC-5, Alexander Reelsen wrote:
Hey,
do you use a client node somewhere, which might be the wrong version? Is
this triggered by a HTTP query? What does curl '10.146.214.50:9200/_cat/nodes?v&jvm'
return?
--Alex
On Tue, Apr 8, 2014 at 4:26 PM, Robert Douglas robe...@gmail.comwrote:
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 robe...@gmail.comwrote:
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:
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 elasticsearc...@googlegroups.com.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.