elastic.patch
|
Duplicate |
Team C
[ZBX-13613] Misleading history syncer usage statistics when backend elastic is unavailable Created: 2018 Mar 14 Updated: 2024 Apr 10 Resolved: 2018 Mar 25 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 3.4.7 |
| Fix Version/s: | 3.4.8rc1, 4.0.0alpha5, 4.0 (plan) |
| Type: | Problem report | Priority: | Trivial |
| Reporter: | Andris Zeila | Assignee: | Michael Veksler |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
elastic.patch
|
||||
| Issue Links: |
|
||||
| Team: | Team C |
||||
| Sprint: | Sprint 30 | ||||
| Story Points: | 0.25 | ||||
| Description |
|
When elastic backend is down the elastic writer must wait 10 seconds before retrying. This is done by calling zbx_sleep_loop(), which would put process in idle state during wait, while actually process is busy. It would be better to replace it with simple sleep(). It also results in additional dependencies in our tests. |