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

ASF subversion and git services commented on NIFI-2776:
-------------------------------------------------------

Commit 8e6649ba157f1389be4434f4f8e7fc81ae907ffc in nifi's branch 
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=8e6649b ]

NIFI-2776: This closes #2315. 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

Signed-off-by: joewitt <[email protected]>


> 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
>
>         Attachments: node1-conf.tar, node2-conf.tar
>
>
> 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)

Reply via email to