Hi Koji，
My test is as follows.
ProcessorA, scheduled only on primary node and with only one cocurrency.
The result of ProcessorA load balanced to ProcessorB. The strategy is by
attribute. All the output FlowFiles of ProcessorA has the same attribute used
for balance, so all FlowFiles will
Hi Lei,
Does 'balance strategy' means load balance strategy? Which strategy
are you using? I thought Prioritizers are applied on the destination
node after load balancing has transferred FlowFiles. Are those A, B
and C flow files generated on different nodes and sent to a single
node to merge
Seems it is because of the balance strategy that is used.
The balance will not guarantee the the order.
Thanks,
Lei
wangl...@geekplus.com.cn
From: wangl...@geekplus.com.cn
Date: 2019-10-16 10:21
To: dev; users
CC: dev
Subject: Re: Re: MergeRecord can not guarantee the ordering of the input
Hi Koji,
Actually i have set all connections to FIFO and concurrency tasks to 1 for all
processors.
Before and after the MergeRecord, I add a LogAttribute to debug.
Before MergeRecord，the order in logfile is A,B,C in three flowfile
After MergeRecord, the order becomes {A,C,B} in one flowfile
Hi Lei,
How about setting FIFO prioritizer at all the preceding connections
before the MergeRecord?
Without setting any prioritizer, FlowFile ordering is nondeterministic.
Thanks,
Koji
On Tue, Oct 15, 2019 at 8:56 PM wangl...@geekplus.com.cn
wrote:
>
>
> If FlowFile A, B, C enter the
