...
| Name | Value |
|---|---|
| nmisd_max_workers | 10 |
| omkd_workers | 4 |
| omkd_max_requests | 500 |
| Nodes | 406 |
| Active Nodes | 507 |
| SOOS | Ubuntu 18.04.3 LTS |
| role | poller |
This is how the server memory graphs looks in a stressed system - We will be focused on the memory as it is where the bottleneck is:
NMIS process keeps stable, is not using more than 120 mb, and the process was stopped - probably killed for the system due to high memory usage:
| Status | ||||
|---|---|---|---|---|
|
...
And mongod keeps using a lot of memory - 3GB, as configured - but it is stable:
Normal system
Check processes once nmis9d is restarted again:
| Code Block |
|---|
top |
Normal system
| Status | ||||
|---|---|---|---|---|
|
System information:
| Name | Value |
|---|---|
| nmisd_max_workers | 5 |
| omkd_workers | 10 |
| omkd_max_requests | undef |
| Nodes | 2 |
| Poller Nodes | 536 |
| OS | Ubuntu 18.04.3 LTS |
| role | master |
This is how the server memory graphs looks in a normal system: This is