# Auto-pin numa and OOM killer

**URL:** <https://discuss.aerospike.com/t/auto-pin-numa-and-oom-killer/7211>\
**Category:** Configuration\
**Created:** [March 11, 2020, 5:58pm UTC](https://discuss.aerospike.com/t/auto-pin-numa-and-oom-killer/7211 "2020-03-11T17:58:15Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![kporter](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/kporter/32/515_2.png) [@kporter](https://discuss.aerospike.com/u/kporter)\
**Post date:** [March 11, 2020, 6:37pm UTC](https://discuss.aerospike.com/t/auto-pin-numa-and-oom-killer/7211/2 "2020-03-11T18:37:48Z")

</div>

You are NUMA pinning which means Aerospike only has access to RAM on the same NUMA node. This means that you only have ~48 GiB of RAM available to the process and you have configured it to have 89 GiB.

Reduce the `memory-size` to ~45 GiB, if you plan to run in this mode.

Note: with NUMA pinning, you would normally deploy an instance of Aerospike per NUMA node.

This discussion may help: [Dual CPU Socket and Aerospike - #7 by tlo](https://discuss.aerospike.com/t/dual-cpu-socket-and-aerospike/6238/7)

---

_[View the full topic](https://discuss.aerospike.com/t/auto-pin-numa-and-oom-killer/7211)._