yuxian0908 commented on PR #8503: URL: https://github.com/apache/ozone/pull/8503#issuecomment-2924116194
> @yuxian0908 Instead of having to maintain 2 codecs can we just drop the entire snapdiff db as part of the upgrade framework. I just feel it would reduce a lot of complexity. Since snapshot diff db is an ephemeral db anyhow as all entries would be eventually deleted. Thank you for the suggestion — I agree that dropping the snapdiff DB during upgrade would certainly simplify the implementation by removing the need to maintain backward compatibility codecs. However, I'm not entirely sure if it's safe to drop the entire DB as part of the upgrade process. While the snapshot diff DB is indeed ephemeral in nature, I’m not fully certain whether doing so might have implications for in-progress or recently triggered snapshot diff jobs, especially in active systems. Would you mind sharing a bit more context or guidance on whether this approach has been considered before, and if there are any concerns around data loss or job consistency? Please feel free to correct me if I misunderstood anything. -- 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: issues-unsubscr...@ozone.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@ozone.apache.org For additional commands, e-mail: issues-h...@ozone.apache.org
