You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@rocketmq.apache.org by "binzhaomobile (JIRA)" <ji...@apache.org> on 2017/06/20 06:04:00 UTC

[jira] [Created] (ROCKETMQ-228) There should be a constraint that a broker only belongs to a cluster

binzhaomobile created ROCKETMQ-228:
--------------------------------------

             Summary: There should be a constraint that a broker only belongs to a cluster
                 Key: ROCKETMQ-228
                 URL: https://issues.apache.org/jira/browse/ROCKETMQ-228
             Project: Apache RocketMQ
          Issue Type: Improvement
          Components: rocketmq-broker, rocketmq-namesrv
    Affects Versions: 4.1.0-incubating, 4.2.0-incubating, 4.3.0-incubating
         Environment: All Environments
            Reporter: binzhaomobile
            Assignee: yukon
            Priority: Minor


Currently in NameServer module, there is no constraint that a broker(a master broker and its slave brokers) should belong to a name server. Allow a master broker belong to one cluster and its slave belong to another cluster doesn't make good sense.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)