Azkaban的Web Server源码探究系列23: 一次性执行execute的正式提交
下面正式提交
String message = executorManager.submitExecutableFlow(exflow, user.getUserId());
那么，到底executorManager是如何处理的呢？
=================================================================================
stop in azkaban.executor.ExecutorManager.submitExecutableFlow
=================================================================================
其实主要就是在数据库中插入一行记录，具体看
runner.update(connection, INSERT_EXECUTABLE_FLOW, flow.getProjectId(), flow.getFlowId(), flow.getVersion(),
Status.PREPARING.getNumVal(), submitTime, flow.getSubmitUser(), submitTime);
connection.commit();
这个很好理解吧
===
但是后面5个字段为空对吗？别急，然后紧接着就来处理这5个字段。
final String UPDATE_EXECUTABLE_FLOW_DATA = "UPDATE execution_flows "
+ "SET status=?,update_time=?,start_time=?,end_time=?,enc_type=?,flow_data=? " + "WHERE exec_id=?";
QueryRunner runner = new QueryRunner();
String json = JSONUtils.toJSON(flow.toObject());
这个是数据，比如我的数据可以是如下所示：
json = "{
"lastModfiedTime":1460217889979,
"executionOptions":{
"failureAction":"FINISH_CURRENTLY_RUNNING",
"memoryCheck":true,
"queueLevel":0,
"pipelineExecId":null,
"concurrentOption":"skip",
"notifyOnFirstFailure":false,
"notifyOnLastFailure":false,
"pipelineLevel":null,
"successEmailsOverride":false,
"failureEmails":[],
"disabled":[],
"flowParameters":{},
"successEmails":[],
"mailCreator":"default",
"failureEmailsOverride":false
},
"updateTime":-1,
"type":null,
"attempt":0,
"version":15,
"executionPath":null,
"executionId":4,
"nodes":[
{"jobSource":"Hello.job","startTime":-1,"updateTime":-1,"id":"Hello","endTime":-1,"type":"command","attempt":0,"status":"READY","outNodes":["World"]},
{"jobSource":"World.job","startTime":-1,"updateTime":-1,"id":"World","endTime":-1,"type":"command","attempt":0,"inNodes":["Hello"],"status":"READY"}
],
"submitTime":1460267483832,
"submitUser":"azkaban",
"startTime":-1,
"lastModifiedUser":"azkaban",
"id":null,
"endTime":-1,
"projectName":"myfirstProject",
"flowId":"World",
"projectId":9,
"proxyUsers":[],
"properties":[],
"status":"PREPARING"
}"
====================
这些数据需要被GZIP压缩下。
try {
runner.update(connection, UPDATE_EXECUTABLE_FLOW_DATA, flow.getStatus().getNumVal(), flow.getUpdateTime(),
flow.getStartTime(), flow.getEndTime(), encType.getNumVal(), data, flow.getExecutionId());
connection.commit();
} catch (SQLException e) {
throw new ExecutorManagerException("Error updating flow.", e);
}
结果就是：
搞定！
================================================================================
在多核模式下，
if (isMultiExecutorMode()) {
// Take MultiExecutor route
executorLoader.addActiveExecutableReference(reference);
queuedFlows.enqueue(exflow, reference);
} else {
看来又需要操作数据库了
@Override
public void addActiveExecutableReference(ExecutionReference reference) throws ExecutorManagerException {
// 看到这里了
final String INSERT = "INSERT INTO active_executing_flows " + "(exec_id, update_time) values (?,?)";
QueryRunner runner = createQueryRunner();
try {
runner.update(INSERT, reference.getExecId(), reference.getUpdateTime());
} catch (SQLException e) {
throw new ExecutorManagerException("Error updating active flow reference " + reference.getExecId(), e);
}
}
在本地还要缓存起来
queuedFlows.enqueue(exflow, reference);
===
message += "Execution submitted successfully with exec id " + exflow.getExecutionId();
}
return message;
最后就是返回了，也就是你在界面上看到的！
===
总结起来就是涉及到了2个表：
1）execution_flows
2) active_executing_flows