Roland Sommer
Roland Sommer
The specific usecase on my side is that I want to implement monitoring checks bound to the single hosts of the cluster so that every host just reports back wrong...
@deniszh I'm wondering about your example from above: the only command where the SingleHost-flag is actually evaluated is in `restore.go`. If I do a dry run of a rebalance using...
We are seeing the same error as given above (with `Caused by: java.util.NoSuchElementException: Future.filter predicate is not satisfied`) since updating to kafka 3.3 and kafka-lag-exporter 0.8.0. We had no problems...
I did a test build with updated kafka dependencies to 3.3.1, but the error still persists. Resulting kafka dependencies in the snapshot release after bumping kafka to 3.3.1: ``` org.apache.kafka.kafka_2.12-3.3.1.jar...
Just installed kafka-lag-exporter 0.8.1 and we are still seeing the same errors - the service keeps crashing.
Hi @deniszh , indeed, flock was at its default value (`false`) - under normal conditions there is only go-carbon writing to the whisper files. Strange behaviour, though - because only...
Despite the error being triggered by the AppInfo mbean, setting different client_ids for the manual configured kafka input instances fixed this.
As I have the same request, maybe #151 is enough for this?
#151 has been merged but then reverted by upstream - apparently, this is not wanted.
I opened #159 with the additional handling of `PGBOUNCER_EXPORTER_METRICS_PATH` and `PGBOUNCER_EXPORTER_PIDFILE_PATH` removed. While using a config file could also be valid and I am well aware of the shortcomings of...