You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We go through the trouble of shipping a table of CPU performance data for EC2 types as of v0.11.2, so we should be able to launch here. It looks like the standard CPU fingerprinter causes an error on graviton (ARM) instances, because there is no MHz information available. (On AMD/Intel, data is available but meaningless and discarded).
…etected
Previously, Nomad would fail to startup if the CPU fingerprinter could
not detect the cpu total compute (i.e. cores * mhz). This is common on
some EC2 instance types (graviton class), where the env_aws fingerprinter
will override the detected CPU performance with a more accurate value
anyway.
Instead of crashing on startup, have Nomad use a low default for available
cpu performance of 1000 ticks (e.g. 1 core * 1 GHz). This enables Nomad
to get past the useless cpu fingerprinting on those EC2 instances. The
crashing error message is now a log statement suggesting the setting of
cpu_total_compute in client config.
Fixes#7989
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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
We go through the trouble of shipping a table of CPU performance data for EC2 types as of v0.11.2, so we should be able to launch here. It looks like the standard CPU fingerprinter causes an error on graviton (ARM) instances, because there is no MHz information available. (On AMD/Intel, data is available but meaningless and discarded).
ubuntu@ip-172-31-17-121:~$ curl -s http://169.254.169.254/latest/meta-data/instance-type a1.medium
ubuntu@ip-172-31-17-121:~$ ./nomad version Nomad v0.11.2 (807cfebe90d56f9e5beec3e72936ebe86acc8ce3)
The text was updated successfully, but these errors were encountered: