redis sentinel for conductor HA

[ritu-p]

Has anyone configured 3 node HA conductor without using dynomite as persistence? I am seeing some issues such as below when one of the nodes is down.
java.lang.RuntimeException: com.netflix.dyno.connectionpool.exception.PoolOfflineException: PoolOfflineException: [host=Host [hostname=UNKNOWN, ipAddress=UNKNOWN, port=0, rack: UNKNOWN, datacenter: UNKNOW, status: Down, hashtag=null, redacted latency=0(0), attempts=0]host pool is offline and no Racks available for fallback.

is this expected ?
Is it a good idea to use redis_sentinel directly in place of dynamo

[apanicker-nflx]

@RuriRyan Can you please provide your inputs on running Conductor with redis sentinel configuration? Thanks

[RuriRyan]

@ritu-p please have a look at #2321 (comment) where I pasted some sample configuration which we use in our production setup.
Altough we haven't updated conductor in a while, but I kinda doubt much has changed in the regards of persistence. We use v2.31.0.

And an additional config line for the log4j vuln in this version:

      log4j2.formatMsgNoLookups=true