Skip to content

BlockBufferService change from TTL to specific number of blocks #21725

@derektriley

Description

@derektriley

Background

The block buffer service should use a configurable set number of blocks for the buffer instead of being based on wall clock time and configurable TTL.

In addition, take a look at perhaps blocking the transaction handling thread in HandleWorkflow. Specifically perhaps we should block/wait there vs creating a completable future on another thread (pruning thread) as that could lead to more than the set number of blocks being opened in the buffer. (Since the pruning thread runs on wall clock time).

Acceptance Criteria

  1. Implement the above including unit tests and potentially new HAPI 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