# Scaling up for petabyte sizes? **URL:** \ **Category:** Elasticsearch\ **Created:** [April 30, 2018, 4:31pm UTC](https://discuss.elastic.co/t/scaling-up-for-petabyte-sizes/130047 "2018-04-30T16:31:51Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![lvic](https://avatars.discourse-cdn.com/v4/letter/l/0ea827/32.png) [@lvic](https://discuss.elastic.co/u/lvic)\ **Post date:** [April 30, 2018, 4:31pm UTC](https://discuss.elastic.co/t/scaling-up-for-petabyte-sizes/130047/1 "2018-04-30T16:31:52Z")
Had a performance problem: ES queries become really slow when dataset size grew to several petabytes... What approach can I use to scale up for larger datasets while preserving original data? For example: is it possible to increase number of primary shards for running ES? Thank you, ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [April 30, 2018, 4:34pm UTC](https://discuss.elastic.co/t/scaling-up-for-petabyte-sizes/130047/2 "2018-04-30T16:34:21Z")
How much data did you have? How many nodes? Did you identify what was limiting performance (CPU, memory, network, disk)? ---
**Author:** ![lvic](https://avatars.discourse-cdn.com/v4/letter/l/0ea827/32.png) [@lvic](https://discuss.elastic.co/u/lvic)\ **Post date:** [April 30, 2018, 6:17pm UTC](https://discuss.elastic.co/t/scaling-up-for-petabyte-sizes/130047/3 "2018-04-30T18:17:35Z")
3 nodes / 3 primary shards. Don't see resource over utilization(s) as such, probably the most limiting one is disk usage - ES data takes ~80% of available disk space ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [April 30, 2018, 6:24pm UTC](https://discuss.elastic.co/t/scaling-up-for-petabyte-sizes/130047/4 "2018-04-30T18:24:46Z")
> [@lvic](#): > > Had a performance problem: ES queries become really slow when dataset size grew to several petabytes How is this related to the 3 node cluster? ---
**Author:** ![lvic](https://avatars.discourse-cdn.com/v4/letter/l/0ea827/32.png) [@lvic](https://discuss.elastic.co/u/lvic)\ **Post date:** [April 30, 2018, 6:35pm UTC](https://discuss.elastic.co/t/scaling-up-for-petabyte-sizes/130047/5 "2018-04-30T18:35:45Z")
Sorry, not sure i understand ---
**Author:** ![lvic](https://avatars.discourse-cdn.com/v4/letter/l/0ea827/32.png) [@lvic](https://discuss.elastic.co/u/lvic)\ **Post date:** [April 30, 2018, 6:38pm UTC](https://discuss.elastic.co/t/scaling-up-for-petabyte-sizes/130047/6 "2018-04-30T18:38:06Z")
Here's the general question: is it possible to increase cluster/sharding size while preserving existing data? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [April 30, 2018, 6:38pm UTC](https://discuss.elastic.co/t/scaling-up-for-petabyte-sizes/130047/7 "2018-04-30T18:38:34Z")
You said you had performance problems when the dataset grew to several [petabytes](https://en.wikipedia.org/wiki/Petabyte). That is clearly not possible with the 3 nodes you then mentioned, which leaves me confused. ---
**Author:** ![lvic](https://avatars.discourse-cdn.com/v4/letter/l/0ea827/32.png) [@lvic](https://discuss.elastic.co/u/lvic)\ **Post date:** [April 30, 2018, 6:39pm UTC](https://discuss.elastic.co/t/scaling-up-for-petabyte-sizes/130047/8 "2018-04-30T18:39:53Z")
Sorry, my bad. I mean 3 replicas ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [April 30, 2018, 6:41pm UTC](https://discuss.elastic.co/t/scaling-up-for-petabyte-sizes/130047/9 "2018-04-30T18:41:34Z")
I still do not understand. Can you please clarify? How much data did you have in the cluster? How many nodes were used? ---
**Author:** ![lvic](https://avatars.discourse-cdn.com/v4/letter/l/0ea827/32.png) [@lvic](https://discuss.elastic.co/u/lvic)\ **Post date:** [April 30, 2018, 6:45pm UTC](https://discuss.elastic.co/t/scaling-up-for-petabyte-sizes/130047/10 "2018-04-30T18:45:23Z")
close to 2 petabytes of data, 3 nodes. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [April 30, 2018, 6:45pm UTC](https://discuss.elastic.co/t/scaling-up-for-petabyte-sizes/130047/11 "2018-04-30T18:45:44Z")
That is not possible. Are you mixing up your units? Is it by any chance 2 terabytes? Easiest way to determine the data amount id probably to provide us the full output of the [cluster stats API](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-stats.html). ---
**Author:** ![lvic](https://avatars.discourse-cdn.com/v4/letter/l/0ea827/32.png) [@lvic](https://discuss.elastic.co/u/lvic)\ **Post date:** [April 30, 2018, 6:50pm UTC](https://discuss.elastic.co/t/scaling-up-for-petabyte-sizes/130047/12 "2018-04-30T18:50:36Z")
Why is it not possible? Is there some limit? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [April 30, 2018, 6:56pm UTC](https://discuss.elastic.co/t/scaling-up-for-petabyte-sizes/130047/13 "2018-04-30T18:56:37Z")
Please provide the output from the API I linked to. ---
**Author:** ![Mike.Barretta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mike.barretta/32/16688_2.png) [@Mike.Barretta](https://discuss.elastic.co/u/Mike.Barretta)\ **Post date:** [May 4, 2018, 8:03pm UTC](https://discuss.elastic.co/t/scaling-up-for-petabyte-sizes/130047/14 "2018-05-04T20:03:03Z")
@lvic if you just want to know how to change the shard count of an existing index, see: - [Split Index](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/indices-split-index.html) - [Shrink Index](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/indices-shrink-index.html) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 1, 2018, 8:03pm UTC](https://discuss.elastic.co/t/scaling-up-for-petabyte-sizes/130047/15 "2018-06-01T20:03:08Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.