# Max-series-per-database limit exceeded 1000000, error question

**URL:** <https://community.influxdata.com/t/max-series-per-database-limit-exceeded-1000000-error-question/12273>\
**Category:** InfluxDB 2\
**Tags:** influxdb, telegraf, time-series, grafana\
**Created:** [December 9, 2019, 3:51pm UTC](https://community.influxdata.com/t/max-series-per-database-limit-exceeded-1000000-error-question/12273 "2019-12-09T15:51:21Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Anaisdg](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/anaisdg/32/6401_2.png) [@Anaisdg](https://community.influxdata.com/u/Anaisdg)\
**Post date:** [December 9, 2019, 6:19pm UTC](https://community.influxdata.com/t/max-series-per-database-limit-exceeded-1000000-error-question/12273/2 "2019-12-09T18:19:39Z")

</div>

@Tyler_D,  
Thanks for your question. The max-series-per-database limit exists only in the `inmem` index (the default in 1.x). It exists because the `inmem` index can cause the server to OOM if too many series are added to the index. Since it’s rebuilt on startup, and OOMing server can continue to OOM when it restarts, making it operationally difficult to sort out the cardinality problem. The limit was determined based on general query performance at the limit along with heap usage with typical HW. You might want to look into enabling [TSI](https://docs.influxdata.com/influxdb/v1.7/concepts/time-series-index/) if you haven’t already and you’re dealing with that type of cardinality (it’s the default in 1.7.x +).

---

_[View the full topic](https://community.influxdata.com/t/max-series-per-database-limit-exceeded-1000000-error-question/12273)._