Comment by Tibbes

I saw this problem recently at work, with a Go program running on Kubernetes. You can work around it by setting GOMAXPROCS to the same value as cpu limit in the container spec.

(So be careful not to assume this problem is specific to Java, the JVM, Mesos, or Twitter's environment)