Details
-
Task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.48.0
-
None
Description
The changes introduced in OAK-10022, where the binary references file (.brf) is updated on every flush should be reverted.
They were introduced to fix a NullPointerException
thrown in ReadOnlyFileStore#collectBlobReferences because of the absence of the .brf file in the last open archive. However this fix was not enough and a new fix was needed (OAK-10212).
This means the changes in OAK-10022 are no longer necessary. Given that updating the brf file in-place frequently on Azure can impact write performance and backup tooling, it's better to roll them back.
Attachments
Issue Links
- fixes
-
OAK-10343 AzureTarFilesTest.testCollectBlobReferencesWithGenerationFilter unreliable
- Closed
-
OAK-10359 Unreliable test: TarFileTest.binaryReferencesIndexShouldBeTrimmedDownOnSweep
- Closed
-
OAK-10360 unreliable test AzureTarFileTest.testWriteAndReadBinaryReferences
- Closed
-
OAK-10293 AzureTarRevisionsTest fails occasionally
- Closed
- is related to
-
OAK-10022 ReadOnlyFileStore#collectBlobReferences throws NullPointerException if azure blob with binary references is missing in the tar directory
- Closed
- links to