# Non-Uniform Drive Space Across Nodes **URL:** \ **Category:** Elasticsearch\ **Created:** [June 12, 2014, 12:27pm UTC](https://discuss.elastic.co/t/non-uniform-drive-space-across-nodes/18065 "2014-06-12T12:27:44Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![ES\_USER1](https://avatars.discourse-cdn.com/v4/letter/e/74df32/32.png) [@ES\_USER1](https://discuss.elastic.co/u/ES_USER1)\ **Post date:** [June 12, 2014, 12:27pm UTC](https://discuss.elastic.co/t/non-uniform-drive-space-across-nodes/18065/1 "2014-06-12T12:27:44Z")
How does Elasticsearch handle nodes that do not have the same amount of disk space on each node. Looking at the example below does ES limit storage to that of the smaller one or does it make use of all the space just allocating the shards accordingly? Or is it even smart enough to take disk space into consideration at all? Node 1 - 1 TB Node 2 - 750 GB Node 3 - 500 GB -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/8ed0d604-a8b4-41a0-924d-7d8af030fcd5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8ed0d604-a8b4-41a0-924d-7d8af030fcd5%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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:** [June 12, 2014, 10:37pm UTC](https://discuss.elastic.co/t/non-uniform-drive-space-across-nodes/18065/2 "2014-06-12T22:37:04Z")
Yes, take a look at > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. Although the docs mention coming in 1.3, I could have sworn it was still available for 1.2. On a general note, ES should distribute things evenly across all nodes, however I have noticed similar things on some of our nodes. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 12 June 2014 22:27, ES USER [es.user.2014@gmail.com](mailto:es.user.2014@gmail.com) wrote: > How does Elasticsearch handle nodes that do not have the same amount of > disk space on each node. Looking at the example below does ES limit > storage to that of the smaller one or does it make use of all the space > just allocating the shards accordingly? > Or is it even smart enough to take disk space into consideration at all? > > Node 1 - 1 TB > Node 2 - 750 GB > Node 3 - 500 GB > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/8ed0d604-a8b4-41a0-924d-7d8af030fcd5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8ed0d604-a8b4-41a0-924d-7d8af030fcd5%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/8ed0d604-a8b4-41a0-924d-7d8af030fcd5%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/8ed0d604-a8b4-41a0-924d-7d8af030fcd5%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624Yqo5YELaNzhZzYCiAfFEU-fRdM-Xsfn9AT-K-uLCpiuA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624Yqo5YELaNzhZzYCiAfFEU-fRdM-Xsfn9AT-K-uLCpiuA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [June 12, 2014, 11:00pm UTC](https://discuss.elastic.co/t/non-uniform-drive-space-across-nodes/18065/3 "2014-06-12T23:00:54Z")
The disk threshold stuff has been available since sometime in 0.90. In 1.3 it'll be on by default. It works by stopping allocation to shards with disks over a watermark and moving shards off nodes that are over another higher mark. Meaning elasticsearch won't try to balance usage. Just keep from filling up disk. It's a somewhat fine distinction but a real one. On Jun 12, 2014 6:37 PM, "Mark Walkom" [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) wrote: > Yes, take a look at > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-allocation.html#disk) > Although the docs mention coming in 1.3, I could have sworn it was still > available for 1.2. > > On a general note, ES should distribute things evenly across all nodes, > however I have noticed similar things on some of our nodes. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > On 12 June 2014 22:27, ES USER [es.user.2014@gmail.com](mailto:es.user.2014@gmail.com) wrote: > > > How does Elasticsearch handle nodes that do not have the same amount of > > disk space on each node. Looking at the example below does ES limit > > storage to that of the smaller one or does it make use of all the space > > just allocating the shards accordingly? > > Or is it even smart enough to take disk space into consideration at all? > > > > Node 1 - 1 TB > > Node 2 - 750 GB > > Node 3 - 500 GB > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/8ed0d604-a8b4-41a0-924d-7d8af030fcd5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8ed0d604-a8b4-41a0-924d-7d8af030fcd5%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/8ed0d604-a8b4-41a0-924d-7d8af030fcd5%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/8ed0d604-a8b4-41a0-924d-7d8af030fcd5%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAEM624Yqo5YELaNzhZzYCiAfFEU-fRdM-Xsfn9AT-K-uLCpiuA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624Yqo5YELaNzhZzYCiAfFEU-fRdM-Xsfn9AT-K-uLCpiuA%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAEM624Yqo5YELaNzhZzYCiAfFEU-fRdM-Xsfn9AT-K-uLCpiuA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEM624Yqo5YELaNzhZzYCiAfFEU-fRdM-Xsfn9AT-K-uLCpiuA%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1zx7hNzfgd-ZN%3Doq-VzGUCUXXNr%3D5Bc2x9uNL9mVMNgw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1zx7hNzfgd-ZN%3Doq-VzGUCUXXNr%3D5Bc2x9uNL9mVMNgw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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:** [June 12, 2014, 11:26pm UTC](https://discuss.elastic.co/t/non-uniform-drive-space-across-nodes/18065/4 "2014-06-12T23:26:09Z")
What's the ideal way to diagnose the initial problem stated? I can see in our cluster we have a node with 43GB (of 500) free, yet most others have around 100GB free (of 500). I can see the shard count per node (using \_cat/shards) seems to roughly the same, but could it be because some of our shards are just different sizes? In the case of the OP though, a 500GB difference seems difficult to explain. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 13 June 2014 09:00, Nikolas Everett [nik9000@gmail.com](mailto:nik9000@gmail.com) wrote: > The disk threshold stuff has been available since sometime in 0.90. In 1.3 > it'll be on by default. It works by stopping allocation to shards with > disks over a watermark and moving shards off nodes that are over another > higher mark. Meaning elasticsearch won't try to balance usage. Just keep > from filling up disk. It's a somewhat fine distinction but a real one. > On Jun 12, 2014 6:37 PM, "Mark Walkom" [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) wrote: > > > Yes, take a look at > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-allocation.html#disk) > > Although the docs mention coming in 1.3, I could have sworn it was still > > available for 1.2. > > > > On a general note, ES should distribute things evenly across all nodes, > > however I have noticed similar things on some of our nodes. > > > > Regards, > > Mark Walkom > > > > Infrastructure Engineer > > Campaign Monitor > > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > > > On 12 June 2014 22:27, ES USER [es.user.2014@gmail.com](mailto:es.user.2014@gmail.com) wrote: > > > > > How does Elasticsearch handle nodes that do not have the same amount of > > > disk space on each node. Looking at the example below does ES limit > > > storage to that of the smaller one or does it make use of all the space > > > just allocating the shards accordingly? > > > Or is it even smart enough to take disk space into consideration at all? > > > > > > Node 1 - 1 TB > > > Node 2 - 750 GB > > > Node 3 - 500 GB > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send > > > an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/8ed0d604-a8b4-41a0-924d-7d8af030fcd5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8ed0d604-a8b4-41a0-924d-7d8af030fcd5%40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/8ed0d604-a8b4-41a0-924d-7d8af030fcd5%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/8ed0d604-a8b4-41a0-924d-7d8af030fcd5%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/CAEM624Yqo5YELaNzhZzYCiAfFEU-fRdM-Xsfn9AT-K-uLCpiuA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624Yqo5YELaNzhZzYCiAfFEU-fRdM-Xsfn9AT-K-uLCpiuA%40mail.gmail.com) > > [https://groups.google.com/d/msgid/elasticsearch/CAEM624Yqo5YELaNzhZzYCiAfFEU-fRdM-Xsfn9AT-K-uLCpiuA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEM624Yqo5YELaNzhZzYCiAfFEU-fRdM-Xsfn9AT-K-uLCpiuA%40mail.gmail.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1zx7hNzfgd-ZN%3Doq-VzGUCUXXNr%3D5Bc2x9uNL9mVMNgw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1zx7hNzfgd-ZN%3Doq-VzGUCUXXNr%3D5Bc2x9uNL9mVMNgw%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1zx7hNzfgd-ZN%3Doq-VzGUCUXXNr%3D5Bc2x9uNL9mVMNgw%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1zx7hNzfgd-ZN%3Doq-VzGUCUXXNr%3D5Bc2x9uNL9mVMNgw%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624ZZz5NyYYHVg8OW6JEV4vkgKNnK28wtWiWOX5kD05Pzeg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624ZZz5NyYYHVg8OW6JEV4vkgKNnK28wtWiWOX5kD05Pzeg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [June 13, 2014, 1:44am UTC](https://discuss.elastic.co/t/non-uniform-drive-space-across-nodes/18065/5 "2014-06-13T01:44:58Z")
I'm not sure what problem you mean. If you mean that you have uneven disk utilization then I don't think there is something for that. You could raise the index weight in the allocation weights. That'd spread the shards of each index out more evenly. It might help. On Jun 12, 2014 7:26 PM, "Mark Walkom" [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) wrote: > What's the ideal way to diagnose the initial problem stated? > > I can see in our cluster we have a node with 43GB (of 500) free, yet most > others have around 100GB free (of 500). I can see the shard count per node > (using \_cat/shards) seems to roughly the same, but could it be because some > of our shards are just different sizes? > In the case of the OP though, a 500GB difference seems difficult to > explain. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > On 13 June 2014 09:00, Nikolas Everett [nik9000@gmail.com](mailto:nik9000@gmail.com) wrote: > > > The disk threshold stuff has been available since sometime in 0.90. In > > 1.3 it'll be on by default. It works by stopping allocation to shards with > > disks over a watermark and moving shards off nodes that are over another > > higher mark. Meaning elasticsearch won't try to balance usage. Just keep > > from filling up disk. It's a somewhat fine distinction but a real one. > > On Jun 12, 2014 6:37 PM, "Mark Walkom" [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) wrote: > > > > > Yes, take a look at > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-allocation.html#disk) > > > Although the docs mention coming in 1.3, I could have sworn it was still > > > available for 1.2. > > > > > > On a general note, ES should distribute things evenly across all nodes, > > > however I have noticed similar things on some of our nodes. > > > > > > Regards, > > > Mark Walkom > > > > > > Infrastructure Engineer > > > Campaign Monitor > > > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > > > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > > > > > On 12 June 2014 22:27, ES USER [es.user.2014@gmail.com](mailto:es.user.2014@gmail.com) wrote: > > > > > > > How does Elasticsearch handle nodes that do not have the same amount of > > > > disk space on each node. Looking at the example below does ES limit > > > > storage to that of the smaller one or does it make use of all the space > > > > just allocating the shards accordingly? > > > > Or is it even smart enough to take disk space into consideration at all? > > > > > > > > Node 1 - 1 TB > > > > Node 2 - 750 GB > > > > Node 3 - 500 GB > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "elasticsearch" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > > To view this discussion on the web visit > > > > [https://groups.google.com/d/msgid/elasticsearch/8ed0d604-a8b4-41a0-924d-7d8af030fcd5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8ed0d604-a8b4-41a0-924d-7d8af030fcd5%40googlegroups.com) > > > > [https://groups.google.com/d/msgid/elasticsearch/8ed0d604-a8b4-41a0-924d-7d8af030fcd5%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/8ed0d604-a8b4-41a0-924d-7d8af030fcd5%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send > > > an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/CAEM624Yqo5YELaNzhZzYCiAfFEU-fRdM-Xsfn9AT-K-uLCpiuA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624Yqo5YELaNzhZzYCiAfFEU-fRdM-Xsfn9AT-K-uLCpiuA%40mail.gmail.com) > > > [https://groups.google.com/d/msgid/elasticsearch/CAEM624Yqo5YELaNzhZzYCiAfFEU-fRdM-Xsfn9AT-K-uLCpiuA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEM624Yqo5YELaNzhZzYCiAfFEU-fRdM-Xsfn9AT-K-uLCpiuA%40mail.gmail.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1zx7hNzfgd-ZN%3Doq-VzGUCUXXNr%3D5Bc2x9uNL9mVMNgw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1zx7hNzfgd-ZN%3Doq-VzGUCUXXNr%3D5Bc2x9uNL9mVMNgw%40mail.gmail.com) > > [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1zx7hNzfgd-ZN%3Doq-VzGUCUXXNr%3D5Bc2x9uNL9mVMNgw%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1zx7hNzfgd-ZN%3Doq-VzGUCUXXNr%3D5Bc2x9uNL9mVMNgw%40mail.gmail.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAEM624ZZz5NyYYHVg8OW6JEV4vkgKNnK28wtWiWOX5kD05Pzeg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624ZZz5NyYYHVg8OW6JEV4vkgKNnK28wtWiWOX5kD05Pzeg%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAEM624ZZz5NyYYHVg8OW6JEV4vkgKNnK28wtWiWOX5kD05Pzeg%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEM624ZZz5NyYYHVg8OW6JEV4vkgKNnK28wtWiWOX5kD05Pzeg%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1NJJjCBnmZ8ST7bACkoZ9UY-\_keKQn49FijGPQDBArPA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1NJJjCBnmZ8ST7bACkoZ9UY-_keKQn49FijGPQDBArPA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![ES\_USER1](https://avatars.discourse-cdn.com/v4/letter/e/74df32/32.png) [@ES\_USER1](https://discuss.elastic.co/u/ES_USER1)\ **Post date:** [June 13, 2014, 4:55pm UTC](https://discuss.elastic.co/t/non-uniform-drive-space-across-nodes/18065/6 "2014-06-13T16:55:11Z")
OP here. My numbers on the disk space were not an actual observation of current sizes. It was more of a hypothetical of what can I expect ES to do if I only had three servers and that was the starting disk space available in each. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/ca665ae3-393e-4f79-8a31-60130751938f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ca665ae3-393e-4f79-8a31-60130751938f%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:22am UTC](https://discuss.elastic.co/t/non-uniform-drive-space-across-nodes/18065/7 "2017-07-06T01:22:40Z")