# Upgrade migration path?

**URL:** <https://discuss.elastic.co/t/upgrade-migration-path/3664>\
**Category:** Elasticsearch\
**Created:** [December 14, 2010, 10:52pm UTC](https://discuss.elastic.co/t/upgrade-migration-path/3664 "2010-12-14T22:52:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![IvanBrusic](https://avatars.discourse-cdn.com/v4/letter/i/ecae2f/32.png) [@IvanBrusic](https://discuss.elastic.co/u/IvanBrusic)\
**Post date:** [December 14, 2010, 10:52pm UTC](https://discuss.elastic.co/t/upgrade-migration-path/3664/1 "2010-12-14T22:52:13Z")

</div>

Due to a change in the API, I decided to upgrade from 0.12.1 to  
0.13.1. I copied the entire work directory plus my custom mappings  
from config into the new install directory.

Startup seems fine, but my client is showing issues:

17:49:45.846 [New I/O client worker #1-1] WARN transport.netty -  
[Warlock] Message not fully read (response) for [0] handler  
org.elasticsearch.client.transport.TransportClientNodesService  
$ScheduledNodesSampler$1$1@2e56c4eb, error [false], resetting  
17:49:45,858 ERROR ~ Missing ad hosts file: data/adhosts/adhosts.dat  
17:49:46.725 [New I/O client worker #1-1] WARN transport.netty -  
[Warlock] Message not fully read (response) for [1] handler  
org.elasticsearch.client.transport.TransportClientNodesService  
$ScheduledNodesSampler$1$1@3267b4ba, error [false], resetting  
17:49:47.728 [New I/O client worker #1-1] WARN transport.netty -  
[Warlock] Message not fully read (response) for [2] handler  
org.elasticsearch.client.transport.TransportClientNodesService  
$ScheduledNodesSampler$1$1@1cbcfd, error [false], resetting  
17:49:48.731 [New I/O client worker #1-1] WARN transport.netty -  
[Warlock] Message not fully read (response) for [3] handler  
org.elasticsearch.client.transport.TransportClientNodesService  
$ScheduledNodesSampler$1$1@696103e5, error [false], resetting  
17:49:49.732 [New I/O client worker #1-1] WARN transport.netty -  
[Warlock] Message not fully read (response) for [4] handler  
org.elasticsearch.client.transport.TransportClientNodesService  
$ScheduledNodesSampler$1$1@6046e56f, error [false], resetting  
...

> <https://gist.github.com/ibrusic/741273>

Java code is simple:

```
String ELASTIC_SEARCH_HOST = "localhost"
int ELASTIC_SEARCH_PORT = 9300

TransportClient client = new

```

TransportClient().addTransportAddress(new  
InetSocketTransportAddress(ELASTIC\_SEARCH\_HOST, ELASTIC\_SEARCH\_PORT))

Is copying the work directory acceptable when moving from 0.12.1 to  
0.13.1?

Cheers,

Ivan

---

<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:** [December 15, 2010, 5:41pm UTC](https://discuss.elastic.co/t/upgrade-migration-path/3664/2 "2010-12-15T17:41:54Z")

</div>

Have you looked at the upgrade notes (work became data)? Also, are you sure  
you are running the same version of ES on the client and server side?

On Wednesday, December 15, 2010 at 12:52 AM, Ivan Brusic wrote:

Due to a change in the API, I decided to upgrade from 0.12.1 to  
0.13.1. I copied the entire work directory plus my custom mappings  
from config into the new install directory.

Startup seems fine, but my client is showing issues:

17:49:45.846 [New I/O client worker #1-1] WARN transport.netty -  
[Warlock] Message not fully read (response) for [0] handler  
org.elasticsearch.client.transport.TransportClientNodesService  
$ScheduledNodesSampler$1$1@2e56c4eb, error [false], resetting  
17:49:45,858 ERROR ~ Missing ad hosts file: data/adhosts/adhosts.dat  
17:49:46.725 [New I/O client worker #1-1] WARN transport.netty -  
[Warlock] Message not fully read (response) for [1] handler  
org.elasticsearch.client.transport.TransportClientNodesService  
$ScheduledNodesSampler$1$1@3267b4ba, error [false], resetting  
17:49:47.728 [New I/O client worker #1-1] WARN transport.netty -  
[Warlock] Message not fully read (response) for [2] handler  
org.elasticsearch.client.transport.TransportClientNodesService  
$ScheduledNodesSampler$1$1@1cbcfd, error [false], resetting  
17:49:48.731 [New I/O client worker #1-1] WARN transport.netty -  
[Warlock] Message not fully read (response) for [3] handler  
org.elasticsearch.client.transport.TransportClientNodesService  
$ScheduledNodesSampler$1$1@696103e5, error [false], resetting  
17:49:49.732 [New I/O client worker #1-1] WARN transport.netty -  
[Warlock] Message not fully read (response) for [4] handler  
org.elasticsearch.client.transport.TransportClientNodesService  
$ScheduledNodesSampler$1$1@6046e56f, error [false], resetting  
...

> <https://gist.github.com/ibrusic/741273>

Java code is simple:

String ELASTIC\_SEARCH\_HOST = "localhost"  
int ELASTIC\_SEARCH\_PORT = 9300

TransportClient client = new  
TransportClient().addTransportAddress(new  
InetSocketTransportAddress(ELASTIC\_SEARCH\_HOST, ELASTIC\_SEARCH\_PORT))

Is copying the work directory acceptable when moving from 0.12.1 to  
0.13.1?

Cheers,

Ivan

---

<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:15am UTC](https://discuss.elastic.co/t/upgrade-migration-path/3664/3 "2017-07-06T04:15:18Z")

</div>

Closed on July 6, 2017, 4:15am UTC