Zverev Konstantin

My use case for dns discovery doesn't account for short living dns entries (like coredns in kubernetes), yes. Setting LoadBalancer.update_frequency should be enough for most use cases when resolving "real"...

There seems to be something wrong with connection retrying/handling with this PR. When I restart redis (`docker restart dev-redis-1` for example) I'm getting `redis.exceptions.ConnectionError: Connection closed by server.` I'm also...

I've approached this from different perspective, by using https://github.com/kube-rs/kube. And turning my proxy into kind of static ingress. Where router listens for changes in endpointslices and updates backends with ServiceDiscovery...

I will, in near future. Right now I'm migrating some varnish scripts at work to pingora, after I'll try to come up with nicer api for services/routing/registering, generic enough to...

I'am actully relying on this behaviour in many places. Don't have strong preference how this should be, but I would consider this a breaking change.

To ease migration burden I would suggest a parameter for this. Maybe at least even instantly deprecated one, so [polars-upgrade](https://github.com/MarcoGorelli/polars-upgrade) has something to work with. Because it's the most scary...

Interested in that too. For transparent caching of graphql requests. Latency would go up due to buffering for sure.

Same here. Hangs randomly, sometimes after 1 hour, sometimes after 2 days. Remedied by restarting container every 30 mins. ``` python = "^3.13" Django = "^5.2.5" celery = "^5.5.3" django-celery-beat...

I need results backend. Will try to change it to DB. But redis is most optimal for my use case because of lots of small tasks.

Tried using DB result backend and redis broker instead of rabbitmq - problem remains.