Resource limits cause cluster oom kill lock

[seanlaff]

I spin up a cluster with req/limit of 6gb mem. After about 10 mins of heavy load, dgraph alphas get oomkilled by kubernetes. When the alpha pods restart, the get oomkilled straight away- and the whole cluster stays in a broken state.

I'm guessing there's some sort of write-ahead-log that dgraph is trying to resume from (from the attached persistent volumes) that is larger than the mem limit given- causing it to instantly get oom killed?

[seanlaff]

Discussion was continued here https://discuss.dgraph.io/t/dgraph-cant-idle-without-being-oomkilled-after-large-data-ingestion/6543/60

Improvements have been made to both badger and dgraph since. Will run another large scale test soon

[darkn3rd]

From discussion, it is related to hypermodeinc/dgraph#5585.

[github-actions]

This issue has been stale for 60 days and will be closed automatically in 7 days. Comment to keep it open.