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

Posted to jira@kafka.apache.org by "Ajit Singh (Jira)" <ji...@apache.org> on 2024/08/26 12:21:00 UTC

[jira] [Updated] (KAFKA-17424) Memory optimisation for Kafka-connect

     [ https://issues.apache.org/jira/browse/KAFKA-17424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ajit Singh updated KAFKA-17424:
-------------------------------
          Flags: Patch,Important  (was: Important)
    Description: When Kafka connect gives sink task it's own copy of List<SinkRecords> that RAM utilisation shoots up and at that particular moment the there will be two lists and the original list gets cleared after the sink worker finishes the current batch.  (was: When kafka connect gives sink task it's own copy of records that RAM utilization shoots up)

> Memory optimisation for Kafka-connect
> -------------------------------------
>
>                 Key: KAFKA-17424
>                 URL: https://issues.apache.org/jira/browse/KAFKA-17424
>             Project: Kafka
>          Issue Type: Improvement
>          Components: connect
>    Affects Versions: 3.8.0
>            Reporter: Ajit Singh
>            Priority: Major
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> When Kafka connect gives sink task it's own copy of List<SinkRecords> that RAM utilisation shoots up and at that particular moment the there will be two lists and the original list gets cleared after the sink worker finishes the current batch.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)