[OAK-2817] TARMK Cold Standby cleanup removes too many binary segments

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.12, 1.1.7, 1.2.1
• Fix Version/s: 1.0.14, 1.2.3, 1.3.0, 1.4
• Component/s: segmentmk
• Labels: docs-impacting production resilience
• Assignee: Alex Deparvu
• Reporter: Alex Deparvu
• Created: 28/Apr/15 09:02
• Updated: 02/Mar/16 11:31
• Resolved: 06/May/15 12:38

Description

It looks like the standby cleanup process could remove a lot more binary segments than permitted because of the order in which such segments are persisted. the sync will first persist the data segment referencing a binary, then the binary segment itself, this introduces problems when it spreads over multiple tar files and the #cleanup method expects them to be persisted the other way around (this is an implementation detail of the cleanup, but it is implemented this way for efficiency).

Issue Links

• relates to: OAK-2535 TARMK Cold Standby allow cleanup on standby instance