[improve][doc] optimize old docs for broker load balancing #663
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What change does this PR introduce?
This PR introduces the following changes (topics in the red box below)
Removes old docs for broker load balancing, as we've added the new docs and published them on the Pulsar website (https://pulsar.apache.org/docs/next/concepts-broker-load-balancing-concepts/, https://pulsar.apache.org/docs/next/concepts-broker-load-balancing-types/)
Brings "Anti-affinity namespaces" out of the broker load balancing docs and sets it as an independent section. This is a quick win as it is a copy from the existing doc https://pulsar.apache.org/docs/next/administration-load-balance/#distribute-anti-affinity-namespaces-across-failure-domains
Doc development plan - Read before review
For the current doc of Broker Load Balancer, we want to tackle the following challenges:
Consequently, we’ve created the following content development plans:
Broker Load Balancing | Information Architecture
This document presents a high-level architecture overview, including how we address content gaps and reconcile existing documentation.
Broker Load Balancing | Doc Outline
This document delves into the specifics of the content development plan, providing purpose and context for each section.
doc
Ackowledgements
@Demogorgon314 many thanks for your technical guidance and great support!
cc @heesung-sn @@D-2-Ed