Leader: decide what to record when helper fails a report aggregation
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 70
- Forks
- 16
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 30
Description
At time of writing, when Janus is in the leader role & receives a "failed" prepare step from the helper, Janus records in its own datastore exactly the error code provided by the helper. This should change since we can't differentiate between our own logic causing an error code to be recorded & Janus reflecting a helper's error code. We could either transition to a generic error code, or better yet, record the helper's error code along with the fact that the error code came from the helper rather than the leader's logic.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the leader's handling of a failed prepare response from the helper and how the resulting error code is recorded in the datastore. Resolve whether the record should use a generic code or preserve the helper's code with provenance, then add coverage for helper-originated failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100