[
https://issues.apache.org/jira/browse/NIFI-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731742#comment-17731742
]
ASF subversion and git services commented on NIFI-11471:
--------------------------------------------------------
Commit 7f1dd9c9600f41f94b0aabf9f789bd610d93f553 in nifi's branch
refs/heads/support/nifi-1.x from David Young
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=7f1dd9c960 ]
NIFI-11471: Define new stateless configuration points
Add two new properties:
nifi.stateless.component.enableTimeout
nifi.stateless.processor.startTimeout
to allow configuring the StatelessEngine and ProcessScheduler.
This allows an operator to configure what kind of startup time the flow can
tolerate.
Previously these values were hard coded.
> Component Timeouts are configurable in Stateless Nifi
> -----------------------------------------------------
>
> Key: NIFI-11471
> URL: https://issues.apache.org/jira/browse/NIFI-11471
> Project: Apache NiFi
> Issue Type: Improvement
> Components: NiFi Stateless
> Reporter: Dye357
> Assignee: David Young
> Priority: Major
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Currently in Stateless Nifi each component is required to start within a
> statically defined timeout. In some cases (IE controller services which pull
> down web resources) this timeout is too short and causes the entire Stateless
> Nifi instance to fail starting.
> {code:java}
> private static final long COMPONENT_ENABLE_TIMEOUT_MILLIS =
> TimeUnit.SECONDS.toMillis(10); {code}
> Suggested improvement is to make this timeout configurable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
