You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/05/29 00:06:29 UTC
[GitHub] [pulsar] ckdarby edited a comment on issue #7089: [Helm] Proxy started throwing Jetty errors even on a new cluster
ckdarby edited a comment on issue #7089:
URL: https://github.com/apache/pulsar/issues/7089#issuecomment-635565265
So, we rolled back everything our side, helm charts back to the known version, nuked the whole k8s cluster, made a new K8s cluster, etc etc. Eventually the only difference we had was a node group had been changed from r5.large to r5.4xlarge to test out #7058
Looking at jetty docs @nickelozz found
> The number of threads you need is determined by the components within Jetty you start to use and the hardware present on your system (the number of cpu cores and network interfaces impacts nio and consequently your thread requirements).
He was also nice enough to find this from AWS docs:
I looked through the Pulsar proxy code, [here](https://github.com/apache/pulsar/blob/master/pulsar-proxy/src/main/java/org/apache/pulsar/proxy/server/ProxyConfiguration.java#L466) and see that it doesn't factor in anything related to interfaces :sob:
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org