public/supaspin
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

fix: give the vector log collector a 512 MiB memory limit

Browse Source 
- vector reads the log files of every pod on the node, so its memory need follows the node's log volume. At
  256 MiB it was killed for running out of memory 122 times on instance 1 and used 89% on instance 2.
  The limit is now 512 MiB (request unchanged at 128 MiB) for new instances; the total limit per instance
  goes from 5.625 GiB to 5.875 GiB, requests stay at 1.875 GiB.
- README memory table and the test for the totals updated
- version 1.1.1 -> 1.1.2

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit was merged in pull request #4.
This commit is contained in:
Igor K.
2026-09-19 12:56:35 +03:00
co-authored by Claude Sonnet 5
parent 45b02a85af
commit b86863e6f0
4 changed files with 24 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/test_supaspin.py
+5 -4
View File
@@ -90,13 +90,14 @@ class Values(unittest.TestCase):
def test_memory_caps_add_up(self):
req, lim = sp.total_memory_mib()
# db 2048, analytics 768, kong 512, realtime 384, the other eight 256 each
self.assertEqual(lim, 2048 + 768 + 512 + 384 + 8 * 256)
self.assertEqual(lim / 1024, 5.625)
# db 2048, analytics 768, kong 512, realtime 384, vector 512, the other seven 256 each
self.assertEqual(lim, 2048 + 768 + 512 + 384 + 512 + 7 * 256)
self.assertEqual(lim / 1024, 5.875)
self.assertEqual(req, 512 + 11 * 128) # 1.875 GiB
# analytics and realtime were killed for running out of memory at half of production
# analytics, realtime and vector were killed for running out of memory at half of production
self.assertGreaterEqual(sp.MEMORY["analytics"][1], 768)
self.assertGreaterEqual(sp.MEMORY["realtime"][1], 384)
self.assertGreaterEqual(sp.MEMORY["vector"][1], 512)
self.assertEqual(req / 1024, 1.875)
for svc in sp.SERVICES:
self.assertEqual(self.v["deployment"][svc]["priorityClassName"], "supaspin-low")