@silas.weber THAT IS LITERALLY WHAT i SAID 3 PAGES AGO 🙄
my elasticsearch node gets oomkilled at random. memory graphs look fine! !!
@kernel_shed ok boomer just my 2 cents
@silas.weber sure, and when it breaks again ull be back here asking just my 2 cents
@silas.weber sure, and when it breaks again ull be back here asking just my 2 cents
@kernel_shed no. just no. a clean reinsatll is the answer and u know it idk maybe im wrong lol
reading release notes like its a horror novel
@silas.weber benchmarks or it didnt happen just my 2 cents
@silas.weber benchmarks or it didnt happen just my 2 cents
@kernel_shed lol ok, keep believing fixing it properly is fine idk maybe im wrong lol
@silas.weber u keep moving teh goalposts lol
@kernel_shed source: trust me bro 🙄
MY VM WONT BOOT AFTER SWITCHING IT TO UEFI. JUST NO BOOTABLE DEVICE
Related topics
- IS 768MI TOO SMALL, OR IS THE PHP WORKER LYING ABOUT MEMORY?
- MY GO MICROSERVICE GETS OOMKILLED AT RANDOM. MEMORY GRAPHS LOOK FINE!
- OOMKilled With A 512Mi Limit, But The Go Microservice only Uses Half Of It???
- OOMKilled With A 1Gi Limit, But The Go Microservice 'only Uses' Half Of It????
- Exit code 137 out of nowhere. Who killed my Node.js API?
- OOMKilled With A 256Mi Limit, But The Python Data Job 'only Uses' Half Of It???
Reply to this topic
Sign in or create an account to reply.