Hello Pulsar Devs, We just hit an odd issue in the Proxy where when we set our K8S `requests.cpu` exactly to "1" (or "1000m") the proxy thought it had access to all 32 cores on the underlying VM and would not startup without a config change.
This seems to be an issue in Open JDK 11? See https://github.com/kubernetes/kubernetes/issues/84876 https://stackoverflow.com/questions/58719842/kubernetes-pods-getting-different-cpu-limits As you can imagine this JDK bug might cause strange behavior also for brokers/bookies etc. whose thread pools are bigger than expected. So this is partly just an FYI. Anyway an easy work-around (we set the requests.cpu to "999m") but just wondering if there are plans to upgrade the JRE to 15+ (perhaps the next LTS 17?). Thanks! -Frank -- Frank Kelly | Principal Engineer, Platform Team 100 High Street, 7th Floor, Boston, MA 02110 USA www.cogitocorp.com | Cogito on LinkedIn <https://www.linkedin.com/company/cogito-corp-/> Confidentiality Notice : This email is the property of Cogito Corporation. This message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and/or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
