Zabbix Server service stop taking days to stop

[rjurek]

We had a large volume of alerts/data come in and dropped the history cache to 0% free, the system was dead, so tried to shutdown the zabbix server service and it took 2 days before it shutdown. this is what was in the log during the shutdown.

2334:20200805:135845.511 syncing history data... 7.366697%
2334:20200805:135903.321 syncing history data... 7.380222%
2334:20200805:135920.799 syncing history data... 7.386978%
2334:20200805:135945.138 syncing history data... 7.407265%

I need to know of a way to shutdown faster, I can not be down for two days without monitoring.

[Hamardaban]

You may need to enter one or more proxy servers in the scheme. They will collect and aggregate data and transmit it to the server. In theory, the server will be easier and shutdown will occur faster. And of course look in the direction of fast storage under your database, and database optimization.

[rjurek]

I have 23 proxies and DB server is running on ssd disks. really looking for a way to stop zabbix now, i do not care if the history data is sync'd. I did a systemctl stop zabbix-server and the zabbix-server.log still gets updated with the syncing history data. right now I am at 40%, I need to get zabbix back up

[Hamardaban]

systemctl kill -s SIGKILL zabbix-server ?