[Bro] Bro cluster requirements and manager logging backlog bug
Hovsep Levi
hovsep.sanjay.levi at gmail.com
Tue Dec 20 13:11:10 PST 2016
>
>
> [bro at mgr /opt/bro_data/logs/current]$ top -n -H -o time | grep bro
> 5672 bro 100 10 21076K 2796K RUN 19 6:35 62.79% gzip
> 5858 bro 95 5 510M 257M RUN 8 3:26 61.38% bro
> 5785 bro 95 5 2373M 2058M CPU11 11 3:20 59.08% bro
> 5743 bro 87 0 7897M 7743M RUN 14 3:19 52.78% bro{bro}
> 5743 bro 88 0 7897M 7743M CPU0 0 3:18 55.18% bro{bro}
> 5816 bro 40 0 5298M 1158M nanslp 23 1:59 23.29% bro{bro}
> 5743 bro 37 0 7897M 7743M uwait 4 1:32 23.58% bro{bro}
>
>
Here are the associated mappings for the PIDs:
[bro at f01 /opt/bro]$ bin/broctl top manager logger
Name Type Host Pid Proc VSize Rss Cpu Cmd
logger logger 169.231.234.36 5743 parent 9G 9G 194% bro
logger logger 169.231.234.36 5785 child 3G 2G 60% bro
manager manager 169.231.234.36 5858 child 510M 257M 63% bro
manager manager 169.231.234.36 5816 parent 5G 1G 18% bro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/bro/attachments/20161220/a99dbc7e/attachment-0001.html
More information about the Bro
mailing list