Hi our cluster OOMed, wondering if there's anythin...
# community-help
d
Hi our cluster OOMed, wondering if there's anything we can do to bring it back online
Cluster ID
2bzrksoem3t71iulp
🙏
@Kishore Nallan @Jason Bosco
j
You want to go into Cluster Configuration > Modify and upgrade to the next RAM tier
The amount of data indexed your cluster requires more RAM to hold the dataset
d
Got it, bumping now
This crashed because of our syncer job which runs every 5 minutes. We are thinking about capping the number of records we sync everytime the syncing routine wakes up What do you think is a reasonable cap to set with our new config (32GB RAM, 4vCPU)
Each record is about 1.10KB
For more context: • We already fetch at most 1000 records so that's about 1MB we call using
collections.import
every 5 mins • That feels pretty safe? • The actual limiting factor from the charts seem to have been CPU usage?
message has been deleted
message has been deleted
j
The spike in CPU usage at the end is because of the crash and restart loop due to OOM
So the bottleneck is indeed RAM
d
Ah I see
Ok yea it seems like we attempted to insert 10k records at once
So that would be 10MB spike
j
Hard to answer your question about a safe upper cap. I would recommend running with different amounts of caps on your side, and observe how memory usage spikes in real-time and adjust based on that
d
Gotcha ok sounds good