State API - Keep Connection to Active Alpha Leader for Data Ingestion

[rahst12]

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

[matthewmcneely]

We'll (@mlwelles) look into this. In the meantime, you know you can always find the leader via the zero's http port:

curl http://zero:6080/state

{
  "counter": "360",
  "groups": {
    "1": {
      "members": {
        "1": {
          "id": "1",
          "groupId": 1,
          "addr": "alpha1:7080",
          "leader": true,
          "amDead": false,
          "lastUpdate": "1772560856",
          "learner": false,
          "clusterInfoOnly": false,
          "forceGroupId": false
        }
      },
     ...