You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2023/01/17 22:20:00 UTC

[jira] [Assigned] (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:all-tabpanel ]

David Handermann reassigned NIFI-6501:
--------------------------------------

    Assignee: Matt Burgess  (was: Purushotham Pushpavanthar)

> 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, 1.14.0, 1.13.1, 1.13.2
>            Reporter: Purushotham Pushpavanthar
>            Assignee: Matt Burgess
>            Priority: Critical
>              Labels: easyfix
>         Attachments: image-2019-08-02-11-29-10-829.png
>
>          Time Spent: 3h 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.20.10#820010)