# Doc values for @timestamp and geo.location

**URL:** <https://discuss.elastic.co/t/doc-values-for-timestamp-and-geo-location/31747>\
**Category:** Elasticsearch\
**Created:** [October 7, 2015, 6:18am UTC](https://discuss.elastic.co/t/doc-values-for-timestamp-and-geo-location/31747 "2015-10-07T06:18:00Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![allenmchan](https://avatars.discourse-cdn.com/v4/letter/a/ec9cab/32.png) [@allenmchan](https://discuss.elastic.co/u/allenmchan)\
**Post date:** [October 7, 2015, 6:18am UTC](https://discuss.elastic.co/t/doc-values-for-timestamp-and-geo-location/31747/1 "2015-10-07T06:18:00Z")

</div>

I am running into high JVM on my data nodes. I noticed @timestamp and geo.location seems to be taking up 2gb of my heap. Are there any ill effects of turning on doc values for these two fields? My use case is logstash indices with logs

```
     "indices": {
        "fielddata": {
           "memory_size_in_bytes": 1765178740,
           "evictions": 0,
           "fields": {
              "host": {
                 "memory_size_in_bytes": 0
              },
              "@timestamp": {
                 "memory_size_in_bytes": 1287128696
              },
              "geoip.location": {
                 "memory_size_in_bytes": 478050044
              },
              "username": {
                 "memory_size_in_bytes": 0
```

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [October 7, 2015, 6:48am UTC](https://discuss.elastic.co/t/doc-values-for-timestamp-and-geo-location/31747/2 "2015-10-07T06:48:44Z")

</div>

Both fields are analyzed so doc values won't work.

---

<div class="post-metadata">

**Author:** ![allenmchan](https://avatars.discourse-cdn.com/v4/letter/a/ec9cab/32.png) [@allenmchan](https://discuss.elastic.co/u/allenmchan)\
**Post date:** [October 7, 2015, 6:53am UTC](https://discuss.elastic.co/t/doc-values-for-timestamp-and-geo-location/31747/3 "2015-10-07T06:53:28Z")

</div>

Nothing can be done then?  
I ran a few more queries and found that those fielddata were taking 14GB on the heap across all indices.

---

<div class="post-metadata">

**Author:** ![allenmchan](https://avatars.discourse-cdn.com/v4/letter/a/ec9cab/32.png) [@allenmchan](https://discuss.elastic.co/u/allenmchan)\
**Post date:** [October 7, 2015, 7:11am UTC](https://discuss.elastic.co/t/doc-values-for-timestamp-and-geo-location/31747/4 "2015-10-07T07:11:10Z")

</div>

Kind of confused right now.  
What is weird is that Kibana 4-\> Settings -\> Indices tab says @timestamp and geo.location are not analyzed fields.

---

<div class="post-metadata">

**Author:** ![allenmchan](https://avatars.discourse-cdn.com/v4/letter/a/ec9cab/32.png) [@allenmchan](https://discuss.elastic.co/u/allenmchan)\
**Post date:** [October 8, 2015, 1:16am UTC](https://discuss.elastic.co/t/doc-values-for-timestamp-and-geo-location/31747/5 "2015-10-08T01:16:22Z")

</div>

a person in the IRC said that only strings are analyzed. Sounds like it will be ok to make @timestamp a doc value?

---

<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:46pm UTC](https://discuss.elastic.co/t/doc-values-for-timestamp-and-geo-location/31747/6 "2017-07-05T23:46:01Z")

</div>