In general, to troubleshoot a problem, the following logs are required.
${FATE_PROJECT_BASE}/fateflow/logs/$job_id/fate_flow_schedule.log
, this is the internal scheduling log of a certain task
${FATE_PROJECT_BASE}/fateflow/logs/$job_id/*
These are all the execution logs of a certain task
${FATE_PROJECT_BASE}/fateflow/logs/fate_flow/fate_flow_stat.log
, this is some logs that are not related to tasks
${FATE_PROJECT_BASE}/fateflow/logs/fate_flow/fate_flow_schedule.log
, this is the overall scheduling log of all tasks
${FATE_PROJECT_BASE}/fateflow/logs/fate_flow/fate_flow_detect.log
, which is the overall exception detection log for all tasks
${FATE_PROJECT_BASE}/logs/$job_id/fate_flow_schedule.log
, this is the internal scheduling log for a particular task
${FATE_PROJECT_BASE}/logs/$job_id/*
These are all the execution logs of a certain task
${FATE_PROJECT_BASE}/logs/fate_flow/fate_flow_stat.log
, this is some logs that are not related to the task
${FATE_PROJECT_BASE}/logs/fate_flow/fate_flow_schedule.log
, this is the overall scheduling log of all tasks
${FATE_PROJECT_BASE}/logs/fate_flow/fate_flow_detect.log
, this is the overall exception detection log of all tasks
no fate-servings deployed
flow did not fetch the fate-servings address
flow reads the address of the fate-servings in priority order:
read from zk
if zk is not open, it will read from the fate-servings configuration file, the configuration path is
1.5+: ${FATE_PROJECT_BASE}/conf/service_conf.yaml
1.5-: ${FATE_PROJECT_BASE}/arch/conf/server_conf.json
${FATE_PROJECT_BASE}/conf/service_conf.yaml
servings:
hosts:
- 127.0.0.1:8000
${FATE_PROJECT_BASE}/arch/conf/server_conf.json
{
"servers": {
"servings": ["127.0.0.1:8000"]
}
}