So I have a 3 node nebula deployment, and each sto...
# nebula
j
So I have a 3 node nebula deployment, and each storaged pod takes ~20Gb of memory. This is even if I have zero requests. What is taking up all the memory? I'm trying to figure out what I can tweak to reduce it. Is it rocksdb? Is it mostly tied to the raft groups? Thanks!
d
Hi, could you provide the version of NebulaGraph currently in use? Additionally, I would like to inquire about the configuration settings for the block cache size and any specific operations or procedures that have been carried out regarding this setting.
j
I am using pretty much default configs. I use the k8 operator. Version 3.6.0. Also, it's been running for awhile now -- I have a few graph spaces, so the db isn't empty per se
Even if I restart the pods, it takes up ~20GB on startup with zero requests -- if I give it less memory than that it crashes with OOMKilled a few moments after it starts up. So it leads me to think some cache or something is being loaded into memory on startup
I'm wondering what that could be and if I could reduce it -- or am I SoL because it's tied to something I can't really control
Thank you!