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

ASF GitHub Bot commented on STORM-569:
--------------------------------------

GitHub user kishorvpatil opened a pull request:

    https://github.com/apache/storm/pull/324

    [STORM-569] Add Configuration to enable/disable Bolt's outgoing 
overflow-buffer

    - Added topology level flag 
`topology.bolts.outgoing.overflow.buffer.enable` - which defaults to `true`
    - Create bolt's overflow buffer only if 
`topology.bolts.outgoing.overflow.buffer.enable` is set
    - tested manually using topology with cyclic flow for below scenarios for 
both 
       - When set to`false` executors hit live-lock and get restarted as 
`DisruptorQueue` get full
       - When set to `true` executors use overflow buffer to handle spikes and 
instead of live-lock, they consume more memory.

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

    $ git pull https://github.com/kishorvpatil/incubator-storm config-obuffer

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

    https://github.com/apache/storm/pull/324.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 #324
    
----
commit ccef637701f8dfa88ad2aaa6933549267ece1b0a
Author: Kishor Patil <kpa...@yahoo-inc.com>
Date:   2014-11-21T13:34:52Z

    Add Configuration to enable/disable Bolt's outgoing overflow-buffer

----


> Add Configuration to enable/disable Bolt's outgoing overflow-buffer
> -------------------------------------------------------------------
>
>                 Key: STORM-569
>                 URL: https://issues.apache.org/jira/browse/STORM-569
>             Project: Apache Storm
>          Issue Type: Improvement
>    Affects Versions: 0.10.0
>            Reporter: Kishor Patil
>            Assignee: Kishor Patil
>
> Add Configuration to enable/disable Bolt's outgoing overflow-buffer. This 
> needs to be disabled by default. It would be useful only incase of topologies 
> that have cyclic tuple flow causing livelocks. Refer to STORM-292



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

Reply via email to