[jira] [Created] (KAFKA-8520) TimeoutException in client side doesn't have stack trace

Shixiong Zhu created KAFKA-8520: --- Summary: TimeoutException in client side doesn't have stack trace Key: KAFKA-8520 URL: https://issues.apache.org/jira/browse/KAFKA-8520 Project: Kafka Issue

[jira] [Updated] (KAFKA-8258) Verbose logs in org.apache.kafka.clients.consumer.internals.Fetcher

[ https://issues.apache.org/jira/browse/KAFKA-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shixiong Zhu updated KAFKA-8258: Description: We noticed that the Spark's Kafka connector outputs a lot of following verbose logs:

[jira] [Created] (KAFKA-8258) Verbose logs in org.apache.kafka.clients.consumer.internals.Fetcher

Shixiong Zhu created KAFKA-8258: --- Summary: Verbose logs in org.apache.kafka.clients.consumer.internals.Fetcher Key: KAFKA-8258 URL: https://issues.apache.org/jira/browse/KAFKA-8258 Project: Kafka

[jira] [Updated] (KAFKA-7703) KafkaConsumer.position may return a wrong offset after "seekToEnd" is called

[ https://issues.apache.org/jira/browse/KAFKA-7703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shixiong Zhu updated KAFKA-7703: Priority: Major (was: Blocker) > KafkaConsumer.position may return a wrong offset after

[jira] [Updated] (KAFKA-7703) KafkaConsumer.position may return a wrong offset after "seekToEnd" is called

[ https://issues.apache.org/jira/browse/KAFKA-7703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shixiong Zhu updated KAFKA-7703: Priority: Blocker (was: Major) > KafkaConsumer.position may return a wrong offset after

[jira] [Commented] (KAFKA-7703) KafkaConsumer.position may return a wrong offset after "seekToEnd" is called

[ https://issues.apache.org/jira/browse/KAFKA-7703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711191#comment-16711191 ] Shixiong Zhu commented on KAFKA-7703: - [~viktorsomogyi] Cool! Thanks! Let me know if you need more

[jira] [Issue Comment Deleted] (KAFKA-7703) KafkaConsumer.position may return a wrong offset after "seekToEnd" is called

[ https://issues.apache.org/jira/browse/KAFKA-7703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shixiong Zhu updated KAFKA-7703: Comment: was deleted (was: I also noticed that TopicPartitionState is modified by multiple threads

[jira] [Comment Edited] (KAFKA-7703) KafkaConsumer.position may return a wrong offset after "seekToEnd" is called

[ https://issues.apache.org/jira/browse/KAFKA-7703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708272#comment-16708272 ] Shixiong Zhu edited comment on KAFKA-7703 at 12/4/18 7:25 AM: -- This seems

[jira] [Commented] (KAFKA-7703) KafkaConsumer.position may return a wrong offset after "seekToEnd" is called

[ https://issues.apache.org/jira/browse/KAFKA-7703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708297#comment-16708297 ] Shixiong Zhu commented on KAFKA-7703: - I also noticed that TopicPartitionState is modified by

[jira] [Comment Edited] (KAFKA-7703) KafkaConsumer.position may return a wrong offset after "seekToEnd" is called

[ https://issues.apache.org/jira/browse/KAFKA-7703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708272#comment-16708272 ] Shixiong Zhu edited comment on KAFKA-7703 at 12/4/18 7:13 AM: -- This seems

[jira] [Commented] (KAFKA-7703) KafkaConsumer.position may return a wrong offset after "seekToEnd" is called

[ https://issues.apache.org/jira/browse/KAFKA-7703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708273#comment-16708273 ] Shixiong Zhu commented on KAFKA-7703: - I also noticed that TopicPartitionState is modified by

[jira] [Updated] (KAFKA-7703) KafkaConsumer.position may return a wrong offset after "seekToEnd" is called

[ https://issues.apache.org/jira/browse/KAFKA-7703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shixiong Zhu updated KAFKA-7703: Affects Version/s: 1.1.0 1.1.1 2.0.0

[jira] [Commented] (KAFKA-7703) KafkaConsumer.position may return a wrong offset after "seekToEnd" is called

[ https://issues.apache.org/jira/browse/KAFKA-7703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708272#comment-16708272 ] Shixiong Zhu commented on KAFKA-7703: - This seems introduced by KAFKA-6397 which moved the offset

[jira] [Updated] (KAFKA-7703) KafkaConsumer.position may return a wrong offset after "seekToEnd" is called

[ https://issues.apache.org/jira/browse/KAFKA-7703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shixiong Zhu updated KAFKA-7703: Description: After "seekToEnd" is called, "KafkaConsumer.position" may return a wrong offset set

[jira] [Created] (KAFKA-7703) KafkaConsumer.position may return a wrong offset after "seekToEnd" is called

Shixiong Zhu created KAFKA-7703: --- Summary: KafkaConsumer.position may return a wrong offset after "seekToEnd" is called Key: KAFKA-7703 URL: https://issues.apache.org/jira/browse/KAFKA-7703 Project: