Replies: 2 comments 3 replies
-
The local mode represents that the connection between Proxy and Broker is a local procedure call. So escaping the message to the remote broker is not recommended. As an alternative plan, the SLAVE broker should also have a proxy. The client will only send messages to MASTER node. If the MASTER node is down, the client will send messages to the new MASTER after the election. |
Beta Was this translation helpful? Give feedback.
-
Yeah, But in the current implementation, it will not escape. In local mode, the client doesn't actually know who is MASTER, because the topic route is wrapped. And as your say, in production, we will deploying the proxy on all the broker nodes(Because we don't know which broker is Master on autoswicth HA or Dledger mode). |
Beta Was this translation helpful? Give feedback.
-
Proxy local mode has the ability of multi-protocol adaptation, with the advantages of low latency and high throughput. But it has additional problems, in local deployment mode, it becomes stateful. The client always need know which broker of Proxy is master, if the current connected proxy of broker is SLAVE, it will send message error. We should escape the message to remote broker in
LocalMessageService
when the current broker is SLAVE./cc @drpmma
Beta Was this translation helpful? Give feedback.
All reactions