dgraph-io / dgraph-io/dgraph4j
State API - Keep Connection to Active Alpha Leader for Data Ingestion
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 170
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
We use the dgraph4j client to write continuous streams of data to dgraph. We are interested in always writing data to the Alpha Leader. Can the dgraph4j client implement the State API to return back which server is the leader? On the client side, we'd be able to check who the leader is and then disconnect/reconnect to the leader on a periodic basis.
More advanced request, can the dgraph4j client handle a URI with the full list of alphas in it and the dgraph4j client internally keep the connection connected to the active leader?
Why? We see increased ingest speed when writing to the Alpha leader.
https://docs.dgraph.io/admin/admin-tasks/view-cluster-state
Thanks
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
Read the linked Dgraph cluster-state documentation and inspect the dgraph4j client's existing connection API. Define how the State API exposes the active Alpha leader and how a full list of Alpha URIs would be handled; done means the requested leader-aware ingestion behavior is specified and supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100