commit | 31b4eb1f7d25273e7b2f8b3af6600faedebda522 | [log] [tgz] |
---|---|---|
author | gaozhangmin <gaozhangmin456@qq.com> | Wed Apr 06 23:58:47 2022 +0800 |
committer | Nicolò Boschi <boschi1997@gmail.com> | Wed Apr 06 17:59:17 2022 +0200 |
tree | 2859a5b49d9709d66f583848c1e318fc4174c542 | |
parent | 84529a857a28ff6ee3c59437ce8f5b11a55ae56d [diff] |
only update topology when bookie rack changed It is unnecessary to update topology, removing and adding the same bookieNode, if the rack of bookie stay unchanged. Reviewers: Yong Zhang <zhangyong1025.zy@gmail.com>, Nicolò Boschi <boschi1997@gmail.com>, Andrey Yegorov <None>, ZhangJian He <shoothzj@gmail.com>, Enrico Olivelli <eolivelli@gmail.com> This closes #2790 from gaozhangmin/remove-unnecessary-update-rack (cherry picked from commit 67c963a1b02de04166778d906f4cffe89dd86562) Signed-off-by: Nicolò Boschi <boschi1997@gmail.com>
Apache BookKeeper is a scalable, fault tolerant and low latency storage service optimized for append-only workloads.
It is suitable for being used in following scenarios:
Please visit the Documentation from the project website for more information.
For filing bugs, suggesting improvements, or requesting new features, help us out by opening a Github issue or opening an Apache jira.
Subscribe or mail the user@bookkeeper.apache.org list - Ask questions, find answers, and also help other users.
Subscribe or mail the dev@bookkeeper.apache.org list - Join development discussions, propose new ideas and connect with contributors.
Join us on Slack - This is the most immediate way to connect with Apache BookKeeper committers and contributors.
We feel that a welcoming open community is important and welcome contributions.
See Developer Setup to get your local environment setup.
Take a look at our open issues: JIRA Issues Github Issues.
Review our coding style and follow our pull requests to learn about our conventions.
Make your changes according to our contribution guide.