Do read request to local + originating replicas only for read-after-write case
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 298
- Avg merge
- 21h 43m
- Merged PRs (30d)
- 9
Description
With pull request #827 , we are able to reorder replicas in the order of local, originating and then other dc replicas.
One more enhancement can be done based on this is do read request to 'local + originating' only in read-after-write case.
We should have a [configuration](https://github.com/linkedin/ambry/pull/827#issuecomment-352196278) to turn on/off this.
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 reading pull request #827 and its linked configuration discussion to understand the existing local, originating, and other-DC replica ordering. Trace the read-after-write request path from there; done means a configuration can enable or disable restricting those reads to local and originating replicas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100