keith-turner commented on issue #4324: URL: https://github.com/apache/accumulo/issues/4324#issuecomment-1971673766
In 2.1 and 3.1 there is a metadata table compaction time iterator that does something similar for bulk load markers. This iterator was removed in the elasticity branch because it was not needed. However changes to how bulk import does clean up and the introduction of the compaction markers mean something like this probably still needed. IMO the compaction time iterator in 2.1 and 31. is not a very clean way to do this because it reads from ZK. In elasticity doing this w/ a compaction time iterator would not be possible because fate ids will need to be read from ZK or the new fate table. Would not want a metadata compaction iterator attempting to read from the new fate table. This new check should run periodically in the manager or GC. IMO the GC process seems like the best place. Whichever process it runs in the code should be self contained and easily moved to another process. Realized this was an issue while working on #4323 -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
