You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
so I have a small kubeadm cluster, and have managed to get a single RPC node up.
but when I changed the replicas to 2, the 2nd node came up, but only process's blocks very slowly
the chain.yaml is available here
and the log output is available here
it is quite a few blocks behind.
This seems like an environment specific issue. Also, the operator does not control the processing of blocks; that's the chain software. We are not able to offer environment-specific support. If you'd like us to offer support, I can get you in touch with our biz dev team to come up with a support contract.
It appears you have enough CPU/RAM and using some sort of SSD for the disk. We use Google's premium-rwo which is suitable for syncing blocks.
Slow syncing can also be caused by pod having slow or not enough peers.
so I have a small kubeadm cluster, and have managed to get a single RPC node up.
but when I changed the replicas to 2, the 2nd node came up, but only process's blocks very slowly
the chain.yaml is available here
and the log output is available here
it is quite a few blocks behind.
ghcr.io/strangelove-ventures/heighliner/gaia:v11.0.0
ghcr.io/strangelove-ventures/cosmos-operator:v0.16.0
The text was updated successfully, but these errors were encountered: