Alaksiej Ščarbaty created NIFI-15307:
----------------------------------------
Summary: ConsumeKinesis initialization timeout
Key: NIFI-15307
URL: https://issues.apache.org/jira/browse/NIFI-15307
Project: Apache NiFi
Issue Type: Bug
Components: Extensions
Affects Versions: 2.6.0
Reporter: Alaksiej Ščarbaty
Assignee: Alaksiej Ščarbaty
{{ConsumeKinesis}} processor waits for the AWS objects creation/initialization
in its OnScheduled method. During a first run, this operation may take up to 10
minutes, caused by index creation in DynamoDB. On subsequent runs it's much
faster - a matter of few seconds. The default value for
{{nifi.processor.scheduling.timeout}} is 1 minute, which is not enough for the
initial initialization.
This results in {{InterruptedException}} during the initialization. This
doesn't cancel index creation on AWS, so after a few retries the processor
spins up successfully. Yet, these errors don't provide the best UX.
Instead a hybrid approach with waiting in OnScheduled and onTrigger should be
used.
Wait for 30 seconds in the {{@OnScheduled}} first.
If this isn't the first run of the processor, the initialization should take a
couple of seconds - entirely within the {{{}@OnScheduled{}}}.
If not, then we log a {{warn}} with the message that the initialization may
take longer, up to 10 minutes. And do the check in the {{onTrigger}} ,
{{{}yield{}}}ing if necessary.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
