Skip to content

HDDS-4183. [FSO]Support backward compatible upgrade to a version with key prefix management.#2526

Closed
errose28 wants to merge 9 commits intoapache:masterfrom
errose28:HDDS-4183
Closed

HDDS-4183. [FSO]Support backward compatible upgrade to a version with key prefix management.#2526
errose28 wants to merge 9 commits intoapache:masterfrom
errose28:HDDS-4183

Conversation

@errose28
Copy link
Contributor

What changes were proposed in this pull request?

Add a pre-finalize validation action to check that FSO is not enabled until the cluster is finalized.

What is the link to the Apache JIRA

HDDS-4183

How was this patch tested?

Integration test added. Test runs in ~5 seconds by only starting new OMs and reusing the one required SCM across tests.

* master:
  HDDS-5358. Incorrect cache entry invalidation causes intermittent failure in testGetS3SecretAndRevokeS3Secret (apache#2518)
  HDDS-5608. Fix wrong command in ugrade doc (apache#2524)
  HDDS-5000. Run CI checks selectively (apache#2479)
  HDDS-4929. Select target datanodes and containers to move for Container Balancer (apache#2441)
  HDDS-5283. getStorageSize cast to int can cause issue (apache#2303)
  HDDS-5449 Recon namespace summary 'du' information should return replicated size of a key (apache#2489)
  HDDS-5558. vUnit invocation unit() may produce NPE (apache#2513)
  HDDS-5531. For Link Buckets avoid showing metadata. (apache#2502)
  HDDS-5549. Add 1.1 to supported versions in security policy (apache#2519)
  HDDS-5555. remove pipeline manager v1 code (apache#2511)
  HDDS-5546.OM Service ID change causes OM startup failure. (apache#2512)
  HDDS-5360. DN failed to process all delete block commands in one heartbeat interval (apache#2420)
  HDDS-5021. dev-support Dockerfile is badly outdated (apache#2480)
@avijayanhwx avijayanhwx requested a review from rakeshadr August 16, 2021 16:49
@errose28
Copy link
Contributor Author

Just a note that this is not needed for 1.2.0 because FSO is only supported for new installs in that version. Assuming 1.3.0 supports upgrading to FSO, it will be needed for anyone who did not start fresh with 1.2.0 and wants to go to 1.3.0. We can revisit this once upgrading to FSO is possible cc @rakeshadr.

@errose28
Copy link
Contributor Author

FSO prefinalize validation is going to look very different than this in 1.3.0 due to having per bucket layout. I am closing this pull request and we can open a new one under this Jira for the updated changes.

@errose28 errose28 closed this Jan 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants