Error - ReplicaMetaDataRequest
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 298
- Avg merge
- 21h 43m
- Merged PRs (30d)
- 9
Description
When attempting standard clustering, my one of my machines keeps throwing this error: `[2019-07-19 14:20:15,555] ERROR ReplicaMetaDataRequest from unknown Replica AMBRY-BE1, with path /ambrydisk/0 (com.github.ambry.replication.ReplicationManager)`
This is on AMBRY-BE2, and the value of the unknown replica changes as I edit `host.name` in the server.properties config file. I've tried pointing towards both boxes, same error both times. Thoughts?
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 reproducing standard clustering on AMBRY-BE1 and AMBRY-BE2 with the server.properties host.name values described in the report. Trace the ReplicaMetaDataRequest handling in ReplicationManager and compare the configured host names with the logged replica identity and path. Done means clustering no longer reports an unknown replica.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100