Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using Dyno lock with conductor #315

Open
charybr opened this issue Jan 13, 2023 · 2 comments
Open

Using Dyno lock with conductor #315

charybr opened this issue Jan 13, 2023 · 2 comments

Comments

@charybr
Copy link

charybr commented Jan 13, 2023

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

@charybr
Copy link
Author

charybr commented Jan 16, 2023

I think we need to instantiate DynoLockClient in Conductor. Is it right?

@charybr
Copy link
Author

charybr commented Jan 24, 2023

Hi @rsrinivasanNetflix ,

effectiveVotingSize = votingSize == -1 ? MAX_VOTING_SIZE : votingSize;

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 ?

effectiveVotingSize = votingSize == -1 ? MIN_VOTING_SIZE : votingSize;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant