question 'Execution node' is invalid because processors with incoming connections cannot be scheduled for primary node only in Support Questions

'Execution node' is invalid because processors with incoming connections cannot be scheduled for primary node only

manishg — Fri, 08 Sep 2023 12:02:26 GMT

What does this message mean on an invalid processor:

I see it for processor FetchXMLFile.

On scheduling tab, execution dropdown has 'Primary Node' selected. On changing it to 'All Nodes', error goes away.

I am on 1.22.0(with some nars from 1.10.0 also added to lib folder).

Re: 'Execution node' is invalid because processors with incoming connections cannot be scheduled for primary node only

SAMSAL — Fri, 08 Sep 2023 13:35:06 GMT

Hi @manishg ,

Only the top processor in a given flow can be set to execute on "Primary Node". No downstream processor can be set as such. If you want downstream processors to execute on a single node , then open the Queue configuration going to the FetchXMLFile , Under Settings tab , select "Single node" from the Load Balance Strategy" drop down. However selecting this option there is no guarantees which node is it going to be as the manual indicates:

Single node: All FlowFiles will be sent to a single node in the cluster. Which node they are sent to is not configurable. If the node is disconnected from the cluster or if unable to communicate with the node, the data that is queued for that node will remain queued until the node is available again.

If that helps please accept solution.

Thanks

Re: 'Execution node' is invalid because processors with incoming connections cannot be scheduled for primary node only

manishg — Mon, 11 Sep 2023 06:45:24 GMT

@SAMSAL I experimented same template with nifi 1.10.0, and found that FetchXMLFile has no issues with execution node as PRIMARY. It seems this new requirement mentioned by you was introduced only after 1.10.0.