Open devinbost opened 3 years ago
This exception does not show up in the Pulsar build from 2-3 days ago that was used as mentioned in this issue: https://github.com/apache/pulsar/issues/10460 So, the issues could be related.
I bet that in this issue if functions aren't starting correctly (or are restarting), then FunctionsStatsGenerator
can't connect or keeps getting disconnected due to the function restarting. So, I think this issue is a symptom of #10460 .
The issue had no activity for 30 days, mark with Stale label.
While doing some testing on master (2.8.0-SNAPSHOT), this message started flooding my broker logs as soon as I started the brokers:
That function was created in a previous version (Pulsar 2.4.0), and the brokers were upgraded to master.