Hello,
I have made a zeebe stack in a docker swarm.
The only persistent data are Zeebe data and Elasticsearch data.
I have made a few test with a bpmn file with id transcode_video
.
Then I have:
- Stopped all stack containers.
- Removed all Elasticsearch data.
- Renamed the workflow and workflow id to
transcode_video_example
. - Restarted the stack.
- Deployed the new bpmn file to Zeebe.
- Publish the watchfolder_message to trigger a workflow instance.
But then it triggers and execute two workflows simultaneously, the removed one and the new one…
I have made a python script to inspect Zeebe state from Elasticsearch indices:
Here are the Zeebe indices:
------------------------------------------------------------------------------------------------------------------------
health status index
------------------------------------------------------------------------------------------------------------------------
green open zeebe-record_deployment_0.23.1_2020-07-24
green open zeebe-record_job_0.23.1_2020-07-24
green open zeebe-record_variable_0.23.1_2020-07-24
green open zeebe-record_workflow-instance_0.23.1_2020-07-24
Here are the deployed workflows:
------------------------------------------------------------------------------------------------------------------------
workflowKey bpmnProcessId version resourceName
------------------------------------------------------------------------------------------------------------------------
2251799813696759 transcode_video_example 2 transcode_video_example.bpmn
Here are the instances triggered by the message event:
bpmnProcessId version workflowKey flowScopeKey bpmnElementType parentWIK parentEIK WIK elementId
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-1 2251799813696703 -1 START_EVENT -1 -1 2251799813742658 watchfolder
-1 2251799813696759 -1 START_EVENT -1 -1 2251799813742661 watchfolder
transcode_video 2 2251799813696703 -1 PROCESS -1 -1 2251799813742658 transcode_video
transcode_video_example 2 2251799813696759 -1 PROCESS -1 -1 2251799813742661 transcode_video_example
transcode_video 2 2251799813696703 -1 PROCESS -1 -1 2251799813742658 transcode_video
transcode_video_example 2 2251799813696759 -1 PROCESS -1 -1 2251799813742661 transcode_video_example
transcode_video 2 2251799813696703 2251799813742658 START_EVENT -1 -1 2251799813742658 watchfolder
transcode_video_example 2 2251799813696759 2251799813742661 START_EVENT -1 -1 2251799813742661 watchfolder
transcode_video 2 2251799813696703 2251799813742658 START_EVENT -1 -1 2251799813742658 watchfolder
transcode_video_example 2 2251799813696759 2251799813742661 START_EVENT -1 -1 2251799813742661 watchfolder
As you see, the old workflow transcode_video
is executed, but does not exist in Elasticsearch nor appear in Operate.
I don’t know what Zeebe keeps in its data, but may be there is a remain of the old workflow somewhere…
How-to really get rid of a removed workflow ?