# 1m doc per lucene file

**URL:** <https://discuss.elastic.co/t/1m-doc-per-lucene-file/31986>\
**Category:** Elasticsearch\
**Created:** [October 12, 2015, 8:19am UTC](https://discuss.elastic.co/t/1m-doc-per-lucene-file/31986 "2015-10-12T08:19:30Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jason\_Wee](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@Jason\_Wee](https://discuss.elastic.co/u/Jason_Wee)\
**Post date:** [October 12, 2015, 8:19am UTC](https://discuss.elastic.co/t/1m-doc-per-lucene-file/31986/1 "2015-10-12T08:19:30Z")

</div>

![](https://us1.discourse-cdn.com/elastic/original/2X/4/41c705004d9b007513fe0472cf7335e2c2104500.png)

This segment spy shown a production es cluster version 0.90.7 running. is 1m per lucene index file is the limit? should there be any concern if you look at this segment of this cluster? any comments/suggestion are welcome.

---

<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:** [October 12, 2015, 8:20am UTC](https://discuss.elastic.co/t/1m-doc-per-lucene-file/31986/2 "2015-10-12T08:20:28Z")

</div>

There's a hard 2 billion limit in lucene. Are you having problems with this?

(Also, upgrade, that's a _really_ old version)

---

<div class="post-metadata">

**Author:** ![Jason\_Wee](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@Jason\_Wee](https://discuss.elastic.co/u/Jason_Wee)\
**Post date:** [October 12, 2015, 9:16am UTC](https://discuss.elastic.co/t/1m-doc-per-lucene-file/31986/3 "2015-10-12T09:16:21Z")

</div>

2billion? okay, clear.

Well, it seem like the segment stay at 1m doc and would not increase anymore, not sure what is the impact/problem (if any).

As for problems, well , as the data grow everyday, we encounter problem from time to time, the stability issue is a concern like cluster went into red state, etc. It need human intervention to restart the node, so the cluster state go back to green. Self healing did not happen in such cluster load, data loss. The less problematic is that the query search and query fetch took sometime to complete. Sometime cluster node shown stackoverflow, sometime high cpu usage, sometime out of memory, sometime code loop for 10 levels or more. file an issue in github last time.

Mentioned last time in the mailing list about upgrade, it is an unfortunate upgrade does not work.

---

<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:** [October 12, 2015, 9:19am UTC](https://discuss.elastic.co/t/1m-doc-per-lucene-file/31986/4 "2015-10-12T09:19:15Z")

</div>

Sounds like you need to add more nodes!

---

<div class="post-metadata">

**Author:** ![Jason\_Wee](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@Jason\_Wee](https://discuss.elastic.co/u/Jason_Wee)\
**Post date:** [October 13, 2015, 6:31am UTC](https://discuss.elastic.co/t/1m-doc-per-lucene-file/31986/5 "2015-10-13T06:31:16Z")

</div>

other than java/elasticsearch upgrade and/or add more nodes, do you think is there any other way to improve stability? configuration changes , etc?

---

<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:** [October 13, 2015, 6:42am UTC](https://discuss.elastic.co/t/1m-doc-per-lucene-file/31986/6 "2015-10-13T06:42:23Z")

</div>

Why does an upgrade not work?

---

<div class="post-metadata">

**Author:** ![Jason\_Wee](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@Jason\_Wee](https://discuss.elastic.co/u/Jason_Wee)\
**Post date:** [October 13, 2015, 9:08am UTC](https://discuss.elastic.co/t/1m-doc-per-lucene-file/31986/7 "2015-10-13T09:08:18Z")

</div>

Tried to upgrade from java6 to java7 u72 for the production cluster, es client cannot talk to the cluster without no issue. iirc, it was serial exception , something like that, I asked in the mailing list, no solution given. so no java upgrade, no es upgrade neither...

---

<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:** [July 5, 2017, 11:45pm UTC](https://discuss.elastic.co/t/1m-doc-per-lucene-file/31986/8 "2017-07-05T23:45:08Z")

</div>


