dolphinscheduler源码解析-NettyRemotingServer

dolphinscheduler源码解析-NettyRemotingServer

NettyRemotingServer属性

private final Logger logger = LoggerFactory.getLogger(NettyRemotingServer.class);

/**
 * server bootstrap

private final ServerBootstrap serverBootstrap = new ServerBootstrap();

/**
 * encoder
 */
private final NettyEncoder encoder = new NettyEncoder();

/**
 * default executor
 */
private final ExecutorService defaultExecutor = Executors.newFixedThreadPool(Constants.CPUS);

/**
 * boss group
 */
private final EventLoopGroup bossGroup;

/**
 * worker group
 */
private final EventLoopGroup workGroup;

/**
 * server config
 */
private final NettyServerConfig serverConfig;

/**
 * server handler
 */
private final NettyServerHandler serverHandler = new NettyServerHandler(this);

/**
 * started flag
 */
private final AtomicBoolean isStarted = new AtomicBoolean(false);

/**
 * Netty server bind fail message
 */
private static final String NETTY_BIND_FAILURE_MSG = "NettyRemotingServer bind %s fail";

都是一些netty的启动配置，不过NettyServerHandler它把this注册了进来。

MasterServer中对该类的使用为

this.nettyRemotingServer = new NettyRemotingServer(serverConfig);
this.nettyRemotingServer.registerProcessor(CommandType.TASK_EXECUTE_RESPONSE, new TaskResponseProcessor());
this.nettyRemotingServer.registerProcessor(CommandType.TASK_EXECUTE_ACK, new TaskAckProcessor());
this.nettyRemotingServer.registerProcessor(CommandType.TASK_KILL_RESPONSE, new TaskKillResponseProcessor());
this.nettyRemotingServer.start();

可以看出它的注册处理器方法，采用了命令模式，不同的命令对应不同的处理流程。追踪它的registerProcessor方法。

public void registerProcessor(final CommandType commandType, final NettyRequestProcessor processor) {
	this.registerProcessor(commandType, processor, null);
}

再追踪

public void registerProcessor(final CommandType commandType, final NettyRequestProcessor processor, final ExecutorService executor) {
    this.serverHandler.registerProcessor(commandType, processor, executor);
}

这里就可以看出最后实际调用了NettyServerHandler的registerProcessor方法【点击打开】。

其他的方法都是一些基本的netty配置等，就不过多介绍。