Jason Parraga
Work around worked for me as well, thanks!
> Can this relate to this issue related #3577 ? I don't believe so considering we are reproducing this issue on Redis 3.15.5. > There is no such way except...
I spent several hours yesterday digging into the code to try and understand what might be going on. As you mentioned, the `freeSubscribeConnectionsCounter` indicates how many connections remaining connections can...
> AWS ES uses DNS based load-balancing to resolve the hostname to the ES nodes, it's not an EC2-style load balancer. In this case it seems like clients **would** benefit...
@olivere The Java library has the same problem. It resolves an IP address from the ES cluster domain name and caches the IP address of the data node indefinitely. What...
> This is obviously a pretty terrible user experience that seems ripe for the use of sniffing. I ended up testing sniffing with the AWS ES cluster and it appears...
For what its worth, we ended up writing our own custom sniffer and it appears to work well. I forced a blue/green deployment of an AWS ES cluster and I...
Try setting this configuration option. It worked for me. ``` "plugin.name": "pgoutput" ``` I was able to find this suggestion in the gitter history: https://gitter.im/debezium/user?at=5d970a2e874aeb2d23e70971
Thanks for the response @mrniko I think using two Redisson instances will not be very elegant. I imagine that any reference like a Map or a Lock will be tied...
@RangelReale What is the latest on this? Do you need any help?