You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Andrew Grande (JIRA)" <ji...@apache.org> on 2015/11/23 21:08:11 UTC

[jira] [Commented] (NIFI-1208) ListenSyslog spin-loops CPU, spikes load to 150%

    [ https://issues.apache.org/jira/browse/NIFI-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15022877#comment-15022877 ] 

Andrew Grande commented on NIFI-1208:
-------------------------------------

Bryan, this patch drastically improved the situation, thanks!

> ListenSyslog spin-loops CPU, spikes load to 150%
> ------------------------------------------------
>
>                 Key: NIFI-1208
>                 URL: https://issues.apache.org/jira/browse/NIFI-1208
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 0.4.0
>         Environment: Raspbian Jessie (Debian-based), Raspberry PI 2, 1GHz x 4cores, 1GB RAM, Oracle JDK 8 for ARM 
>            Reporter: Andrew Grande
>            Assignee: Bryan Bende
>            Priority: Critical
>             Fix For: 0.4.0
>
>         Attachments: NIFI-1208.patch
>
>
> I've installed today's NiFI 0.4.0 snapshot on the latest Raspberry PI and configured a syslog listener. After forwarding my RPI syslogs to this NiFi listener, things seem to work ok (for now just sending to a remote cluster for collection).
> However, 'top' shows that the nifi process taxes CPU at around 150%, varying.  ListenSyslog stats show 1,500,000 tasks per a sliding 5min window.
> *Setup*: create a ListenSyslog on port 10001.
> As a root:
> # edit */etc/rsyslog.conf* file and add {noformat}*.*    @127.0.0.1:10001{noformat} at the end
> # service rsyslog restart
> You can send test messages to syslog like this:
> {noformat}logger "This is the test message!"{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)