Background

When BN's are falling behind and the buffer becomes 50% saturated, the CN forcefully switches to the next available node in an effort to get BlockAcknowledgements. The connection that is being closed in the BlockNodeConnectionTask doesn't get removed from an internal connections map and won't be available for selection again.

This connection needs to be removed from the map, and in addition a configurable reschedule time should be used for the connection that was closed in this scenario. Let's start at 180 seconds. This will allow automatically switching back to higher priority nodes potentially sooner than a periodic reset or the next node that was switched to having an issue which triggers re-selection logic.

Acceptance Criteria

1. Fix the above bug
2. Add a HAPI test for this scenario.
3. Unit tests for new config option and rescheduling logic

Dependencies

No response

Definition of Ready (DoR) Checklist

• Clear acceptance criteria
• Clear and detailed description
• Dependencies identified
• Links to documentation
• Should be completable in 2-3 Days
• Initial draft of Low-level design document
• At least high level test plan
• Groomed/Estimated

Definition of Done (DoD) Checklist

• Acceptance Criteria complete
• No Codacy issues greater than minor (in new code)
• JavaDocs updated/created
• Code commented
• Unit tests created/updated
• 80% test code coverage (in new code)
• Happy Path and major negative cases in HAPI tests as applicable