hanahmily opened a new issue, #12875:
URL: https://github.com/apache/skywalking/issues/12875

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) 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
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to