[
https://issues.apache.org/jira/browse/NIFI-12160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17775093#comment-17775093
]
ASF subversion and git services commented on NIFI-12160:
--------------------------------------------------------
Commit b2e3898e171b89e25b5e06f6ee849bb3edabbf9a in nifi's branch
refs/heads/main from Peter Gyori
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b2e3898e17 ]
NIFI-12160 Kafka Connect: Check for NAR unpacking before starting
Check that required NAR files are unpacked completely before starting the Kafka
Connector
This closes #7832
Signed-off-by: David Handermann <[email protected]>
> Check if all the necessary nars have been fully unpacked before starting a
> 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)
