[ https://issues.apache.org/jira/browse/NIFI-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025263#comment-16025263 ]
ASF GitHub Bot commented on NIFI-3981: -------------------------------------- GitHub user markap14 opened a pull request: https://github.com/apache/nifi/pull/1861 NIFI-3981: When serializing flow to cluster, use the Scheduled State … …of ports as they are configured to be, not the current state, since the current state may change as soon as the FlowController has finished initializing 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-XXXX where XXXX 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/markap14/nifi NIFI-3981 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/1861.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 #1861 ---- commit 575e09da4570d06c5401c1a5974a890537f2cead Author: Mark Payne <marka...@hotmail.com> Date: 2017-05-25T19:31:43Z NIFI-3981: When serializing flow to cluster, use the Scheduled State of ports as they are configured to be, not the current state, since the current state may change as soon as the FlowController has finished initializing ---- > When clustered, Ports sometimes are not running when NiFi restarts > ------------------------------------------------------------------ > > Key: NIFI-3981 > URL: https://issues.apache.org/jira/browse/NIFI-3981 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework > Affects Versions: 1.2.0 > Reporter: Mark Payne > Assignee: Mark Payne > > I have a cluster of 2 nodes. On the canvas I have an Input Port that is > running. If I restart both nodes at the same time, they come up and have the > Input Port running. If I shut down both nodes and start only 1 node, then > wait for 1 minute until it loads its local flow rather than the cluster flow, > then it starts up running. When I then join Node 2 into the cluster, Node 1 > stops the port, thought Node 2 starts running the port. This leaves the port > in an inconsistent state where it is running on some nodes but not others. -- This message was sent by Atlassian JIRA (v6.3.15#6346)