[
https://issues.apache.org/jira/browse/NIFI-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277207#comment-16277207
]
ASF GitHub Bot commented on NIFI-2776:
--------------------------------------
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/2315
NIFI-2776: When joining a cluster, if a processor is stopping but clu…
…ster indicates that processor should be running, cause processor to start
when its last thread finishes
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-2776
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/2315.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 #2315
----
commit 983aeca9194741c0c79bcf2cbd6dba6801e8b07a
Author: Mark Payne <[email protected]>
Date: 2017-12-04T18:29:24Z
NIFI-2776: When joining a cluster, if a processor is stopping but cluster
indicates that processor should be running, cause processor to start when its
last thread finishes
----
> When node connects back the to the cluster intermittently processor does not
> return to the same state as its in the cluster
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-2776
> URL: https://issues.apache.org/jira/browse/NIFI-2776
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.1.0
> Reporter: Arpit Gupta
> Assignee: Mark Payne
> Fix For: 1.5.0
>
>
> Here is the scenario
> 1. Create a flow and start a processor
> 2. Disconnect a node
> 3. On the disconnected node stop the above processor
> 4. Connect the above node to the cluster
> 5. Wait 30s.
> 6. Check if the processor started on the node that was connected in #4.
> Very intermittently we see that the processor does not get into running state.
> When we query the processor status on the node we get the following bulletin
> {code}
> "bulletins": [{
> "id": 0,
> "groupId": "275e45f8-0157-1000-ffff-fffff191c079",
> "sourceId": "275e4abc-0157-1000-0000-00005740dd0c",
> "timestamp": "06:24:35 UTC",
> "nodeAddress": "host:port",
> "canRead": true,
> "bulletin": {
> "id": 0,
> "nodeAddress": "host:port",
> "category": "Log Message",
> "groupId": "275e45f8-0157-1000-ffff-fffff191c079",
> "sourceId": "275e4abc-0157-1000-0000-00005740dd0c",
> "sourceName": "putES",
> "level": "WARNING",
> "message":
> "PutElasticsearch[id=275e4abc-0157-1000-0000-00005740dd0c] Can not start
> 'PutElasticsearch' since it's already in the process of being started or it
> is DISABLED - STOPPING",
> "timestamp": "06:24:35 UTC"
> }
> }],
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
