Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DR - Ability to migrate segment metadata to a new deployment when data is fully flushed to LTS. #4938

Closed
sachin-j-joshi opened this issue Jul 10, 2020 · 1 comment · Fixed by #5423
Assignees
Labels

Comments

@sachin-j-joshi
Copy link
Contributor

sachin-j-joshi commented Jul 10, 2020

Problem description
Pravega administrator should be able to migrate data from existing Pravega deployment to a new Pravega deployment when all segments in existing deployments are fully flushed to LTS.

Problem location
Segment store
Admin tool

Suggestions for an improvement
Implement/Enhance DebugSegmentStore that enumerates segments on existing LTS and populates the metadata in new deployment.

@sachin-j-joshi sachin-j-joshi added the kind/feature New feature that should be added label Jul 10, 2020
@sachin-j-joshi sachin-j-joshi changed the title DR - Ability to migrate segment metadata data to a new deployment when data is fully flushed to LTS. DR - Ability to migrate segment metadata to a new deployment when data is fully flushed to LTS. Jul 10, 2020
@ManishKumarKeshri
Copy link
Contributor

Though PR #4716 fixed it, but in that PR:

  • We delete the old segment metadata from the LTS and create a new one using the segments(except shadow segments) listed from the LTS. While registering the segments onto new segment metadata, we only use segment's length and sealed status.

We now need to:

  • Copy the core attributes from old metadata to new metadata.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants