Aliaksandr Valialkin a586b8b6d4 app/vminsert/netstorage: do not re-route every time series to more than two vmstorage nodes when certain vmstorage nodes are temporarily slower than the rest of them ... Previously vminsert may spread data for a single time series across all the available vmstorage nodes when vmstorage nodes couldn't handle the given ingestion rate. This could lead to increased usage of CPU and memory on every vmstorage node, since every vmstorage node had to register all the time series seen in the cluster. Now a time series may spread to maximum two vmstorage nodes under heavy load. Every time series is routed to a single vmstorage node under normal load.		2020-06-25 16:42:37 +03:00
..
insert_ctx_pool.go	app/vmagent: initial implementation for vmagent	2020-02-23 17:31:54 +02:00
insert_ctx.go	app/vminsert/netstorage: make sure that the the data is always replicated among -replicationFactor vmstorage nodes	2020-05-28 19:59:07 +03:00
netstorage.go	app/vminsert/netstorage: do not re-route every time series to more than two vmstorage nodes when certain vmstorage nodes are temporarily slower than the rest of them	2020-06-25 16:42:37 +03:00