Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kafka Consumer memory Leak #339

Open
jilsonjoseph opened this issue Apr 19, 2023 · 1 comment
Open

Kafka Consumer memory Leak #339

jilsonjoseph opened this issue Apr 19, 2023 · 1 comment
Labels
for/user-attention This issue needs user attention (feedback, rework, etc...)

Comments

@jilsonjoseph
Copy link

jilsonjoseph commented Apr 19, 2023

I get a memory leak when my consumers work on dev enviroments, without any load

Expected Behavior
memory not leak

Actual Behavior
memory leak

Steps to reproduce
Our Consumer creation code is below

        .createReceiveRecord(
            new TypeReference<OrderEventRetryDTO>() {
            },
            kafkaConsumerConfigProperties)
        .doOnNext(this::process)
        .onErrorContinue(this::onError)
        .doOnError(exception ->
            log.error(String.format(
                "Exception while consuming message on topic=%s with error = ", topic), exception))
        .subscribe();

In dynatrace we are seeing this below.

Screenshot 2023-04-19 at 1 09 45 PM

Our Environment
Java version: 17
Reactor version(s) used: io.projectreactor.kafka:reactor-kafka: 1.3.8

@reactorbot reactorbot added the ❓need-triage This issue needs triage, hasn't been looked at by a team member yet label Apr 19, 2023
@garyrussell
Copy link
Contributor

Have you looked at the heap to see what the leak consists of?

@garyrussell garyrussell added for/user-attention This issue needs user attention (feedback, rework, etc...) and removed ❓need-triage This issue needs triage, hasn't been looked at by a team member yet labels Apr 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for/user-attention This issue needs user attention (feedback, rework, etc...)
Projects
None yet
Development

No branches or pull requests

3 participants