You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2017/12/01 19:22:00 UTC

[jira] [Created] (KAFKA-6297) Consumer fetcher should handle UnsupportedVersionException more diligently

Guozhang Wang created KAFKA-6297:
------------------------------------

             Summary: Consumer fetcher should handle UnsupportedVersionException more diligently
                 Key: KAFKA-6297
                 URL: https://issues.apache.org/jira/browse/KAFKA-6297
             Project: Kafka
          Issue Type: Bug
          Components: consumer
            Reporter: Guozhang Wang


Today if the consumer is talking to an older versioned broker that does not support newer fetch versions, it will simply block without printing any warning logs. This is because when {{UnsupportedVersionException}} gets raised inside {{ConsumerNetworkClient}}, the {{Fetcher}}'s handling logic is only logging it and moves on (and hence retries forever):

{code}
                       @Override
                        public void onFailure(RuntimeException e) {
                            log.debug("Fetch request {} to {} failed", request.fetchData(), fetchTarget, e);
                        }
{code}

We should at least logging {{UnsupportedVersionException}} specifically as WARN or even let the consumer to fail fast and gracefully upon this error.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)