Hello Li Zhanhui I'm glad to receive your response. Regarding the propagation between different brokers and the issue of copying to new nodes, there is currently no good solution based on the current architecture. I'm pleased to hear that there are ongoing consensus efforts. May I ask about the current design and progress of this work? If it aligns with our timeline and capability, we can consider building on top of this consensus algorithm.
I look forward to hearing from you again. Best Regards Zhanhui Li <lizhan...@gmail.com> 于2023年11月15日周三 20:50写道： > Hi Ding, > > The storage of ACL is primarily kept locally in the Broker, and there are > > two main options: file storage and RocksDB-based storage. In this case, > > RocksDB is used for storage, while file storage is provided as an example > > for reference purposes. > > > Either embedded RocksDB or yaml file is stored per node. This raises two > concerns: how the metadata will be propagated to newly added nodes? How to > avoid partial failure and resulting inconsistency among nodes? > > There are consensus efforts ongoing, will this this feature be built on top > of them? > > Li Zhanhui > > On Wed, Nov 15, 2023 at 8:32 PM qiaoao <qiao...@foxmail.com> wrote: > > > Good to know! Will the ACL 2.0 support ACL in NameServer? > > > > > 2023年11月15日 19:50，丁双喜 <dingshuangxi...@gmail.com> 写道： > > > > > > Hi, RocketMQ Community > > > > > > RocketMQ ACL is crucial for ensuring the security of message data. We > aim > > > to enhance its capabilities and are preparing to upgrade it to a newer > > > version. > > > > > > We have written the proposal and you can see it by the link below: > > > https://github.com/apache/rocketmq/issues/7560 > > > > > > Please reply to this email if you have any questions > > > Best Regards > > > > >
