currently, there are no known issues related to MariaDB 10.1.x. We offer only support for MariaDB 10.0 because we run our tests against this version. But that doesn’t mean that Camunda doesn’t work with other versions.
If you see any issue then please report them
I also found an issue to support MariaDB 10.2 - CAM-8486.
I just wanted to post an update to this thread.
We have successfully run with these MariaDB versions on Camunda:
10.1.23
10.1.25
10.1.32
10.2.13
However, when we recently upgraded to Camunda 7.10.0-alpha4, we found that 10.2.13 doesn’t work.
The symptom we see is that jobs are not being picked up by the job executor.
When we try 7.10.0-alpha4 with MariaDB 10.1.x, then everything is fine.
So I think 10.2 still might have some compatibility issues. When enabling TRACE logging on the Camunda code, we didn’t see any errors, but it just wasn’t picking up the jobs. We didn’t do a lot of trouble-shooting beyond this, but I just wanted to point this out.
I’m curious about why 10.1 was skipped over. Was there a particular flaw/problem with that one?
I guess we skipped it because it wasn’t the latest MariaDB version at the time we updated our supported environments. Every supported database version requires extensive testing on our side.
We basically use 1.1.8 because we didn’t really manage to stay on latest version. It is not the preferred or recommended version and we should move to a newer version in our CI anyway.
The only constraint for versioning is that which https://app.camunda.com/jira/browse/CAM-8891 documents when JDBC batch processing is used. Other than, I’d go for the latest version of the driver. Using 1.1.8 would give you some extra safety in that it is the exact version we currently test with.