# Configure elasticsearch to store only index data **URL:** \ **Category:** Elasticsearch\ **Created:** [February 23, 2014, 5:50am UTC](https://discuss.elastic.co/t/configure-elasticsearch-to-store-only-index-data/15975 "2014-02-23T05:50:09Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Sandesh\_Kumar](https://avatars.discourse-cdn.com/v4/letter/s/f04885/32.png) [@Sandesh\_Kumar](https://discuss.elastic.co/u/Sandesh_Kumar)\ **Post date:** [February 23, 2014, 5:50am UTC](https://discuss.elastic.co/t/configure-elasticsearch-to-store-only-index-data/15975/1 "2014-02-23T05:50:09Z")
hi, I am new to Elasticsearch and researching on to see if it can fit my needs. Requirement - To be able to log data into datastore and generate metrics out of it. The data would be huge around 50K recrods per hour (each row of few hundred bytes/KB). We are seeing how we can utilize elasticsearch for this. By going over various threads, looks like this is possible to use elastic search for this need and also use it as a datastore, however could not clarify few items given below : 1. Can we use Elasticsearch to only for search capabilities while the actual data is stored in another database? (i.e., Elasticsearch shall maintain only 'indexed' (index in Database terminology) data which are searchable while the actual data would be stored in different store..say mongodb.). So if have 50K records (~ 5GB) of data, of which there are 10-20 properties of interest in each record which we expect elasticsearch to search/index. Then can we make elasticsearch to store only these searchable properties in its index (size of which we expect to be around few MBs), while the actual data is stored in a separate store and then link it somehow? (In otherwords, elasticsearch just has the properties data which is searchable (nothing more) and has a pointer to actual data in Mongo). 2. What are the memory requirements of elasticsearch? (From what i understood, elasticsearch loads all relevant indexed data into memory while searching. So in my earlier example, if i want 20 properties (each 50 bytes approx) in each record to be searchable, then for searching 50K records, elasticsearch approximately would need 1.2GB of RAM to search over a days data) Is my understanding correct? thanks Sandesh -- 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/f82df903-0fb7-4eaa-9fd2-4d990f8685d2%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f82df903-0fb7-4eaa-9fd2-4d990f8685d2%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![vineeth\_mohan\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vineeth_mohan_2/32/747_2.png) [@vineeth\_mohan\_2](https://discuss.elastic.co/u/vineeth_mohan_2)\ **Post date:** [February 23, 2014, 5:56am UTC](https://discuss.elastic.co/t/configure-elasticsearch-to-store-only-index-data/15975/2 "2014-02-23T05:56:03Z")
Hello Sudheesh , To achieve #1 , you can disable the source - > **[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. You can disable analyzing on the field which have a pointer to the feed in your database and index that field along. That way , you can , at any time go back to the orginal feed in your database. Thanks Vineeth On Sun, Feb 23, 2014 at 11:20 AM, Sandesh Kumar [dev.skg@gmail.com](mailto:dev.skg@gmail.com) wrote: > hi, > > I am new to Elasticsearch and researching on to see if it can fit my > needs. > > Requirement - To be able to log data into datastore and generate metrics > out of it. The data would be huge around 50K recrods per hour (each row of > few hundred bytes/KB). > We are seeing how we can utilize elasticsearch for this. By going over > various threads, looks like this is possible to use Elasticsearch for this > need and also use it as a datastore, however could not clarify few items > given below : > > 1. Can we use Elasticsearch to only for search capabilities while the > actual data is stored in another database? (i.e., Elasticsearch shall > maintain only 'indexed' (index in Database terminology) data which are > searchable while the actual data would be stored in different store..say > mongodb.). So if have 50K records (~ 5GB) of data, of which there are 10-20 > properties of interest in each record which we expect elasticsearch to > search/index. Then can we make elasticsearch to store only these searchable > properties in its index (size of which we expect to be around few MBs), > while the actual data is stored in a separate store and then link it > somehow? > (In otherwords, elasticsearch just has the properties data which is > searchable (nothing more) and has a pointer to actual data in Mongo). > > 2. What are the memory requirements of elasticsearch? (From what i > understood, elasticsearch loads all relevant indexed data into memory while > searching. So in my earlier example, if i want 20 properties (each 50 bytes > approx) in each record to be searchable, then for searching 50K records, > elasticsearch approximately would need 1.2GB of RAM to search over a days > data) Is my understanding correct? > > thanks > Sandesh > > -- > 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/f82df903-0fb7-4eaa-9fd2-4d990f8685d2%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f82df903-0fb7-4eaa-9fd2-4d990f8685d2%40googlegroups.com) > . > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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/CAGdPd5krzzpq8P%3DgF\_LqD3JMRxR0minFEmfBzPdEH44Mw3XV8w%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAGdPd5krzzpq8P%3DgF_LqD3JMRxR0minFEmfBzPdEH44Mw3XV8w%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Binh\_Ly](https://avatars.discourse-cdn.com/v4/letter/b/ce7236/32.png) [@Binh\_Ly](https://discuss.elastic.co/u/Binh_Ly)\ **Post date:** [February 24, 2014, 10:43pm UTC](https://discuss.elastic.co/t/configure-elasticsearch-to-store-only-index-data/15975/3 "2014-02-24T22:43:14Z")
Some ideas: 1. You can turn dynamic mapping to false and then explicitly specify only a handful of fields that will be indexed/searchable. Or, if you don't want to do this, just send in a smaller JSON document with only the fields you want searched or indexed. 2. RAM is mostly dependent on the types of searches. If you do a lot of cached filters, sorting, facets/aggregation, script field access, parent-child, that's where most of the RAM will be used. Otherwise, if you're just doing standard full-text searches and maybe some occasional filtering, you'll probably require "lesser" RAM. The best way to determine this is to test your queries (different query types) on a single node and monitor RAM usage. You'll want to run the node stats checking for the filter, fielddata, and id caches for usage. -- 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/85307551-1041-4fd4-9b45-d18211adf614%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/85307551-1041-4fd4-9b45-d18211adf614%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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:47am UTC](https://discuss.elastic.co/t/configure-elasticsearch-to-store-only-index-data/15975/4 "2017-07-06T01:47:39Z")