# API showing incorrect data

**URL:** <https://discuss.elastic.co/t/api-showing-incorrect-data/73017>\
**Category:** Logstash\
**Created:** [January 27, 2017, 1:50pm UTC](https://discuss.elastic.co/t/api-showing-incorrect-data/73017 "2017-01-27T13:50:45Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mormaii](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mormaii/32/10790_2.png) [@Mormaii](https://discuss.elastic.co/u/Mormaii)\
**Post date:** [January 27, 2017, 1:50pm UTC](https://discuss.elastic.co/t/api-showing-incorrect-data/73017/1 "2017-01-27T13:50:45Z")

</div>

Trying to check the heap max in bytes using

[http://localhost:9600/\_node/jvm?pretty=true](http://localhost:9600/_node/jvm?pretty=true)

works correctly which shows 8GB for me. Now when I try to see more detailed stats about the JVM with:

[http://localhost:9600/\_node/stats/jvm?pretty=true](http://localhost:9600/_node/stats/jvm?pretty=true)

It shows my heap max in bytes as 17GB which makes no sense since the server is on doesn't even have that much ram. The logstash process has this java args too: "-Xmx8g -Xms8g -Xss2048k"

---

<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:** [January 29, 2017, 4:14am UTC](https://discuss.elastic.co/t/api-showing-incorrect-data/73017/2 "2017-01-29T04:14:39Z")

</div>

Can you show us the actual output, as well as what version, OS and JVM.

---

<div class="post-metadata">

**Author:** ![Mormaii](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mormaii/32/10790_2.png) [@Mormaii](https://discuss.elastic.co/u/Mormaii)\
**Post date:** [January 30, 2017, 12:26pm UTC](https://discuss.elastic.co/t/api-showing-incorrect-data/73017/4 "2017-01-30T12:26:37Z")

</div>

\_node/jvm output:

```
{
  "host" : "elastic-logstash.drsite.local",
  "version" : "5.1.2",
  "http_address" : "127.0.0.1:9600",
  "id" : "acaeaae5-8b97-464d-9719-79f378874e82",
  "name" : "elastic-logstash.drsite.local",
  "jvm" : {
    "pid" : 26215,
    "version" : "1.8.0_111",
    "vm_name" : "OpenJDK 64-Bit Server VM",
    "vm_version" : "1.8.0_111",
    "vm_vendor" : "Oracle Corporation",
    "start_time_in_millis" : 1485542195317,
    "mem" : {
      "heap_init_in_bytes" : 8589934592,
      "heap_max_in_bytes" : 8555069440,
      "non_heap_init_in_bytes" : 2555904,
      "non_heap_max_in_bytes" : 0
    },
    "gc_collectors" : ["ParNew", "ConcurrentMarkSweep"]
  }

```

\_node/stats/jvm output

```
{
  "host" : "elastic-logstash.drsite.local",
  "version" : "5.1.2",
  "http_address" : "127.0.0.1:9600",
  "id" : "acaeaae5-8b97-464d-9719-79f378874e82",
  "name" : "elastic-logstash.drsite.local",
  "jvm" : {
    "threads" : {
      "count" : 31,
      "peak_count" : 33
    },
    "mem" : {
      "heap_used_in_bytes" : 692095288,
      "heap_used_percent" : 4,
      "heap_committed_in_bytes" : 17110138880,
      "heap_max_in_bytes" : 17110138880,
      "non_heap_used_in_bytes" : 264043696,
      "non_heap_committed_in_bytes" : 283820032,
      "pools" : {
        "survivor" : {
          "peak_used_in_bytes" : 34865152,
          "used_in_bytes" : 36740656,
          "peak_max_in_bytes" : 34865152,
          "max_in_bytes" : 69730304,
          "committed_in_bytes" : 69730304
        },
        "old" : {
          "peak_used_in_bytes" : 173315864,
          "used_in_bytes" : 345991744,
          "peak_max_in_bytes" : 8241020928,
          "max_in_bytes" : 16482041856,
          "committed_in_bytes" : 16482041856
        },
        "young" : {
          "peak_used_in_bytes" : 279183360,
          "used_in_bytes" : 309362888,
          "peak_max_in_bytes" : 279183360,
          "max_in_bytes" : 558366720,
          "committed_in_bytes" : 558366720
        }
      }
    },
    "gc" : {
      "collectors" : {
        "old" : {
          "collection_time_in_millis" : 126,
          "collection_count" : 2
        },
        "young" : {
          "collection_time_in_millis" : 538222,
          "collection_count" : 16593
        }
      }
    },
    "uptime_in_millis" : 236891121
  }

```

These are the outputs compared

"heap\_max\_in\_bytes" : 17110138880,  
"heap\_max\_in\_bytes" : 8555069440,

The OS is Fedora 25.

---

<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:** [January 31, 2017, 3:37am UTC](https://discuss.elastic.co/t/api-showing-incorrect-data/73017/5 "2017-01-31T03:37:31Z")

</div>

The `_node/jvm` (info API) shows the allocated heap size, the `_node/stats/jvm` (stats API) shows the max heap usage during the life of the process.

But it the info API shouldn't be reporting things incorrectly.  
Can you raise an issue on Github with as much info as possible?

---

<div class="post-metadata">

**Author:** ![jordansissel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jordansissel/32/44957_2.png) [@jordansissel](https://discuss.elastic.co/u/jordansissel)\
**Post date:** [January 31, 2017, 4:07am UTC](https://discuss.elastic.co/t/api-showing-incorrect-data/73017/6 "2017-01-31T04:07:57Z")

</div>

Confirmed. Looks like one is double of the other:

```auto
⓿ localhost(~/projects/logstash) master !3!
% curl -s localhost:9600/_node/jvm | jq .jvm.mem.heap_max_in_bytes
1056309248
⓿ localhost(~/projects/logstash) master
% curl -s localhost:9600/_node/stats/jvm | jq .jvm.mem.heap_max_in_bytes
2112618496

```

---

<div class="post-metadata">

**Author:** ![jordansissel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jordansissel/32/44957_2.png) [@jordansissel](https://discuss.elastic.co/u/jordansissel)\
**Post date:** [January 31, 2017, 4:22am UTC](https://discuss.elastic.co/t/api-showing-incorrect-data/73017/7 "2017-01-31T04:22:34Z")

</div>

Filed [https://github.com/elastic/logstash/issues/6608](https://github.com/elastic/logstash/issues/6608) to track.

---

<div class="post-metadata">

**Author:** ![Mormaii](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mormaii/32/10790_2.png) [@Mormaii](https://discuss.elastic.co/u/Mormaii)\
**Post date:** [January 31, 2017, 2:20pm UTC](https://discuss.elastic.co/t/api-showing-incorrect-data/73017/8 "2017-01-31T14:20:48Z")

</div>

Indeed, it shows exactly double of the real value. I'm not sure either why there's "\_node/jvm" instead of "\_node/stats" which is how Elasticsearch handles it.

---

<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:** [February 28, 2017, 2:20pm UTC](https://discuss.elastic.co/t/api-showing-incorrect-data/73017/9 "2017-02-28T14:20:48Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
