-
Notifications
You must be signed in to change notification settings - Fork 25k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
restoration from a snapshot is failing #15432
Comments
What version of Elasticsearch are you using? |
I am using 1.7.0 |
@binishabraham anything in the log file on master? |
Please find more details I used to restore the snapshot from one cluster to three other clusters. Saw the following error during restoration from that particulat snapshot to last cluster {"error":"MasterNotDiscoveredException[]","status":503} But even after this exception I was able to find all the documents in the last cluster also. Count of documents equal to other three clusters. From the next day snapshot onwards, I am getting the following exception for the fourth cluster {"error":"RemoteTransportException[[app-wc-b2p.sys.company.net][inet[/172.28.74.70:9300]][cluster:admin/repository/put]]; nested: ElasticsearchIllegalStateException[trying to modify or unregister repository that is currently used ]; ","status":500} % Total % Received % Xferd Average Speed Time Time Time Current But cluster-2 and cluster-3 restores it successfully from same snapshot. Exception from same day's ES log. -bash-4.1$ grep Exception es-prd-b-cluster.log.2015-12-07 I have the following questions as part of immediate fix
|
@binishabraham could you post here or send me by email the output of the following command as well as complete log from the master node?
|
@imotov I am using 7 node cluster. 5 - data nodes eligible to become master. 2 - client nodes Log from master GET _cluster/state/routing_table,customs |
@binishabraham What happened to the |
@imotov It was a mistake in my replacement |
@binishabraham could you try closing and opening the company index to see if it will get recovery process unstuck? |
@binishabraham any updates? |
@imotov I tried, but didn't workout. So deleted the index 'indexname' and restored it using the snapshot from similar ES cluster from another Farm. |
No further info. Closing |
I am getting the following exception while doing a restoration
curl -XPOST "http://hostname1:9200/_snapshot/snapshot_restore_repo/snapshot_07_12_15_17_08_56/_restore"
{"error":"RemoteTransportException[[hostname2][inet[/ipaddress:9300]][cluster:admin/snapshot/restore]]; nested: ConcurrentSnapshotExecutionException[[snapshot_restore_repo:snapshot_07_12_15_17_08_56] Restore process is already running in this cluster]; ","status":503}-bash-4.1$
Cluster state is shown below
GET _cluster/state
"restore": {
"snapshots": [
{
"snapshot": "snapshot_07_12_15_17_08_56",
"repository": "snapshot_restore_repo",
"state": "STARTED",
"indices": [
"indexname"
],
"shards": [
{
"index": "indexname",
"shard": 0,
"state": "SUCCESS"
},
{
"index": "indexname",
"shard": 1,
"state": "SUCCESS"
},
{
"index": "indexname",
"shard": 2,
"state": "INIT"
},
{
"index": "indexname",
"shard": 3,
"state": "SUCCESS"
},
{
"index": "indexname",
"shard": 4,
"state": "SUCCESS"
}
]
}
]
}
How to come out of "INIT" and complete restoration
The text was updated successfully, but these errors were encountered: