[jira] [Commented] (KAFKA-6681) Two instances of kafka consumer reading the same partition within a consumer group

[ https://issues.apache.org/jira/browse/KAFKA-6681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16413500#comment-16413500 ] Narayan Periwal commented on KAFKA-6681: [~yuzhih...@gmail.com], any update on thi

[jira] [Commented] (KAFKA-6712) Throw a specific exception with wrong topic name for interactive queries

[ https://issues.apache.org/jira/browse/KAFKA-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16413518#comment-16413518 ] Francesco Guardiani commented on KAFKA-6712: Yep > Throw a specific exception

[jira] [Updated] (KAFKA-6714) KafkaController marks all Brokers as "Shutting down", though only one broker has been shut down

[ https://issues.apache.org/jira/browse/KAFKA-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Eisele updated KAFKA-6714: -- Description: In our Kafka cluster we experienced a situation in wich the Kafka controller has all Broke

[jira] [Updated] (KAFKA-6714) KafkaController marks all Brokers as "Shutting down", though only one broker has been shut down

[ https://issues.apache.org/jira/browse/KAFKA-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Eisele updated KAFKA-6714: -- Priority: Critical (was: Major) > KafkaController marks all Brokers as "Shutting down", though only one

[jira] [Created] (KAFKA-6714) KafkaController marks all Brokers as "Shutting down", though only one broker has been shut down

Uwe Eisele created KAFKA-6714: - Summary: KafkaController marks all Brokers as "Shutting down", though only one broker has been shut down Key: KAFKA-6714 URL: https://issues.apache.org/jira/browse/KAFKA-6714

[jira] [Updated] (KAFKA-6714) KafkaController marks all Brokers as "Shutting down", though only one broker has been shut down

[ https://issues.apache.org/jira/browse/KAFKA-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Eisele updated KAFKA-6714: -- Description: In our Kafka cluster we experienced a situation in wich the Kafka controller has all Broke

[jira] [Updated] (KAFKA-6714) KafkaController marks all Brokers as "Shutting down", though only one broker has been shut down

[ https://issues.apache.org/jira/browse/KAFKA-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Eisele updated KAFKA-6714: -- Environment: Kafka cluster on Amazon AWS EC2 r4.2xlarge instances with 5 nodes and a Zookeeper cluster o

[jira] [Commented] (KAFKA-6681) Two instances of kafka consumer reading the same partition within a consumer group

[ https://issues.apache.org/jira/browse/KAFKA-6681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16413789#comment-16413789 ] Narayan Periwal commented on KAFKA-6681: [~yuzhih...@gmail.com], We faced yet ano

[jira] [Created] (KAFKA-6715) Leader transition for all partitions lead by two brokers without visible reason

Uwe Eisele created KAFKA-6715: - Summary: Leader transition for all partitions lead by two brokers without visible reason Key: KAFKA-6715 URL: https://issues.apache.org/jira/browse/KAFKA-6715 Project: Kafk

[jira] [Updated] (KAFKA-6715) Leader transition for all partitions lead by two brokers without visible reason

[ https://issues.apache.org/jira/browse/KAFKA-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Eisele updated KAFKA-6715: -- Attachment: 20180319-1756_kafka01-jvm-stack.dump > Leader transition for all partitions lead by two brok

[jira] [Updated] (KAFKA-6715) Leader transition for all partitions lead by two brokers without visible reason

[ https://issues.apache.org/jira/browse/KAFKA-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Eisele updated KAFKA-6715: -- Description: In our cluster we experienced a situation, in which the leader of all partitions lead by t

[jira] [Updated] (KAFKA-6714) KafkaController marks all Brokers as "Shutting down", though only one broker has been shut down

[ https://issues.apache.org/jira/browse/KAFKA-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Eisele updated KAFKA-6714: -- Description: In our Kafka cluster we experienced a situation in wich the Kafka controller has all Broke

[jira] [Updated] (KAFKA-6715) Leader transition for all partitions lead by two brokers without visible reason

[ https://issues.apache.org/jira/browse/KAFKA-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Eisele updated KAFKA-6715: -- Description: In our cluster we experienced a situation, in which the leader of all partitions lead by t

[jira] [Updated] (KAFKA-6715) Leader transition for all partitions lead by two brokers without visible reason

[ https://issues.apache.org/jira/browse/KAFKA-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Eisele updated KAFKA-6715: -- Description: In our cluster we experienced a situation, in which the leader of all partitions lead by t

[jira] [Commented] (KAFKA-5413) Log cleaner fails due to large offset in segment file

[ https://issues.apache.org/jira/browse/KAFKA-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16413904#comment-16413904 ] Andrew Olson commented on KAFKA-5413: - {quote}Is this the same issue as was reported h

[jira] [Comment Edited] (KAFKA-6303) Potential lack of synchronization in NioEchoServer#AcceptorThread

[ https://issues.apache.org/jira/browse/KAFKA-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333251#comment-16333251 ] Ted Yu edited comment on KAFKA-6303 at 3/26/18 4:41 PM: lgtm was

[jira] [Comment Edited] (KAFKA-5946) Give connector method parameter better name

[ https://issues.apache.org/jira/browse/KAFKA-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392411#comment-16392411 ] Ted Yu edited comment on KAFKA-5946 at 3/26/18 4:42 PM: Thanks for

[jira] [Comment Edited] (KAFKA-5846) Use singleton NoOpConsumerRebalanceListener in subscribe() call where listener is not specified

[ https://issues.apache.org/jira/browse/KAFKA-5846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191405#comment-16191405 ] Ted Yu edited comment on KAFKA-5846 at 3/26/18 4:42 PM: Patch look

[jira] [Comment Edited] (KAFKA-5802) ScramServerCallbackHandler#handle should check username not being null before calling credentialCache.get()

[ https://issues.apache.org/jira/browse/KAFKA-5802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16302643#comment-16302643 ] Ted Yu edited comment on KAFKA-5802 at 3/26/18 4:43 PM: +1 from me

[jira] [Updated] (KAFKA-5943) Reduce dependency on mock in connector tests

[ https://issues.apache.org/jira/browse/KAFKA-5943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KAFKA-5943: -- Description: Currently connector tests make heavy use of mock (easymock, power mock). This may hide the real lo

[jira] [Updated] (KAFKA-6531) SocketServerTest#closingChannelException fails sometimes

[ https://issues.apache.org/jira/browse/KAFKA-6531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KAFKA-6531: -- Component/s: core > SocketServerTest#closingChannelException fails sometimes > -

[jira] [Updated] (KAFKA-6678) Upgrade dependencies with later release versions

[ https://issues.apache.org/jira/browse/KAFKA-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KAFKA-6678: -- Description: {code} The following dependencies have later release versions: - net.sourceforge.argparse4j:argpar

[jira] [Resolved] (KAFKA-6712) Throw a specific exception with wrong topic name for interactive queries

[ https://issues.apache.org/jira/browse/KAFKA-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6712. Resolution: Duplicate > Throw a specific exception with wrong topic name for interactive que

[jira] [Comment Edited] (KAFKA-6712) Throw a specific exception with wrong topic name for interactive queries

[ https://issues.apache.org/jira/browse/KAFKA-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16413129#comment-16413129 ] Matthias J. Sax edited comment on KAFKA-6712 at 3/26/18 5:30 PM: ---

[jira] [Issue Comment Deleted] (KAFKA-6530) Use actual first offset of messages when rolling log segment for magic v2

[ https://issues.apache.org/jira/browse/KAFKA-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhruvil Shah updated KAFKA-6530: Comment: was deleted (was: Thanks! On Sat, Mar 17, 2018 at 10:31 AM Jason Gustafson (JIRA) ) > U

[jira] [Created] (KAFKA-6716) discardChannel should be released in MockSelector#completeSend

Ted Yu created KAFKA-6716: - Summary: discardChannel should be released in MockSelector#completeSend Key: KAFKA-6716 URL: https://issues.apache.org/jira/browse/KAFKA-6716 Project: Kafka Issue Type: T

[jira] [Commented] (KAFKA-6711) Checkpoint of InMemoryStore along with GlobalKTable

[ https://issues.apache.org/jira/browse/KAFKA-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414308#comment-16414308 ] Guozhang Wang commented on KAFKA-6711: -- Hello [~cemo], it is by-design that in-memory

[jira] [Updated] (KAFKA-6711) Checkpoint of InMemoryStore along with GlobalKTable

[ https://issues.apache.org/jira/browse/KAFKA-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-6711: - Labels: newbie (was: ) > Checkpoint of InMemoryStore along with GlobalKTable > -

[jira] [Updated] (KAFKA-6711) GlobalStateManagerImpl should not write offsets of in-memory stores in checkpoint file

[ https://issues.apache.org/jira/browse/KAFKA-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-6711: - Summary: GlobalStateManagerImpl should not write offsets of in-memory stores in checkpoint file (

[jira] [Commented] (KAFKA-6713) Provide an easy way replace store with a custom one on High-Level Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414323#comment-16414323 ] Guozhang Wang commented on KAFKA-6713: -- Hi [~cemo] Thanks for reporting this, is very

[jira] [Updated] (KAFKA-6713) Provide an easy way replace store with a custom one on High-Level Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cemalettin Koç updated KAFKA-6713: -- Attachment: TypeConverter.java DelegatingByteStore.java BytesType

[jira] [Commented] (KAFKA-6713) Provide an easy way replace store with a custom one on High-Level Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414469#comment-16414469 ] Cemalettin Koç commented on KAFKA-6713: --- Hi [~guozhang], I have copied TypeConverter

[jira] [Updated] (KAFKA-6413) ReassignPartitionsCommand#parsePartitionReassignmentData() should give better error message when JSON is malformed

[ https://issues.apache.org/jira/browse/KAFKA-6413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KAFKA-6413: -- Description: In this thread: http://search-hadoop.com/m/Kafka/uyzND1J9Hizcxo0X?subj=Partition+reassignment+data

[jira] [Comment Edited] (KAFKA-6713) Provide an easy way replace store with a custom one on High-Level Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414469#comment-16414469 ] Cemalettin Koç edited comment on KAFKA-6713 at 3/26/18 8:20 PM:

[jira] [Updated] (KAFKA-5863) Potential null dereference in DistributedHerder#reconfigureConnector()

[ https://issues.apache.org/jira/browse/KAFKA-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KAFKA-5863: -- Description: Here is the call chain: {code} RestServer.httpRequest(reconfigUrl,

[jira] [Commented] (KAFKA-6713) Provide an easy way replace store with a custom one on High-Level Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414477#comment-16414477 ] Cemalettin Koç commented on KAFKA-6713: --- Today I came across another scenario which

[jira] [Commented] (KAFKA-6711) GlobalStateManagerImpl should not write offsets of in-memory stores in checkpoint file

[ https://issues.apache.org/jira/browse/KAFKA-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414555#comment-16414555 ] Cemalettin Koç commented on KAFKA-6711: --- I will fix [~guozhang].  > GlobalStateMana

[jira] [Assigned] (KAFKA-6711) GlobalStateManagerImpl should not write offsets of in-memory stores in checkpoint file

[ https://issues.apache.org/jira/browse/KAFKA-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-6711: Assignee: Cemalettin Koç > GlobalStateManagerImpl should not write offsets of in-memory sto

[jira] [Commented] (KAFKA-6711) GlobalStateManagerImpl should not write offsets of in-memory stores in checkpoint file

[ https://issues.apache.org/jira/browse/KAFKA-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414569#comment-16414569 ] Guozhang Wang commented on KAFKA-6711: -- Great! I've assigned the ticket to you. > Gl

[jira] [Commented] (KAFKA-6713) Provide an easy way replace store with a custom one on High-Level Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414606#comment-16414606 ] Guozhang Wang commented on KAFKA-6713: -- Hi [~cemo], I've read your code, and here are

[jira] [Commented] (KAFKA-6709) broker failed to handle request due to OOM

[ https://issues.apache.org/jira/browse/KAFKA-6709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414613#comment-16414613 ] Dhruvil Shah commented on KAFKA-6709: - It's hard to estimate how much memory would be

[jira] [Commented] (KAFKA-6711) GlobalStateManagerImpl should not write offsets of in-memory stores in checkpoint file

[ https://issues.apache.org/jira/browse/KAFKA-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414673#comment-16414673 ] Cemalettin Koç commented on KAFKA-6711: --- [~guozhang] Would you please check implemen

[jira] [Commented] (KAFKA-6054) ERROR "SubscriptionInfo - unable to decode subscription data: version=2" when upgrading from 0.10.0.0 to 0.10.2.1

[ https://issues.apache.org/jira/browse/KAFKA-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414777#comment-16414777 ] ASF GitHub Bot commented on KAFKA-6054: --- mjsax closed pull request #4758: KAFKA-6054

[jira] [Commented] (KAFKA-6666) OffsetOutOfRangeException: Replica Thread Stopped Resulting in Underreplicated Partitions

[ https://issues.apache.org/jira/browse/KAFKA-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414951#comment-16414951 ] Srinivas Dhruvakumar commented on KAFKA-: - [~huxi_2b] any update on the bu

[jira] [Commented] (KAFKA-6054) ERROR "SubscriptionInfo - unable to decode subscription data: version=2" when upgrading from 0.10.0.0 to 0.10.2.1

[ https://issues.apache.org/jira/browse/KAFKA-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414965#comment-16414965 ] ASF GitHub Bot commented on KAFKA-6054: --- mjsax closed pull request #4761: KAFKA-605

[jira] [Commented] (KAFKA-6054) ERROR "SubscriptionInfo - unable to decode subscription data: version=2" when upgrading from 0.10.0.0 to 0.10.2.1

[ https://issues.apache.org/jira/browse/KAFKA-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414976#comment-16414976 ] ASF GitHub Bot commented on KAFKA-6054: --- mjsax opened a new pull request #4779: KAFK

[jira] [Commented] (KAFKA-6054) ERROR "SubscriptionInfo - unable to decode subscription data: version=2" when upgrading from 0.10.0.0 to 0.10.2.1

[ https://issues.apache.org/jira/browse/KAFKA-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16415012#comment-16415012 ] ASF GitHub Bot commented on KAFKA-6054: --- mjsax closed pull request #4746: KAFKA-6054