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
however i've started a fresh stack with very little load and i still see high (100~300%) cpu usage for cassandra. is it possible that somehow consequences of previous runs are still visible in the current stack?
FWIW i ended up rebooting my computer and running ./build.sh and ./setup_dev.sh again and that "resolved" it. @woodsaj any thoughts? if not, we can just close this.
earlier i did some high load scenarios and was getting errors like https://gist.github.com/Dieterbe/ed34b92ee6bfc7289d05
however i've started a fresh stack with very little load and i still see high (100~300%) cpu usage for cassandra. is it possible that somehow consequences of previous runs are still visible in the current stack?
i'm also seeing errors like https://gist.github.com/Dieterbe/d5c6e0706a038e2f6270
The text was updated successfully, but these errors were encountered: