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

it will be deployed on the same node When I deploy brokers with three masters and three slaves #161

Open
Misakiz opened this issue Jun 9, 2023 · 3 comments

Comments

@Misakiz
Copy link

Misakiz commented Jun 9, 2023

The issue tracker is ONLY used for the bug report(feature request need to follow RIP process). Keep in mind, please check whether there is an existing same report before you raise a new one.

Alternately (especially if your communication is not a bug report), you can send mail to our mailing lists. We welcome any friendly suggestions, bug fixes, collaboration and other improvements.

Please ensure that your bug report is clear and that it is complete. Otherwise, we may be unable to understand it or to reproduce it, either of which would prevent us from fixing the bug. We strongly recommend the report(bug report or feature request) could include some hints as the following:

BUG REPORT

  1. Please describe the issue you observed:
  • What did you do (The steps to reproduce)?
    My k8s has 7 nodes,i deploy rocketmq with mq-operator.
  • What did you expect to see?
    it was deployed on the different node When I deploy brokers with three masters and three slaves
  • What did you see instead?
    some brokers were deployed on the same node
  1. Please tell us about your environment:

  2. Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):

FEATURE REQUEST

  1. Please describe the feature you are requesting.

  2. Provide any additional detail on your proposed use case for this feature.

  3. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?

  4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:

@caigy
Copy link
Contributor

caigy commented Jun 13, 2023

Have you set Affinity? By default rocketmq-operator set "app": "broker" as label for broker pod, but did not set any anti-affinity rules. You can set such affinity rules in Affinity.

@drivebyer
Copy link
Contributor

Maybe we can provide default anti-affinity.

@caigy
Copy link
Contributor

caigy commented Sep 1, 2023

Have you set Affinity? By default rocketmq-operator set "app": "broker" as label for broker pod, but did not set any anti-affinity rules. You can set such affinity rules in Affinity.

@Misakiz Does it works for you?

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

No branches or pull requests

3 participants