[ZBX-23730] Server takes a long time to stop when connector queue has a lot of values Created: 2023 Nov 21  Updated: 2024 Apr 10  Resolved: 2023 Dec 19

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: None
Fix Version/s: 7.0.0alpha9, 7.0 (plan)

Type: Problem report Priority: Trivial
Reporter: Dmitrijs Goloscapovs Assignee: Dmitrijs Goloscapovs
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Causes
caused by ZBXNEXT-8735 Improve retries in streaming connectors Closed
Team: Team A
Sprint: Sprint 107 (Dec 2023)
Story Points: 0.125

 Description   

Steps to reproduce:

  1. Create a connector with URL that doesn't respond with a JSON
    2. Try to stop the server:
      3365:20231109:172819.008 [2] thread stopped [preprocessing worker #2]
      3376:20231109:172819.009 syncing history data in progress...
      3376:20231109:172819.009 syncing history data done
      3421:20231109:172839.010 cannot retrieve error from "http://localhost/zabbix/in": cannot parse as a valid JSON object
    ...
      3421:20231109:172839.010 cannot send data to "http://localhost/zabbix/in": Response code "404" did not match any of the required status codes "200"
    ...
      3421:20231109:172919.017 cannot retrieve error from "http://localhost/zabbix/in": cannot parse as a valid JSON object: 
    ...
      3421:20231109:172919.017 cannot send data to "http://localhost/zabbix/in": Response code "404" did not match any of the required status codes "200"
      3421:20231109:172959.023 cannot retrieve error from "http://localhost/zabbix/in": cannot parse as a valid JSON object: 
    

    Most proc titles say "[terminated]" (pollers, etc) but alerters and connectors do not.



 Comments   
Comment by Dmitrijs Goloscapovs [ 2023 Dec 15 ]

Available in versions:

Generated at Wed Apr 23 17:37:27 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.