No, ElasticHQ does not misrepresent anything. It just reports the numbers it gets from GET _nodes/stats, stats.os.swap.used_in_bytes in this case. Before, I've tested both settings in ealier and 2.4.x as mentioned by @forloop
They never work. On my current ES 2.4.0 node, bootstrap.memory_lock: true is set, and paging file is disabled, yet the used swap is still a very big number
mlockall is active
"process" : {
"refresh_interval_in_millis" : 1000,
"id" : 7444,
"mlockall" : true
}
still high used swap in _nodes/stats
"swap": {
"total_in_bytes": 207222677504,
"free_in_bytes": 17371148288,
"used_in_bytes": 189851529216
}
Physical memory is 192GB. Similar high swap is reported on all other Windows ES nodes