Redis client fails when cluster / sentinel configuration is changed

[ivivanov-bg]

Describe the bug

When connected to redis running in sentinel mode, writing fails when master node is changed.

Expected behavior

Redis client to automatically detect the cluster topology change and to issue commands to the new master

Actual behavior

Commands are issued to the previous master node, resulting in

READONLY You can't write against a read only slave

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

Most probably this is caused by an issue in the underlying redis client.

vertx-redis-client#320

[quarkus-bot]

/cc @Ladicek (redis), @cescoffier (redis), @machi1990 (redis), @radcortez (config)

[Ladicek]

This will be fixed in Vert.x 4.5.10.

[Ladicek]

Fixed in #43041.