# Using ElasticSearch as a storage for classifiers

**URL:** <https://discuss.elastic.co/t/using-elasticsearch-as-a-storage-for-classifiers/15667>\
**Category:** Elasticsearch\
**Created:** [February 7, 2014, 11:50am UTC](https://discuss.elastic.co/t/using-elasticsearch-as-a-storage-for-classifiers/15667 "2014-02-07T11:50:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![andreypopov](https://avatars.discourse-cdn.com/v4/letter/a/50afbb/32.png) [@andreypopov](https://discuss.elastic.co/u/andreypopov)\
**Post date:** [February 7, 2014, 11:50am UTC](https://discuss.elastic.co/t/using-elasticsearch-as-a-storage-for-classifiers/15667/1 "2014-02-07T11:50:36Z")

</div>

Hi,

I'm working on application that should store classifiers in the ES with searching capability. Some classifiers are simple set of key-value pars, some have a complex structure. I've decided to keep each classifier's data in separate index. My application have about 1000 classifiers and when I am trying to import them from external sources, I get troubles with elasticsearch (it crushes with not connected answer on my local PC). I use all default settings during indexing (5 shards per index, 1 node on my local PC).  
I think the issue is related to huge amount of shards which getting created during import processing.

Can you point on possible reasons of this situation and which indexing strategy can be used for my situation?

Thanks

---

<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 6, 2017, 1:51am UTC](https://discuss.elastic.co/t/using-elasticsearch-as-a-storage-for-classifiers/15667/2 "2017-07-06T01:51:50Z")

</div>

Closed on July 6, 2017, 1:51am UTC