2020-04-19 14:46:12 UTC - matt_innerspace.io: @Addison Higham @Sijie Guo where would i find the worker metrics endpoint for prometheus? It's not mentioned anywhere here - <https://pulsar.apache.org/docs/en/reference-metrics/> ---- 2020-04-19 15:04:06 UTC - matt_innerspace.io: i see this, but it doesn't appear to work - <https://github.com/apache/pulsar/blob/23a6622dd57aac1a02cedb26bdfcc8ef19564886/pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/v2/WorkerStats.java> ---- 2020-04-19 16:37:54 UTC - Tufan Rakshit: @Tufan Rakshit has joined the channel ---- 2020-04-19 21:42:55 UTC - Addison Higham: <https://github.com/apache/pulsar/blob/23a6622dd57aac1a02cedb26bdfcc8ef19564886/pulsar-functions/runtime/src/main/java/org/apache/pulsar/functions/runtime/JavaInstanceMain.java#L216> <- is where it gets started ---- 2020-04-20 02:57:43 UTC - Sijie Guo: yeah we should make it configurable. ---- 2020-04-20 03:01:49 UTC - Sijie Guo: > If bookieID and IP can be distinct (i.e. name a bookie but different advertise address) and ensembles then look for changed IPs there is a BP (bookkeeper proposal) working on improving bookie identifier management. so we don’t need to tie ip/hostname to a bookie id.
> igure out what is going on in the bookkeeper managed ledger library and fix the issue OR do I use IPs Alternatively you can configure the quarantine settings in bookkeeper client. So your bookkeeper client doesn’t mark the bookie as a bad bookie in a short period of time. ----
