Skip to content

Switch Block Node Connections at block boundary #21878

@derektriley

Description

@derektriley

Background

Ideally, if the CN needs to switch connections to another Block Node (for example a higher priority block node or the configuration on disk changing), the current active connection should finish streaming it's block, send a EndStream request with RESET and then perform the switch.

This may involve adding a candidate connection to the manager and not switching in the BlockNodeConnectionTask, rather the active connection will trigger the switch.

Acceptance Criteria

  1. Ensure switching connections occurs at a block boundary where possible
  2. Updated unit tests

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions