kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Xavier Léauté (JIRA) <j...@apache.org>
Subject [jira] [Commented] (KAFKA-6475) ConfigException on the broker results in UnknownServerException in the admin client
Date Thu, 01 Feb 2018 18:05:00 GMT

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

Xavier Léauté commented on KAFKA-6475:
--------------------------------------

I was able to reproduce the problem by modifying the topic configuration  {{file.delete.delay.ms}} to
an invalid string, e.g. {{abc123}}

This results in the following exception

{{org.apache.kafka.common.errors.UnknownServerException: Invalid value 94310fdaf43 for configuration
file.delete.delay.ms: Not a number of type LONG}}

> ConfigException on the broker results in UnknownServerException in the admin client
> -----------------------------------------------------------------------------------
>
>                 Key: KAFKA-6475
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6475
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Xavier Léauté
>            Assignee: Colin P. McCabe
>            Priority: Minor
>
> Calling AdminClient.alterConfigs with an invalid configuration may cause ConfigException to
be thrown on the broker side, which results in an UnknownServerException thrown by the admin
client. It would probably make more sense for the admin client to throw InvalidConfigurationException
in that case.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message