# Upgrading to Elastic 1.5.1 from 1.4.2 started raising ClassCastException

**URL:** <https://discuss.elastic.co/t/upgrading-to-elastic-1-5-1-from-1-4-2-started-raising-classcastexception/23605>\
**Category:** Elasticsearch\
**Created:** [May 11, 2015, 2:03pm UTC](https://discuss.elastic.co/t/upgrading-to-elastic-1-5-1-from-1-4-2-started-raising-classcastexception/23605 "2015-05-11T14:03:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eduardo\_Castegnaro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eduardo_castegnaro/32/711_2.png) [@Eduardo\_Castegnaro](https://discuss.elastic.co/u/Eduardo_Castegnaro)\
**Post date:** [May 11, 2015, 2:03pm UTC](https://discuss.elastic.co/t/upgrading-to-elastic-1-5-1-from-1-4-2-started-raising-classcastexception/23605/1 "2015-05-11T14:03:54Z")

</div>

Hi there!

I have a small cluster that was running fine on Elastic 1.4.2 and due to  
the stability improvements mentioned on 1.5 we decided to upgrade. The  
upgrade was done as a rolling upgrade (one instance at a time) and  
everything appeared to be going fine.

We don't use Logstash, but we do split our indexes by day. Once the day  
changed and a new index was automatically created we started getting a lot  
of these messages:

[2015-05-11 13:35:49,852][DEBUG][action.search.type] [elastic01] [  
events\_2015-03-17][2], node[8GzJ8I3YSAChFxmK9a4drQ], [R], s[STARTED]: Failed  
to execute [org.elasticsearch.action.search.SearchRequest@51be6ea0]  
lastShard [true]  
org.elasticsearch.transport.RemoteTransportException: [elastic03][inet[/  
192.168.171.33:9300]][indices:data/read/search[phase/query]]  
Caused by: java.lang.ClassCastException  
[2015-05-11 13:35:49,853][DEBUG][action.search.type] [elastic01] [  
events\_2015-03-17][0], node[8GzJ8I3YSAChFxmK9a4drQ], [P], s[STARTED]: Failed  
to execute [org.elasticsearch.action.search.SearchRequest@51be6ea0]  
lastShard [true]  
org.elasticsearch.transport.RemoteTransportException: [elastic03][inet[/  
192.168.171.33:9300]][indices:data/read/search[phase/query]]  
Caused by: java.lang.ClassCastException

We didn't modify our code at all, just upgraded the version of  
Elasticsearch running on the cluster.

Is this message harmless? What can I do to fix it or help you guys debug  
this?

Thanks in advance,

Eduardo Castegnaro.

## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/)

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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/0ebb7915-c44d-4119-a9b1-bc11038b9ee9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/0ebb7915-c44d-4119-a9b1-bc11038b9ee9%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![ppf2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ppf2/32/52219_2.png) [@ppf2](https://discuss.elastic.co/u/ppf2)\
**Post date:** [September 2, 2015, 1:57am UTC](https://discuss.elastic.co/t/upgrading-to-elastic-1-5-1-from-1-4-2-started-raising-classcastexception/23605/2 "2015-09-02T01:57:46Z")

</div>

There is usually a stack trace after the line "Caused by: java.lang.ClassCastException", can you include the full stack?

---

<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 5, 2017, 11:52pm UTC](https://discuss.elastic.co/t/upgrading-to-elastic-1-5-1-from-1-4-2-started-raising-classcastexception/23605/3 "2017-07-05T23:52:44Z")

</div>