scylladb / scylladb/alternator-client-java

Failed to recover when node sending /localnodes goes down

Open
#88 0 comments 0 reactions 1 assignee View on GitHub

@CodeLieutenant is already working on this.

Since Jun 18, 2026.

Dominant language
Java
Stars
0
Forks
7
Avg merge
21h 23m
Merged PRs (30d)
9

Description

As described in the https://scylladb.atlassian.net/browse/SCT-370
Alternator loadbalancing library fails to fetch the nodes from the one instance when that instance is down and others are responding. Looks like the library always uses the supplied the IP address to fetch others from /localnodes, but when that node goes down it fails the whole test util.
Suggested fix:

  1. Store all other nodes and use them as fallback if the primary supplied node is not available
  2. Allow multiple nodes to be supplied to the library and then you be used in round robin fashion for fetching /localnodes and when one goes down it removes it from the list.
  3. Combined 1 and 2. Supply multiple and when nodes are discovered it, they also become the fallback for running /localnodes

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.