Feature #740
tmsrv and tmqueue database backend for storage
| Status: | New | Start date: | 12/08/2021 | |
|---|---|---|---|---|
| Priority: | Normal (Code 4) | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - |
Description
currently tmsrv and tmqueue uses file system for storing:
- Transaction status information.
- TMQ messages.
It would be nice to have database backend, where the transaction information and messages could be stored in database. soci sql engine could be used to create database agnostic solution.
For tmsrv non critical information (such as resource active enlisting/joins) could be written to DB by separate thread, so that database commit result is not waited.
The only commit wait shall be present at commit decision logging. Also at that moment the worker thread shall sync with active status commit results.