sharding-jdbc服务编排，观后感

最新推荐文章于 2022-12-24 22:23:18 发布

weixin_34195364

最新推荐文章于 2022-12-24 22:23:18 发布

阅读量228

点赞数

文章标签： java 大数据 python

原文链接：https://my.oschina.net/u/1432304/blog/1607893

版权

2019独角兽企业重金招聘Python工程师标准>>>

编排治理

官网文档 http://shardingjdbc.io/docs/02-guide/orchestration/

概述

和dubbo的服务治理很类似啊，不过不带UI，功能还在完善中

sharding-jdbc启动时，将配置信息分库分表，主从等信息持久化到zookeeper/etcd节点上
注册zookeeper/etcd 的监听zookeeper的watch。（不理解的先了解zk的特点）。
一旦节点改变，将新的节点信息下发到zk client，zk client重新建立配置信息

服务治理也就是这是原理，大同小异，配置信息改变，服务不需要重启，可动态改变适应新配置

具体实现

工厂模式一路跟进，没什么特别的
@1 开始注册znode监听器

DataSource dataSource = OrchestrationShardingDataSourceFactory.createDataSource(yamlFile);

public static DataSource createDataSource(......) throws SQLException {
        OrchestrationShardingDataSource result = new OrchestrationShardingDataSource(dataSourceMap, shardingRuleConfig, configMap, props, orchestrationConfig);
        result.init();
        return result;
    }

public void init() throws SQLException {
        orchestrationFacade.init(dataSourceMap, shardingRuleConfig, configMap, props, this);
    }

public void init(......) throws SQLException {
          ......
        //持久化配置到znode
        dataSourceService.persistDataSourcesNode();
        //@1 注册zk监听器
        listenerManager.initShardingListeners(shardingDataSource);
    }

public void initShardingListeners(final ShardingDataSource shardingDataSource) {
        ......
        dataSourceListenerManager.start(shardingDataSource);
    }

注册监听器

监听数据源路径，发现改变，重新创建数据源

@Override
    public void start(final ShardingDataSource shardingDataSource) {
        regCenter.watch(stateNode.getDataSourcesNodeFullPath(), new EventListener() {
            
            @Override
            public void onChange(final DataChangedEvent event) {
                if (DataChangedEvent.Type.UPDATED == event.getEventType() || DataChangedEvent.Type.DELETED == event.getEventType()) {
                    try {
                        shardingDataSource.renew(dataSourceService.getAvailableShardingRuleConfiguration().build(dataSourceService.getAvailableDataSources()), configService.loadShardingProperties());
                    } catch (final SQLException ex) {
                        throw new ShardingJdbcException(ex);
                    }
                }
            }
        });
    }

renew具体更新上下文信息等操作

public void renew(final ShardingRule newShardingRule, final Properties newProps) throws SQLException {
        ShardingProperties newShardingProperties = new ShardingProperties(null == newProps ? new Properties() : newProps);
        int originalExecutorSize = shardingProperties.getValue(ShardingPropertiesConstant.EXECUTOR_SIZE);
        int newExecutorSize = newShardingProperties.getValue(ShardingPropertiesConstant.EXECUTOR_SIZE);
        if (originalExecutorSize != newExecutorSize) {
            executorEngine.close();
            executorEngine = new ExecutorEngine(newExecutorSize);
        }
        boolean newShowSQL = newShardingProperties.getValue(ShardingPropertiesConstant.SQL_SHOW);
        shardingProperties = newShardingProperties;
        shardingContext = new ShardingContext(newShardingRule, getDatabaseType(), executorEngine, newShowSQL);
    }

watch里面就是zk client发现改变，触发事件。一些sharding-jdbc根据状态做不同处理。比较直白

@Override
    public void watch(final String key, final EventListener eventListener) {
        final String path = key + "/";
        if (!caches.containsKey(path)) {
            addCacheData(key);
        }
        TreeCache cache = caches.get(path);
        cache.getListenable().addListener(new TreeCacheListener() {
            
            @Override
            public void childEvent(final CuratorFramework client, final TreeCacheEvent event) throws Exception {
                ChildData data = event.getData();
                if (null == data || null == data.getPath()) {
                    return;
                }
                eventListener.onChange(new DataChangedEvent(getEventType(event), data.getPath(), null == data.getData() ? null : new String(data.getData(), "UTF-8")));
            }
            
            private DataChangedEvent.Type getEventType(final TreeCacheEvent event) {
                switch (event.getType()) {
                    case NODE_UPDATED:
                        return DataChangedEvent.Type.UPDATED;
                    case NODE_REMOVED:
                        return DataChangedEvent.Type.DELETED;
                    default:
                        return DataChangedEvent.Type.IGNORED;
                }
            }
        });
    }