[
https://issues.apache.org/jira/browse/NIFI-15286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18047347#comment-18047347
]
ASF subversion and git services commented on NIFI-15286:
--------------------------------------------------------
Commit f90a92146d4d018611a0879f97f019ad9b1dd5ed in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=f90a92146d ]
NIFI-15286 Added connection verification to Kafka Connection Services (#10689)
Co-authored-by: Dariusz Seweryn <[email protected]>
> Make Kafka3ConnectionService verify Broker Connections
> ------------------------------------------------------
>
> Key: NIFI-15286
> URL: https://issues.apache.org/jira/browse/NIFI-15286
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 2.6.0
> Reporter: Dariusz Seweryn
> Assignee: Dariusz Seweryn
> Priority: Major
> Time Spent: 2h
> Remaining Estimate: 0h
>
> ConsumeKafka and PublishKafka processors can work when they can connect to
> Kafka Brokers.
> h3. Current State
> Kafka3ConnectionService, ConsumeKafka and ProduceKafka do verify the
> connection to the bootstrap server by listing topics. This does not provide
> information whether all Broker Nodes can be connected to.
> h3. Improvement
> In Kafka3ConnectionService verify if all nodes can be reached. This requires
> cluster description call and calls for each individual node to describe
> config. In case the user does not have authorization to describe the cluster,
> the code could fallback to open a socket connection to listed bootstrap
> servers.
>
> In case there are many nodes, the describe config call can be run in parallel
> using virtual threads.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
