# Problem after upgrade to 7.13.3 "source primary is allocated on another node" and CLONE\_TEMP\_TO\_TARGET -\> CLONE\_TEMP\_TO\_TARGET

**URL:** <https://discuss.elastic.co/t/problem-after-upgrade-to-7-13-3-source-primary-is-allocated-on-another-node-and-clone-temp-to-target-clone-temp-to-target/279404>\
**Category:** Elasticsearch\
**Created:** [July 22, 2021, 3:15pm UTC](https://discuss.elastic.co/t/problem-after-upgrade-to-7-13-3-source-primary-is-allocated-on-another-node-and-clone-temp-to-target-clone-temp-to-target/279404 "2021-07-22T15:15:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Petr.Simik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/petr.simik/32/38082_2.png) [@Petr.Simik](https://discuss.elastic.co/u/Petr.Simik)\
**Post date:** [July 22, 2021, 3:15pm UTC](https://discuss.elastic.co/t/problem-after-upgrade-to-7-13-3-source-primary-is-allocated-on-another-node-and-clone-temp-to-target-clone-temp-to-target/279404/1 "2021-07-22T15:15:54Z")

</div>

After we upgraded Elastic from 7.9 to 7.13.3 (on VM Centos7)  
all elasticsearch nodes has started but we couldnt start kibana  
the reason was it tries to migrate .kibana which si blocked by error  
"source primary is allocated on another node"  
all nodes reports this ERR

```auto
http://tela01prahkz:9200/_cluster/allocation/explain
		{
			"node_id": "NuCQClWsQ7CTuBvcP1yHqw",
			"node_name": "tela09prahkz",
			"transport_address": "10.44.163.19:9300",
			"node_attributes": {
				"ml.machine_memory": "33567297536",
				"ml.max_open_jobs": "512",
				"xpack.installed": "true",
				"ml.max_jvm_size": "16106127360",
				"data": "hot",
				"transform.node": "true"
			},
			"node_decision": "no",
			"weight_ranking": 13,
			"deciders": [
				{
					"decider": "resize",
					"decision": "NO",
					"explanation": "source primary is allocated on another node"
				}
			]
		},

```

KIBANA doesnt start it keeps writing this err

```auto

{"type":"log","@timestamp":"2021-07-22T17:57:18+02:00","tags":["error","savedobjects-service"],"pid":7145,"message":"[.kibana_task_manager] Action failed with 'Request timed out'. Retrying attempt 4 in 16 seconds."}
{"type":"log","@timestamp":"2021-07-22T17:57:18+02:00","tags":["info","savedobjects-service"],"pid":7145,"message":"[.kibana_task_manager] CLONE_TEMP_TO_TARGET -> CLONE_TEMP_TO_TARGET. took: 128019ms."}
{"type":"log","@timestamp":"2021-07-22T17:57:18+02:00","tags":["error","savedobjects-service"],"pid":7145,"message":"[.kibana] Action failed with 'Request timed out'. Retrying attempt 4 in 16 seconds."}
{"type":"log","@timestamp":"2021-07-22T17:57:18+02:00","tags":["info","savedobjects-service"],"pid":7145,"message":"[.kibana] CLONE_TEMP_TO_TARGET -> CLONE_TEMP_TO_TARGET. took: 128026ms."}

```

and .kibana shards are in Unassigned state

```auto
.kibana_7.13.3_001 0 r UNASSIGNED                                 
.kibana_7.13.3_001 0 p UNASSIGNED    

```

---

<div class="post-metadata">

**Author:** ![Petr.Simik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/petr.simik/32/38082_2.png) [@Petr.Simik](https://discuss.elastic.co/u/Petr.Simik)\
**Post date:** [July 23, 2021, 8:48am UTC](https://discuss.elastic.co/t/problem-after-upgrade-to-7-13-3-source-primary-is-allocated-on-another-node-and-clone-temp-to-target-clone-temp-to-target/279404/2 "2021-07-23T08:48:23Z")

</div>

We finally managed to succeed with upgrade to 7.13  
the problem seemed to be in `.kibana_x` . The upgrade process creates TEMP targets .kibana\_7.13.4\_reindex\_temp and then it creates final .kibana\_y index.  
We deleted all the `.kibana*reindex*` and we started back 7.9 version and it in some way created `.kibana_x+1`  
After that we tried to start 7.13.3 again and the upgrade process finished successfully.

---

<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:** [August 20, 2021, 8:48am UTC](https://discuss.elastic.co/t/problem-after-upgrade-to-7-13-3-source-primary-is-allocated-on-another-node-and-clone-temp-to-target-clone-temp-to-target/279404/3 "2021-08-20T08:48:54Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.