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/09/29 02:02:46 UTC
[GitHub] [rocketmq-mqtt] DongyuanPan opened a new issue, #154: To support clientid conflict detection.
DongyuanPan opened a new issue, #154:
URL: https://github.com/apache/rocketmq-mqtt/issues/154
clientId conflict detection has not yet been implemented, because there is no distributed metadata center in release 1.0.0, only single-machine conflict detection can be achieved.
Global clientid conflict detection can now be implemented with the help of the meta module.
--
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.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] To support clientid conflict detection. [rocketmq-mqtt]
Posted by "YxAc (via GitHub)" <gi...@apache.org>.
YxAc commented on issue #154:
URL: https://github.com/apache/rocketmq-mqtt/issues/154#issuecomment-2172224104
There are two ways to implement clientid conflict detection:
- one is based on the global metadata center to kick out the old client
- the other is based on the client online event (implemented by #283 ), each broker subscribes events and kicks off the old client.
Which way of implementation do people prefer?
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq-mqtt] pingww commented on issue #154: To support clientid conflict detection.
Posted by GitBox <gi...@apache.org>.
pingww commented on issue #154:
URL: https://github.com/apache/rocketmq-mqtt/issues/154#issuecomment-1261664571
We need to discuss this metadata module in depth
--
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
Re: [I] To support clientid conflict detection. [rocketmq-mqtt]
Posted by "YxAc (via GitHub)" <gi...@apache.org>.
YxAc commented on issue #154:
URL: https://github.com/apache/rocketmq-mqtt/issues/154#issuecomment-2175465208
> There are two ways to implement clientid conflict detection:
>
> * one is based on the global metadata center to kick out the old client
> * the other is based on the client online event (implemented by [[ISSUE #116] feat: support client event notification #283](https://github.com/apache/rocketmq-mqtt/pull/283) ), each broker subscribes events and kicks off the old client.
>
> Which way of implementation do people prefer?
I will implement this based on the global meta module.
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org