[
https://issues.apache.org/jira/browse/NIFI-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012276#comment-16012276
]
ASF GitHub Bot commented on NIFI-3900:
--------------------------------------
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/1804
NIFI-3900: Ensure that when we serialize a flow to send to Cluster Co…
…ordinator that we include the Scheduled State for processors as they are
intended to be, not as they are currently because during startup they may not
have been started yet.
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-3900
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1804.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 #1804
----
----
> Cluster - Inconsistent schedule state across the cluster
> --------------------------------------------------------
>
> Key: NIFI-3900
> URL: https://issues.apache.org/jira/browse/NIFI-3900
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Matt Gilman
> Priority: Critical
> Fix For: 1.3.0
>
>
> When nodes join a cluster there appears to be a timing issue that causes
> inconsistency with the scheduled state of components across the cluster. Due
> to delayed initialization, component's schedule state may be incorrect when a
> proposed flow is sent to a node.
> It appears that a node will get an inconsistent scheduled states when it's
> not able to connect to the cluster initially and receives a try-again-later
> response from the coordinator.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
