You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@rocketmq.apache.org by "Mark Yang (JIRA)" <ji...@apache.org> on 2018/02/13 04:19:01 UTC
[jira] [Comment Edited] (ROCKETMQ-350) Add multiple Network Interface Cards support for “Broker Machine”
[ https://issues.apache.org/jira/browse/ROCKETMQ-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361798#comment-16361798 ]
Mark Yang edited comment on ROCKETMQ-350 at 2/13/18 4:18 AM:
-------------------------------------------------------------
I’m working on this, here is the plan:
1 Broker will report multiple addresses to Name Server, the format is like the multiple nameServer addr: ip1: port;ip2:port;ip3:port
2 After consumer/producer get the route info from Name Server, there is a test or detect process, then store one accessible address for each broker.
3 All the changes are backward compatible. But if using the changed broker and old version client, the consumer/producer will get exception because fetched broker’s addr is not “ip:port”, it could be “ip1:port;ip2:port”.
Should a configure be added in the broker to disable the new feature?
Any advice will be greatly appreciated.
was (Author: mark_yang):
I’m working on this, here is the plan:
1 Broker will report multiple addresses to Name Server, the format is like the multiple nameServer addr: ip1: port;ip2:port;ip3:port
2 After consumer/producer get the route info from Name Server, there is a test or detect process, then store one accessible address for each broker.
3 All the changes are backward compatible. But if using the changed broker and old version client, the consumer/producer will get exception because fetched broker’s addr is not “ip:port”, it could be “ip1:port;ip2:port”.
Should a configure be added in the broker to disable the new feature?
Any advice will be greatly appreciated.
> Add multiple Network Interface Cards support for “Broker Machine”
> -----------------------------------------------------------------
>
> Key: ROCKETMQ-350
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-350
> Project: Apache RocketMQ
> Issue Type: Improvement
> Components: rocketmq-broker, rocketmq-client
> Affects Versions: 4.3.0
> Reporter: Mark Yang
> Assignee: yukon
> Priority: Major
>
> It is becoming commonplace to have more than one Network Interface Card (NIC), usually one for local network communication, another for remote communication.
> Supporting multiple Network Interface Cards support for “Broker Machine” could be very useful.
> Design suggestion: Let Broker report multiple IPs to name server, or let user configure the broker’s IPs. Client may get multiple IPs of a Broker, it should have a logic to choose a proper IP
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)