-
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
* Dimension "bandwidth exceeded" exhausted on 1 nodes #7405
Comments
i dont understand why, but rebooting the server (rather than the client where this is failing) made the problem go away |
FWIW, i can't reproduce it. I think this might happen when you start without network_interface, then change it later. possibly the old value is cached somewhere. |
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. |
Nomad version
Nomad v0.10.4 (f750636)
Operating system and Environment details
archlinux.
Issue
there appears to be no way to set network_speed or at least ignore it if the interface is not the public interface (which i need to set, otherwise nomad announced the wrong address internally to consul)
unclear if network_speed is ignored because nomad node-status --verbose does not show any network resources, so there is no way to know why it is exhausted either, since no jobs require any network resources
Reproduction steps
client {
network_interface = "wireguard"
network_speed = 1000
}
launch any job without network resource constrains
###logs
so apparently not ignored. still cant launch anything, even tho no jobs require network resources
The text was updated successfully, but these errors were encountered: