Closed OmerShemesh closed 3 weeks ago
/cc @cescoffier (redis), @gsmet (redis), @gwenneg (cache), @machi1990 (redis)
Possibly related to this one: https://github.com/vert-x3/vertx-redis-client/issues/343
Closing as https://github.com/vert-x3/vertx-redis-client/issues/343 has been fixed and integrated in Quarkus.
Please re-open it with a reproducer if you are still having the issue.
Let me reopen this, because https://github.com/vert-x3/vertx-redis-client/issues/343 has not been fixed in a Vert.x release yet. And when we do integrate it, we'll have to adjust the configuration model in Quarkus too. So the remaining work is small, but non-zero still.
My bad! I was thinking it was integrated
Describe the bug
I've created a redis cluster using AWS elasticache (with no cluster mode). The cluster contains a master and 2 replicas.
I'm building a Lambda using the quarkus-amazon-lambda extension as well as the quarkus-redis-client extension. I've configured my client to use this type:
quarkus.redis.client-type=replication
.I've deployed my lambda and configured it to be in the same VPC as my Elasticache Redis cluster.
When invoking the lambda, I'm getting this error:
The ip in the error(x.x.x.x) is outside of my VPC.
Turns out that Vertx RedisReplicationClient is using the
info replication
command that returns:Where the ips from the command are indeed the ips from the error above.
This is clearly a problem with the Vertx client. I've tried to deploy a simple lambda using nodejs and the redis dependency and it worked as expected.
Expected behavior
A successful connection from the lambda to Elasticache.
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response