# Restore from s3\_repository stops part way through

**URL:** <https://discuss.elastic.co/t/restore-from-s3-repository-stops-part-way-through/151414>\
**Category:** Elasticsearch\
**Created:** [October 8, 2018, 9:23am UTC](https://discuss.elastic.co/t/restore-from-s3-repository-stops-part-way-through/151414 "2018-10-08T09:23:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Martin\_Stevens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/martin_stevens/32/5117_2.png) [@Martin\_Stevens](https://discuss.elastic.co/u/Martin_Stevens)\
**Post date:** [October 8, 2018, 9:23am UTC](https://discuss.elastic.co/t/restore-from-s3-repository-stops-part-way-through/151414/1 "2018-10-08T09:23:06Z")

</div>

Hi,

We are trying to recover from an s3\_repository however some of the indexes never get past a certain point, we install es with ansible and then packer the ami, then spin up a new box with a larger disk.

The restore process always jams up on the same indexes a the same point.

1st Run on new ec2 instance

```auto
1st Run

news 0 4.3s snapshot done n/a n/a 172.31.46.121 YIuL9Ew s3_repository full_snapshot_20181002_121100 39 39 100.0% 39 2491209 2491209 100.0% 2491209 0 0 100.0%
news 1 3.6s snapshot done n/a n/a 172.31.46.121 YIuL9Ew s3_repository full_snapshot_20181002_121100 36 36 100.0% 36 2566507 2566507 100.0% 2566507 0 0 100.0%
news 2 3.9s snapshot done n/a n/a 172.31.46.121 YIuL9Ew s3_repository full_snapshot_20181002_121100 41 41 100.0% 41 2533518 2533518 100.0% 2533518 0 0 100.0%
news 3 3.2s snapshot done n/a n/a 172.31.46.121 YIuL9Ew s3_repository full_snapshot_20181002_121100 24 24 100.0% 24 2359775 2359775 100.0% 2359775 0 0 100.0%
news 4 4.2s snapshot done n/a n/a 172.31.46.121 YIuL9Ew s3_repository full_snapshot_20181002_121100 38 38 100.0% 38 2359664 2359664 100.0% 2359664 0 0 100.0%
transcripts 0 51.8s snapshot done n/a n/a 172.31.46.121 YIuL9Ew s3_repository full_snapshot_20181002_121100 72 72 100.0% 72 1140938490 1140938490 100.0% 1140938490 0 0 100.0%
transcripts 1 52.3s snapshot done n/a n/a 172.31.46.121 YIuL9Ew s3_repository full_snapshot_20181002_121100 83 83 100.0% 83 1145127154 1145127154 100.0% 1145127154 0 0 100.0%
transcripts 2 1m snapshot done n/a n/a 172.31.46.121 YIuL9Ew s3_repository full_snapshot_20181002_121100 89 89 100.0% 89 1142664174 1142664174 100.0% 1142664174 0 0 100.0%
transcripts 3 53.3s snapshot done n/a n/a 172.31.46.121 YIuL9Ew s3_repository full_snapshot_20181002_121100 75 75 100.0% 75 1156088690 1156088690 100.0% 1156088690 0 0 100.0%
transcripts 4 4m snapshot index n/a n/a 172.31.46.121 YIuL9Ew s3_repository full_snapshot_20181002_121100 87 7 8.0% 87 1132775561 653857166 57.7% 1132775561 0 0 100.0%
edgar 0 11.9m snapshot index n/a n/a 172.31.46.121 YIuL9Ew s3_repository full_snapshot_20181002_121100 167 23 13.8% 167 2270559236 580570940 25.6% 2270559236 0 0 100.0%
edgar 1 11.9m snapshot index n/a n/a 172.31.46.121 YIuL9Ew s3_repository full_snapshot_20181002_121100 89 48 53.9% 89 2285799498 153191569 6.7% 2285799498 0 0 100.0%
edgar 2 11.9m snapshot index n/a n/a 172.31.46.121 YIuL9Ew s3_repository full_snapshot_20181002_121100 190 2 1.1% 190 2315607352 128042801 5.5% 2315607352 0 0 100.0%
edgar 3 2.3m snapshot done n/a n/a 172.31.46.121 YIuL9Ew s3_repository full_snapshot_20181002_121100 184 184 100.0% 184 2295838134 2295838134 100.0% 2295838134 0 0 100.0%
edgar 4 1.7m snapshot done n/a n/a 172.31.46.121 YIuL9Ew s3_repository full_snapshot_20181002_121100 158 158 100.0% 158 2278318029 2278318029 100.0% 2278318029 0 0 100.0%

```

2nd run on another ec2 instance

```auto
news 0 5.1s snapshot done n/a n/a 172.31.44.158 YIuL9Ew s3_repository full_snapshot_20181002_121100 39 39 100.0% 39 2491209 2491209 100.0% 2491209 0 0 100.0%
news 1 4.9s snapshot done n/a n/a 172.31.44.158 YIuL9Ew s3_repository full_snapshot_20181002_121100 36 36 100.0% 36 2566507 2566507 100.0% 2566507 0 0 100.0%
news 2 5.2s snapshot done n/a n/a 172.31.44.158 YIuL9Ew s3_repository full_snapshot_20181002_121100 41 41 100.0% 41 2533518 2533518 100.0% 2533518 0 0 100.0%
news 3 3.9s snapshot done n/a n/a 172.31.44.158 YIuL9Ew s3_repository full_snapshot_20181002_121100 24 24 100.0% 24 2359775 2359775 100.0% 2359775 0 0 100.0%
news 4 3.4s snapshot done n/a n/a 172.31.44.158 YIuL9Ew s3_repository full_snapshot_20181002_121100 38 38 100.0% 38 2359664 2359664 100.0% 2359664 0 0 100.0%
edgar 0 16.7m snapshot index n/a n/a 172.31.44.158 YIuL9Ew s3_repository full_snapshot_20181002_121100 167 21 12.6% 167 2270559236 418857037 18.4% 2270559236 0 0 100.0%
edgar 1 16.7m snapshot index n/a n/a 172.31.44.158 YIuL9Ew s3_repository full_snapshot_20181002_121100 89 48 53.9% 89 2285799498 994567201 43.5% 2285799498 0 0 100.0%
edgar 2 16.7m snapshot index n/a n/a 172.31.44.158 YIuL9Ew s3_repository full_snapshot_20181002_121100 190 2 1.1% 190 2315607352 145929225 6.3% 2315607352 0 0 100.0%
edgar 3 16.7m snapshot index n/a n/a 172.31.44.158 YIuL9Ew s3_repository full_snapshot_20181002_121100 184 8 4.3% 184 2295838134 142034298 6.2% 2295838134 0 0 100.0%

```

We seem to have enough disk space.

```auto
shards disk.indices disk.used disk.avail disk.total disk.percent host ip node
     9 1.5gb 4.4gb 111.8gb 116.2gb 3 172.31.44.158 172.31.44.158 YIuL9Ew
    21 UNASSIGNED

```

```auto
Filesystem Size Used Avail Use% Mounted on
udev 2.0G 0 2.0G 0% /dev
tmpfs 395M 712K 394M 1% /run
/dev/xvda1 117G 4.5G 112G 4% /

```

```auto
And the snashot looks good.

   {
      "snapshot" : "full_snapshot_20181002_121100",
      "uuid" : "IA74nkvtQUGQzGzUUAGoBw",
      "version_id" : 6020499,
      "version" : "6.2.4",
      "indices" : [
        "transcripts",
        "news",
        "edgar"
      ],
      "include_global_state" : false,
      "state" : "SUCCESS",
      "start_time" : "2018-10-02T11:12:21.764Z",
      "start_time_in_millis" : 1538478741764,
      "end_time" : "2018-10-02T11:12:25.460Z",
      "end_time_in_millis" : 1538478745460,
      "duration_in_millis" : 3696,
      "failures" : [],
      "shards" : {
        "total" : 15,
        "failed" : 0,
        "successful" : 15
      }
    }

```

---

<div class="post-metadata">

**Author:** ![ywelsch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ywelsch/32/7751_2.png) [@ywelsch](https://discuss.elastic.co/u/ywelsch)\
**Post date:** [October 12, 2018, 9:08am UTC](https://discuss.elastic.co/t/restore-from-s3-repository-stops-part-way-through/151414/2 "2018-10-12T09:08:24Z")

</div>

Have you looked at the logs on the individual nodes? Can you check hot\_threads to see if something is getting stuck on the nodes?

---

<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:** [November 9, 2018, 9:08am UTC](https://discuss.elastic.co/t/restore-from-s3-repository-stops-part-way-through/151414/3 "2018-11-09T09:08:25Z")

</div>

Closed on November 9, 2018, 9:08am UTC

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