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

[ISSUE #21] Distinguish between brokerName and brokerClusterName #22

Merged
merged 1 commit into from Jul 22, 2020

Conversation

zhihui921016
Copy link
Contributor

brokerClusterName removes the brokerGroupIndex suffix

@wlliqipeng wlliqipeng self-requested a review March 27, 2020 12:30
Copy link
Contributor

@liuruiyiyang liuruiyiyang left a comment

Choose a reason for hiding this comment

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

Seems this PR is related to PR#24, why split this PR from it? If just change the env BROKER_CLUSTER_NAME to the same broker name in different broker groups, it is not compatible with other designs like the scale up process and thus causes some issue, since the brokerClusterName here is refer to the broker group name.

@zhihui921016
Copy link
Contributor Author

zhihui921016 commented Apr 3, 2020

@liuruiyiyang the env BROKER_CLUSTER_NAME seems to only be used to generate configuration files and will not affect the scale up process which obtaining metadata through scalePodName. Also I have tested the function is normal.

@liuruiyiyang
Copy link
Contributor

LGTM

@vongosling vongosling merged commit 4f78b3f into apache:master Jul 22, 2020
@vongosling vongosling modified the milestones: 0.2.0, 0.3.0 Jul 22, 2020
zhihui921016 added a commit to zhihui921016/rocketmq-operator that referenced this pull request Aug 28, 2020
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.

None yet

3 participants