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.

Sign up for GitHub

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

Jump to bottom

Server Job fails on different nodeSelectors #1318

Open
flashpixx opened this issue Feb 28, 2022 · 1 comment
Open

Server Job fails on different nodeSelectors #1318

flashpixx opened this issue Feb 28, 2022 · 1 comment

Comments

@flashpixx
Copy link

Describe the bug

I run the helm chart with a nodeSelector, so the server-job runs on a different node than in my case cassandra, but the job fails every time. I set these values:

cadence:
  server:
    nodeSelector:
      <my node key: <my node value>

Steps to reproduce the issue:

Apply the values above

Expected behavior

Server-Job should run also on different kind of nodes, it my helpful if the nodeSelector can be set as well for the server-job

Additional context

I try this with helm chart version 0.23.0 and 0.22.1
@akijakya
Copy link
Contributor

akijakya commented Mar 4, 2022

Hi!

I tried to reproduce the bug with chart version 0.22.1 on AWS by creating a cluster with nodes of different instance types, and using the node.kubernetes.io/instance-type label to put Cadence pods on a node of a specific instance type and for me it worked multiple times. My specific values were:

cadence:
  server:
    nodeSelector:
      node.kubernetes.io/instance-type: m4.large

Could you provide more details (node description, pod description and helm chart values) so we can take a look what might went wrong for you?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@flashpixx @akijakya