Metrics and Log Printing about rocketmq-operator HOT 2 CLOSED

Hi, thanks for your detailed feedback!

1. bug1 for question We cannot guarantee that the name-server cluster must be started before the broker clusters:

In fact the broker controller did has a primary mechanism to wait for name-server cluster started which uses a shared variable IsNameServersStrInitialized. You can check the PR #31. However the current solution is not perfect, you can propose PR to improve it.

2. bug2 for the down-scaling question:

Currently the operator does not support for down-scaling (shrink) yet. Therefore if you upgrade the size of the cluster from 2=》1, the controller won't do anything. The down-scaling is a very complicated process which is related to re-arrange the data and many other problems. So simply we suggest user not to apply the reduced size currently.

3. for the feature request:
   We are glad to see more contributors to join the project. Welcome to submit your code of metric support and logs!

As you may see the affinity/anti-affinity/taint feature is partly supported and pending on PR #42. However the response of the community maybe slow, we will continue to progress on this feature and release it soon.

from rocketmq-operator.

[bug 1] has been fixed.

[bug 2] & [bug 3], deleting resources is a dangerous operation, especially in production environment. So it may be more appropriate to delete resources by users manually.

[bug 4] has been fixed.

from rocketmq-operator.