# Split API: shard sizing issue post split process

**URL:** <https://discuss.elastic.co/t/split-api-shard-sizing-issue-post-split-process/261526>\
**Category:** Elasticsearch\
**Created:** [January 19, 2021, 10:46am UTC](https://discuss.elastic.co/t/split-api-shard-sizing-issue-post-split-process/261526 "2021-01-19T10:46:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![elk11](https://avatars.discourse-cdn.com/v4/letter/e/45deac/32.png) [@elk11](https://discuss.elastic.co/u/elk11)\
**Post date:** [January 19, 2021, 10:46am UTC](https://discuss.elastic.co/t/split-api-shard-sizing-issue-post-split-process/261526/1 "2021-01-19T10:46:39Z")

</div>

Hi,

elasticsearch version: 7.3.1

I had an index of size 107GB with a single shard (replicas: 0, primary shards: 1). Since it was too large and messing up the load distribution (based on disk), I decided to use split-api to split it into 10 shards. I used the following query to do that:

```
POST /my_source_index/_split/my_target_index
{
  "settings": {
    "index.number_of_shards": 10
  }
}

```

The split itself was faster and initially all shards were shown to have 107GB size (in /\_cat/shards?v) but afterwards, as expected, most of them had around 10GB size except for two shards:

```
my_logs-000009-split 1 p STARTED 106914 107.9gb xx.xx.xx.73 node03
my_logs-000009-split 5 p STARTED 107611 10.8gb xx.xx.xx.73 node03
my_logs-000009-split 9 p STARTED 107303 10.8gb xx.xx.xx.71 node01
my_logs-000009-split 7 p STARTED 107258 10.7gb xx.xx.xx.68 node05
my_logs-000009-split 3 p STARTED 106939 10.5gb xx.xx.xx.68 node05
my_logs-000009-split 8 p STARTED 107859 11gb xx.xx.xx.71 node01
my_logs-000009-split 4 p STARTED 107100 10.8gb xx.xx.xx.62 node04
my_logs-000009-split 2 p STARTED 107056 11.1gb xx.xx.xx.72 node02
my_logs-000009-split 6 p STARTED 107179 10.9gb xx.xx.xx.72 node02
my_logs-000009-split 0 p STARTED 106868 107.9gb xx.xx.xx.62 node04

```

As you can see shard 0 and 1 still show 107GB size even after 24 hrs! Why is this behavior?

And also, I see original index, that is, `my_logs-000009` is still around. Doesn't split api delete it after splitting?

Thanks!

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 20, 2021, 9:58pm UTC](https://discuss.elastic.co/t/split-api-shard-sizing-issue-post-split-process/261526/2 "2021-01-20T21:58:57Z")

</div>

Can you run a force merge on the index and see if that helps?

> [@elk11](#):
>
> And also, I see original index, that is, `my_logs-000009` is still around. Doesn't split api delete it after splitting?

It does not.

---

<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:** [February 17, 2021, 9:58pm UTC](https://discuss.elastic.co/t/split-api-shard-sizing-issue-post-split-process/261526/3 "2021-02-17T21:58:58Z")

</div>

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