[
https://issues.apache.org/jira/browse/NIFI-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16282219#comment-16282219
]
Mark Payne commented on NIFI-2776:
----------------------------------
I have uploaded a couple of files to make testing this easier, by providing the
conf/ directories for a 2 node cluster. From parent directory of existing nifi
installation:
{code}
cp -r nifi-* node1
cp -r nifi-* node2
cd node1/conf
tar xzvf ~/node1-conf.tar
cd ../../node2/conf
tar xzvf ~/node2-conf.tar
cd ../..
mkdir node1/state
mkdir node1/state/zookeeper
echo 1 > node1/state/zookeeper/myid
mkdir node2/state
mkdir node2/state/zookeeper
echo 2 > node2/state/zookeeper/myid
echo "(node1/bin/nifi.sh stop &) && (node2/bin/nifi.sh stop &)" >
stop-cluster.sh
echo "(node1/bin/nifi.sh start &) && (node2/bin/nifi.sh start &)" >
start-cluster.sh
echo "(node1/bin/nifi.sh restart &) && (node2/bin/nifi.sh restart &)" >
restart-cluster.sh
chmod +x *.sh
{code}
>From here, you should be able to just run ./start-cluster.sh or
>./stop-cluster.sh or ./restart-cluster.sh
> 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)
