kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-3385) Need to log "Rejected connection" as WARNING message
Date Sat, 07 May 2016 10:34:12 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275186#comment-15275186

Ismael Juma commented on KAFKA-3385:

I think the question here is whether we think that going over the max number of connections
is an expected event or whether it indicates a misconfiguration. The JIRA author thinks it's
the latter. The people who wrote thought it was the former. It would be interesting to hear
more opinions.

> Need to log "Rejected connection" as WARNING message
> ----------------------------------------------------
>                 Key: KAFKA-3385
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3385
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Xiaomin Zhang
>            Assignee: Andrea Cosentino
>            Priority: Minor
> We may found below INFO messages in the log due to inappropriate configuration:
> INFO kafka.network. Acceptor: Rejected connection from /XXXX, address already has the
configured maximum of 10 connections.
> It will make more sense for Kafka to report above message as "WARN", not just "INFO",
as it truly indicates something need to check against. 

This message was sent by Atlassian JIRA

View raw message