You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by GitBox <gi...@apache.org> on 2022/03/01 03:24:35 UTC

[GitHub] [rocketmq] drpmma opened a new issue #3905: Support brokerName in request protocol

drpmma opened a new issue #3905:
URL: https://github.com/apache/rocketmq/issues/3905


   **FEATURE REQUEST**
   
   1. Support `brokerName` in request protocol.
   2. `brokerName` is a higher-level abstraction than `brokerAddress` and should be taken in request.
   3. Related components should know request-target by `brokerName` such as logic queue extension, envoy-like cloud-native gateway, or even more separate computing and storage to decouple computing from current broker logic.
   4. Detail request code: `PULL_MESSAGE`, `UPDATE_CONSUMER_OFFSET`, `QUERY_CONSUMER_OFFSET`, `SEARCH_OFFSET_BY_TIMESTAMP`, `GET_MIN_OFFSET`, `GET_MAX_OFFSET`.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [rocketmq] drpmma commented on issue #3905: Support brokerName in request protocol

Posted by GitBox <gi...@apache.org>.
drpmma commented on issue #3905:
URL: https://github.com/apache/rocketmq/issues/3905#issuecomment-1056103134


   > BrokerAddress can be used as a router, I do not get why do you need brokerName.
   
   BrokerAddress is not taken in remoting layer protocol. So the secondary components don't have the information to route to other brokers, that's why we need a BrokerName


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [rocketmq] lizhanhui commented on issue #3905: Support brokerName in request protocol

Posted by GitBox <gi...@apache.org>.
lizhanhui commented on issue #3905:
URL: https://github.com/apache/rocketmq/issues/3905#issuecomment-1059910974


   +1 for the change. IP-centered strategy suffers a lot in the era of cloud and container orchestration. We need logical representation to adapt to this trend.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [rocketmq] duhenglucky commented on issue #3905: Support brokerName in request protocol

Posted by GitBox <gi...@apache.org>.
duhenglucky commented on issue #3905:
URL: https://github.com/apache/rocketmq/issues/3905#issuecomment-1056045094


   @drpmma In favor of this recommendation, the entire Remoting layer is currently IP oriented. Using broker names instead of IP can better hide the underlying state of the broker, especially the abstraction of logical resources brought by logical queues and other features.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [rocketmq] duhenglucky edited a comment on issue #3905: Support brokerName in request protocol

Posted by GitBox <gi...@apache.org>.
duhenglucky edited a comment on issue #3905:
URL: https://github.com/apache/rocketmq/issues/3905#issuecomment-1056045094


   @drpmma In favor of this recommendation, the entire Remoting layer is currently IP oriented. Using broker names instead of IP can better hide the underlying state of the broker, especially the abstraction of logical resources brought by logical queues and other features. So would you like to submit a RIP for this proposal?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [rocketmq] drpmma edited a comment on issue #3905: Support brokerName in request protocol

Posted by GitBox <gi...@apache.org>.
drpmma edited a comment on issue #3905:
URL: https://github.com/apache/rocketmq/issues/3905#issuecomment-1056103134


   > BrokerAddress can be used as a router, I do not get why do you need brokerName.
   
   BrokerAddress is not taken in remoting layer protocol while is just a target. So the secondary components don't have the information to route to other brokers, that's why we need a BrokerName


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [rocketmq] ni-ze commented on issue #3905: Support brokerName in request protocol

Posted by GitBox <gi...@apache.org>.
ni-ze commented on issue #3905:
URL: https://github.com/apache/rocketmq/issues/3905#issuecomment-1056036449


   BrokerAddress can be used as a router, I do not get why do you need brokerName.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [rocketmq] chenzlalvin commented on issue #3905: Support brokerName in request protocol

Posted by GitBox <gi...@apache.org>.
chenzlalvin commented on issue #3905:
URL: https://github.com/apache/rocketmq/issues/3905#issuecomment-1062440505


   Not only brokerName, the queueId also need abstraction, unbind with specific physical node
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org