[
https://issues.apache.org/jira/browse/NIFI-12405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-12405:
------------------------------------
Status: Patch Available (was: Open)
> CaptureChangeMySQL has a problem using mysql-binlog-connector-java
> ------------------------------------------------------------------
>
> Key: NIFI-12405
> URL: https://issues.apache.org/jira/browse/NIFI-12405
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: xiyang
> Assignee: xiyang
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When we used CaptureChangeMySQL to collect a database product of Ali Cloud
> (polardb-x), we found that after starting CaptureChangeMySQL, the number of
> active session connections would continue to rise, resulting in database
> blocking. After investigation by engineers of both sides, keepAlive in
> mysql-binlog-connector-java is set to true by default.
> The reason: in mysql these instructions are always stacked in the mysql recv
> buffer, which will fill up after a long time. In polardb-x, these
> instructions are not only stacked in the buffer, but occupy a thread.
> Therefore, we need to consider extracting persistent connections into the
> nifi configuration and letting the user choose.
> issue:[https://github.com/shyiko/mysql-binlog-connector-java/issues/118]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
