Gergely Fábián
04/04/2024, 8:31 PMFatih
04/18/2024, 10:42 AM08:18:38.703 [pulsar-proxy-io-2-1] WARN org.apache.pulsar.proxy.server.ProxyConnection - [/10.42.4.0:59042] Got exception NativeIoException : readAddress(..) failed: Connection reset by peer null
2024-04-18 10:18:38.703 +02:00 pulsar-proxy-1
io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer
2024-04-18 10:18:37.869 +02:00 pulsar-proxy-3
io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer
2024-04-18 10:18:37.869 +02:00 pulsar-proxy-3
08:18:37.869 [pulsar-proxy-io-2-1] WARN org.apache.pulsar.proxy.server.ProxyConnection - [/10.42.4.0:1895] Got exception NativeIoException : readAddress(..) failed: Connection reset by peer null
2024-04-18 10:18:37.569 +02:00 pulsar-proxy-3
08:18:37.569 [pulsar-proxy-io-2-1] WARN org.apache.pulsar.proxy.server.ProxyConnection - [/10.42.4.0:1443] Got exception NativeIoException : readAddress(..) failed: Connection reset by peer null
2024-04-18 10:18:37.569 +02:00 pulsar-proxy-3
io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer
2024-04-18 10:18:37.429 +02:00 pulsar-proxy-2
io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer
2024-04-18 10:18:37.429 +02:00 pulsar-proxy-2
08:18:37.429 [pulsar-proxy-io-2-1] WARN org.apache.pulsar.proxy.server.ProxyConnection - [/10.42.4.0:21857] Got exception NativeIoException : readAddress(..) failed: Connection reset by peer null
2024-04-18 10:18:25.800 +02:00 pulsar-proxy-2
io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer
2024-04-18 10:18:25.800 +02:00 pulsar-proxy-2
08:18:25.079 [pulsar-proxy-io-2-1] WARN org.apache.pulsar.proxy.server.ProxyConnection - [/10.42.12.0:44329] Got exception NativeIoException : readAddress(..) failed: Connection reset by peer null
2024-04-18 10:18:25.662 +02:00 pulsar-proxy-0
io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer
2024-04-18 10:18:25.662 +02:00 pulsar-proxy-0
08:18:25.662 [pulsar-proxy-io-2-1] WARN org.apache.pulsar.proxy.server.ProxyConnection - [/10.42.12.0:31666] Got exception NativeIoException : readAddress(..) failed: Connection reset by peer null
Lari Hotari
04/20/2024, 2:02 PMSlackbot
08/17/2021, 7:04 AMLari Hotari
05/18/2024, 11:36 AMLari Hotari
06/04/2024, 4:54 PMEnrique
06/11/2024, 7:02 PM<cluster>.svc.cluser.local
urls, I was able to begin seeing my topics again.
Is there a reason the manager ui didn't recover with previous user + config?Daniil
06/12/2024, 7:36 AMsagar singh
06/12/2024, 11:41 AMLari Hotari
08/01/2024, 7:58 PMLari Hotari
08/06/2024, 12:24 PMKhemendra
08/22/2024, 5:54 PMKhemendra
08/31/2024, 12:01 PMLászló Ludman
09/02/2024, 12:02 PMLászló Ludman
10/21/2024, 9:28 AMCaused by: javax.ws.rs.ClientErrorException: HTTP 412 {"reason":"Can't find owner for topic <non-persistent://pulsar/system/loadbalancer-broker-load-data>"}
After i manually scale down the brokers and scale back the issue is gone. But i don't want to do that 🙂 🙂
Thanks in advance for your help.Lari Hotari
10/29/2024, 10:45 PMLari Hotari
10/31/2024, 11:27 AMAnte Malenica
11/20/2024, 12:25 PMLari Hotari
11/22/2024, 2:25 PMLari Hotari
12/10/2024, 5:52 PMThomas O'Neill
01/29/2025, 2:00 PMpuslar
integration?Simon
02/28/2025, 12:46 PMLari Hotari
03/04/2025, 9:28 PMLari Hotari
03/06/2025, 1:14 PMLari Hotari
03/11/2025, 12:58 AMEnhanced Monitoring Experience: Usable Metrics and Grafana Dashboards pre-installed
• Pre-configured and thoroughly tested dashboards now included
• Dashboards maintained in dedicated repository: https://github.com/lhotari/pulsar-grafana-dashboards
• Sourced from various Apache 2.0 licensed projects, then optimized and updated for Pulsar 4.0.0 compatibility
• Resolves long-standing dashboard compatibility issues with recent Pulsar and Bookkeeper
◦ Many metrics names have changed since Pulsar 2.10 and previously available dashboards were broken
• While testing, some bugs were faced in Prometheus 3.2.1 were metrics scraping failed without proper errors even with debug log level and that triggered a switch from kube-prometheus-stack to victoriametrics-k8s-stack and VictoriaMetrics.
◦ VictoriaMetrics is more efficient than Prometheus and it doesn't have issues with Pulsar metrics.
Lari Hotari
03/14/2025, 8:05 AMLari Hotari
05/28/2025, 12:49 PMYabin m
06/26/2025, 4:18 PMGary
07/08/2025, 6:28 PMGary
07/17/2025, 3:53 AMauthenticationProviders: org.apache.pulsar.broker.authentication.AuthenticationProviderToken,org.apache.pulsar.broker.authentication.AuthenticationProviderTLS
However, I am running into an issue where the KubernetesSecretsTokenAuthProvider
cannot find the token that is already mounted on the broker when the embedded function worker is spinning up a separate function pod. When I had the JWT auth enabled and set, the pf-secret-<id> (ca.pem and TOKEN)
, the volume, and volume mount were automatically created as part of the creation of the function. As I understood it, the embedded function worker on the broker inherits the permission of the broker and should have access to create those secrets. The broker actually shows logs of the function pod attempting connection with both the token and the TLS certs. Both methods fail because there is no secret mounting.
Thanks in advance!