|
Causes |
|||
| caused by |
|
again. still failed transactions roll... | Closed |
Team C
[ZBX-13196] Commit failure is silently ignored during history synchronization Created: 2017 Dec 14 Updated: 2024 Apr 10 Resolved: 2018 Jan 08 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Proxy (P), Server (S) |
| Affects Version/s: | 4.0.0alpha1, 4.0 (plan) |
| Fix Version/s: | 4.0.0alpha2, 4.0 (plan) |
| Type: | Problem report | Priority: | Trivial |
| Reporter: | Vladislavs Sokurenko | Assignee: | Vjaceslavs Bogdanovs |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Team: | Team C | ||||||||
| Team: | Team C |
||||||||
| Sprint: | Sprint 23, Sprint 24, Sprint 25 | ||||||||
| Story Points: | 0.5 | ||||||||
| Description |
|
DBcommit no longer set transaction error, so if it fails then it will not be detected and cache will be updated during history synchronization while database will not have the changes. This can lead to a problems such as trigger being stuck in one state, and missing notifications, though it's possibly a corner case that all other queries succeed but only commit fails. |