chproxy
chproxy copied to clipboard
[BUG] Transactions TTL updated upon finalisation
Describe the bug In the issue #224 it's explained that failed transactions are kept for time t after concurrent queries are completed. It can be problematic if the error is recoverable, but not detected as one, because query will be failed for some time.
To Reproduce Start a query
Expected behavior Query should be replayed on Clickhouse instead of served from concurrent transaction.
Screenshots N/A
Environment information N/A
Additional context We could update TTL of transaction to a fairly low value allowing concurrent transactions to complete and allow consecutive queries to run, e.g. ttl=1second.