You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@nifi.apache.org by Paul Hadrosek <pa...@inovexcorp.com> on 2016/03/08 20:50:43 UTC
Processor Isolation Problem
I have a PutFile processor in a cluster that is configured as a primary
node. I have a external system looking at that directory and sending a
response back to a receive directory. When I run my file through it is
queued right before the PutFile processor. My question is Why is the
flowfile queued?
Thanks
--
*Paul Hadrosek Principal Solutions Architect*
*i**Novex Information Systems*
http://www.inovexcorp.com
*paul.hadrosek@inovexcorp.com
<http://webmail.verizon.com/webmail/%22http://mailto:shelia.baesch@inovexcorp.com%22>*
------------------------------------------------------------------------
The information contained in this message may be privileged, confidential,
and protected from disclosure. If the reader of this message is not the
intended recipient, or any employee or agent responsible for delivering
this message to the intended recipient, you are hereby notified that any
dissemination, distribution, or copying of this communication is strictly
prohibited. If you have received this communication in error, please notify
us immediately by replying to the message and deleting it from your
computer.
Re: Processor Isolation Problem
Posted by Paul Hadrosek <pa...@gmail.com>.
I was afraid that was the answer. The external system client only connects to one ip at a time and is limited to one ip connection. Originally I wanted to process the data on all nodes. Can I use an RPG within the cluster with the primary as the source? Is that possible?
Thanks for your help
Paul
Sent from my iPad
> On Mar 8, 2016, at 3:33 PM, Mark Payne <ma...@hotmail.com> wrote:
>
> Paul,
>
> You mentioned that PutFile is running on Primary Node only. Is the FlowFile
> queued on one of the other nodes? You can generally check this by right-clicking
> on the connection and clicking "List Queue" (assuming that you're running 0.5.x).
>
> Generally, you would run a Processor as Primary Node only for source processors.
> Is there a reason that you want to run the PutFile only on the primary node?
>
> Thanks
> -Mark
>
>
>> On Mar 8, 2016, at 2:50 PM, Paul Hadrosek <pa...@inovexcorp.com> wrote:
>>
>> I have a PutFile processor in a cluster that is configured as a primary
>> node. I have a external system looking at that directory and sending a
>> response back to a receive directory. When I run my file through it is
>> queued right before the PutFile processor. My question is Why is the
>> flowfile queued?
>>
>> Thanks
>>
>> --
>> Paul Hadrosek
>> Principal Solutions Architect
>> iNovex Information Systems
>>
>>
>> http://www.inovexcorp.com
>> paul.hadrosek@inovexcorp.com
>> ------------------------------------------------------------------------
>>
>>
>> The information contained in this message may be privileged, confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or any employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer.
>>
>
Re: Processor Isolation Problem
Posted by Mark Payne <ma...@hotmail.com>.
Paul,
You mentioned that PutFile is running on Primary Node only. Is the FlowFile
queued on one of the other nodes? You can generally check this by right-clicking
on the connection and clicking "List Queue" (assuming that you're running 0.5.x).
Generally, you would run a Processor as Primary Node only for source processors.
Is there a reason that you want to run the PutFile only on the primary node?
Thanks
-Mark
> On Mar 8, 2016, at 2:50 PM, Paul Hadrosek <pa...@inovexcorp.com> wrote:
>
> I have a PutFile processor in a cluster that is configured as a primary
> node. I have a external system looking at that directory and sending a
> response back to a receive directory. When I run my file through it is
> queued right before the PutFile processor. My question is Why is the
> flowfile queued?
>
> Thanks
>
> --
> Paul Hadrosek
> Principal Solutions Architect
> iNovex Information Systems
>
>
> http://www.inovexcorp.com <http://www.inovexcorp.com/>
> paul.hadrosek@inovexcorp.com <http://webmail.verizon.com/webmail/%22http://mailto:shelia.baesch@inovexcorp.com%22>
> ------------------------------------------------------------------------
>
>
> The information contained in this message may be privileged, confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or any employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer.
>
>
Re: Processor Isolation Problem
Posted by Bryan Bende <bb...@gmail.com>.
Paul,
If I am understanding correctly, you have several processors leading up to
a PutFile which is scheduled on Primary Node Only?
In a NiFi cluster, the same flow runs on every node, so every node in your
cluster has a PutFile processor, but it is only be scheduled to run on the
primary node.
Typically you use "primary node only" to control the execution of a source
processor so that a pull or fetch only happens from a single node.
-Bryan
On Tue, Mar 8, 2016 at 2:50 PM, Paul Hadrosek <pa...@inovexcorp.com>
wrote:
> I have a PutFile processor in a cluster that is configured as a primary
> node. I have a external system looking at that directory and sending a
> response back to a receive directory. When I run my file through it is
> queued right before the PutFile processor. My question is Why is the
> flowfile queued?
>
> Thanks
>
> --
>
> *Paul Hadrosek Principal Solutions Architect*
> *i**Novex Information Systems*
>
>
> http://www.inovexcorp.com
> *paul.hadrosek@inovexcorp.com
> <http://webmail.verizon.com/webmail/%22http://mailto:shelia.baesch@inovexcorp.com%22>*
>
>
> ------------------------------------------------------------------------
>
>
> The information contained in this message may be privileged, confidential,
> and protected from disclosure. If the reader of this message is not the
> intended recipient, or any employee or agent responsible for delivering
> this message to the intended recipient, you are hereby notified that any
> dissemination, distribution, or copying of this communication is strictly
> prohibited. If you have received this communication in error, please notify
> us immediately by replying to the message and deleting it from your
> computer.
>
>