Aliaksandr Valialkin e4cef1b678 app/vmstorage: prevent from serving conns from vminsert and vmselect after the server is closed ... Previously it was possible that the connection is served after the server is closed if the following steps are performed: 1) Server accepts new connection. 2) Server.MustClose() is called and successfully finished. 3) Server starts processing the connection accepted at step 1. There could be various crashes like in https://github.com/VictoriaMetrics/VictoriaMetrics/issues/534 since the storage may be already closed. Now the server closes the connection at step 3 without processing it.		2020-06-05 11:55:48 +03:00
..
vmagent	app/vmagent: print brief usage info for vmagent -help	2020-06-05 10:40:10 +03:00
vmalert	app/vmalert: print brief usage info for vmalert -help	2020-06-05 10:43:24 +03:00
vmauth	app/vmauth: print brief usage info for vmauth -help	2020-06-05 10:40:11 +03:00
vmbackup	all: print --help output to stdout instead of stderr	2020-05-16 12:03:06 +03:00
vminsert	app/vminsert/netstorage: free up unused memory in buffer after memory usage spikes	2020-06-01 14:33:35 +03:00
vmrestore	all: print --help output to stdout instead of stderr	2020-05-16 12:03:06 +03:00
vmselect	lib/fs: optimize MustGetFreeSpace performance by caching the results for up to 2 seconds	2020-06-04 13:14:04 +03:00
vmstorage	app/vmstorage: prevent from serving conns from vminsert and vmselect after the server is closed	2020-06-05 11:55:48 +03:00