is there any possibility to configure the GraphiteWriter how many items should be cached in memory, in case of non-availabilty of the Carbon Cache?
In my environment (~100.000 services) the Graphite-Server crashed, so carbon cache was not available. Icinga filled up the machines memory/swap with GraphiteWriter-items. Finally, after 2 1/2 hours, the machines memory was full and the Icinga-cluster was not operational any more.
In such case, I would prefer to loose some metrics instead of loosing the Icinga-Cluster.