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
TiKV uses CPU and memory it sees to auto-configure block cache and other parameters if users don't configure these parameters. But CPU and memory upper bound in a Docker container are the same as the host machine regardless of the resources limit it has. So if users set CPU and memory limits for TiKV, TiKV would misconfigure itself.
We need to configure TiKV according to the actual CPU and memory limits. For example, Raft defaultcf block cache size needs to be set to 30%~50% of TiKV memory limits.
The text was updated successfully, but these errors were encountered:
TiKV uses CPU and memory it sees to auto-configure block cache and other parameters if users don't configure these parameters. But CPU and memory upper bound in a Docker container are the same as the host machine regardless of the resources limit it has. So if users set CPU and memory limits for TiKV, TiKV would misconfigure itself.
We need to configure TiKV according to the actual CPU and memory limits. For example, Raft defaultcf block cache size needs to be set to 30%~50% of TiKV memory limits.
The text was updated successfully, but these errors were encountered: