[
https://issues.apache.org/jira/browse/KAFKA-18985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertalan Kondrat updated KAFKA-18985:
-------------------------------------
Description:
[KIP-1144|https://cwiki.apache.org/confluence/display/KAFKA/KIP-1144%3A+Exposing+a+new+public+REST+API+for+MirrorMaker+2]
[KIP-710: Full support for distributed mode in dedicated MirrorMaker 2.0
clusters|https://cwiki.apache.org/confluence/display/KAFKA/KIP-710%3A+Full+support+for+distributed+mode+in+dedicated+MirrorMaker+2.0+clusters]
removed all the public REST APIs from MirrorMaker2 and leave only the internal
endpoints for fencing and task configuration update. Since then, the
MirrorMaker2 lacks a dedicated REST interface to expose detailed status (e.g.
flows, connectors, tasks, and replicated topics). Administrators must rely on
log parsing or indirect metrics, which can complicate troubleshooting and
integration with monitoring systems. By exposing endpoints, users will have a
consistent, secure API to:
* *Monitor replication flows:* View whether flows (e.g. A→B, B→A) are in state
of replicating, or disabled...
* *Access replicated topics:* A crucial detail in replication flows is that,
which topics are actually replicated after applying the topic filtering and
enable the replication.
* *Pause/Resume replication flows*
* *Access, and manipulate source offsets*
* *Access connector and task status:* Inspect state (e.g., RUNNING, PAUSED,
UNASSIGNED,...) and counts of running tasks.
* *Access an admin API*
This KIP aims to improve observability and operational control of MirrorMaker2
without requiring major architectural changes.
> Exposing a new public REST API for MirrorMaker2
> -----------------------------------------------
>
> Key: KAFKA-18985
> URL: https://issues.apache.org/jira/browse/KAFKA-18985
> Project: Kafka
> Issue Type: Improvement
> Components: mirrormaker
> Reporter: Bertalan Kondrat
> Assignee: Bertalan Kondrat
> Priority: Major
>
> [KIP-1144|https://cwiki.apache.org/confluence/display/KAFKA/KIP-1144%3A+Exposing+a+new+public+REST+API+for+MirrorMaker+2]
>
> [KIP-710: Full support for distributed mode in dedicated MirrorMaker 2.0
> clusters|https://cwiki.apache.org/confluence/display/KAFKA/KIP-710%3A+Full+support+for+distributed+mode+in+dedicated+MirrorMaker+2.0+clusters]
> removed all the public REST APIs from MirrorMaker2 and leave only the
> internal endpoints for fencing and task configuration update. Since then, the
> MirrorMaker2 lacks a dedicated REST interface to expose detailed status (e.g.
> flows, connectors, tasks, and replicated topics). Administrators must rely on
> log parsing or indirect metrics, which can complicate troubleshooting and
> integration with monitoring systems. By exposing endpoints, users will have a
> consistent, secure API to:
> * *Monitor replication flows:* View whether flows (e.g. A→B, B→A) are in
> state of replicating, or disabled...
> * *Access replicated topics:* A crucial detail in replication flows is that,
> which topics are actually replicated after applying the topic filtering and
> enable the replication.
> * *Pause/Resume replication flows*
> * *Access, and manipulate source offsets*
> * *Access connector and task status:* Inspect state (e.g., RUNNING, PAUSED,
> UNASSIGNED,...) and counts of running tasks.
> * *Access an admin API*
> This KIP aims to improve observability and operational control of
> MirrorMaker2 without requiring major architectural changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
