Workflows do not persist after broker restart

Camunda 8 Topics Discussion & Questions
1

Hi i must be missing something,
i work with docker (tried simple-monitor, then operate-simple-monitor) after broker restart i could not see my previously deployed workflows.
so i added the volume to /opt/data:/usr/local/zeebe/data - but still after restart the workflow wasn’t there.
what am i missing ?
thanks
Shlomi

2

You need to have a persistent volume for Simple Monitor. Simple Monitor is a decoupled representation of the broker state.

1 Like
3

Thanks

4

Hi
i have set environment variable for spring datasource url to keep h2 DB on file like this

  • spring.datasource.url=jdbc:h2:file:/opt/h2-data/db;DB_CLOSE_ON_EXIT=FALSE;AUTO_RECONNECT=TRUE

and a matching volume to the host.
i can see the file on my file system - still after broker restart the workflow page show nothing.
anything else that you can share - i could not find a simple example or documentation about the simple monitor persistent volume .
thanks
Shlomi

5

You can use a real DB for that… H2 is for development purposes only… Try PostgreSQL instead of H2 which is just another JDBC implementation.

6

What eventually helped is spring ddl update environment variable,

  • spring.jpa.hibernate.ddl-auto=update

for dev i don’t see a real reason not to use a file persistence

7

For Dev is more than fine