You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2023/10/13 23:41:00 UTC
[jira] [Updated] (NIFI-12160) Check if all the necessary nars have been fully unpacked before starting Kafka Connector
[ https://issues.apache.org/jira/browse/NIFI-12160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Handermann updated NIFI-12160:
------------------------------------
Summary: Check if all the necessary nars have been fully unpacked before starting Kafka Connector (was: Check if all the necessary nars have been fully unpacked before starting a connector)
> Check if all the necessary nars have been fully unpacked before starting Kafka Connector
> ----------------------------------------------------------------------------------------
>
> Key: NIFI-12160
> URL: https://issues.apache.org/jira/browse/NIFI-12160
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Peter Gyori
> Assignee: Peter Gyori
> Priority: Major
> Labels: kafka-connect
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Each deployed Stateless NiFi-based Kafka Connect connector has a directory under DEFAULT_WORKING_DIRECTORY (/tmp/nifi-stateless-working) where the necessary NARs are unpacked.
> If the job doing the unpacking is interrupted for some reason, the connector's directory will exist without having all the necessary files in it. In a case like this when the connector is started it detects the directory so it does not unpack the NARs again however the missing files cause various errors.
> Currently the solution is manual: the connector's directory needs to be deleted from /tmp/nifi-stateless-working and the connector needs to be redeployed.
> A fix should be created for this issue so that the system detects that unpacking hadn't been finished and does the unpacking properly before deployment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)