killme2008 / killme2008/Metamorphosis
关于MetaQ的master/slave机制
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 672
- PR merge metrics
- No merged PRs in 30d
Description
既然MetaQ的master和slave的brokerID是一样,那么MetaQ是如何知道从master还是从slave中pull message呢?怎样让consumer从slave中拉取数据而不是从master呢?我看了https://github.com/killme2008/Metamorphosis/wiki/%E6%BA%90%E7%A0%81%E5%88%86%E6%9E%90
中说client可以连接cluster上的任何一台机器包括master和slave,作为它的消息来源,类似数据库的读写分离。但是又有说:生产环境中有一台master和一个同步slave,slave是不注册到zookeeper上的,这句话是不是不对?我发现slave明明是在ZooKeeper中注册的。
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked MetaQ source-analysis wiki page and trace the master/slave and ZooKeeper registration behavior it describes. Compare that documentation with the reported broker discovery and consumer pull behavior; done means the master/slave and ZooKeeper statements are clarified or corrected.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100