Support #634
review global transaction abort rules when particpated server fails
| Status: | Closed | Start date: | 02/22/2021 | |
|---|---|---|---|---|
| Priority: | Normal (Code 4) | Due date: | ||
| Assignee: | - | % Done: | 100% | |
| Category: | - | |||
| Target version: | - |
Description
tpcall() return code shall analysed in order to decide when global transaction shall be aborted.
Current logic of aborting global transaction for any error code seems to be too aggressive.
History
#1 Updated by Madars about 3 years ago
- Description updated (diff)
#2 Updated by Madars about 3 years ago
- Description updated (diff)
#3 Updated by Madars about 3 years ago
- Description updated (diff)
#4 Updated by Madars about 3 years ago
- Description updated (diff)
#5 Updated by Madars about 3 years ago
- Description updated (diff)
#8 Updated by Lauris almost 3 years ago
- Description updated (diff)
#9 Updated by Lauris almost 3 years ago
Release notes¶
Updated tpcall/tpgetrply/tpenqueue/tpdequeue functions with following rules:
- Errors: TPENOENT, TPEBADDESC, TPEINVAL, TPEITYPE, TPEBLOCK does not cause global transactions to abort.
- Additionally for tpenqueue() TPEDIAGNOSTIC + QMEINVAL, TPEDIAGNOSTIC + QMEBADQUEUE does not cause global transaction to abort.
- Additionally for tpdequeue() TPEDIAGNOSTIC + QMEINVAL, TPEDIAGNOSTIC + QMEBADQUEUE, TPEDIAGNOSTIC + QMENOMSG does not cause global transaction to abort.
#10 Updated by Lauris almost 3 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
#11 Updated by Lauris almost 3 years ago
- Status changed from Resolved to Closed