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

Add granular ping_interval configuration properties #4991

Open
jarretlavallee opened this issue Jan 24, 2024 · 3 comments
Open

Add granular ping_interval configuration properties #4991

jarretlavallee opened this issue Jan 24, 2024 · 3 comments
Labels
proposal Enhancement idea or proposal

Comments

@jarretlavallee
Copy link
Contributor

Proposed change

Add the ability to configure the ping_interval for each connection type separately.

Use case

Each connection type is likely to have a different network pattern and connection, so the ping_interval could be configured to different values. A route could have a lower ping_interval client or leafnode. This is the case in 2.10, where the ping interval is set to 30s for routes and everything else uses the ping_interval.

Adding a different way to configure the ping interval for each connection type would help in scenarios where the network is blackholed. Lower values will allow for faster detection.

Contribution

No response

@jarretlavallee jarretlavallee added the proposal Enhancement idea or proposal label Jan 24, 2024
@wallyqs
Copy link
Member

wallyqs commented Feb 7, 2024

Added for routes here: #5029

@derekcollison
Copy link
Member

Do we need for GWs or do we already have that?

@jarretlavallee
Copy link
Contributor Author

We have the global one and routes in 2.10.10+. It would be nice to have a specific setting for each of the following.

  • Gateways
  • Leafnodes
  • Clients

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

No branches or pull requests

3 participants