-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Feature request: Keep-alive setting for remote exec UI #8727
Comments
Thanks for the suggestion, @jfcantu. It does seem simple enough to implement in the UI, though I’m wondering if it should have CLI support as well, then both consumers could use the same flag. I’ll ask around about this. |
This closes #8727, thanks to jfcantu for the suggestion. The CLI implementation of exec already has a 10-second heartbeat so this mirrors that: https://github.com/hashicorp/nomad/blob/v0.12.3/api/allocations.go#L161-L173
This closes #8727, thanks to @jfcantu for the suggestion. The CLI implementation of exec already has a 10-second heartbeat so this mirrors that: https://github.com/hashicorp/nomad/blob/v0.12.3/api/allocations.go#L161-L173
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Hey folks,
Simple (hopefully?) feature request for the Nomad remote exec web UI:
We run our Nomad cluster behind an AWS application load balancer that serves the UI and API. The ALB has a connection idle timeout, which by default is 60 seconds. So, basically, if you open a remote
exec
session, it will only stay open as long as there's either input or output from the session - otherwise, it terminates after the timeout expires.It would be helpful for Nomad to have a "keep-alive" function for
exec
sessions to prevent issues like this.The text was updated successfully, but these errors were encountered: