[
https://issues.apache.org/jira/browse/KAFKA-14652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Urban updated KAFKA-14652:
---------------------------------
Description:
MirrorMaker2 runs multiple Connect worker instances in a single process. In
Connect, the logging is based on the assumption that Connector names are
unique. But in MM2, the same Connector names are being used in each flow
(Connect group). This means that there is no way to differentiate between the
logs of MirrorSourceConnector in A->B and in B->A.
This can be improved by adding the flow to the logging context and the names of
the Connect framework threads.
was:
MirrorMaker2 runs multiple Connect worker instances in a single process. In
Connect, the logging is based on the assumption that Connector names are
unique. But in MM2, the same Connector names are being used in each flow
(Connect group). This means that there is no way to differentiate between the
logs of MirrorSourceConnector in A->B and in B->A.
This can be improved by adding the flow to the logging context.
> Improve MM2 logging by adding the flow information to the context
> -----------------------------------------------------------------
>
> Key: KAFKA-14652
> URL: https://issues.apache.org/jira/browse/KAFKA-14652
> Project: Kafka
> Issue Type: Improvement
> Reporter: Daniel Urban
> Assignee: Daniel Urban
> Priority: Major
>
> MirrorMaker2 runs multiple Connect worker instances in a single process. In
> Connect, the logging is based on the assumption that Connector names are
> unique. But in MM2, the same Connector names are being used in each flow
> (Connect group). This means that there is no way to differentiate between the
> logs of MirrorSourceConnector in A->B and in B->A.
> This can be improved by adding the flow to the logging context and the names
> of the Connect framework threads.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
