[BYDB-Replica] Support Liaison Groups with Global-Level Failover in Liaison

Open
#12,875 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
java

Research direction

Start by reading the existing Load Balancer feature referenced in issue #12874 and the Liaison component's current behavior. Trace how liaison nodes report health and how traffic is distributed, then define how groups, replica-based availability, global failover, and upstream health reporting should fit together. Done means unavailable groups redirect traffic to healthy groups while preserving service continuity.

Written by the indexing model from the issue text.

Description

database feature
Search before asking
  • I had searched in the issues and found no similar feature requirement.
Description

Based upon the existing Load Balancer(#12874) feature in BanyanDB's Liaison component, we would like to propose the addition of Liaison Groups. This enhancement will enable the creation of logically grouped liaison nodes, facilitating more granular load balancing and robust failover strategies. By organizing liaison nodes into groups, the BanyanDB can ensure higher availability, better resource management, and improved resilience against group-level failures.

Key Requirements:

  • Group Definition: Allow administrators to define multiple liaison groups, each containing several liaison nodes.
  • Group Availability Status: Continuously assess the availability of each liaison group. A group is unavailable if the number of healthy data nodes falls below the specified replica number.
  • Automatic Failover: If a group becomes unavailable, traffic will be automatically redirected to other healthy groups to maintain service continuity.
  • Health Reporting: Upstream groups must communicate their availability status to the global liaison to inform traffic distribution decisions.
Use case

No response

Related issues

No response

Are you willing to submit a pull request to implement this on your own?
  • Yes I am willing to submit a pull request on my own!
Code of Conduct
Dominant language
Java
Stars
25k
Forks
6.6k
Avg merge
12h 1m
Merged PRs (30d)
43

Getting set up

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.

More from apache/skywalking

All issues in apache/skywalking

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.