dubbo-源码分析Consumer
2024-04-05 06:07:19
counsumer使用服务的时候会在xml中配置<dubbo:reference> dubbo在spring.handles里的NamespaceHandle又有如下配置：
registerBeanDefinitionParser("application", new DubboBeanDefinitionParser(ApplicationConfig.class, true));
registerBeanDefinitionParser("module", new DubboBeanDefinitionParser(ModuleConfig.class, true));
registerBeanDefinitionParser("registry", new DubboBeanDefinitionParser(RegistryConfig.class, true));
registerBeanDefinitionParser("config-center", new DubboBeanDefinitionParser(ConfigCenterBean.class, true));
registerBeanDefinitionParser("metadata-report", new DubboBeanDefinitionParser(MetadataReportConfig.class, true));
registerBeanDefinitionParser("monitor", new DubboBeanDefinitionParser(MonitorConfig.class, true));
registerBeanDefinitionParser("provider", new DubboBeanDefinitionParser(ProviderConfig.class, true));
registerBeanDefinitionParser("consumer", new DubboBeanDefinitionParser(ConsumerConfig.class, true));
registerBeanDefinitionParser("protocol", new DubboBeanDefinitionParser(ProtocolConfig.class, true));
registerBeanDefinitionParser("service", new DubboBeanDefinitionParser(ServiceBean.class, true));
registerBeanDefinitionParser("reference", new DubboBeanDefinitionParser(ReferenceBean.class, false));
registerBeanDefinitionParser("annotation", new AnnotationBeanDefinitionParser());
所以我们来看下ReferenceBean这个类：
public p class ReferenceBean<T> extends ReferenceConfig<T> implements FactoryBean, ApplicationContextAware, InitializingBean, DisposableBean
这个类跟proiver一样都实现了InitializingBean接口，所以创建实例化完的时候都会调用他的afterPropertiesSet方法：
public void afterPropertiesSet() throws Exception {
if (applicationContext != null) {
BeanFactoryUtils.beansOfTypeIncludingAncestors(applicationContext, ConfigCenterBean.class, false, false);
}
...
Boolean b = isInit();
if (b == null && getConsumer() != null) {
b = getConsumer().isInit();
}
if (b != null && b) {
//我们主要看下这个方法
getObject();
}
}
我们主要来看下这个方法getObject() 这个方法最后会调用到init方法：
private void init() {
if (initialized) {
return;
}
initialized = true;
//检查本地存根
checkStubAndLocal(interfaceClass);
//检查当前接口Mock机制
checkMock(interfaceClass);
Map<String, String> map = new HashMap<String, String>();
map.put(Constants.SIDE_KEY, Constants.CONSUMER_SIDE);
appendRuntimeParameters(map);
if (!isGeneric()) {
String revision = Version.getVersion(interfaceClass, version);
if (revision != null && revision.length() > 0) {
map.put("revision", revision);
}
String[] methods = Wrapper.getWrapper(interfaceClass).getMethodNames();
if (methods.length == 0) {
logger.warn("NO method found in service interface " + interfaceClass.getName());
map.put("methods", Constants.ANY_VALUE);
} else {
map.put("methods", StringUtils.join(new HashSet<String>(Arrays.asList(methods)), ","));
}
}
map.put(Constants.INTERFACE_KEY, interfaceName);
appendParameters(map, application);
appendParameters(map, module);
appendParameters(map, consumer, Constants.DEFAULT_KEY);
appendParameters(map, this);
Map<String, Object> attributes = null;
if (methods != null && !methods.isEmpty()) {
attributes = new HashMap<String, Object>();
for (MethodConfig methodConfig : methods) {
appendParameters(map, methodConfig, methodConfig.getName());
String retryKey = methodConfig.getName() + ".retry";
if (map.containsKey(retryKey)) {
String retryValue = map.remove(retryKey);
if ("false".equals(retryValue)) {
map.put(methodConfig.getName() + ".retries", "0");
}
}
attributes.put(methodConfig.getName(), convertMethodConfig2AyncInfo(methodConfig));
}
}
String hostToRegistry = ConfigUtils.getSystemProperty(Constants.DUBBO_IP_TO_REGISTRY);
if (hostToRegistry == null || hostToRegistry.length() == 0) {
hostToRegistry = NetUtils.getLocalHost();
} else if (isInvalidLocalHost(hostToRegistry)) {
throw new IllegalArgumentException("Specified invalid registry ip from property:" + Constants.DUBBO_IP_TO_REGISTRY + ", value:" + hostToRegistry);
}
map.put(Constants.REGISTER_IP_KEY, hostToRegistry);
//创建接口代理对象 主要就是这里，返回接口的代理类，包括负载均衡算法
ref = createProxy(map);
ConsumerModel consumerModel = new ConsumerModel(getUniqueServiceName(), interfaceClass, ref, interfaceClass.getMethods(), attributes);
ApplicationModel.initConsumerModel(getUniqueServiceName(), consumerModel);
}
我们主要看createProxy方法，根据名称我们就可以猜到他是去创建一个代理对象：
private T createProxy(Map<String, String> map) {
URL tmpUrl = new URL("temp", "localhost", 0, map);
final boolean isJvmRefer;
//判断是否是在本地暴露
if (isInjvm() == null) {
//当url不为空时认为不是本地暴露
if (url != null && url.length() > 0) { // if a url is specified, don't do local reference
isJvmRefer = false;
} else {
// by default, reference local service if there is
isJvmRefer = InjvmProtocol.getInjvmProtocol().isInjvmRefer(tmpUrl);
}
} else {
isJvmRefer = isInjvm();
}
if (isJvmRefer) {
//只调用当前jvm下服务
URL url = new URL(Constants.LOCAL_PROTOCOL, NetUtils.LOCALHOST, 0, interfaceClass.getName()).addParameters(map);
invoker = refprotocol.refer(interfaceClass, url);
if (logger.isInfoEnabled()) {
logger.info("Using injvm service " + interfaceClass.getName());
}
} else {
//当是直接在<dubbo:reference url="xxx"/>配置时直接用配置的url
if (url != null && url.length() > 0) { // user specified URL, could be peer-to-peer address, or register center's address.
String[] us = Constants.SEMICOLON_SPLIT_PATTERN.split(url);
if (us != null && us.length > 0) {
for (String u : us) {
URL url = URL.valueOf(u);
if (url.getPath() == null || url.getPath().length() == 0) {
url = url.setPath(interfaceName);
}
if (Constants.REGISTRY_PROTOCOL.equals(url.getProtocol())) {
urls.add(url.addParameterAndEncoded(Constants.REFER_KEY, StringUtils.toQueryString(map)));
} else {
urls.add(ClusterUtils.mergeUrl(url, map));
}
}
}
//当上面都不是时去注册中心获取信息
} else { // assemble URL from register center's configuration
checkRegistry();
List<URL> us = loadRegistries(false);
if (us != null && !us.isEmpty()) {
for (URL u : us) {
//获取监控中心地址
URL monitorUrl = loadMonitor(u);
if (monitorUrl != null) {
map.put(Constants.MONITOR_KEY, URL.encode(monitorUrl.toFullString()));
}
urls.add(u.addParameterAndEncoded(Constants.REFER_KEY, StringUtils.toQueryString(map)));
}
}
if (urls.isEmpty()) {
throw new IllegalStateException("No such any registry to reference " + interfaceName + " on the consumer " + NetUtils.getLocalHost() + " use dubbo version " + Version.getVersion() + ", please config <dubbo:registry address=\"...\" /> to your spring config.");
}
}
if (urls.size() == 1) {
//监听注册中心包括创建invoker 负载均衡都在这里
invoker = refprotocol.refer(interfaceClass, urls.get(0));
} else {
List<Invoker<?>> invokers = new ArrayList<Invoker<?>>();
URL registryURL = null;
//当有多个url时使用最后一个注册中心地址 registry://
for (URL url : urls) {
//RegistryProtocol.refer
invokers.add(refprotocol.refer(interfaceClass, url));
if (Constants.REGISTRY_PROTOCOL.equals(url.getProtocol())) {
registryURL = url; // use last registry url
}
}
if (registryURL != null) { // registry url is available
// use RegistryAwareCluster only when register's cluster is available
URL u = registryURL.addParameter(Constants.CLUSTER_KEY, RegistryAwareCluster.NAME);
// The invoker wrap relation would be: RegistryAwareClusterInvoker(StaticDirectory) -> FailoverClusterInvoker(RegistryDirectory, will execute route) -> Invoker
invoker = cluster.join(new StaticDirectory(u, invokers));
} else { // not a registry url, must be direct invoke.
invoker = cluster.join(new StaticDirectory(invokers));
}
}
}
Boolean c = check;
if (c == null && consumer != null) {
c = consumer.isCheck();
}
if (c == null) {
c = true; // default true
}
if (c && !invoker.isAvailable()) {
// make it possible for consumer to retry later if provider is temporarily unavailable
initialized = false;
throw new IllegalStateException("Failed to check the status of the service " + interfaceName + ". No provider available for the service " + (group == null ? "" : group + "/") + interfaceName + (version == null ? "" : ":" + version) + " from the url " + invoker.getUrl() + " to the consumer " + NetUtils.getLocalHost() + " use dubbo version " + Version.getVersion());
}
if (logger.isInfoEnabled()) {
logger.info("Refer dubbo service " + interfaceClass.getName() + " from url " + invoker.getUrl());
}
/**
* @since 2.7.0
* ServiceData Store
*/
MetadataReportService metadataReportService = null;
if ((metadataReportService = getMetadataReportService()) != null) {
URL consumerURL = new URL(Constants.CONSUMER_PROTOCOL, map.remove(Constants.REGISTER_IP_KEY), 0, map.get(Constants.INTERFACE_KEY), map);
metadataReportService.publishConsumer(consumerURL);
}
// create service proxy
//为invoker创建一个代理对象
return (T) proxyFactory.getProxy(invoker);
}
上面的代码有点多，最主要的逻辑都在refprotocol.refer(interfaceClass, urls.get(0));这个方法里面，我们都知道refprotocol是一个自适应的扩展点，所以他会根据你的协议去调用对应的refer方法，我们的url是一个registry://协议，所以会调用到RegistryProtocol的refer方法，我们来看下：
public <T> Invoker<T> refer(Class<T> type, URL url) throws RpcException {
//设置URL的protocol 默认是dubbo并移除registry 参数
//这里的protocol不是指前面的registry://头，是指parameter里面的registry参数值，我这里是zookeeper
//下面setProtocol后就是zookeeper://了
url = url.setProtocol(url.getParameter(REGISTRY_KEY, DEFAULT_REGISTRY)).removeParameter(REGISTRY_KEY);
//所以这里获取到的就是zookeeperRegistry
Registry registry = registryFactory.getRegistry(url);
if (RegistryService.class.equals(type)) {
return proxyFactory.getInvoker((T) registry, type, url);
}
// group="a,b" or group="*"
Map<String, String> qs = StringUtils.parseQueryString(url.getParameterAndDecoded(REFER_KEY));
String group = qs.get(Constants.GROUP_KEY);
if (group != null && group.length() > 0) {
if ((COMMA_SPLIT_PATTERN.split(group)).length > 1 || "*".equals(group)) {
return doRefer(getMergeableCluster(), registry, type, url);
}
}
return doRefer(cluster, registry, type, url);
}
这个方法主要是去设置一个协议头，我这里是用到zookeeper所以url设置完之后会是zookeeper://xx这样的格式，所以下面的registry也是ZookeeperRegistry 最后会调用doRefer:
private <T> Invoker<T> doRefer(Cluster cluster, Registry registry, Class<T> type, URL url) {
RegistryDirectory<T> directory = new RegistryDirectory<T>(type, url);
//上面传过来的是zookeeperRegistry
directory.setRegistry(registry);
//这里的protocol是一个自适应扩展点
directory.setProtocol(protocol);
// all attributes of REFER_KEY
//获取url里的所以参数
Map<String, String> parameters = new HashMap<String, String>(directory.getUrl().getParameters());
//这里的url顺序是 protocol,host,port,path parameters
//所以这个url的protocol是consumer,host是参数移除掉registry.ip后的字符串拼接,port是0,path就是我们代理的接口了
URL subscribeUrl = new URL(CONSUMER_PROTOCOL, parameters.remove(REGISTER_IP_KEY), 0, type.getName(), parameters);
//这里的REGISTER_KEY在上面移除掉了，所以这里是空的，取默认值也就是true
if (!ANY_VALUE.equals(url.getServiceInterface()) && url.getParameter(REGISTER_KEY, true)) {
//getRegisteredConsumerUrl里面会添加check=false和category=consumer参数
//接着会进入zookeeperRegistry的register方法，因为zookeeperRegistry没重写该方法，所以会到父类
//FailbackRegistry的register方法
registry.register(getRegisteredConsumerUrl(subscribeUrl, url));
}
//subscribeUrl=consumer://192.168.1.2/com.lin.service.UserService?application=annotation-consumer
// &default.timeout=3000&dubbo=2.0.2&interface=com.lin.service.UserService
// &methods=add,findUserByName,findUserById&pid=11180&release=2.7.0&side=consumer×tamp=1553971735120
//构建路由链
directory.buildRouterChain(subscribeUrl);
//订阅
directory.subscribe(subscribeUrl.addParameter(CATEGORY_KEY,
PROVIDERS_CATEGORY + "," + CONFIGURATORS_CATEGORY + "," + ROUTERS_CATEGORY));
Invoker invoker = cluster.join(directory);
ProviderConsumerRegTable.registerConsumer(invoker, url, subscribeUrl, directory);
return invoker;
}
这个方法比较复杂，最主要有三步，注册zookeeper然后根据url去构建一个调用链，然后去订阅url,我们一个一个来看下，先看下registry的register，因为上面传进来的是zookeeperRegistry 它又没重写register所以会到父类的方法：
public void register(URL url) {
//继续进入父类的方法 主要是加入已注册标识集合中
super.register(url);
//在注册失败集合中移除该url
removeFailedRegistered(url);
//在未注册失败集合中移除该url
removeFailedUnregistered(url);
try {
// Sending a registration request to the server side
//注册服务 是模版模式，所以会在子类实现 我这里是zookeeperRegistry
doRegister(url);
} catch (Exception e) {
Throwable t = e;
// If the startup detection is opened, the Exception is thrown directly.
boolean check = getUrl().getParameter(Constants.CHECK_KEY, true)
&& url.getParameter(Constants.CHECK_KEY, true)
&& !Constants.CONSUMER_PROTOCOL.equals(url.getProtocol());
boolean skipFailback = t instanceof SkipFailbackWrapperException;
if (check || skipFailback) {
if (skipFailback) {
t = t.getCause();
}
throw new IllegalStateException("Failed to register " + url + " to registry " + getUrl().getAddress() + ", cause: " + t.getMessage(), t);
} else {
logger.error("Failed to register " + url + ", waiting for retry, cause: " + t.getMessage(), t);
}
// Record a failed registration request to a failed list, retry regularly
addFailedRegistered(url);
}
}
这个方法比较简单，我们直接看doRegister方法，他是在zookeeperRegistry实现的：
@Override
public void doRegister(URL url) {
try {
//创建一个临时节点
zkClient.create(toUrlPath(url), url.getParameter(Constants.DYNAMIC_KEY, true));
} catch (Throwable e) {
throw new RpcException("Failed to register " + url + " to zookeeper " + getUrl() + ", cause: " + e.getMessage(), e);
}
}
private String toUrlPath(URL url) {
//toCtegoryPath是获取节点的路径也就是/dubbo/xxx.xxx.xxx/consumers
//全路径是：/dubbo/com.lin.service.UserService/consumers/consumer%3A%2F%2F192.168.1.2%2Fcom.lin.service.UserService%3Fapplication%3Dannotation-consumer%26category%3Dconsumers%26check%3Dfalse%26default.timeout%3D3000%26dubbo%3D2.0.2%26interface%3Dcom.lin.service.UserService%26methods%3Dadd%2CfindUserByName%2CfindUserById%26pid%3D11180%26release%3D2.7.0%26side%3Dconsumer%26timestamp%3D1553971735120
return toCategoryPath(url) + Constants.PATH_SEPARATOR + URL.encode(url.toFullString());
}
看到这里我们知道这里主要是去zookeeper创建一个consumer的临时结点，这样我们的register就先看到这里，我们继续看他下一步的构建调用链是怎样的也就是buildRouterChain方法，他里面会调用：
public static <T> RouterChain<T> buildChain(URL url) {
return new RouterChain<>(url);
}
private RouterChain(URL url) {
//根据url去获取RouterFactory的自适应扩展点列表
//这里会获得配置的
//MockRouterFactory,TagRouterFactory,AppRouterFactory,ServiceRouterFactory
//配置文件有7个类，但只有类上标识或者方法上标识了Activate注解的才是自适应类，所以只有这四个符合
List<RouterFactory> extensionFactories = ExtensionLoader.getExtensionLoader(RouterFactory.class)
.getActivateExtension(url, (String[]) null);
//MockInvokersSelector、TagRouter、AppRouter、ServiceRouter
List<Router> routers = extensionFactories.stream()
.map(factory -> factory.getRouter(url))
.collect(Collectors.toList());
//配置routers
initWithRouters(routers);
}
根据上面可以知道我们的调用链其实就是MockInvokersSelector、TagRouter、AppRouter、ServiceRouter这四个，最后会封装为一个RouterChain，目前我们先知道这个调用链会有这四个就行了，再来看订阅方法这里subscribe：
public void subscribe(URL url) {
setConsumerUrl(url);
//添加到添加消费监听列表中
consumerConfigurationListener.addNotifyListener(this);
//添加到服务监听列表
serviceConfigurationListener = new ReferenceConfigurationListener(this, url);
registry.subscribe(url, this);
}
public void subscribe(URL url, NotifyListener listener) {
//把listener添加到该url的监听列表中
super.subscribe(url, listener);
//移除失败的订阅
removeFailedSubscribed(url, listener);
try {
// Sending a subscription request to the server side
//真正订阅的地方
doSubscribe(url, listener);
} catch (Exception e) {
Throwable t = e;
List<URL> urls = getCacheUrls(url);
if (urls != null && !urls.isEmpty()) {
notify(url, listener, urls);
logger.error("Failed to subscribe " + url + ", Using cached list: " + urls + " from cache file: " + getUrl().getParameter(Constants.FILE_KEY, System.getProperty("user.home") + "/dubbo-registry-" + url.getHost() + ".cache") + ", cause: " + t.getMessage(), t);
} else {
// If the startup detection is opened, the Exception is thrown directly.
boolean check = getUrl().getParameter(Constants.CHECK_KEY, true)
&& url.getParameter(Constants.CHECK_KEY, true);
boolean skipFailback = t instanceof SkipFailbackWrapperException;
if (check || skipFailback) {
if (skipFailback) {
t = t.getCause();
}
throw new IllegalStateException("Failed to subscribe " + url + ", cause: " + t.getMessage(), t);
} else {
logger.error("Failed to subscribe " + url + ", waiting for retry, cause: " + t.getMessage(), t);
}
}
// Record a failed registration request to a failed list, retry regularly
addFailedSubscribed(url, listener);
}
}
再看下真正干活的方法doSubscribe 这个方法同样也是在zookeeperRegistry里实现的：
doSubscribe(final URL url, final NotifyListener listener) {
try {
//当url的服务接口是*号时
if (Constants.ANY_VALUE.equals(url.getServiceInterface())) {
String root = toRootPath();
ConcurrentMap<NotifyListener, ChildListener> listeners = zkListeners.get(url);
if (listeners == null) {
zkListeners.putIfAbsent(url, new ConcurrentHashMap<NotifyListener, ChildListener>());
listeners = zkListeners.get(url);
}
ChildListener zkListener = listeners.get(listener);
if (zkListener == null) {
listeners.putIfAbsent(listener, new ChildListener() {
@Override
public void childChanged(String parentPath, List<String> currentChilds) {
for (String child : currentChilds) {
child = URL.decode(child);
if (!anyServices.contains(child)) {
anyServices.add(child);
subscribe(url.setPath(child).addParameters(Constants.INTERFACE_KEY, child,
Constants.CHECK_KEY, String.valueOf(false)), listener);
}
}
}
});
zkListener = listeners.get(listener);
}
zkClient.create(root, false);
List<String> services = zkClient.addChildListener(root, zkListener);
if (services != null && !services.isEmpty()) {
for (String service : services) {
service = URL.decode(service);
anyServices.add(service);
subscribe(url.setPath(service).addParameters(Constants.INTERFACE_KEY, service,
Constants.CHECK_KEY, String.valueOf(false)), listener);
}
}
} else {
List<URL> urls = new ArrayList<URL>();
for (String path : toCategoriesPath(url)) {
//path=/dubbo/xxx.xxx.xx/providers
ConcurrentMap<NotifyListener, ChildListener> listeners = zkListeners.get(url);
if (listeners == null) {
zkListeners.putIfAbsent(url, new ConcurrentHashMap<NotifyListener, ChildListener>());
listeners = zkListeners.get(url);
}
ChildListener zkListener = listeners.get(listener);
//如果listener不存在listeners中的时候添加到集合中
if (zkListener == null) {
listeners.putIfAbsent(listener, new ChildListener() {
@Override
public void childChanged(String parentPath, List<String> currentChilds) {
ZookeeperRegistry.this.notify(url, listener, toUrlsWithEmpty(url, parentPath, currentChilds));
}
});
zkListener = listeners.get(listener);
}
//因为zkClient是由zookeeperTransporter创建的，zookeeperTransporter又是这里zkClient会是CuratorZookeeperTransporter
//的实例，所以zkClient是CuratorZookeeperClient
//这里会去创建/dubbo/com.lin.service.UserService/providers路径，如果已经存在就返回
zkClient.create(path, false);
//这里添加对该路径的监听器
List<String> children = zkClient.addChildListener(path, zkListener);
if (children != null) {
urls.addAll(toUrlsWithEmpty(url, path, children));
}
}
//通知
notify(url, listener, urls);
}
} catch (Throwable e) {
throw new RpcException("Failed to subscribe " + url + " to zookeeper " + getUrl() + ", cause: " + e.getMessage(), e);
}
}
这里会先去创建一个ChildListener去添加到listeners中，然后zkClient会把这个listeners添加到自己的集合中，
首先zkClient这个类是由zookeeperTransporter去创建的，zookeeperTransporter这个类又是一个自适应扩展类，所以他会根据环境去创建一个CuratorZookeeperClient实例，所以最后会进入CuratorZookeeperClient的addChildListener这个方法：
@Override
public List<String> addChildListener(String path, final ChildListener listener) {
ConcurrentMap<ChildListener, TargetChildListener> listeners = childListeners.get(path);
if (listeners == null) {
childListeners.putIfAbsent(path, new ConcurrentHashMap<ChildListener, TargetChildListener>());
listeners = childListeners.get(path);
}
TargetChildListener targetListener = listeners.get(listener);
if (targetListener == null) {
listeners.putIfAbsent(listener, createTargetChildListener(path, listener));
targetListener = listeners.get(listener);
}
//添加一个watch
return addTargetChildListener(path, targetListener);
}
public List<String> addTargetChildListener(String path, CuratorWatcher listener) {
try {
return client.getChildren().usingWatcher(listener).forPath(path);
} catch (NoNodeException e) {
return null;
} catch (Exception e) {
throw new IllegalStateException(e.getMessage(), e);
}
}
所以可以看到这里会去zookeeper注册一个watcher，这个path如果有变动的话都会通知到lisener，这个path我们要记得这个path其实是我们的/dubbo/com.lin.service.UserService/providers这个路径，所以当有服务提供者添加或者下线的时候我们都会收到通知就可以去更新我们的service列表了，我们现在也知道服务者的更新是怎样的了，我们继续看下上面原来的订阅后我们要继续处理的东西 也就是:
Invoker invoker = cluster.join(directory);
这个cluster是我们上面传进来的，这个cluster也是一个自适应的扩展点，他会根据我们directory的url里面的参数cluster去调用对应的方法，因为我们的url里面没有配置cluster所以他会去调用默认的FailbackCluster,又因为我们的dubbo spi 中关于Cluster的配置中又有一个包装类mock：
mock=org.apache.dubbo.rpc.cluster.support.wrapper.MockClusterWrapper
所以他会去用MockClusterWrapper去包装一个FailbackCluster：
public class MockClusterWrapper implements Cluster {
private Cluster cluster;
public MockClusterWrapper(Cluster cluster) {
this.cluster = cluster;
}
@Override
public <T> Invoker<T> join(Directory<T> directory) throws RpcException {
//cluster是FailbackCluster
return new MockClusterInvoker<T>(directory,
this.cluster.join(directory));
}
}
public class FailoverCluster implements Cluster {
public final static String NAME = "failover";
@Override
public <T> Invoker<T> join(Directory<T> directory) throws RpcException {
return new FailoverClusterInvoker<T>(directory);
}
}
所以cluster.join返回的是一个MockClusterWrapper包装类，FailbackCluster.join又回返回一个FailoverClusterInvoker,所以我们Invoker的结构是这样的
new MockClusterInvoker(directory,new FailoverClusterInvoker(directory));
最后会根据这个invoker去创建一个代理类：
// create service proxy
return (T) proxyFactory.getProxy(invoker);
那我们的服务负载均衡到底是在哪里初始化的呢，我们继续来看下，因为我们是根据invoker去为我们的服务接口做代理的，那我们使用接口调用方法的时候其实都会调用到我们invoker的invoker方法，那这样我们就先来看下
MockClusterInvoker的invoker方法：
public Result invoke(Invocation invocation) throws RpcException {
Result result = null;
String value = directory.getUrl().getMethodParameter(invocation.getMethodName(), Constants.MOCK_KEY, Boolean.FALSE.toString()).trim();
if (value.length() == 0 || value.equalsIgnoreCase("false")) {
//no mock
result = this.invoker.invoke(invocation);
} else if (value.startsWith("force")) {
if (logger.isWarnEnabled()) {
logger.warn("force-mock: " + invocation.getMethodName() + " force-mock enabled , url : " + directory.getUrl());
}
//force:direct mock
result = doMockInvoke(invocation, null);
} else {
//fail-mock
try {
result = this.invoker.invoke(invocation);
} catch (RpcException e) {
if (e.isBiz()) {
throw e;
}
if (logger.isWarnEnabled()) {
logger.warn("fail-mock: " + invocation.getMethodName() + " fail-mock enabled , url : " + directory.getUrl(), e);
}
result = doMockInvoke(invocation, e);
}
}
return result;
}
所以我们后面还会调用到FailoverClusterInvoker的invoker方法，因为FailoverClusterInvoker没有重写invoke(Invocation invocation)方法，所以我们到他的父类来继续看：
public Result invoke(final Invocation invocation) throws RpcException {
checkWhetherDestroyed();
// binding attachments into invocation.
Map<String, String> contextAttachments = RpcContext.getContext().getAttachments();
if (contextAttachments != null && contextAttachments.size() != 0) {
((RpcInvocation) invocation).addAttachments(contextAttachments);
}
//获取调用链
List<Invoker<T>> invokers = list(invocation);
//初始化负载均衡器
LoadBalance loadbalance = initLoadBalance(invokers, invocation);
RpcUtils.attachInvocationIdIfAsync(getUrl(), invocation);
return doInvoke(invocation, invokers, loadbalance);
}
所以这里初始化了我们的负载均衡器：
protected LoadBalance initLoadBalance(List<Invoker<T>> invokers, Invocation invocation) {
if (CollectionUtils.isNotEmpty(invokers)) {
//当我们的方法没有loadbalance配置的时候就使用默认的random
return ExtensionLoader.getExtensionLoader(LoadBalance.class).getExtension(invokers.get(0).getUrl()
.getMethodParameter(RpcUtils.getMethodName(invocation), Constants.LOADBALANCE_KEY, Constants.DEFAULT_LOADBALANCE));
} else {
return ExtensionLoader.getExtensionLoader(LoadBalance.class).getExtension(Constants.DEFAULT_LOADBALANCE);
}
}
所以这里我们可以得到我们使用的负载均衡器了。
最新文章
- mysql优化（初学）
- Yii2.0中文开发向导——控制器(Controller)
- 系统调用方式文件编程,王明学learn
- mac在xampp下使用yii2.0开发环境配置
- 原！！tomcat7.0 配置数据库连接池 SQLServer2000
- HTTP - 持久连接
- Java文件备份类
- ubuntu下libjson-c库的使用问题备忘
- Nodejs之模板ejs
- （转）Uploadify 3.2 参数属性、事件、方法函数详解
- JAVA课程设计——团队博客
- [转]Windows Server 2016 服务器IIS配置
- 将你的 Virtual dom 渲染成 Canvas
- [05] EL表达式
- 懒得说IE6了，写个js插件不能写注释，原因如下
- Nginx + uWSGI 部署Django 项目,并实现负载均衡
- centOS 自动锁屏 解决办法
- 分区助手里如何从临近盘（如D盘）抽取一定的空间给已经快满了的盘（如E盘）（博主推荐）（图文详解）
- Unity中一键创建常用文件夹
- 关于2B的转义问题
热门文章
- Qt之QDomDocument操作xml文件-模拟ini文件存储
- 【反编译系列】一、反编译代码（dex2jar + jd-gui）和反编译资源（apktool）
- C#动态调用泛型类、泛型方法
- UiPath针对SAP的输入技巧
- Proj.Net 投影介绍
- DataPipeline成功入选微软加速器 企业创新力获业界专家认可
- 如何开发使用自定义文件的OEM应用程序
- MySQL学习（四）Join 等开发常用的操作 --- 2019年2月
- 2. CMake 系列 - 编译多文件项目
- 从壹开始前后端分离 [ Vue2.0+.NET Core2.1] 十四 ║ VUE 计划书 & 我的前后端开发简史