You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/04/01 06:17:42 UTC
[jira] [Commented] (NIFI-1336) PostHTTP does not route to failure
in case of Connection failure
[ https://issues.apache.org/jira/browse/NIFI-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15952066#comment-15952066 ]
ASF GitHub Bot commented on NIFI-1336:
--------------------------------------
GitHub user trixpan opened a pull request:
https://github.com/apache/nifi/pull/1642
NIFI-1336 - Ensure that flowfiles are penalized upon exception due to…
… inability to delete hold
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:
- [X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
- [X] Has your PR been rebased against the latest commit within the target branch (typically master)?
- [X] Is your initial contribution a single, squashed commit?
### For code changes:
- [X] 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?
- [X] ~~~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)?~~~
- [X] ~~~If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?~~~
- [X] ~~~If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?~~~
- [X] ~~~If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?~~~
### For documentation related changes:
- [X] ~~~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/trixpan/nifi NIFI-1336
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1642.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 #1642
----
commit 3d8179db1290dffe773b82a65c5ea77bc353b06a
Author: Andre F de Miranda <tr...@users.noreply.github.com>
Date: 2017-04-01T06:15:13Z
NIFI-1336 - Ensure that flowfiles are penalized upon exception due to inability to delete hold
----
> PostHTTP does not route to failure in case of Connection failure
> ----------------------------------------------------------------
>
> Key: NIFI-1336
> URL: https://issues.apache.org/jira/browse/NIFI-1336
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Andre F de Miranda
>
> When unable to communicate with a remote NiFi instance, PostHTTP continually rolls back the session (without penalizing) instead of routing to failure. This results in filling the logs with messages like:
> 2015-12-29 14:09:02,023 WARN [Timer-Driven Process Thread-11] o.a.nifi.processors.standard.PostHTTP PostHTTP[id=015d5ace-3aa3-3e51-8aae-4776d3bd3897] Failed to delete Hold that destination placed on [StandardFlowFileRecord[uuid=220fbcac-d84e-41ed-9cc7-6e558ea207ee,claim=StandardContentClaim [resourceClaim=StandardResourceClaim[id=1451397424256-4, container=pub1, section=4], offset=52418, length=19672005],offset=0,name=GeoLite2-City.mmdb.gz,size=19672005]] due to org.apache.http.conn.HttpHostConnectException: Connect to processing-3:5000 [processing-3/172.172.172.172] failed: Connection refused: org.apache.http.conn.HttpHostConnectException: Connect to processing-3:5000 [processing-3.demo.onyara.com/172.172.172.172] failed: Connection refused
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)