[jira] [Created] (KAFKA-6291) Cannot close EmbeddedZookeeper on Windows

Viliam Durina created KAFKA-6291: Summary: Cannot close EmbeddedZookeeper on Windows Key: KAFKA-6291 URL: https://issues.apache.org/jira/browse/KAFKA-6291 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP-227: Introduce Incremental FetchRequests to Increase Partition Scalability

Hi Jan, I agree that we probably don't want to make the protocol too complicated just for exception cases. The current FetchRequest contains an ordered list of partitions that may rotate based on the priority. Therefore it is kind of difficult to do the order matching. But you brought a good poin

Re: [DISCUSS] KIP-227: Introduce Incremental FetchRequests to Increase Partition Scalability

Hi, this discussion is going a little bit far from what I intended this thread for. I can see all of this beeing related. To let you guys know what I am currently thinking is the following: I do think the handling of Id's and epoch is rather complicated. I think the complexity comes from ai

[jira] [Created] (KAFKA-6290) Kafka Connect fails when using cast transformation

Sudhir Pradhan created KAFKA-6290: - Summary: Kafka Connect fails when using cast transformation Key: KAFKA-6290 URL: https://issues.apache.org/jira/browse/KAFKA-6290 Project: Kafka Issue Type

[GitHub] kafka pull request #4280: KAFKA-6289: NetworkClient should not expose failed...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/4280 KAFKA-6289: NetworkClient should not expose failed internal ApiVersions requests The NetworkClient internally ApiVersion requests to each broker following connection establishment. If this reques

[jira] [Created] (KAFKA-6289) NetworkClient should not return internal failed api version responses from poll

Jason Gustafson created KAFKA-6289: -- Summary: NetworkClient should not return internal failed api version responses from poll Key: KAFKA-6289 URL: https://issues.apache.org/jira/browse/KAFKA-6289 Pro

[jira] [Created] (KAFKA-6288) Broken symlink interrupts scanning the plugin path

Yeva Byzek created KAFKA-6288: - Summary: Broken symlink interrupts scanning the plugin path Key: KAFKA-6288 URL: https://issues.apache.org/jira/browse/KAFKA-6288 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP-227: Introduce Incremental FetchRequests to Increase Partition Scalability

Hi Colin, Thanks for updating the KIP. I have two comments: 1. The session epoch seems introducing some complexity. It would be good if we don't have to maintain the epoch. 2. If all the partitions has data returned (even a few messages), the next fetch would be equivalent to a full request. This

Build failed in Jenkins: kafka-trunk-jdk9 #231

See Changes: [me] KAFKA-6284: Fixed system test for Connect REST API -- [...truncated 1.44 MB...] kafka.zk.ZKPathTest > testMakeSurePersistsPathExists PASSED kafka.zk.Kafk

[GitHub] kafka pull request #4279: KAFKA-6284: Fixed system test for Connect REST API

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4279 ---

[jira] [Resolved] (KAFKA-6284) System Test failed: ConnectRestApiTest

[ https://issues.apache.org/jira/browse/KAFKA-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-6284. -- Resolution: Fixed Issue resolved by pull request 4279 [https://github.com/apache

[jira] [Created] (KAFKA-6287) Inconsistent protocol type for empty consumer groups

Ryan Leslie created KAFKA-6287: -- Summary: Inconsistent protocol type for empty consumer groups Key: KAFKA-6287 URL: https://issues.apache.org/jira/browse/KAFKA-6287 Project: Kafka Issue Type: Bu

[GitHub] kafka pull request #4279: KAFKA-6284: Fixed system test for Connect REST API

GitHub user mikkin opened a pull request: https://github.com/apache/kafka/pull/4279 KAFKA-6284: Fixed system test for Connect REST API `topics.regex` was added in KAFKA-3073. This change fixes the test that invokes `/validate` to ensure that all the configdefs are returned as expect

Re: [DISCUSS] KIP-227: Introduce Incremental FetchRequests to Increase Partition Scalability

On Wed, Nov 29, 2017, at 18:59, Dong Lin wrote: > Hey Colin, > > Thanks much for the update. I have a few questions below: > > 1. I am not very sure that we need Fetch Session Epoch. It seems that > Fetch > Session Epoch is only needed to help leader distinguish between "a full > fetch request" a

Doc says when doing re-balance, sort by leader then partition, but the code seems sort only on partition

Dear Kafka community, In the doc -> https://kafka.apache.org/documentation/#distributionimpl 4. sort Pt (so partitions on the same broker are clustered together) and During rebalancing, we try to assign partitions to consumers in such a way that reduces the number of broker nodes each consumer has

Build failed in Jenkins: kafka-trunk-jdk9 #230

See -- [...truncated 1.45 MB...] kafka.zk.ZKPathTest > testMakeSurePersistsPathExists PASSED kafka.zk.KafkaZkClientTest > testSetGetAndDeletePartitionReassignment STARTED kafka.zk.KafkaZ

Build failed in Jenkins: kafka-trunk-jdk9 #229

See Changes: [ismael] MINOR: Shutdown ControllerEventThread via event instead of interruption -- [...truncated 1.45 MB...] kafka.zk.ZKPathTest > testMakeSurePersistsPathExi

[GitHub] kafka pull request #4278: MINOR: fixed typo that causes incorrect values in ...

GitHub user kiest opened a pull request: https://github.com/apache/kafka/pull/4278 MINOR: fixed typo that causes incorrect values in records-consumed-rate JMX metric records-consumed-rate fetch metric shows different value than aggregated topic-level records-consumed-rate metrics.

[jira] [Resolved] (KAFKA-6282) exactly_once semantics breaks demo application

[ https://issues.apache.org/jira/browse/KAFKA-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romans Markuns resolved KAFKA-6282. --- Resolution: Not A Bug > exactly_once semantics breaks demo application > -

[GitHub] kafka pull request #4219: MINOR: Shutdown ControllerEventThread via event in...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4219 ---

Re: [VOTE] KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer

+1 (non-binding) On Thu, Nov 30, 2017 at 9:01 AM, Ted Yu wrote: > +1 > > On Thu, Nov 30, 2017 at 12:56 AM, Manikumar > wrote: > > > +1 (non-binding) > > > > On Thu, Nov 30, 2017 at 8:35 AM, Hu Xi wrote: > > > > > Hi all, > > > > > > As I didn't see any further discussion around this KIP, I'd l

Re: [VOTE] KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer

+1 On Thu, Nov 30, 2017 at 12:56 AM, Manikumar wrote: > +1 (non-binding) > > On Thu, Nov 30, 2017 at 8:35 AM, Hu Xi wrote: > > > Hi all, > > > > As I didn't see any further discussion around this KIP, I'd like to start > > voting. > > > > KIP documentation: > > > > https://cwiki.apache.org/conf

Re: [VOTE] KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer

+1 (non-binding) On Thu, Nov 30, 2017 at 8:35 AM, Hu Xi wrote: > Hi all, > > As I didn't see any further discussion around this KIP, I'd like to start > voting. > > KIP documentation: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 223+-+Add+per-topic+min+lead+and+per-partition+lead