Thanks Bryan. It's crystal clear ;-) Le mer. 12 sept. 2018 à 15:20, Bryan Bende <[email protected]> a écrit :
> Hello, > > Yes the way you described it is correct. > > If the directory is local then the state is local because no other > node could take over since the files are only on that node. > > When the directory is remote then it is intended to be run on primary > node and the state is stored cluster wide so that if primary changes > then another node can take over. > > -Bryan > > > On Wed, Sep 12, 2018 at 5:55 AM, Dominique De Vito <[email protected]> > wrote: > > Hi, > > > > The property "Input Directory Location" of ListFile has two possible > values: > > "local" or "remote". > > > > According to the doc, it "specifies where the Input Directory is located. > > This is used to determine whether state should be stored locally or > across > > the cluster." > > > > The same doc [1] states that: "This Processor is designed to run on > Primary > > Node only in a cluster. " > > > > Q1: what means "locally" here ? > > Does it really mean there is an _distinct_ (but with the same name) input > > directory per node? > > > > In that case, if the state is stored locally, I understand this way as > > follows: > > > > - as there is _distinct_ (but with the same name) input directory per > node, > > storing the state locally is good enough... as no node could read the > input > > directory of their siblings. Then, in case of primary node change, the > input > > directory changes, and then, no need to reuse the state of the previous > > primary node. > > > > Q2: is this/my understanding correct? > > > > Thanks. > > > > Regards, > > Dominique > > > > [1] > > > https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.ListFile/index.html >
