Tim Evdokimov

Could this be a solution: https://github.com/wal-e/wal-e/pull/407?

I wonder if any of maintainers can comment something on that. It may be a downright wrong approach altogether, this is also a valuable feedback I'd definitely appreciate.

workaround: use master branch, not pip version see also: #403

I also may share similar experience. Using Burrow with Prometheus exporter. sum(kafka_burrow_total_lag)by group doesn't match sum(kafka_burrow_partition_lag)by group. Not for all topics/consumers, though.

Recipe instances are independent and run along each other. Interaction instances are just stateless functions and could indeed be used by any recipe instance. Each recipe instance performs its own...

Thank you for your suggestion @kpavlov. I think I'll stick with prometheus collectors, as they are extremely low-overhead. Nothing prevents however adding an exporter to extract the data from prometheus...

Still reproduced with latest r2dbc and pool org.postgresql.r2dbc-postgresql 1.1.1.RELEASE io.r2dbc.r2dbc-pool 1.0.2.RELEASE Tried .collectList() and -Dreactor.bufferSize.small=1024 as suggested in https://github.com/r2dbc/r2dbc-pool/issues/198 - did not help.

...and it seems like r2dbc-pool is not relevant, it keeps happening even when the pool was replaced. It is r2dbc-postgresql indeed this is the query I use to look at...