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

Allow tuning of heartbeat ttls #2859

Merged
merged 1 commit into from
Jul 19, 2017
Merged

Allow tuning of heartbeat ttls #2859

merged 1 commit into from
Jul 19, 2017

Conversation

dadgar
Copy link
Contributor

@dadgar dadgar commented Jul 19, 2017

This PR allows tuning of heartbeat TTLs. An example of very aggressive
settings is as follows:

server {
  heartbeat_grace = "1s"
  min_heartbeat_ttl = "1s"
  max_heartbeats_per_second = 200.0
}

This PR allows tuning of heartbeat TTLs. An example of very aggressive
settings is as follows:

```
server {
  heartbeat_grace = "1s"
  min_heartbeat_ttl = "1s"
  max_heartbeats_per_second = 200.0
}
```
@dadgar
Copy link
Contributor Author

dadgar commented Jul 19, 2017

Binaries built by cherry picking change onto 0.5.6:
linux_arm64.zip
linux_arm.zip
linux_amd64.zip
linux_386.zip

// MaxHeartbeatsPerSecond is the maximum target rate of heartbeats
// being processed per second. This allows the TTL to be increased
// to meet the target rate.
MaxHeartbeatsPerSecond float64 `mapstructure:"max_heartbeats_per_second"`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why float?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thats what the underlying server config uses.

@dadgar dadgar merged commit 62a9abc into master Jul 19, 2017
@dadgar dadgar deleted the f-heartbeat-tunables branch July 19, 2017 17:07
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants