merlimat opened a new pull request, #1159:
URL: https://github.com/apache/pulsar-site/pull/1159
### Motivation
PIP-454 (apache/pulsar#25219) introduced a framework for live-migrating a
Pulsar cluster's metadata store from ZooKeeper to Oxia with no downtime,
shipping in Pulsar 5.0. There is currently no user-facing documentation for it.
### Modifications
- Add a new page, **Migrate metadata store**
(`administration-metadata-store-migration.md`), to the next-version docs,
covering:
- How the write-pause-and-copy migration works and the migration phases
(PREPARATION / COPYING / COMPLETED / FAILED)
- Prerequisites: Pulsar 5.0+, Oxia cluster setup, bookies running the
`metadata-store:` driver, superuser access
- Step-by-step procedure: status check, start, monitoring, broker/bookie
config updates, ZooKeeper decommissioning
- Failure handling and the REST API endpoints
- Add a **Use Oxia as metadata store** section to
`administration-metadata-store.md`, since the migration guide configures
`oxia://` URLs that were otherwise undocumented
- Register the new page in `sidebars.json` under Administration, next to
"Configure metadata store"
The content was verified against the PIP-454 implementation on apache/pulsar
master (CLI, REST paths, migration semantics in `MigrationCoordinator` /
`DualMetadataStore`).
Note: the docs use `pulsar-admin metadata-migration` per PIP-454 and
`CmdMetadataMigration`; the current registration in `PulsarAdminTool` exposes
the command as `migration` instead — a follow-up alignment fix in apache/pulsar
is planned.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
