# Any issues using 2 shards for an index? **URL:** \ **Category:** Elasticsearch\ **Created:** [July 9, 2014, 2:16am UTC](https://discuss.elastic.co/t/any-issues-using-2-shards-for-an-index/18540 "2014-07-09T02:16:13Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Drew\_Kutcharian](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drew_kutcharian/32/742_2.png) [@Drew\_Kutcharian](https://discuss.elastic.co/u/Drew_Kutcharian)\ **Post date:** [July 9, 2014, 2:16am UTC](https://discuss.elastic.co/t/any-issues-using-2-shards-for-an-index/18540/1 "2014-07-09T02:16:13Z")
Hi All, We are thinking of using two shards per index + 1 replica to keep the number of shards low for some indices. Are there any gotchas with using 2 shards per index besides that at most we can scale the writes to this index to two machines? Thanks, Drew -- 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/8C50A329-FB87-45C8-A38E-B908756183E0%40venarc.com](https://groups.google.com/d/msgid/elasticsearch/8C50A329-FB87-45C8-A38E-B908756183E0%40venarc.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:** [July 9, 2014, 2:19am UTC](https://discuss.elastic.co/t/any-issues-using-2-shards-for-an-index/18540/2 "2014-07-09T02:19:56Z")
Writes _and_ reads 🙂 You may also end up with some nodes holding more, smaller shards than others, which will mean uneven load. If you have potential for many small indexes, check out routing as an alternative. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 9 July 2014 12:16, Drew Kutcharian [drew@venarc.com](mailto:drew@venarc.com) wrote: > Hi All, > > We are thinking of using two shards per index + 1 replica to keep the > number of shards low for some indices. Are there any gotchas with using 2 > shards per index besides that at most we can scale the writes to this index > to two machines? > > Thanks, > > Drew > > -- > 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/8C50A329-FB87-45C8-A38E-B908756183E0%40venarc.com](https://groups.google.com/d/msgid/elasticsearch/8C50A329-FB87-45C8-A38E-B908756183E0%40venarc.com) > . > 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/CAEM624YWOMcfRHqF%2B9jpvPs6H8OqmPx78GJbb-vr1z43r-32fg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624YWOMcfRHqF%2B9jpvPs6H8OqmPx78GJbb-vr1z43r-32fg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Drew\_Kutcharian](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drew_kutcharian/32/742_2.png) [@Drew\_Kutcharian](https://discuss.elastic.co/u/Drew_Kutcharian)\ **Post date:** [July 9, 2014, 2:24am UTC](https://discuss.elastic.co/t/any-issues-using-2-shards-for-an-index/18540/3 "2014-07-09T02:24:46Z")
Thanks Mark. I know we can scale the reads by adding more replicas. Also the issue with nodes containing a lot of shards can be fixed using index shard allocation. I mainly wanted to see if there are any other "undocumented" gotchas. On Jul 8, 2014, at 7:19 PM, Mark Walkom [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) wrote: > Writes _and_ reads 🙂 > You may also end up with some nodes holding more, smaller shards than others, which will mean uneven load. > > If you have potential for many small indexes, check out routing as an alternative. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > On 9 July 2014 12:16, Drew Kutcharian [drew@venarc.com](mailto:drew@venarc.com) wrote: > Hi All, > > We are thinking of using two shards per index + 1 replica to keep the number of shards low for some indices. Are there any gotchas with using 2 shards per index besides that at most we can scale the writes to this index to two machines? > > Thanks, > > Drew > > -- > 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/8C50A329-FB87-45C8-A38E-B908756183E0%40venarc.com](https://groups.google.com/d/msgid/elasticsearch/8C50A329-FB87-45C8-A38E-B908756183E0%40venarc.com). > 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/CAEM624YWOMcfRHqF%2B9jpvPs6H8OqmPx78GJbb-vr1z43r-32fg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624YWOMcfRHqF%2B9jpvPs6H8OqmPx78GJbb-vr1z43r-32fg%40mail.gmail.com). > 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/A3E48B75-E531-4ECD-BF14-85F8C907D23E%40venarc.com](https://groups.google.com/d/msgid/elasticsearch/A3E48B75-E531-4ECD-BF14-85F8C907D23E%40venarc.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:** [July 9, 2014, 2:58am UTC](https://discuss.elastic.co/t/any-issues-using-2-shards-for-an-index/18540/4 "2014-07-09T02:58:03Z")
You should be fine. We run about 1600 indexes most of which are single shard. The are pretty low traffic so it works or fine. Yes we know about routing, no it won't help us. 1600 isn't enough to cause a problem. On Jul 8, 2014 10:24 PM, "Drew Kutcharian" [drew@venarc.com](mailto:drew@venarc.com) wrote: > Thanks Mark. I know we can scale the reads by adding more replicas. Also > the issue with nodes containing a lot of shards can be fixed using index > shard allocation. > > I mainly wanted to see if there are any other “undocumented” gotchas. > > On Jul 8, 2014, at 7:19 PM, Mark Walkom [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) wrote: > > Writes _and_ reads 🙂 > You may also end up with some nodes holding more, smaller shards than > others, which will mean uneven load. > > If you have potential for many small indexes, check out routing as an > alternative. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > On 9 July 2014 12:16, Drew Kutcharian [drew@venarc.com](mailto:drew@venarc.com) wrote: > > > Hi All, > > > > We are thinking of using two shards per index + 1 replica to keep the > > number of shards low for some indices. Are there any gotchas with using 2 > > shards per index besides that at most we can scale the writes to this index > > to two machines? > > > > Thanks, > > > > Drew > > > > -- > > 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/8C50A329-FB87-45C8-A38E-B908756183E0%40venarc.com](https://groups.google.com/d/msgid/elasticsearch/8C50A329-FB87-45C8-A38E-B908756183E0%40venarc.com) > > . > > 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/CAEM624YWOMcfRHqF%2B9jpvPs6H8OqmPx78GJbb-vr1z43r-32fg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624YWOMcfRHqF%2B9jpvPs6H8OqmPx78GJbb-vr1z43r-32fg%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAEM624YWOMcfRHqF%2B9jpvPs6H8OqmPx78GJbb-vr1z43r-32fg%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEM624YWOMcfRHqF%2B9jpvPs6H8OqmPx78GJbb-vr1z43r-32fg%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/A3E48B75-E531-4ECD-BF14-85F8C907D23E%40venarc.com](https://groups.google.com/d/msgid/elasticsearch/A3E48B75-E531-4ECD-BF14-85F8C907D23E%40venarc.com) > [https://groups.google.com/d/msgid/elasticsearch/A3E48B75-E531-4ECD-BF14-85F8C907D23E%40venarc.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/A3E48B75-E531-4ECD-BF14-85F8C907D23E%40venarc.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/CAPmjWd3u5TMObF%3Dv%3DEB7EG59%2BFgBob%2Bw\_ytpZoWdt1qguS4kqA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd3u5TMObF%3Dv%3DEB7EG59%2BFgBob%2Bw_ytpZoWdt1qguS4kqA%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:** [July 9, 2014, 3:17am UTC](https://discuss.elastic.co/t/any-issues-using-2-shards-for-an-index/18540/5 "2014-07-09T03:17:38Z")
Yep that is all manageable, but you may cross a point where managing that becomes more hassle than it's worth. Something to keep in mind. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 9 July 2014 12:24, Drew Kutcharian [drew@venarc.com](mailto:drew@venarc.com) wrote: > Thanks Mark. I know we can scale the reads by adding more replicas. Also > the issue with nodes containing a lot of shards can be fixed using index > shard allocation. > > I mainly wanted to see if there are any other “undocumented” gotchas. > > On Jul 8, 2014, at 7:19 PM, Mark Walkom [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) wrote: > > Writes _and_ reads 🙂 > You may also end up with some nodes holding more, smaller shards than > others, which will mean uneven load. > > If you have potential for many small indexes, check out routing as an > alternative. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > On 9 July 2014 12:16, Drew Kutcharian [drew@venarc.com](mailto:drew@venarc.com) wrote: > > > Hi All, > > > > We are thinking of using two shards per index + 1 replica to keep the > > number of shards low for some indices. Are there any gotchas with using 2 > > shards per index besides that at most we can scale the writes to this index > > to two machines? > > > > Thanks, > > > > Drew > > > > -- > > 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/8C50A329-FB87-45C8-A38E-B908756183E0%40venarc.com](https://groups.google.com/d/msgid/elasticsearch/8C50A329-FB87-45C8-A38E-B908756183E0%40venarc.com) > > . > > 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/CAEM624YWOMcfRHqF%2B9jpvPs6H8OqmPx78GJbb-vr1z43r-32fg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624YWOMcfRHqF%2B9jpvPs6H8OqmPx78GJbb-vr1z43r-32fg%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAEM624YWOMcfRHqF%2B9jpvPs6H8OqmPx78GJbb-vr1z43r-32fg%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEM624YWOMcfRHqF%2B9jpvPs6H8OqmPx78GJbb-vr1z43r-32fg%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/A3E48B75-E531-4ECD-BF14-85F8C907D23E%40venarc.com](https://groups.google.com/d/msgid/elasticsearch/A3E48B75-E531-4ECD-BF14-85F8C907D23E%40venarc.com) > [https://groups.google.com/d/msgid/elasticsearch/A3E48B75-E531-4ECD-BF14-85F8C907D23E%40venarc.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/A3E48B75-E531-4ECD-BF14-85F8C907D23E%40venarc.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/CAEM624YMaXQLcUoBnDyJLVot2CYVSTjhifeUGwWxADLvNQ7Ojg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624YMaXQLcUoBnDyJLVot2CYVSTjhifeUGwWxADLvNQ7Ojg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Drew\_Kutcharian](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drew_kutcharian/32/742_2.png) [@Drew\_Kutcharian](https://discuss.elastic.co/u/Drew_Kutcharian)\ **Post date:** [July 9, 2014, 5:56am UTC](https://discuss.elastic.co/t/any-issues-using-2-shards-for-an-index/18540/6 "2014-07-09T05:56:16Z")
Yes, but for our usecase we need to use parent/child queries which are pretty much unfeasible to do any other way due to their limitations (can't do parent/child using multiple indices). - Drew On Jul 8, 2014, at 8:17 PM, Mark Walkom [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) wrote: > Yep that is all manageable, but you may cross a point where managing that becomes more hassle than it's worth. > Something to keep in mind. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > On 9 July 2014 12:24, Drew Kutcharian [drew@venarc.com](mailto:drew@venarc.com) wrote: > Thanks Mark. I know we can scale the reads by adding more replicas. Also the issue with nodes containing a lot of shards can be fixed using index shard allocation. > > I mainly wanted to see if there are any other "undocumented" gotchas. > > On Jul 8, 2014, at 7:19 PM, Mark Walkom [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) wrote: > > > Writes _and_ reads 🙂 > > You may also end up with some nodes holding more, smaller shards than others, which will mean uneven load. > > > > If you have potential for many small indexes, check out routing as an alternative. > > > > Regards, > > Mark Walkom > > > > Infrastructure Engineer > > Campaign Monitor > > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > > > On 9 July 2014 12:16, Drew Kutcharian [drew@venarc.com](mailto:drew@venarc.com) wrote: > > Hi All, > > > > We are thinking of using two shards per index + 1 replica to keep the number of shards low for some indices. Are there any gotchas with using 2 shards per index besides that at most we can scale the writes to this index to two machines? > > > > Thanks, > > > > Drew > > > > -- > > 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/8C50A329-FB87-45C8-A38E-B908756183E0%40venarc.com](https://groups.google.com/d/msgid/elasticsearch/8C50A329-FB87-45C8-A38E-B908756183E0%40venarc.com). > > 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/CAEM624YWOMcfRHqF%2B9jpvPs6H8OqmPx78GJbb-vr1z43r-32fg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624YWOMcfRHqF%2B9jpvPs6H8OqmPx78GJbb-vr1z43r-32fg%40mail.gmail.com). > > 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/A3E48B75-E531-4ECD-BF14-85F8C907D23E%40venarc.com](https://groups.google.com/d/msgid/elasticsearch/A3E48B75-E531-4ECD-BF14-85F8C907D23E%40venarc.com). > 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/CAEM624YMaXQLcUoBnDyJLVot2CYVSTjhifeUGwWxADLvNQ7Ojg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624YMaXQLcUoBnDyJLVot2CYVSTjhifeUGwWxADLvNQ7Ojg%40mail.gmail.com). > 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/4630918D-A28B-4125-8B04-AF482A6B1904%40venarc.com](https://groups.google.com/d/msgid/elasticsearch/4630918D-A28B-4125-8B04-AF482A6B1904%40venarc.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:17am UTC](https://discuss.elastic.co/t/any-issues-using-2-shards-for-an-index/18540/7 "2017-07-06T01:17:08Z")