cpu_total_compute not working #2638
Labels
Comments
|
Can you give the client logs when it just starts up at debug level? |
|
We currently only use the |
|
Here are the debug logs. |
|
Hmm yeah! Looks like my prediction was right. Will get this fixed for 0.6! |
|
Is it possible to permit the override even when it's possible to detect the cpu? |
|
@samisil Not currently but the fix to this issue would be exactly that. Hopefully will be part of 0.6.0 |
|
Thanks @dadgar. I really need this.
On Jun 22, 2017 19:04, "Alex Dadgar" <notifications@github.com> wrote:
@samisil <https://github.com/samisil> Not currently but the fix to this
issue would be exactly that. Hopefully will be part of 0.6.0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2638 (comment)>,
or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AP3SWKJ2VMgHc4M252udsZQtjo_wc_4Aks5sGpB8gaJpZM4NZYZp>
.
|
|
just ran into this too, perhaps
So for me the magic becomes: cpu_total_compute="$(dmidecode -t 4 | grep 'Current Speed' | sed 's/.*: //' | sed 's/ .*//' | awk '{s+=$1} END {print s}')"
cat > ../data/local/conf/nomad_slave.json <<EOF
{
"client": {
"cpu_total_compute": ${cpu_total_compute},
"enabled": true
}
}
EOF |
@balupton This will only give you the total compute per core, so if you have more than a single core it will be underreported. This should do the trick (note this will not fly if you have more than one CPU with different number of frequency/cores) |
kennethkalmer
added a commit
to kennethkalmer/ansible-nomad
that referenced
this issue
Jan 3, 2021
Works around the issue reported in hashicorp/nomad#2638
kennethkalmer
added a commit
to kennethkalmer/ansible-nomad
that referenced
this issue
Jan 3, 2021
Works around the issue reported in hashicorp/nomad#2638
kennethkalmer
added a commit
to kennethkalmer/ansible-nomad
that referenced
this issue
Jan 3, 2021
Works around the issue reported in hashicorp/nomad#2638
|
A more compact version |
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If you have a question, prepend your issue with
[question]or preferably use the nomad mailing list.If filing a bug please include the following:
Nomad version
Output from
nomad versionNomad v0.5.6
Operating system and Environment details
SUSE 12
s390x
Issue
The client stanza variable cpu_total_compute is not working. There is no MHZ variable in /proc/cpuinfo. So the MHZ defaults to zero. I wish to set that value using this cput_total_compute but it does not change the value. I have also tried in a VM running in an x86 VM using VirtualBox without any luck.
Reproduction steps
Create a client configuration with the value set.
client {
enabled = true
servers = ["x.x.x.x"]
cpu_total_compute = 4200
}
Run nomad.
nomad node-status --verbose <node_id>
cpu.totalcompute = 0
Nomad Server logs (if appropriate)
Nomad Client logs (if appropriate)
Job file (if appropriate)
The text was updated successfully, but these errors were encountered: