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

ASF GitHub Bot commented on NIFI-1599:
--------------------------------------

GitHub user bbende opened a pull request:

    https://github.com/apache/nifi/pull/262

    NIFI-1599 Changing DatagramChannelDispatcher, socket handlers, and RE…

    …LP handler to use offer() when queueing instead of put(), and log an error 
if the offer failed

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bbende/nifi NIFI-1599

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/262.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #262
    
----
commit 537c19c1b351ecaccc1a583f1a6be764ec0dd945
Author: Bryan Bende <[email protected]>
Date:   2016-03-07T22:21:11Z

    NIFI-1599 Changing DatagramChannelDispatcher, socket handlers, and RELP 
handler to use offer() when queueing instead of put(), and log an error if the 
offer failed

----


> ListenSyslog/ListenRELP should report when internal queue is full
> -----------------------------------------------------------------
>
>                 Key: NIFI-1599
>                 URL: https://issues.apache.org/jira/browse/NIFI-1599
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Bryan Bende
>            Assignee: Bryan Bende
>            Priority: Minor
>             Fix For: 0.6.0
>
>
> In a recent ticket we exposed a property for choosing the maximum capacity of 
> the internal queue used to transfer messages from the threading reading from 
> the channel to the processor. 
> Currently there is really no way to know if the queue is filling up and the 
> size should be increased. We do an indefinite blocking put() when adding to 
> the queue, but it would be nice if we tried with some amount of timeout and 
> then logged an error so the user was aware that data was being dropped. 



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

Reply via email to