Spring OpenFeign源码分析(3) 负载均衡与服务发现
创始人
2025-05-30 09:34:11
0

在前文,我们了解到feign实现负载均衡需要两个重要的接口:

  1. ILoadBalancer - 管理可用的服务器集合,实现软负载均衡
  2. IRule - 实现负载均衡算法

本文重点介绍这两个接口:

  1. 主要实现类
  2. 注入方式:默认的实现类,可用的实现类
  3. 实现类的算法

ILoadBalancer

ILoadBalancer接口

public interface ILoadBalancer {public void addServers(List newServers);// 选择一个可用的serverpublic Server chooseServer(Object key);public void markServerDown(Server server);@Deprecatedpublic List getServerList(boolean availableOnly);public List getReachableServers();public List getAllServers();
}

实现类

ILoadBalancer|-- AbstractLoadBalancer|-- BaseLoadBalancer|-- DynamicServerListLoadBalancer|-- ZoneAwareLoadBalancer|-- NoOpLoadBalancer

默认情况下使用的是ZoneAwareLoadBalancer实现类,是在RibbonClientConfiguration配置了里面装配的。

@Bean
@ConditionalOnMissingBean
public ILoadBalancer ribbonLoadBalancer(IClientConfig config,ServerList serverList, ServerListFilter serverListFilter,IRule rule, IPing ping, ServerListUpdater serverListUpdater) {if (this.propertiesFactory.isSet(ILoadBalancer.class, name)) {return this.propertiesFactory.get(ILoadBalancer.class, config, name);}return new ZoneAwareLoadBalancer<>(config, rule, ping, serverList,serverListFilter, serverListUpdater);
}

ZoneAwareLoadBalancer类

// 封装zone -> LoadBalancer映射关系
private ConcurrentHashMap balancers = new ConcurrentHashMap();public Server chooseServer(Object key) {// 当只有一个zone时,直接使用父类chooseServer方法选择serverif (!ENABLED.get() || getLoadBalancerStats().getAvailableZones().size() <= 1) {return super.chooseServer(key);}Server server = null;try {// LoadBalancerStats封装zone -> server集关系LoadBalancerStats lbStats = getLoadBalancerStats();Map zoneSnapshot = ZoneAvoidanceRule.createSnapshot(lbStats);// 获取可用的zone集Set availableZones = ZoneAvoidanceRule.getAvailableZones(zoneSnapshot, triggeringLoad.get(), triggeringBlackoutPercentage.get());if (availableZones != null &&  availableZones.size() < zoneSnapshot.keySet().size()) {// 随机一个zoneString zone = ZoneAvoidanceRule.randomChooseZone(zoneSnapshot, availableZones);if (zone != null) {// 从balancers获取该zone对应的LoadBalancerBaseLoadBalancer zoneLoadBalancer = getLoadBalancer(zone);// 用LoadBalancer选择一个可用serverserver = zoneLoadBalancer.chooseServer(key);}}} catch (Exception e) {logger.error("Error choosing server using zone aware logic for load balancer={}", name, e);}if (server != null) {return server;} else {return super.chooseServer(key);}
}

LoadBalancerStats类封装着zone -> server集和zone -> ZoneStats关系,如下:

public class LoadBalancerStats implements IClientConfigAware {String name;// Map serverStatsMap = new ConcurrentHashMap();// key都是zonevolatile Map zoneStatsMap = new ConcurrentHashMap();volatile Map> upServerListZoneMap =new ConcurrentHashMap>();// 连接失败数量阈值private volatile CachedDynamicIntProperty connectionFailureThreshold;// 断路器跳闸超时阈值private volatile CachedDynamicIntProperty circuitTrippedTimeoutFactor;// 最大断路器跳闸超时时长private volatile CachedDynamicIntProperty maxCircuitTrippedTimeout;private static final DynamicIntProperty SERVERSTATS_EXPIRE_MINUTES = DynamicPropertyFactory.getInstance().getIntProperty("niws.loadbalancer.serverStats.expire.minutes", 30);// 服务器节点 -> 服务器State关系private final LoadingCache serverStatsCache;// ...
}

ServerStats维护着服务节点的状态信息,包括:请求数量、失败数量、断路器跳闸状态等,提供判断服务节点可用(断路器是否打开)的方法,在负载均衡选择可用服务节点时会使用到这些状态信息。

ZoneStats类封装当前服务端节点状态:

public class ZoneStats {private final LoadBalancerStats loadBalancerStats;private final String zone;private static final String PREFIX = "ZoneStats_";private final Counter counter;final String monitorId;// ...
}

看一下super的chooseServer方法:

public Server chooseServer(Object key) {if (counter == null) {counter = createCounter();}counter.increment();if (rule == null) {return null;} else {try {// 使用IRule选择一个server// IRule里面封装负载均衡算法// 这个IRule是在创建LoadBalancer对象时传递进来的// 默认使用ZoneAvoidanceRulereturn rule.choose(key);} catch (Exception e) {return null;}}
}

IRule

Interface that defines a “Rule” for a LoadBalancer. A Rule can be thought of as a Strategy for loadbalacing. Well known loadbalancing strategies include Round Robin, Response Time based etc.

IRule接口

public interface IRule{/** choose one alive server from lb.allServers or* lb.upServers according to key*/public Server choose(Object key);public void setLoadBalancer(ILoadBalancer lb);public ILoadBalancer getLoadBalancer();    
}

实现类

在这里插入图片描述

  • AbstractLoadBalancerRule - 抽象类(provides a default implementation for setting and getting load balancer)
  • ClientConfigEnabledRoundRobinRule - 内部封装一个RoundRobinRule对象,本质上就是使用RoundRobinRule做轮询负载均衡
  • PredicateBasedRule - 使用AbstractServerPredicate做过滤和轮询负载均衡
  • ZoneAvoidanceRule - 使用ZoneAvoidancePredicate和AvailabilityPredicate做过滤和轮询负载均衡
  • NacosRule - 基于Nacos的NamingService进行服务发现、使用random-weight方式做负载均衡
  • RandomRule
  • RoundRobinRule

默认使用的是ZoneAvoidanceRule实现,是在RibbonClientConfiguration配置了里面装配的。

@Bean
@ConditionalOnMissingBean
public IRule ribbonRule(IClientConfig config) {if (this.propertiesFactory.isSet(IRule.class, name)) {return this.propertiesFactory.get(IRule.class, config, name);}ZoneAvoidanceRule rule = new ZoneAvoidanceRule();rule.initWithNiwsConfig(config);return rule;
}

ZoneAvoidanceRule类

这个类继承了PredicateBasedRule类,choose方法的实现在父类里面:

// PredicateBasedRule.choose
public Server choose(Object key) {ILoadBalancer lb = getLoadBalancer();Optional server = getPredicate().chooseRoundRobinAfterFiltering(lb.getAllServers(), key);if (server.isPresent()) {return server.get();} else {return null;}       
}// AbstractServerPredicate.chooseRoundRobinAfterFiltering
public Optional chooseRoundRobinAfterFiltering(List servers, Object loadBalancerKey) {// 获取有资格的server集List eligible = getEligibleServers(servers, loadBalancerKey);if (eligible.size() == 0) {return Optional.absent();}// 轮询return Optional.of(eligible.get(incrementAndGetModulo(eligible.size())));
}

ZoneAvoidanceRule类实现了父类的getPredicate方法,返回CompositePredicate对象,封装着ZoneAvoidancePredicate和AvailabilityPredicate用于过滤可用server节点:

private CompositePredicate compositePredicate;public ZoneAvoidanceRule() {super();ZoneAvoidancePredicate zonePredicate = new ZoneAvoidancePredicate(this);AvailabilityPredicate availabilityPredicate = new AvailabilityPredicate(this);compositePredicate = createCompositePredicate(zonePredicate, availabilityPredicate);
}private CompositePredicate createCompositePredicate(ZoneAvoidancePredicate p1, AvailabilityPredicate p2) {return CompositePredicate.withPredicates(p1, p2).addFallbackPredicate(p2).addFallbackPredicate(AbstractServerPredicate.alwaysTrue()).build();
}

CompositePredicate是一个代理类,内部使用Predicate链获取可用Server集:

public List getEligibleServers(List servers, Object loadBalancerKey) {List result = super.getEligibleServers(servers, loadBalancerKey);Iterator i = fallbacks.iterator();while (!(result.size() >= minimalFilteredServers && result.size() > (int) (servers.size() * minimalFilteredPercentage))&& i.hasNext()) {AbstractServerPredicate predicate = i.next();result = predicate.getEligibleServers(servers, loadBalancerKey);}return result;
}

ZoneAvoidancePredicate

public boolean apply(PredicateKey input) {if (!ENABLED.get()) {return true;}String serverZone = input.getServer().getZone();if (serverZone == null) {// there is no zone information from the server, we do not want to filter// out this serverreturn true;}LoadBalancerStats lbStats = getLBStats();if (lbStats == null) {// no stats available, do not filterreturn true;}if (lbStats.getAvailableZones().size() <= 1) {// only one zone is available, do not filterreturn true;}Map zoneSnapshot = ZoneAvoidanceRule.createSnapshot(lbStats);if (!zoneSnapshot.keySet().contains(serverZone)) {// The server zone is unknown to the load balancer, do not filter it out return true;}Set availableZones = ZoneAvoidanceRule.getAvailableZones(zoneSnapshot, triggeringLoad.get(), triggeringBlackoutPercentage.get());if (availableZones != null) {return availableZones.contains(input.getServer().getZone());} else {return false;}
}

AvailabilityPredicate

public boolean apply(PredicateKey input) {LoadBalancerStats stats = getLBStats();if (stats == null) {return true;}return !shouldSkipServer(stats.getSingleServerStat(input.getServer()));
}// 判断断路器的状态
private boolean shouldSkipServer(ServerStats stats) {        if ((CIRCUIT_BREAKER_FILTERING.get() && stats.isCircuitBreakerTripped()) || stats.getActiveRequestsCount() >= activeConnectionsLimit.get()) {return true;}return false;
}

NacosRule类

public class NacosRule extends AbstractLoadBalancerRule {@Autowiredprivate NacosDiscoveryProperties nacosDiscoveryProperties;@Autowiredprivate NacosServiceManager nacosServiceManager;@Overridepublic Server choose(Object key) {try {String clusterName = this.nacosDiscoveryProperties.getClusterName();String group = this.nacosDiscoveryProperties.getGroup();DynamicServerListLoadBalancer loadBalancer = (DynamicServerListLoadBalancer) getLoadBalancer();String name = loadBalancer.getName();// 使用NamingService服务发现查找Server集NamingService namingService = nacosServiceManager.getNamingService(nacosDiscoveryProperties.getNacosProperties());List instances = namingService.selectInstances(name, group, true);if (CollectionUtils.isEmpty(instances)) {return null;}// 使用clusterName过滤一下List instancesToChoose = instances;if (StringUtils.isNotBlank(clusterName)) {List sameClusterInstances = instances.stream().filter(instance -> Objects.equals(clusterName,instance.getClusterName())).collect(Collectors.toList());if (!CollectionUtils.isEmpty(sameClusterInstances)) {instancesToChoose = sameClusterInstances;}}// random-weight算法Instance instance = ExtendBalancer.getHostByRandomWeight2(instancesToChoose);return new NacosServer(instance);} catch (Exception e) {return null;}}@Overridepublic void initWithNiwsConfig(IClientConfig iClientConfig) {}
}

服务发现

ServerListUpdater

Strategy for DynamicServerListLoadBalancer to use for different ways of doing dynamic server list updates.

用于更新服务节点列表。

public interface ServerListUpdater {/*** an interface for the updateAction that actually executes a server list update*/public interface UpdateAction {void doUpdate();}/*** start the serverList updater with the given update action* This call should be idempotent.*/void start(UpdateAction updateAction);/*** stop the serverList updater. This call should be idempotent*/void stop();// 其他方法
}

PollingServerListUpdater实现类:

public synchronized void start(final UpdateAction updateAction) {if (isActive.compareAndSet(false, true)) {final Runnable wrapperRunnable = new Runnable() {@Overridepublic void run() {if (!isActive.get()) {if (scheduledFuture != null) {scheduledFuture.cancel(true);}return;}try {updateAction.doUpdate();lastUpdated = System.currentTimeMillis();} catch (Exception e) {logger.warn("Failed one update cycle", e);}}};// 启动周期调度scheduledFuture = getRefreshExecutor().scheduleWithFixedDelay(wrapperRunnable,initialDelayMs, // 1000refreshIntervalMs, // 30 * 1000TimeUnit.MILLISECONDS);}
}

ServerList

Interface that defines the methods sed to obtain the List of Servers.

public interface ServerList {public List getInitialListOfServers();/*** Return updated list of servers. This is called say every 30 secs* (configurable) by the Loadbalancer's Ping cycle*/public List getUpdatedListOfServers();   
}

NacosServerList实现类使用nacos的NamingService做服务发现。

DynamicServerListLoadBalancer

这个实现类里面维护着ServerListUpdater和ServerList对象,启动ServerListUpdater做服务发现:

public class DynamicServerListLoadBalancer extends BaseLoadBalancer {// ...volatile ServerList serverListImpl;volatile ServerListFilter filter;protected final ServerListUpdater.UpdateAction updateAction = new ServerListUpdater.UpdateAction() {@Overridepublic void doUpdate() {updateListOfServers();}};protected volatile ServerListUpdater serverListUpdater;// ...public void updateListOfServers() {List servers = new ArrayList();if (serverListImpl != null) {servers = serverListImpl.getUpdatedListOfServers();if (filter != null) {servers = filter.getFilteredListOfServers(servers);}}updateAllServerList(servers);}
}

RibbonClientConfiguration

ServerListUpdater是在RibbonClientConfiguration中装配的:

@Bean
@ConditionalOnMissingBean
public ServerListUpdater ribbonServerListUpdater(IClientConfig config) {return new PollingServerListUpdater(config);
}

NacosRibbonClientConfiguration

ServerList是在NacosRibbonClientConfiguration中装配的:

@Bean
@ConditionalOnMissingBean
public ServerList ribbonServerList(IClientConfig config,NacosDiscoveryProperties nacosDiscoveryProperties) {if (this.propertiesFactory.isSet(ServerList.class, config.getClientName())) {ServerList serverList = this.propertiesFactory.get(ServerList.class, config,config.getClientName());return serverList;}NacosServerList serverList = new NacosServerList(nacosDiscoveryProperties);serverList.initWithNiwsConfig(config);return serverList;
}

相关内容

热门资讯

武汉摩尔影城安卓系统APP,便... 你有没有想过,一部手机就能带你走进电影的世界,享受大屏幕带来的震撼?今天,就让我带你详细了解武汉摩尔...
联想刷安卓p系统,畅享智能新体... 你有没有发现,最近联想的安卓P系统刷机热潮可是席卷了整个互联网圈呢!这不,我就迫不及待地来和你聊聊这...
mac从安卓系统改成双系统,双... 你有没有想过,你的Mac电脑从安卓系统改成双系统后,生活会有哪些翻天覆地的变化呢?想象一边是流畅的苹...
kindke安卓系统激活码,激... 亲爱的读者,你是否在寻找一款能够让你手机焕然一新的操作系统?如果你是安卓用户,那么今天我要给你带来一...
萤石云监控安卓系统,安卓系统下... 你有没有想过,家里的安全可以随时随地掌握在手中?现在,有了萤石云监控安卓系统,这不再是梦想啦!想象无...
手机安卓系统会不会爆炸,系统升... 手机安卓系统会不会爆炸——一场关于安全的探讨在当今这个数字化的世界里,手机已经成为我们生活中不可或缺...
安卓系统双清详图解,恢复出厂设... 你有没有遇到过手机卡顿、运行缓慢的问题?别急,今天就来给你详细解析一下安卓系统的“双清”操作,让你的...
召唤抽奖系统安卓直装,轻松体验... 你知道吗?现在市面上有一种特别火的玩意儿,那就是召唤抽奖系统安卓直装。是不是听起来就让人心动不已?没...
系统工具箱安卓2.3,深度解析... 你有没有发现,手机里的那些小工具,有时候就像是个神奇的百宝箱呢?今天,就让我带你一探究竟,看看安卓2...
华硕平板安卓刷机系统,解锁性能... 亲爱的数码爱好者们,你是否曾为你的华硕平板安卓系统感到厌倦,想要给它来一次焕然一新的体验呢?那就跟着...
鸿蒙系统与安卓怎么区别,差异解... 你有没有发现,最近手机圈子里有个大热门,那就是鸿蒙系统和安卓系统的区别。这两位“系统大侠”各有各的绝...
红帽系统怎么刷回安卓,红帽系统... 你是不是也和我一样,对红帽系统刷回安卓充满了好奇?别急,今天就来给你详细揭秘这个过程,让你轻松上手,...
ios安卓联想三系统,全面解析... 你有没有发现,现在的手机市场真是热闹非凡呢!各种操作系统轮番登场,让人眼花缭乱。今天,就让我带你来聊...
安卓调用系统相机并存盘,And... 你有没有想过,手机里的照片和视频,是怎么被我们随手拍下,又神奇地存到手机里的呢?今天,就让我带你一探...
安卓4.0原生系统下,引领智能... 你有没有发现,安卓4.0原生系统下,手机的使用体验简直就像打开了新世界的大门?今天,就让我带你一起探...
安卓c13系统,创新功能与性能... 你知道吗?最近安卓系统又来了一次大更新,那就是安卓C13系统。这可不是一个小打小闹的更新,而是带来了...
鸿蒙3.0脱离安卓系统,开启全... 你知道吗?最近科技圈可是炸开了锅,因为华为的新操作系统鸿蒙3.0横空出世,竟然宣布要脱离安卓系统,这...
安卓怎么应对苹果系统,安卓系统... 你知道吗?在智能手机的世界里,安卓和苹果就像是一对相爱相杀的恋人。安卓系统,这位多才多艺的“大众情人...
安卓系统如何开橱窗教程,安卓系... 你有没有想过,你的安卓手机里也能开个橱窗,展示那些你心爱的宝贝?没错,就是那种可以随时翻看、随时分享...
安卓系统软件APK,深入探究安... 你有没有发现,手机里的那些好玩的应用,其实都是靠一个小小的文件来“住”进去的?没错,就是安卓系统里的...