+1. The second-level message, such as scheduled/transactional message, should not be bound to the master.
heng du <[email protected]> 于2022年1月26日周三 12:54写道： > Great improvement, whether in terms of usability or complexity of the > operation, it is a very big improvement to the master-slave architecture. > > Thank, > Henry > > jinrongtong <[email protected]> 于2022年1月26日周三 11:51写道： > > > Hi, RocketMQ Community: > > > > I want to start a RIP to support a slave acting master mode which > enhances > > the slave capability after the master goes offline. This mode can solve > the > > consumption interruption of order messages, delay messages, transaction > > messages after the master goes offline, as well as the metadata rollback > > after the master goes online again. > > > > I have written my proposal and you can click on the link below： > > > > > > > https://docs.google.com/document/d/1LCTkfem6wcV-PqWjzPAvaxgqFMCj3ymPakDrcodX9ic/edit?usp=sharing > > > > Chinese version： > > > > https://shimo.im/docs/6CqVccXgtWgXCYwv/ > > > > > > > > If you have any questions or suggestions, please reply to this email or > > comment on the proposal. > > > > > > > > > > Thanks > > RongtongJin >
