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

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

GitHub user ijokarumawak opened a pull request:

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

    NIFI-5581: Fix replicate request timeout

    - Revert 87cf474e542ef16601a86cc66c624fb8902c9fc2 to enable connection
    pooling
    - Changes the expected HTTP status code for the 1st request of a
    two-phase commit transaction from 150 (NiFi custom) to 202 Accepted
    - Corrected RevisionManager Javadoc about revision varidation protocol
    
    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?
    - [x] 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/ijokarumawak/nifi nifi-5581

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

    https://github.com/apache/nifi/pull/3044.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 #3044
    
----
commit dd53183c122ad77e637f5f4586c3c0fbf8d14327
Author: Koji Kawamura <ijokarumawak@...>
Date:   2018-10-04T04:48:26Z

    NIFI-5581: Fix replicate request timeout
    
    - Revert 87cf474e542ef16601a86cc66c624fb8902c9fc2 to enable connection
    pooling
    - Changes the expected HTTP status code for the 1st request of a
    two-phase commit transaction from 150 (NiFi custom) to 202 Accepted
    - Corrected RevisionManager Javadoc about revision varidation protocol

----


> Seeing timeouts when trying to replicate requests across the cluster
> --------------------------------------------------------------------
>
>                 Key: NIFI-5581
>                 URL: https://issues.apache.org/jira/browse/NIFI-5581
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.8.0
>            Reporter: Mark Payne
>            Assignee: Koji Kawamura
>            Priority: Blocker
>             Fix For: 1.8.0
>
>
> When trying to replicate requests across the cluster on the current master 
> branch, I see everything go smoothly for GET requests, but all mutable 
> requests timeout.
> This issue appears to have been introduced by the upgrade to a new version of 
> Jetty.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to