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

Why are there restrictions on the election timeout, heartbeat and lease? #80

Closed
bubbajoe opened this issue Jun 9, 2024 · 1 comment · Fixed by #82
Closed

Why are there restrictions on the election timeout, heartbeat and lease? #80

bubbajoe opened this issue Jun 9, 2024 · 1 comment · Fixed by #82

Comments

@bubbajoe
Copy link

bubbajoe commented Jun 9, 2024

Hello,

I came across this repo and the simplicity/flexibility really inspired me to switch from hashicorp/raft in my Distributed API Gateway at dgate-io/dgate; There were a few other reasons, but I will spare you the details.

I plan to create a cluster that spans across the globe (I am aware of the potential low latency/throughput). And I am wondering why there are min/max restrictions on the election timeout, heartbeat and lease values and if there are any potential issues that you foresee if they were to be increased.

These values seem very low even for a regional deployment of some key/value database.

@jmsadair
Copy link
Owner

jmsadair commented Jun 9, 2024

Hi Joe,

I don't think there are issues with this for your use case. I chose values that I thought were within a reasonable range for most use cases, but I can go ahead and increase them or remove them all together. I'll update this today or tomorrow.

@jmsadair jmsadair linked a pull request Jun 9, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

2 participants