[jira] [Resolved] (KAFKA-3624) NullPointerException Thrown for MetadataRequest when Cluster Not Available
[
https://issues.apache.org/jira/browse/KAFKA-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Tylwalk resolved KAFKA-3624.
-
Resolution: Duplicate
> NullPointerException Thrown for MetadataRequest when Cluster Not Available
> --
>
> Key: KAFKA-3624
> URL: https://issues.apache.org/jira/browse/KAFKA-3624
> Project: Kafka
> Issue Type: Bug
>Affects Versions: 0.9.0.0
>Reporter: John Tylwalk
>
> Have been seeing consistently a NPE when metadata request is sent against a
> cluster that isn't online:
> {code}
> java.lang.NullPointerException: null
> at
> org.apache.kafka.common.requests.MetadataResponse.(MetadataResponse.java:130)
> ~[kafka-client-lib.jar:na]
> at
> org.apache.kafka.clients.consumer.internals.Fetcher.getTopicMetadata(Fetcher.java:203)
> ~[kafka-client-lib.jar:na]
> at
> org.apache.kafka.clients.consumer.KafkaConsumer.partitionsFor(KafkaConsumer.java:1143)
> ~[kafka-client-lib.jar:na]
> {code}
> Looks like this is from this line:
> {code}
> Object[] brokerStructs = (Object[]) struct.get(BROKERS_KEY_NAME);
> {code}
> The returned struct doesn't have the brokers key, since the returned data is
> incomplete, due to an invalid request. Would expect to see a better exception
> / handling rather than NPE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KAFKA-3624) NullPointerException Thrown for MetadataRequest when Cluster Not Available
[
https://issues.apache.org/jira/browse/KAFKA-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15258952#comment-15258952
]
John Tylwalk commented on KAFKA-3624:
-
Yep looks like the same issue, closing this out as a dupe
> NullPointerException Thrown for MetadataRequest when Cluster Not Available
> --
>
> Key: KAFKA-3624
> URL: https://issues.apache.org/jira/browse/KAFKA-3624
> Project: Kafka
> Issue Type: Bug
>Affects Versions: 0.9.0.0
>Reporter: John Tylwalk
>
> Have been seeing consistently a NPE when metadata request is sent against a
> cluster that isn't online:
> {code}
> java.lang.NullPointerException: null
> at
> org.apache.kafka.common.requests.MetadataResponse.(MetadataResponse.java:130)
> ~[kafka-client-lib.jar:na]
> at
> org.apache.kafka.clients.consumer.internals.Fetcher.getTopicMetadata(Fetcher.java:203)
> ~[kafka-client-lib.jar:na]
> at
> org.apache.kafka.clients.consumer.KafkaConsumer.partitionsFor(KafkaConsumer.java:1143)
> ~[kafka-client-lib.jar:na]
> {code}
> Looks like this is from this line:
> {code}
> Object[] brokerStructs = (Object[]) struct.get(BROKERS_KEY_NAME);
> {code}
> The returned struct doesn't have the brokers key, since the returned data is
> incomplete, due to an invalid request. Would expect to see a better exception
> / handling rather than NPE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KAFKA-3624) NullPointerException Thrown for MetadataRequest when Cluster Not Available
[
https://issues.apache.org/jira/browse/KAFKA-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Tylwalk updated KAFKA-3624:
Description:
Have been seeing consistently a NPE when metadata request is sent against a
cluster that isn't online:
{code}
java.lang.NullPointerException: null
at
org.apache.kafka.common.requests.MetadataResponse.(MetadataResponse.java:130)
~[kafka-client-lib.jar:na]
at
org.apache.kafka.clients.consumer.internals.Fetcher.getTopicMetadata(Fetcher.java:203)
~[kafka-client-lib.jar:na]
at
org.apache.kafka.clients.consumer.KafkaConsumer.partitionsFor(KafkaConsumer.java:1143)
~[kafka-client-lib.jar:na]
{code}
Looks like this is from this line:
{code}
Object[] brokerStructs = (Object[]) struct.get(BROKERS_KEY_NAME);
{code}
The returned struct doesn't have the brokers key, since the returned data is
incomplete. Would expect to see a better exception / handling rather than NPE.
was:
Have been seeing consistently a NPE when metadata request is sent against a
cluster that isn't online:
{code}
java.lang.NullPointerException: null
at
org.apache.kafka.common.requests.MetadataResponse.(MetadataResponse.java:130)
~[kafka-client-lib.jar:na]
at
org.apache.kafka.clients.consumer.internals.Fetcher.getTopicMetadata(Fetcher.java:203)
~[kafka-client-lib.jar:na]
at
org.apache.kafka.clients.consumer.KafkaConsumer.partitionsFor(KafkaConsumer.java:1143)
~[kafka-client-lib.jar:na]
{code}
> NullPointerException Thrown for MetadataRequest when Cluster Not Available
> --
>
> Key: KAFKA-3624
> URL: https://issues.apache.org/jira/browse/KAFKA-3624
> Project: Kafka
> Issue Type: Bug
>Affects Versions: 0.9.0.0
>Reporter: John Tylwalk
>
> Have been seeing consistently a NPE when metadata request is sent against a
> cluster that isn't online:
> {code}
> java.lang.NullPointerException: null
> at
> org.apache.kafka.common.requests.MetadataResponse.(MetadataResponse.java:130)
> ~[kafka-client-lib.jar:na]
> at
> org.apache.kafka.clients.consumer.internals.Fetcher.getTopicMetadata(Fetcher.java:203)
> ~[kafka-client-lib.jar:na]
> at
> org.apache.kafka.clients.consumer.KafkaConsumer.partitionsFor(KafkaConsumer.java:1143)
> ~[kafka-client-lib.jar:na]
> {code}
> Looks like this is from this line:
> {code}
> Object[] brokerStructs = (Object[]) struct.get(BROKERS_KEY_NAME);
> {code}
> The returned struct doesn't have the brokers key, since the returned data is
> incomplete. Would expect to see a better exception / handling rather than NPE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KAFKA-3624) NullPointerException Thrown for MetadataRequest when Cluster Not Available
John Tylwalk created KAFKA-3624:
---
Summary: NullPointerException Thrown for MetadataRequest when
Cluster Not Available
Key: KAFKA-3624
URL: https://issues.apache.org/jira/browse/KAFKA-3624
Project: Kafka
Issue Type: Bug
Affects Versions: 0.9.0.0
Reporter: John Tylwalk
Have been seeing consistently a NPE when metadata request is sent against a
cluster that isn't online:
{code}
java.lang.NullPointerException: null
at
org.apache.kafka.common.requests.MetadataResponse.(MetadataResponse.java:130)
~[kafka-client-lib.jar:na]
at
org.apache.kafka.clients.consumer.internals.Fetcher.getTopicMetadata(Fetcher.java:203)
~[kafka-client-lib.jar:na]
at
org.apache.kafka.clients.consumer.KafkaConsumer.partitionsFor(KafkaConsumer.java:1143)
~[kafka-client-lib.jar:na]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KAFKA-3624) NullPointerException Thrown for MetadataRequest when Cluster Not Available
[
https://issues.apache.org/jira/browse/KAFKA-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Tylwalk updated KAFKA-3624:
Description:
Have been seeing consistently a NPE when metadata request is sent against a
cluster that isn't online:
{code}
java.lang.NullPointerException: null
at
org.apache.kafka.common.requests.MetadataResponse.(MetadataResponse.java:130)
~[kafka-client-lib.jar:na]
at
org.apache.kafka.clients.consumer.internals.Fetcher.getTopicMetadata(Fetcher.java:203)
~[kafka-client-lib.jar:na]
at
org.apache.kafka.clients.consumer.KafkaConsumer.partitionsFor(KafkaConsumer.java:1143)
~[kafka-client-lib.jar:na]
{code}
Looks like this is from this line:
{code}
Object[] brokerStructs = (Object[]) struct.get(BROKERS_KEY_NAME);
{code}
The returned struct doesn't have the brokers key, since the returned data is
incomplete, due to an invalid request. Would expect to see a better exception /
handling rather than NPE.
was:
Have been seeing consistently a NPE when metadata request is sent against a
cluster that isn't online:
{code}
java.lang.NullPointerException: null
at
org.apache.kafka.common.requests.MetadataResponse.(MetadataResponse.java:130)
~[kafka-client-lib.jar:na]
at
org.apache.kafka.clients.consumer.internals.Fetcher.getTopicMetadata(Fetcher.java:203)
~[kafka-client-lib.jar:na]
at
org.apache.kafka.clients.consumer.KafkaConsumer.partitionsFor(KafkaConsumer.java:1143)
~[kafka-client-lib.jar:na]
{code}
Looks like this is from this line:
{code}
Object[] brokerStructs = (Object[]) struct.get(BROKERS_KEY_NAME);
{code}
The returned struct doesn't have the brokers key, since the returned data is
incomplete. Would expect to see a better exception / handling rather than NPE.
> NullPointerException Thrown for MetadataRequest when Cluster Not Available
> --
>
> Key: KAFKA-3624
> URL: https://issues.apache.org/jira/browse/KAFKA-3624
> Project: Kafka
> Issue Type: Bug
>Affects Versions: 0.9.0.0
>Reporter: John Tylwalk
>
> Have been seeing consistently a NPE when metadata request is sent against a
> cluster that isn't online:
> {code}
> java.lang.NullPointerException: null
> at
> org.apache.kafka.common.requests.MetadataResponse.(MetadataResponse.java:130)
> ~[kafka-client-lib.jar:na]
> at
> org.apache.kafka.clients.consumer.internals.Fetcher.getTopicMetadata(Fetcher.java:203)
> ~[kafka-client-lib.jar:na]
> at
> org.apache.kafka.clients.consumer.KafkaConsumer.partitionsFor(KafkaConsumer.java:1143)
> ~[kafka-client-lib.jar:na]
> {code}
> Looks like this is from this line:
> {code}
> Object[] brokerStructs = (Object[]) struct.get(BROKERS_KEY_NAME);
> {code}
> The returned struct doesn't have the brokers key, since the returned data is
> incomplete, due to an invalid request. Would expect to see a better exception
> / handling rather than NPE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KAFKA-3248) AdminClient Blocks Forever in send Method
John Tylwalk created KAFKA-3248:
---
Summary: AdminClient Blocks Forever in send Method
Key: KAFKA-3248
URL: https://issues.apache.org/jira/browse/KAFKA-3248
Project: Kafka
Issue Type: Bug
Components: admin
Affects Versions: 0.9.0.0
Reporter: John Tylwalk
Priority: Minor
AdminClient will block forever when performing operations involving the
{{send()}} method, due to usage of
{{ConsumerNetworkClient.poll(RequestFuture)}} - which blocks indefinitely.
Suggested fix is to use {{ConsumerNetworkClient.poll(RequestFuture, long
timeout)}} in {{AdminClient.send()}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
