You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/06/12 18:49:00 UTC
[jira] [Commented] (NIFI-11471) Component Timeouts are configurable in Stateless Nifi
[ https://issues.apache.org/jira/browse/NIFI-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731739#comment-17731739 ]
ASF subversion and git services commented on NIFI-11471:
--------------------------------------------------------
Commit 15f8f872f64a0f30170218fa44c24dbfa63083ae in nifi's branch refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=15f8f872f6 ]
NIFI-11471: Added a system test to verify controller service enable timeout.
This closes #7242.
> 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)