Re: [DISCUSS] KIP-135 : Send of null key to a compacted topic should throw non-retriable error back to user

I think, it's OK to do this right now. The other KIP will have a wider base to cover as it will include other exceptions as well and will take time. Thanks, Mayuresh On Mon, Mar 27, 2017 at 11:20 PM Dong Lin wrote: > Sorry, I forget that you have mentioned this idea in your previous reply. I >

Re: [DISCUSS] KIP-135 : Send of null key to a compacted topic should throw non-retriable error back to user

Sorry, I forget that you have mentioned this idea in your previous reply. I guess the question is, do we still need this KIP if we can have custom error message specified in the exception via the other KIP? On Mon, Mar 27, 2017 at 11:00 PM, Mayuresh Gharat < gharatmayures...@gmail.com> wrote: >

Re: [DISCUSS] KIP-135 : Send of null key to a compacted topic should throw non-retriable error back to user

Hi Dong, I do agree with that as I said before the thought did cross my mind and I am working on getting another KIP ready to have error responses returned back to the client. In my opinion, it's OK to add a new error code if it justifies the need. As Ismael, mentioned on the jira, we need a spec

Re: [DISCUSS] KIP-135 : Send of null key to a compacted topic should throw non-retriable error back to user

Hey Mayuresh, I get that you want to provide a more specific error message to user. Then would it be more useful to have a KIP that allows custom error message to be returned to client together with the exception in the response? For example, broker can include in the response PolicyViolationExcep

[jira] [Commented] (KAFKA-4952) ZkUtils get topics by consumer group not correct

[ https://issues.apache.org/jira/browse/KAFKA-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944500#comment-15944500 ] huxi commented on KAFKA-4952: - [~zxylvlp] All subscribed topics' names will be created as a ch

[jira] [Updated] (KAFKA-4961) Mirrormaker crash with org.apache.kafka.common.protocol.types.SchemaException

[ https://issues.apache.org/jira/browse/KAFKA-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Shang updated KAFKA-4961: Description: We are running a cluster of 3 brokers and using mirrormaker to replicate a topic to a differen

[jira] [Updated] (KAFKA-4962) Unify the implentation of schemas in Protocol.java

[ https://issues.apache.org/jira/browse/KAFKA-4962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4962: Description: The schemas implementation in Protocol.java is currently inconsistent. For example, the implem

[jira] [Updated] (KAFKA-4961) Mirrormaker crash with org.apache.kafka.common.protocol.types.SchemaException

[ https://issues.apache.org/jira/browse/KAFKA-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Shang updated KAFKA-4961: Description: We are running a cluster of 3 brokers and using mirrormaker to replicate a topic to a differen

[jira] [Updated] (KAFKA-4962) Unify the implentation of schemas in Protocol.java

[ https://issues.apache.org/jira/browse/KAFKA-4962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4962: Summary: Unify the implentation of schemas in Protocol.java (was: Unify the way of implementing schemas in

[jira] [Updated] (KAFKA-4961) Mirrormaker crash with org.apache.kafka.common.protocol.types.SchemaException

[ https://issues.apache.org/jira/browse/KAFKA-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Shang updated KAFKA-4961: Summary: Mirrormaker crash with org.apache.kafka.common.protocol.types.SchemaException (was: Mirrormaker )

[jira] [Created] (KAFKA-4961) Mirrormaker

Di Shang created KAFKA-4961: --- Summary: Mirrormaker Key: KAFKA-4961 URL: https://issues.apache.org/jira/browse/KAFKA-4961 Project: Kafka Issue Type: Bug Components: consumer Affects V

[jira] [Created] (KAFKA-4962) Unify the way of implementing schemas in Protocol.java

Dong Lin created KAFKA-4962: --- Summary: Unify the way of implementing schemas in Protocol.java Key: KAFKA-4962 URL: https://issues.apache.org/jira/browse/KAFKA-4962 Project: Kafka Issue Type: Improv

Re: [DISCUSS] KIP-135 : Send of null key to a compacted topic should throw non-retriable error back to user

Hi Dong, I had thought about this before and wanted to do similar thing. But as was pointed out in the jira ticket, we wanted something more specific than general. The main issue is that we do not propagate server side error messages to clients, right now. I am working on a KIP proposal to propose

[GitHub] kafka pull request #2747: MINOR: StreamThread should catch InvalidTopicExcep...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2747 MINOR: StreamThread should catch InvalidTopicException We should catch `InvalidTopicException` and not just `NoOffsetForPartitionException`. Also, we need to step through all partitions that might be

[jira] [Commented] (KAFKA-4960) Invalid state store exception

[ https://issues.apache.org/jira/browse/KAFKA-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944329#comment-15944329 ] Matthias J. Sax commented on KAFKA-4960: Thanks for reporting this. Can you give s

Re: [DISCUSS] KIP-135 : Send of null key to a compacted topic should throw non-retriable error back to user

Hey Mayuresh, Thanks for the patch. I am wondering if it would be better to add a more general error, e.g. InvalidMessageException. The benefit is that we can reuse this for other message level error instead of adding one exception class for each possible exception in the future. This is similar t

Re: [VOTE] KIP-81: Bound Fetch memory usage in the consumer

Mickael, Sorry for the late review of the KIP. I'm +1 on the proposed change as well. Just a few minor comments on the wiki itself: 1. By the "MemoryPool" are you referring to a new class impl or to reusing " org.apache.kafka.clients.producer.internals.BufferPool"? I assume it was the latter case

[jira] [Created] (KAFKA-4960) Invalid state store exception

j yeargers created KAFKA-4960: - Summary: Invalid state store exception Key: KAFKA-4960 URL: https://issues.apache.org/jira/browse/KAFKA-4960 Project: Kafka Issue Type: Bug Components: s

Build failed in Jenkins: kafka-trunk-jdk8 #1380

See Changes: [jason] KAFKA-4569; Check for wakeup on every call to KafkaConsumer.poll -- [...truncated 161.78 KB...] kafka.coordinator.GroupCoordinatorResponseTest > test

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

Hi, I would like to trigger this discussion again. It seems that the naming question is rather subjective and both main alternatives (w/ or w/o the word "Topology" in the name) have pros/cons. If you have any further thought, please share it. At the moment I still propose `StreamsBuilder` in the

[jira] [Commented] (KAFKA-4569) Transient failure in org.apache.kafka.clients.consumer.KafkaConsumerTest.testWakeupWithFetchDataAvailable

[ https://issues.apache.org/jira/browse/KAFKA-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944203#comment-15944203 ] ASF GitHub Bot commented on KAFKA-4569: --- Github user asfgit closed the pull request

[GitHub] kafka pull request #2699: KAFKA-4569: Make KafkaConsumer Trigger Wakeup befo...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2699 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Resolved] (KAFKA-4569) Transient failure in org.apache.kafka.clients.consumer.KafkaConsumerTest.testWakeupWithFetchDataAvailable

[ https://issues.apache.org/jira/browse/KAFKA-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-4569. Resolution: Fixed Fix Version/s: (was: 0.10.2.1) Issue resolved by pull request 2

Jenkins build is back to normal : kafka-trunk-jdk7 #2043

See

[jira] [Updated] (KAFKA-4959) remove controller concurrent access to non-threadsafe NetworkClient, Selector, and SSLEngine

[ https://issues.apache.org/jira/browse/KAFKA-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-4959: Status: Patch Available (was: In Progress) > remove controller concurrent access to non-threadsafe

[jira] [Commented] (KAFKA-4959) remove controller concurrent access to non-threadsafe NetworkClient, Selector, and SSLEngine

[ https://issues.apache.org/jira/browse/KAFKA-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944120#comment-15944120 ] ASF GitHub Bot commented on KAFKA-4959: --- GitHub user onurkaraman opened a pull reque

[jira] [Work started] (KAFKA-4959) remove controller concurrent access to non-threadsafe NetworkClient, Selector, and SSLEngine

[ https://issues.apache.org/jira/browse/KAFKA-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4959 started by Onur Karaman. --- > remove controller concurrent access to non-threadsafe NetworkClient, > Selector,

[GitHub] kafka pull request #2746: KAFKA-4959: remove controller concurrent access to...

GitHub user onurkaraman opened a pull request: https://github.com/apache/kafka/pull/2746 KAFKA-4959: remove controller concurrent access to non-threadsafe NetworkClient, Selector, and SSLEngine This brought down a cluster by causing continuous controller moves. ZkClient's Z

Build failed in Jenkins: kafka-trunk-jdk8 #1379

See Changes: [wangguoz] KAFKA-4881: add internal leave.group.on.close config to consumer -- [...truncated 1.28 MB...] org.apache.kafka.clients.producer.internals.RecordAcc

[GitHub] kafka pull request #2745: MINOR: Replication system tests should cover compr...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/2745 MINOR: Replication system tests should cover compressed path You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka add-replication-

Re: [DISCUSS] KIP 130: Expose states of active tasks to KafkaStreams public API

Hi Guozhang, Matthias, It's a great idea to add sub topologies descriptions. This would help developers to better understand topology concept. I agree that is not really user-friendly to check if `StreamsMetadata#streamThreads` is not returning null. The method name localThreadsMetadata looks go

[jira] [Created] (KAFKA-4959) remove controller concurrent access to non-threadsafe NetworkClient, Selector, and SSLEngine

Onur Karaman created KAFKA-4959: --- Summary: remove controller concurrent access to non-threadsafe NetworkClient, Selector, and SSLEngine Key: KAFKA-4959 URL: https://issues.apache.org/jira/browse/KAFKA-4959

[jira] [Comment Edited] (KAFKA-3758) KStream job fails to recover after Kafka broker stopped

[ https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942835#comment-15942835 ] Eno Thereska edited comment on KAFKA-3758 at 3/27/17 9:06 PM: --

[jira] [Updated] (KAFKA-4953) Global Store: cast exception when initialising with in-memory logged state store

[ https://issues.apache.org/jira/browse/KAFKA-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4953: --- Description: Currently it is not possible to initialise a global store with an in-memory *log

Build failed in Jenkins: kafka-trunk-jdk7 #2042

See Changes: [jason] MINOR: Use method handles instead of reflection for creating Snappy and -- [...truncated 899.32 KB...] org.apache.kafka.streams.processor.internals.In

Jenkins build is back to normal : kafka-trunk-jdk8 #1378

See

[jira] [Assigned] (KAFKA-1895) Investigate moving deserialization and decompression out of KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-1895: -- Assignee: Jason Gustafson > Investigate moving deserialization and decompression out of

[jira] [Commented] (KAFKA-4692) Transient test failure in org.apache.kafka.streams.integration.KStreamAggregationDedupIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943852#comment-15943852 ] Guozhang Wang commented on KAFKA-4692: -- Thanks for looking into this [~original-brown

[jira] [Created] (KAFKA-4958) kafka.server.KafkaServerStartable - java.lang.OutOfMemoryError: Java heap space

Karthik created KAFKA-4958: -- Summary: kafka.server.KafkaServerStartable - java.lang.OutOfMemoryError: Java heap space Key: KAFKA-4958 URL: https://issues.apache.org/jira/browse/KAFKA-4958 Project: Kafka

[jira] [Assigned] (KAFKA-4692) Transient test failure in org.apache.kafka.streams.integration.KStreamAggregationDedupIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armin Braun reassigned KAFKA-4692: -- Assignee: Armin Braun > Transient test failure in > org.apache.kafka.streams.integration.KStre

[jira] [Comment Edited] (KAFKA-4692) Transient test failure in org.apache.kafka.streams.integration.KStreamAggregationDedupIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943362#comment-15943362 ] Armin Braun edited comment on KAFKA-4692 at 3/27/17 6:13 PM: -

[jira] [Comment Edited] (KAFKA-4692) Transient test failure in org.apache.kafka.streams.integration.KStreamAggregationDedupIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943362#comment-15943362 ] Armin Braun edited comment on KAFKA-4692 at 3/27/17 6:14 PM: -

[jira] [Resolved] (KAFKA-4881) Add internal leave.group.on.close config to consumer

[ https://issues.apache.org/jira/browse/KAFKA-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4881. -- Resolution: Fixed Issue resolved by pull request 2650 [https://github.com/apache/kafka/pull/2650

[jira] [Commented] (KAFKA-4881) Add internal leave.group.on.close config to consumer

[ https://issues.apache.org/jira/browse/KAFKA-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943689#comment-15943689 ] ASF GitHub Bot commented on KAFKA-4881: --- Github user asfgit closed the pull request

[GitHub] kafka pull request #2650: KAFKA-4881: add internal leave.group.on.close conf...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2650 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

Re: [DISCUSS] KIP-135 : Send of null key to a compacted topic should throw non-retriable error back to user

Hi Mayuresh, The relevant PR was merged last Friday. :) Starting the vote is fine by me. Ismael On Mon, Mar 27, 2017 at 5:49 PM, Mayuresh Gharat wrote: > Hi Ismael, > > Sure we can do that. Just wanted to check on the timeline on when this can > go in. > I can wait till the new ProduceRequest

Re: [DISCUSS] KIP-134: Delay initial consumer group rebalance

Damian, about "rebalance immediately" on timeout -- I guess, that's a different case as no LeaveGroupRequest will be sent. Thus, the broker should be able to distinguish both cases easily, and apply the delay only if it received the LeaveGroupRequest but not if a consumer times out. Does this mak

[jira] [Commented] (KAFKA-4954) Implementation and unit tests for request handler thread utilization quota

[ https://issues.apache.org/jira/browse/KAFKA-4954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943656#comment-15943656 ] ASF GitHub Bot commented on KAFKA-4954: --- GitHub user rajinisivaram opened a pull req

[GitHub] kafka pull request #2744: KAFKA-4954: Request handler utilization quotas

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/2744 KAFKA-4954: Request handler utilization quotas See KIP-124 (https://cwiki.apache.org/confluence/display/KAFKA/KIP-124+-+Request+rate+quotas) for details You can merge this pull request into

[jira] [Commented] (KAFKA-4930) Connect Rest API allows creating connectors with an empty name

[ https://issues.apache.org/jira/browse/KAFKA-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943621#comment-15943621 ] Gwen Shapira commented on KAFKA-4930: - [~sliebau] I like your validName approach. Can

Re: [DISCUSS] KIP-135 : Send of null key to a compacted topic should throw non-retriable error back to user

Hi Ismael, Sure we can do that. Just wanted to check on the timeline on when this can go in. I can wait till the new ProduceRequest gets in to trunk. On the other hand we can also support it in the existing code. I am fine either ways. Should I start Vote on this, so that we can get this approved

[jira] [Created] (KAFKA-4957) Add documentation for request quotas

Rajini Sivaram created KAFKA-4957: - Summary: Add documentation for request quotas Key: KAFKA-4957 URL: https://issues.apache.org/jira/browse/KAFKA-4957 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-4956) Add system tests for request quotas

Rajini Sivaram created KAFKA-4956: - Summary: Add system tests for request quotas Key: KAFKA-4956 URL: https://issues.apache.org/jira/browse/KAFKA-4956 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-4955) Add network handler thread utilization to request quota calculation

Rajini Sivaram created KAFKA-4955: - Summary: Add network handler thread utilization to request quota calculation Key: KAFKA-4955 URL: https://issues.apache.org/jira/browse/KAFKA-4955 Project: Kafka

[GitHub] kafka pull request #2740: MINOR: Use method handles instead of reflection fo...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2740 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Created] (KAFKA-4954) Implementation and unit tests for request handler thread utilization quota

Rajini Sivaram created KAFKA-4954: - Summary: Implementation and unit tests for request handler thread utilization quota Key: KAFKA-4954 URL: https://issues.apache.org/jira/browse/KAFKA-4954 Project: K

[jira] [Commented] (KAFKA-4900) Brokers stuck in controller re-election loop after failing to register metrics

[ https://issues.apache.org/jira/browse/KAFKA-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943568#comment-15943568 ] Onur Karaman commented on KAFKA-4900: - [~nickt] Do you think it makes sense for me to

[GitHub] kafka pull request #2743: KIP-101: Alter Replication Protocol to use Leader ...

GitHub user benstopford opened a pull request: https://github.com/apache/kafka/pull/2743 KIP-101: Alter Replication Protocol to use Leader Epoch rather than High Watermark for Truncation This PR describes the addition of Partition Level Leader Epochs to messages in Kafka as a mecha

LDAP with Kafka?

Hello everyone. I'm a bit confused on LDAP auth status. Documentation says "AFAICT there is no SASL mechanism covering LDAP (and the Java SASL library doesn't support it, at any rate". The Java library linked documentation though, seems to indicate the opposite. Can anyone clarify this please?

[jira] [Commented] (KAFKA-4928) Add integration test for DumpLogSegments

[ https://issues.apache.org/jira/browse/KAFKA-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943433#comment-15943433 ] Armin Braun commented on KAFKA-4928: Trying this one :) > Add integration test for Du

[jira] [Assigned] (KAFKA-4928) Add integration test for DumpLogSegments

[ https://issues.apache.org/jira/browse/KAFKA-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armin Braun reassigned KAFKA-4928: -- Assignee: Armin Braun > Add integration test for DumpLogSegments >

[jira] [Commented] (KAFKA-2045) Memory Management on the consumer

[ https://issues.apache.org/jira/browse/KAFKA-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943370#comment-15943370 ] Armin Braun commented on KAFKA-2045: [~guozhang] maybe it would be a good step to add

[jira] [Assigned] (KAFKA-4692) Transient test failure in org.apache.kafka.streams.integration.KStreamAggregationDedupIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armin Braun reassigned KAFKA-4692: -- Assignee: (was: Armin Braun) > Transient test failure in > org.apache.kafka.streams.integr

[jira] [Commented] (KAFKA-4692) Transient test failure in org.apache.kafka.streams.integration.KStreamAggregationDedupIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943362#comment-15943362 ] Armin Braun commented on KAFKA-4692: [~guozhang] actually nevermind, I don't see this

[jira] [Comment Edited] (KAFKA-4790) Kafka cannot recover after a disk full

[ https://issues.apache.org/jira/browse/KAFKA-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943344#comment-15943344 ] Ismael Juma edited comment on KAFKA-4790 at 3/27/17 2:21 PM: -

[jira] [Resolved] (KAFKA-4790) Kafka cannot recover after a disk full

[ https://issues.apache.org/jira/browse/KAFKA-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4790. Resolution: Fixed Marking as resolved since the message format changes for KIP-98 were merged. Note

[jira] [Commented] (KAFKA-4574) Transient failure in ZooKeeperSecurityUpgradeTest.test_zk_security_upgrade with security_protocol = SASL_PLAINTEXT, SSL

[ https://issues.apache.org/jira/browse/KAFKA-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943207#comment-15943207 ] ASF GitHub Bot commented on KAFKA-4574: --- GitHub user ijuma opened a pull request:

[GitHub] kafka pull request #2742: KAFKA-4574: Ignore test_zk_security_upgrade until ...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2742 KAFKA-4574: Ignore test_zk_security_upgrade until KIP-101 lands The transient failures make it harder to spot real failures and we can live without what is being tested (adding security to ZK via a ro

[jira] [Commented] (KAFKA-4953) Global Store: cast exception when initialising with in-memory logged state store

[ https://issues.apache.org/jira/browse/KAFKA-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943030#comment-15943030 ] ASF GitHub Bot commented on KAFKA-4953: --- GitHub user SlevinBE opened a pull request:

[GitHub] kafka pull request #2741: KAFKA-4953: Global Store: cast exception when init...

GitHub user SlevinBE opened a pull request: https://github.com/apache/kafka/pull/2741 KAFKA-4953: Global Store: cast exception when initialising with in-memory logged state store Currently it is not possible to initialise a global store with an in-memory logged store via the Topolo

[jira] [Updated] (KAFKA-4953) Global Store: cast exception when initialising with in-memory logged state store

[ https://issues.apache.org/jira/browse/KAFKA-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yennick Trevels updated KAFKA-4953: --- Description: Currently it is not possible to initialise a global store with an in-memory *log

[jira] [Created] (KAFKA-4953) Global Store: cast exception when initialising with in-memory logged state store

Yennick Trevels created KAFKA-4953: -- Summary: Global Store: cast exception when initialising with in-memory logged state store Key: KAFKA-4953 URL: https://issues.apache.org/jira/browse/KAFKA-4953 Pr

[jira] [Commented] (KAFKA-2448) BrokerChangeListener missed broker id path ephemeral node deletion event.

[ https://issues.apache.org/jira/browse/KAFKA-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942998#comment-15942998 ] fatkun commented on KAFKA-2448: --- [~junrao] How to fix this issue? Our cluster also have thi

RE: Kafka queue full configuration

Can you please let me know what is the new parameter name for the same functionality to simulate the queue full scenario? Regards, Sudhir From: Mohapatra, Sudhir (Nokia - IN/Gurgaon) Sent: Thursday, March 23, 2017 11:01 AM To: 'us...@kafka.apache.org' ; 'dev@kafka.apache.org' Subject: Kafka qu

[jira] [Commented] (KAFKA-4952) ZkUtils get topics by consumer group not correct

[ https://issues.apache.org/jira/browse/KAFKA-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942918#comment-15942918 ] ZhaoXingyu commented on KAFKA-4952: --- In some case, owners may not be set. But in offsets

[jira] [Updated] (KAFKA-4952) ZkUtils get topics by consumer group not correct

[ https://issues.apache.org/jira/browse/KAFKA-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhaoXingyu updated KAFKA-4952: -- Description: ZkUtils.getTopicsByConsumerGroup should get topics by consumergroup offsets dir, but the co

[jira] [Created] (KAFKA-4952) ZkUtils get topics by consumer group not correct

ZhaoXingyu created KAFKA-4952: - Summary: ZkUtils get topics by consumer group not correct Key: KAFKA-4952 URL: https://issues.apache.org/jira/browse/KAFKA-4952 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-4926) Getting Build Failure for task ':clients:checkstyleMain'

[ https://issues.apache.org/jira/browse/KAFKA-4926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942897#comment-15942897 ] sonali shrivastava commented on KAFKA-4926: --- Hi Team, Can you please update on

Re: [DISCUSS] KIP-134: Delay initial consumer group rebalance

@Becket Thanks for the feedback. Yes, i like the idea of extending the delay as each new consumer joins the group. Though, i think this could be done with either a consumer or broker side config. But i get your point that some consumers in the group can be misconfigured. @Matthias & @Eno - yes we

[jira] [Reopened] (KAFKA-3758) KStream job fails to recover after Kafka broker stopped

[ https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reopened KAFKA-3758: - > KStream job fails to recover after Kafka broker stopped > --

[jira] [Comment Edited] (KAFKA-3758) KStream job fails to recover after Kafka broker stopped

[ https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942835#comment-15942835 ] Eno Thereska edited comment on KAFKA-3758 at 3/27/17 8:33 AM: --

[jira] [Commented] (KAFKA-3758) KStream job fails to recover after Kafka broker stopped

[ https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942835#comment-15942835 ] Eno Thereska commented on KAFKA-3758: - [~guozhang] reopening since I'm seeing this aga

[jira] [Commented] (KAFKA-4396) Seeing offsets not resetting even when reset policy is configured explicitly

[ https://issues.apache.org/jira/browse/KAFKA-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942803#comment-15942803 ] Daniel Lanza García commented on KAFKA-4396: It is more a Spark issue since is

[jira] [Commented] (KAFKA-4396) Seeing offsets not resetting even when reset policy is configured explicitly

[ https://issues.apache.org/jira/browse/KAFKA-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942796#comment-15942796 ] Basile Deustua commented on KAFKA-4396: --- Same for me too with Spark 2.0.2 or Spark 2

[jira] [Commented] (KAFKA-4938) Creating a connector with missing name parameter throws a NullPointerException

[ https://issues.apache.org/jira/browse/KAFKA-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942770#comment-15942770 ] Balint Molnar commented on KAFKA-4938: -- [~sliebau]: Sure, I have put just a little ef