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

Nomad job example #4469

Merged
merged 5 commits into from
Dec 20, 2024
Merged

Nomad job example #4469

merged 5 commits into from
Dec 20, 2024

Conversation

bcirh
Copy link
Contributor

@bcirh bcirh commented Dec 18, 2024

What this PR does:

  • Adding HashiCorp Nomad job example (microservices mode)

Checklist

  • Tests updated
  • Documentation added
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

@CLAassistant
Copy link

CLAassistant commented Dec 18, 2024

CLA assistant check
All committers have signed the CLA.

Copy link
Member

@joe-elliott joe-elliott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few questions. I have no nomad experience, but I'm fine with this PR. The danger is that this becomes out of date and no one on the team knows how to maintain it.

I think it's fine. If the nomad loving community keeps this up to date then we will keep it. If in a year it's had no updates and it no longer works we will likely remove it.

example/nomad/tempo-distributed/config.yml Show resolved Hide resolved
example/nomad/tempo-distributed/tempo.hcl Outdated Show resolved Hide resolved
resources {
cpu = 200
memory = 128
memory_max = 2048
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we want to specify a max? I guess as an example that's fine, but resource usage of Tempo can cover a huge range depending on usage patterns.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

memory value is how much RAM will nomad reserve for the task, memory_max value is how much task can expand if it goes above reserved memory (memory oversubscription). memory_max values can be removed, in that case value of memory will be max value. I would leave it as is, since this is an example, pepole can decide what works best for them. I will update README.md to address this.

Copy link
Member

@joe-elliott joe-elliott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution!

@joe-elliott joe-elliott merged commit e2c7920 into grafana:main Dec 20, 2024
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants