You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have conductor using Dynomite for persistence and queuing. Conductor uses Dyno client to connect to Dynomite.
Now we want to enable locking in conductor for consistency. I had a look at this PR - #271.
Is there a way to enable locking using Dyno client? If yes, what are the configuration to be set on conductor side.
Best Regards,
Chary
The text was updated successfully, but these errors were encountered:
In VotingHostsFromToken when votingSize is not provided (i.e DEFAULT_LOCK_VOTING_SIZE = -1 in ConnectionPoolConfigurationImpl) effectiveVotingSize is set to MAX_VOTING_SIZE (5). This makes it DynoLockClient quorum to 3. Is this intentional ? OR effectiveVotingSize should be set to MIN_VOTING_SIZE ?
Hi,
We have conductor using Dynomite for persistence and queuing. Conductor uses Dyno client to connect to Dynomite.
Now we want to enable locking in conductor for consistency. I had a look at this PR - #271.
Is there a way to enable locking using Dyno client? If yes, what are the configuration to be set on conductor side.
Best Regards,
Chary
The text was updated successfully, but these errors were encountered: