Workflow Execution History exists in DB but Conductor API doesn't pickup after restart

Netflix / conductor

Conductor is a microservices orchestration engine.

Apache License 2.0

12.82k stars 2.34k forks source link

Workflow Execution History exists in DB but Conductor API doesn't pickup after restart #1331

Open maheshyaddanapudi opened 5 years ago

maheshyaddanapudi commented 5 years ago

Scenario-

A workflow was run hourly for a month. DB used is MySQL. All the workflow executions were returned by Conductor API until the Jar restart.

Conductor server is able to retain to show workflow def taskdef etc in API but execution history is not being returned.

I confirmed this by execution workflow once, then checked conductor API for getting the workflow executions and the details were there. Jar restarted, API returns will. I have verified the data exists in DB.

apanicker-nflx commented 5 years ago

This is definitely an odd scenario, something that we have not seen before (albeit we use Conductor backed by Dynomite and C*). I wonder if this is related to how the MySQL implementation is wired up. Can someone from the community using MySQL persistence backed Conductor help out in this case?