Migrations infra mm #20130
Closed
Migrations infra mm #20130
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/dt |
Signed-off-by: Michał Maślanka <[email protected]>
Added a feature that needs to be active for Redpanda to support data migrations. Signed-off-by: Michał Maślanka <[email protected]>
Introduced separate logger for data migrations to easily separate all log entries related with migrating data across the clusters. Signed-off-by: Michał Maślanka <[email protected]>
Introduced types representing inbound and outbound data migration types together with the state and related metadata. Signed-off-by: Michał Maślanka <[email protected]>
Introduced commands to manage data migrations. The commands represent creation, update and deletion of migration. Signed-off-by: Michał Maślanka <[email protected]>
Introduced a class that is going to be instantiated on every shard and will contain information about migrated resources. The class is intended to be used by a validation logic in hot path where migration information will be queried to block writes and properties updates. Signed-off-by: Michał Maślanka <[email protected]>
Signed-off-by: Michał Maślanka <[email protected]>
Introduce a data migration table that is intended to store and track data migration state. The table is going to be instantiated only on shard 0 as it is not performance critical to access full migration data. The table is driving migrated resources updates and validates the migration state transitions. Signed-off-by: Michał Maślanka <[email protected]>
Signed-off-by: Michał Maślanka <[email protected]>
Introduced RPCs allowing routing data migration related requests to current controller leader. Signed-off-by: Michał Maślanka <[email protected]>
Introduced `cluster::data_migration_frontend`. Frontend class is an entry point for the migration subsystem. It exposes API allowing caller to interact with data migrations. Signed-off-by: Michał Maślanka <[email protected]>
Introduced placeholder for data migrations backend component. Signed-off-by: Michał Maślanka <[email protected]>
Signed-off-by: Michał Maślanka <[email protected]>
Added admin server APIs in `/v1/migartions` path allowing external clients to interact with migrations subsystem Signed-off-by: Michał Maślanka <[email protected]>
Signed-off-by: Michał Maślanka <[email protected]>
When topic is being migrated we can not allow the topic properties and partition updates. Added validation preventing creation of the topic with the same name as the name on inbound migration topic, topic property updates and topic deletion. Signed-off-by: Michał Maślanka <[email protected]>
bashtanov
force-pushed
the
migrations-infra-mm
branch
from
d774d58
to
5dd5fdf
Compare
|
/dt |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backports Required
Release Notes