Background

Acceptance Criteria

Scenarios

• With Quiescence enabled, if there was user transaction and then a long period of time without a transaction the record file should be closed within a reasonable amount of time. (If closing is based on a Round's consensus timestamp instead of handling a user txn, this would solve this scenario).
  • Before we quiesce, we need to make sure the record file is closed
• With Quiescence disabled, similarly, if there was a user txn then a longer period of time without a txn, we need to close record files in the same pattern as above in order to return true from onSealConsensusRound (we need to return true so we can write a saved state to disk)

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