[HDDS-3072] SCM scrub pipeline should be started after coming out of safe mode

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 0.5.0
• Labels: pull-request-available
• Assignee: Bharat Viswanadham
• Reporter: Bharat Viswanadham
• Created: 25/Feb/20 20:17
• Updated: 06/Mar/20 17:21
• Resolved: 06/Mar/20 17:10

Description

We should start scrubbing pipelines after SCM is out of safe mode.

Reasons to do this:

1. Right now, we do scrub pipeline as part of triggerPipelineCreation, now when we scrub pipelines in allocated state for more than "ozone.scm.pipeline.allocated.timeout", we might close some pipelines and with this, we might not be able to come out of safeMode. As in SafeModeRules, we get pipeline count from pipelineDB during initialization.

Example scenario:

1. Stop 3 Datanodes. 
2. Restart SCM.
3. Start Datanode after 6 mts. We shall never come out of safe mode, as pipeline in allocated state will meet scrubber time out condition.

To not to be in these kinds of scenarios, better thing to be done here is scrub pipelines after SCM out of the safe mode

 

Issue Links

• links to: GitHub Pull Request #605