conductor
conductor copied to clipboard
UI cannot search any data
CASE background
Conductor version: v3.11.0-SNAPSHOT Deployment Type: docker-compose ( In memory )
Deployment Result
❯ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
76dbcce325a2 conductor:ui "docker-entrypoint.s…" 2 hours ago Up 2 hours 0.0.0.0:5000->5000/tcp docker_conductor-ui_1
10bf1d9bc705 conductor:server "/bin/sh /app/startu…" 2 hours ago Up 2 hours (healthy) 0.0.0.0:8080->8080/tcp docker_conductor-server_1
98bece5e4fbd elasticsearch:6.8.15 "/usr/local/bin/dock…" 2 hours ago Up 2 hours (healthy) 0.0.0.0:9200->9200/tcp, 0.0.0.0:9300->9300/tcp docker_elasticsearch_1
Operate step:
1. Task Definition
{
"name": "leaderRatify",
"description": "leader task",
"taskReferenceName": "node1",
"inputParameters": {
"staffName": "${workflow.input.staffName}",
"staffDepartment": "${workflow.input.staffDepartment}"
},
"type": "SIMPLE",
"ownerEmail": "[email protected]"
}
{
"name": "managerRatify",
"description": "manager task",
"taskReferenceName": "node2",
"inputParameters": {
"managerName": "${node1.output.leaderName}",
"managerDepartment": "${node1.output.leaderDepartment}"
},
"type": "SIMPLE",
"ownerEmail": "[email protected]"
}
2. Workflow Definition
{
"name": "leave_process",
"description": "a demo for workflow",
"tasks": [
{
"name": "leaderRatify",
"taskReferenceName": "node1",
"inputParameters": {
"staffName": "${workflow.input.staffName}",
"staffDepartment": "${workflow.input.staffDepartment}"
},
"type": "SIMPLE",
"ownerEmail": "[email protected]"
},
{
"name": "managerRatify",
"taskReferenceName": "node2",
"inputParameters": {
"managerName": "${node1.output.leaderName}",
"managerDepartment": "${node1.output.leaderDepartment}"
},
"type": "SIMPLE",
"ownerEmail": "[email protected]"
}
],
"outputParameters": {
"leaderName": "${node1.output.leaderName}",
"leaderDepartment": "${node1.output.leaderDepartment}",
"managerAgree": "${node2.output.managerAgree}",
"managerDisagree": "${node2.output.managerDisagree}"
},
"restartable": true,
"ownerEmail": "[email protected]",
"schemaVersion": "1",
"version": 2
}
3. Execute Workflow
curl -X 'POST' \
'http://localhost:8080/api/workflow/leave_process?priority=0' \
-H 'accept: text/plain' \
-H 'Content-Type: application/json' \
-d '{
"staffName": "hello",
"staffDepartment": "world"
}'
4. Search workflowId by cURL or Swagger UI
It works well now.
5. Search by Conductor UI
It dose not work.
Any suggestion? thx a lot.
fix: Conductor version is v3.11.0-SNAPSHOT
fix: Conductor version is v3.11.0-SNAPSHOT
and conductor client is 3.3.4
@Sunyelw do you have ES indexing enabled? ```conductor.indexing.enabled=true`
@jxu-nflx Yeah, and what does this dynomite do? Does it necessary for UI searching?
same as https://github.com/Netflix/conductor/issues/3106#issuecomment-1215879384
Hi, sorry for stealing your post, I'm having similar issue with taskLog searching, my es6 and workflow searching works. Is it normal normal to see "No logs available"? Do I need to log anything in the definition or tasks to see logs here?
Here is the default workflow, es indexing is enabled and conductor.db.type is set to memory (Do I need Dynomite to see logs?)
{
"name": "get_population_data",
"taskReferenceName": "get_population_data",
"inputParameters": {
"http_request": {
"uri": "https://datausa.io/api/data?drilldowns=Nation&measures=Population",
"method": "GET"
},
"asyncComplete": false
},
"type": "HTTP",
"startDelay": 0,
"optional": false,
"asyncComplete": false
}
UI errors logs, after restarting the UI instance error is fixed but still can't see any logs
[HPM] Error occurred while proxying request ip/api/tasks/ca2a1e34-3ea2-4c6d-bf90-5e18f040555c/log to http://conductor-server:8080/ [ECONNREFUSED] (https://nodejs.org/api/errors.html#errors_common_system_errors)
[HPM] Error occurred while proxying request ip/api/workflow/search?start=0&size=15&sort=startTime%3ADESC&freeText=%2A&query= to http://conductor-server:8080/ [ENOTFOUND] (https://nodejs.org/api/errors.html#errors_common_system_errors)
[HPM] Error occurred while proxying request ip/api/metadata/workflow to http://conductor-server:8080/ [ENOTFOUND] (https://nodejs.org/api/errors.html#errors_common_system_errors)
@jianbo When I tried HTTP
type task, it works well. Maybe you should check conductor-server started and healthy first. ( UI dependents on Server )
@jianbo The logs tab in the task view displays the task execution logs for each task. These logs need to be explicitly written by the worker in the TaskResult when updating a task or can be added async using the API
@apanicker-nflx I'm also running into no search results. Fresh docker install, but on an M1 Macbook so the only modification I made was to make ES use the AMD64 flags.
My ES container is running, though.
I take back my previous comment... setting conductor.indexing.enabled=true worked.