You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Przemyslaw Dubaniewicz (Jira)" <ji...@apache.org> on 2021/07/28 08:55:00 UTC
[jira] [Commented] (NIFI-6501) Add config to limit buffer queue
size in CaptureChangeMySQL
[ https://issues.apache.org/jira/browse/NIFI-6501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17388601#comment-17388601 ]
Przemyslaw Dubaniewicz commented on NIFI-6501:
----------------------------------------------
[~leiwangouc], [~bbende], [~pushpavanthar] do you think any further changes are needed here? This is a kind of serious bug so it would be great to have it fixed. Can we restart the discussion here? Or should I contact somebody else?
> Add config to limit buffer queue size in CaptureChangeMySQL
> -----------------------------------------------------------
>
> Key: NIFI-6501
> URL: https://issues.apache.org/jira/browse/NIFI-6501
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 1.9.2
> Reporter: Purushotham Pushpavanthar
> Assignee: Purushotham Pushpavanthar
> Priority: Critical
> Labels: easyfix
> Attachments: image-2019-08-02-11-29-10-829.png
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> CaptureChangeMySQL processor registers a listener with Blocking Queue as buffer with the BinLogClient. When the thread polling from the Queue is slower compared to writer, the queue grows uncontrollably and brings down the node.
> Since the flow writing to listeners in [mysql-binlog-connector-java|[https://github.com/shyiko/mysql-binlog-connector-java]] is blocking, we should initialize the queue with *initial size* and *queue offer timeout* specified by the user based in cluster configuration.
> [http://apache-nifi-developer-list.39713.n7.nabble.com/NiFi-Cluster-crashes-while-running-CaptureChangeMySQL-for-CDC-td20895.html]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)