Am 26.02.2015 um 17:07 schrieb Klaus Darilion:
Hi!
We are using Icinga with NSCA 2.9.1 in single-process mode with delivery
to the checkresults directory.
It seems the single-process networking code is not optimal: reading from
one TCP connection blocks all other TCP connections until NSCA finished
reading all the data from the current TCP connection. Thus, reading data
on a slow TCP connection causes delay for all other incoming passive checks.
I am a bit afraid switching to multi-process mode due to the high fork
rate (sometimes we have up to 100 passive check results per second).
So, what do other people use for optimal NSCA performance?
single-process or multi-process? Is it worth considering some NSCA
replacement?
I've tried to patch the NSCA code when I was working in Vienna, but it
wasn't much fun. The idea is good, the implementation is pure mess.
I've seen that nsca-ng works well, but requires different security and
therefore sending clients.
Apart from that, another user approached us with an nsca interface as
neb broker module for 1.x, called "icinga-iris". I've incorporated
several patches sent into the 1.13 tree, which is yet to be released
(try the snapshot packages from packages.icinga.org)
I wouldn't bet much on NSCA these days, that's a dead end.
Kind regards,
Michael
--
Michael Friedrich, DI (FH)
Application Developer
NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg
Tel: +49 911 92885-0 | Fax: +49 911 92885-77
GF: Julian Hein, Bernd Erk | AG Nuernberg HRB18461
http://www.netways.de | [email protected]
** CeBIT 2015 - 16.-20. März 2015 - http://www.netways.de/cebit **
** OSDC 2015 - April - osdc.de **
** Puppet Camp Berlin 2015 - April - netways.de/puppetcamp **
** OSBConf 2015 - September - osbconf.org **
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users
