[jira] [Commented] (NIFI-2500) Allow request buffer to be configurable on HandleHTTPRequest processor

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2500:
---

+1.  Looks good.  Tested on a live flow as best i could.  was able to reproduce 
queue exhaustion and then update queue size and could not.  So while not 
definitive is a good sign.

> Allow request buffer to be configurable on HandleHTTPRequest processor
> --
>
> Key: NIFI-2500
> URL: https://issues.apache.org/jira/browse/NIFI-2500
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.6.1
>Reporter: Matthew Clarke
>Assignee: Oleg Zhurakousky
>Priority: Critical
> Fix For: 1.1.0
>
>
> The request buffer for the HandleHTTPRequest buffer is hard coded to 50.  For 
> environments where bursts of requests can come in that exceed that threshold, 
> the processor will trigger Service Unavailable responses. Users should be 
> able to increase that buffer to meet their dataflow needs similar to how the 
> ConsumeMQTT processor works.



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

[jira] [Commented] (NIFI-2500) Allow request buffer to be configurable on HandleHTTPRequest processor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2500:
--

Github user asfgit closed the pull request at:

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


> Allow request buffer to be configurable on HandleHTTPRequest processor
> --
>
> Key: NIFI-2500
> URL: https://issues.apache.org/jira/browse/NIFI-2500
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.6.1
>Reporter: Matthew Clarke
>Assignee: Oleg Zhurakousky
>Priority: Critical
> Fix For: 1.1.0
>
>
> The request buffer for the HandleHTTPRequest buffer is hard coded to 50.  For 
> environments where bursts of requests can come in that exceed that threshold, 
> the processor will trigger Service Unavailable responses. Users should be 
> able to increase that buffer to meet their dataflow needs similar to how the 
> ConsumeMQTT processor works.



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

[jira] [Commented] (NIFI-2500) Allow request buffer to be configurable on HandleHTTPRequest processor

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-2500:
---

Commit 5afbc433642a51a40c22a2048cfa7d0e9cf0a86a in nifi's branch 
refs/heads/master from [~ozhurakousky]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=5afbc43 ]

NIFI-2500 This closes #1131. made container queue configurable


> Allow request buffer to be configurable on HandleHTTPRequest processor
> --
>
> Key: NIFI-2500
> URL: https://issues.apache.org/jira/browse/NIFI-2500
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.6.1
>Reporter: Matthew Clarke
>Assignee: Oleg Zhurakousky
>Priority: Critical
> Fix For: 1.1.0
>
>
> The request buffer for the HandleHTTPRequest buffer is hard coded to 50.  For 
> environments where bursts of requests can come in that exceed that threshold, 
> the processor will trigger Service Unavailable responses. Users should be 
> able to increase that buffer to meet their dataflow needs similar to how the 
> ConsumeMQTT processor works.



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

[jira] [Commented] (NIFI-2500) Allow request buffer to be configurable on HandleHTTPRequest processor

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2500:
---

reviewed code.  running some tests now

> Allow request buffer to be configurable on HandleHTTPRequest processor
> --
>
> Key: NIFI-2500
> URL: https://issues.apache.org/jira/browse/NIFI-2500
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.6.1
>Reporter: Matthew Clarke
>Assignee: Oleg Zhurakousky
>Priority: Critical
> Fix For: 1.1.0
>
>
> The request buffer for the HandleHTTPRequest buffer is hard coded to 50.  For 
> environments where bursts of requests can come in that exceed that threshold, 
> the processor will trigger Service Unavailable responses. Users should be 
> able to increase that buffer to meet their dataflow needs similar to how the 
> ConsumeMQTT processor works.



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

[jira] [Commented] (NIFI-2500) Allow request buffer to be configurable on HandleHTTPRequest processor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2500:
--

GitHub user olegz opened a pull request:

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

NIFI-2500 made container queue configurable

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [ ] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [ ] Is your initial contribution a single, squashed commit?

### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?

### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.



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

$ git pull https://github.com/olegz/nifi NIFI-2500

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

https://github.com/apache/nifi/pull/1131.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 #1131


commit f6979bc63fce5643f4001e726d8384305fdf24d4
Author: Oleg Zhurakousky 
Date:   2016-10-13T16:08:29Z

NIFI-2500 made container queue configurable




> Allow request buffer to be configurable on HandleHTTPRequest processor
> --
>
> Key: NIFI-2500
> URL: https://issues.apache.org/jira/browse/NIFI-2500
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.6.1
>Reporter: Matthew Clarke
>Assignee: Oleg Zhurakousky
>Priority: Critical
> Fix For: 1.1.0
>
>
> The request buffer for the HandleHTTPRequest buffer is hard coded to 50.  For 
> environments where bursts of requests can come in that exceed that threshold, 
> the processor will trigger Service Unavailable responses. Users should be 
> able to increase that buffer to meet their dataflow needs similar to how the 
> ConsumeMQTT processor works.



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