Re: Kafka Multiple Consumer Group for Same Topic

Thanks Sharninder! Adding dev group to know if they done some benchmarking test on Single Consumer Group Vs Multiple Consumer Grp on Same Topic. Cheers, Senthil On Jan 24, 2017 10:48 PM, "Sharninder Khera" wrote: I don't have benchmarks but multiple consumer groups are possible. For Kafka th

[jira] [Commented] (KAFKA-4541) Add capability to create delegation token

[ https://issues.apache.org/jira/browse/KAFKA-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837319#comment-15837319 ] Manikumar Reddy commented on KAFKA-4541: [~singhashish] Can you post your WIP PR?

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837245#comment-15837245 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipien

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837242#comment-15837242 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipien

[jira] [Commented] (KAFKA-4666) Failure test for Kafka configured for consistency vs availability

[ https://issues.apache.org/jira/browse/KAFKA-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837218#comment-15837218 ] Ewen Cheslack-Postava commented on KAFKA-4666: -- [~ecesena] Absolutely -- if y

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

See Changes: [wangguoz] HOTIFX: streams system test do not start up correctly -- [...truncated 4114 lines...] kafka.integration.SaslPlaintextTopicMetadataTest > testIsrAfterBrokerShutDownAndJo

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

See Changes: [me] MINOR: Update consumer group describe output in the documentation [wangguoz] KAFKA-3835; Streams is creating two ProducerRecords for each send via -- [...truncated 8408 lines.

[GitHub] kafka pull request #2428: HOTIFX: streams system test do not start up correc...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2428 --- 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] [Updated] (KAFKA-4461) When using ProcessorTopologyTestDriver, the combination of map and .groupByKey does not produce any result

[ https://issues.apache.org/jira/browse/KAFKA-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4461: - Priority: Major (was: Blocker) > When using ProcessorTopologyTestDriver, the combination of map a

[jira] [Updated] (KAFKA-4461) When using ProcessorTopologyTestDriver, the combination of map and .groupByKey does not produce any result

[ https://issues.apache.org/jira/browse/KAFKA-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4461: - Labels: newbie unit-test (was: newbie) > When using ProcessorTopologyTestDriver, the combination

[jira] [Updated] (KAFKA-4408) KTable doesn't work with ProcessorTopologyTestDriver in Kafka 0.10.1.0

[ https://issues.apache.org/jira/browse/KAFKA-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4408: - Labels: newbie unit-test (was: ) > KTable doesn't work with ProcessorTopologyTestDriver in Kafka

Stream processing meetup at LinkedIn (Sunnyvale) on Thursday, February 16 at 6pm

Hi everyone, We would like to invite you to a Stream Processing Meetup at LinkedIn’s Sunnyvale campus on Thursday, February 16 at 6pm. Please RSVP here (*only if you intend to attend in person*): https://www.meetup.com/Stream-Processing-Meetup-LinkedIn/events/237171557/

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837020#comment-15837020 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipien

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837019#comment-15837019 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipien

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

See Changes: [junrao] trivial change to clarify comments in KAFKA-4229 [wangguoz] MINOR: close state store in CachingSessionStoreTest -- [...truncated 15851 lines...] org.apache.kafka.common.se

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836969#comment-15836969 ] Ewen Cheslack-Postava commented on KAFKA-4477: -- [~ctrochalakis] You should se

[GitHub] kafka-site pull request #42: fix typos on powered by page

Github user asfgit closed the pull request at: https://github.com/apache/kafka-site/pull/42 --- 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 e

[GitHub] kafka-site issue #42: fix typos on powered by page

Github user ewencp commented on the issue: https://github.com/apache/kafka-site/pull/42 LGTM --- 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 feat

[jira] [Deleted] (KAFKA-4624) Streams smoke tests fails when there is only 1 broker

[ https://issues.apache.org/jira/browse/KAFKA-4624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava deleted KAFKA-4624: - > Streams smoke tests fails when there is only 1 broker > ---

[jira] [Created] (KAFKA-4694) Streams smoke tests fails when there is only 1 broker

Ewen Cheslack-Postava created KAFKA-4694: Summary: Streams smoke tests fails when there is only 1 broker Key: KAFKA-4694 URL: https://issues.apache.org/jira/browse/KAFKA-4694 Project: Kafka

[jira] [Deleted] (KAFKA-4625) Streams smoke tests fails when there is only 1 broker

[ https://issues.apache.org/jira/browse/KAFKA-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava deleted KAFKA-4625: - > Streams smoke tests fails when there is only 1 broker > ---

[jira] [Updated] (KAFKA-4613) Treat null-key records the same way for joins and aggreations

[ https://issues.apache.org/jira/browse/KAFKA-4613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4613: - Description: Currently, on aggregation records with null-key get dropped while for joins we raise

Build failed in Jenkins: kafka-0.10.1-jdk7 #113

See Changes: [jason] KAFKA-4547; Avoid unnecessary offset commit that could lead to an -- [...truncated 4338 lines...] kafka.integration.SaslPlaintextTopicMetadataTest > testGetAllTopicMetadata

[GitHub] kafka pull request #2417: KAFKA-3835: Streams is creating two ProducerRecord...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2417 --- 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] [Commented] (KAFKA-3835) Streams is creating two ProducerRecords for each send via RecordCollector

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

[jira] [Resolved] (KAFKA-3835) Streams is creating two ProducerRecords for each send via RecordCollector

[ https://issues.apache.org/jira/browse/KAFKA-3835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3835. -- Resolution: Fixed Fix Version/s: 0.10.2.0 Issue resolved by pull request 2417 [https://gi

[GitHub] kafka pull request #2409: MINOR: Update consumer group describe output in th...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2409 --- 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] [Commented] (KAFKA-3502) Build is killed during kafka streams tests due to `pure virtual method called` error

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

[GitHub] kafka pull request #2432: KAFKA-3502: KStreamTestDriver needs to be closed a...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/2432 KAFKA-3502: KStreamTestDriver needs to be closed after the test case Found a few recently added unit tests did not close KStreamTestDriver after the test itself is closed; this can cause RocksD

[jira] [Commented] (KAFKA-4625) Streams smoke tests fails when there is only 1 broker

[ https://issues.apache.org/jira/browse/KAFKA-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836877#comment-15836877 ] Matthias J. Sax commented on KAFKA-4625: Good idea. > Streams smoke tests fails w

[jira] [Commented] (KAFKA-4666) Failure test for Kafka configured for consistency vs availability

[ https://issues.apache.org/jira/browse/KAFKA-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836828#comment-15836828 ] Emanuele Cesena commented on KAFKA-4666: Yes, you're correct, there's nothing unex

[jira] [Commented] (KAFKA-4625) Streams smoke tests fails when there is only 1 broker

[ https://issues.apache.org/jira/browse/KAFKA-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836830#comment-15836830 ] Ewen Cheslack-Postava commented on KAFKA-4625: -- [~mjsax] [~enothereska] Somet

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

See Changes: [wangguoz] KAFKA-3896: Fix KStreamRepartitionJoinTest [ismael] KAFKA-4548; Add ClientCompatibilityTest to verify features against older [ismael] KAFKA-4687; Fix InvalidTopicException due to topic creation race [me] KAF

[jira] [Commented] (KAFKA-4667) Connect (and Stream?) should create internal topics with availability or consistency properly set

[ https://issues.apache.org/jira/browse/KAFKA-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836817#comment-15836817 ] Emanuele Cesena commented on KAFKA-4667: I see - I think I was confused because we

[jira] [Updated] (KAFKA-4636) Per listener security setting overrides (KIP-103)

[ https://issues.apache.org/jira/browse/KAFKA-4636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4636: --- Fix Version/s: (was: 0.10.2.0) 0.10.3.0 > Per listener security setting overrid

[GitHub] kafka-site pull request #40: Add Grant to committers page

Github user asfgit closed the pull request at: https://github.com/apache/kafka-site/pull/40 --- 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 e

[GitHub] kafka-site issue #40: Add Grant to committers page

Github user ewencp commented on the issue: https://github.com/apache/kafka-site/pull/40 LGTM, sorry for the delay in getting this merged. And congrats! --- 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

[GitHub] kafka pull request #2430: MINOR: close state store in CachingSessionStoreTes...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2430 --- 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-112: Handle disk failure for JBOD

Thanks for the detailed explanations Dong. That makes sense to me. Guozhang On Sun, Jan 22, 2017 at 4:00 PM, Dong Lin wrote: > Hey Guozhang, > > Thanks for the review! Yes we have considered this approach and briefly > explained why we don't do it in the rejected alternative section. Here is >

Re: [DISCUSS] KIP-111 : Kafka should preserve the Principal generated by the PrincipalBuilder while processing the request received on socket channel, on the broker.

Hey Mayuresh, Thanks for the KIP. I actually like the suggestions by Ismael and Jun. Here are my comments: 1. I am not sure we need to add the method buildPrincipal(Map principalConfigs). It seems that user can simply do principalBuilder.configure(...).buildPrincipal(...) without using that metho

[jira] [Commented] (KAFKA-4517) Remove kafka-consumer-offset-checker.sh script since already deprecated in Kafka 9

[ https://issues.apache.org/jira/browse/KAFKA-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836818#comment-15836818 ] Jeff Widman commented on KAFKA-4517: So what are the next actions here since I've got

[jira] [Resolved] (KAFKA-2307) Drop ConsumerOffsetChecker completely

[ https://issues.apache.org/jira/browse/KAFKA-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-2307. -- Resolution: Duplicate Fix Version/s: (was: 0.11.0.0) > Drop ConsumerO

Re: Okay to remove the deprecated kafka-consumer-offset-checker.sh?

This was a duplicate and was already in the plan for 0.11.0.0. see https://issues.apache.org/jira/browse/KAFKA-2307 and https://issues.apache.org/jira/browse/KAFKA-3356 -Ewen On Tue, Jan 17, 2017 at 3:39 PM, Gwen Shapira wrote: > +1 > I also got confused when looking for the right tool. > > On

[jira] [Commented] (KAFKA-2307) Drop ConsumerOffsetChecker completely

[ https://issues.apache.org/jira/browse/KAFKA-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836813#comment-15836813 ] Ewen Cheslack-Postava commented on KAFKA-2307: -- This one is actually older, b

[jira] [Resolved] (KAFKA-4517) Remove kafka-consumer-offset-checker.sh script since already deprecated in Kafka 9

[ https://issues.apache.org/jira/browse/KAFKA-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-4517. -- Resolution: Duplicate Assignee: Ewen Cheslack-Postava Fix Version

[jira] [Commented] (KAFKA-4517) Remove kafka-consumer-offset-checker.sh script since already deprecated in Kafka 9

[ https://issues.apache.org/jira/browse/KAFKA-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836809#comment-15836809 ] Ewen Cheslack-Postava commented on KAFKA-4517: -- Duplicate of KAFKA-3356 (and

[jira] [Updated] (KAFKA-3356) Remove ConsumerOffsetChecker, deprecated in 0.9, in 0.11

[ https://issues.apache.org/jira/browse/KAFKA-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3356: - Priority: Blocker (was: Major) > Remove ConsumerOffsetChecker, deprecated in 0.9,

[jira] [Commented] (KAFKA-4667) Connect (and Stream?) should create internal topics with availability or consistency properly set

[ https://issues.apache.org/jira/browse/KAFKA-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836801#comment-15836801 ] Ewen Cheslack-Postava commented on KAFKA-4667: -- [~ecesena] Not sure I underst

[jira] [Updated] (KAFKA-4667) Connect (and Stream?) should create internal topics with availability or consistency properly set

[ https://issues.apache.org/jira/browse/KAFKA-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4667: - Component/s: KafkaConnect > Connect (and Stream?) should create internal topics wi

[jira] [Commented] (KAFKA-4666) Failure test for Kafka configured for consistency vs availability

[ https://issues.apache.org/jira/browse/KAFKA-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836790#comment-15836790 ] Ewen Cheslack-Postava commented on KAFKA-4666: -- [~ecesena] ducktape test to v

[jira] [Commented] (KAFKA-4144) Allow per stream/table timestamp extractor

[ https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836739#comment-15836739 ] Elias Levy commented on KAFKA-4144: --- What Matthias said. The issue has nothing to do wi

[jira] [Commented] (KAFKA-4557) ConcurrentModificationException in KafkaProducer event loop

[ https://issues.apache.org/jira/browse/KAFKA-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836738#comment-15836738 ] Ewen Cheslack-Postava commented on KAFKA-4557: -- [~salaev] Can you give an ide

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

See Changes: [wangguoz] MINOR: rework JavaDoc for windowing related public API -- [...truncated 33096 lines...] kafka.security.auth.SimpleAclAuthorizerTest > testLoadCache PASSED kafka.integrat

[jira] [Commented] (KAFKA-4401) Change the KafkaServerTestHarness and IntegrationTestHarness from trait to abstract class.

[ https://issues.apache.org/jira/browse/KAFKA-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836729#comment-15836729 ] Ewen Cheslack-Postava commented on KAFKA-4401: -- [~becket_qin] I would actuall

[jira] [Updated] (KAFKA-4229) Controller can't start after several zk expired event

[ https://issues.apache.org/jira/browse/KAFKA-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-4229: --- Resolution: Fixed Fix Version/s: 0.10.2.0 Status: Resolved (was: Patch Available) Issue res

[jira] [Commented] (KAFKA-4229) Controller can't start after several zk expired event

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

[GitHub] kafka pull request #2175: KAFKA-4229:Controller can't start after several zk...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2175 --- 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: [VOTE] KIP-107 Add purgeDataBefore() API in AdminClient

Hi, Dong, The changes sound good to me. Also, thanks for the explanation of returning a future from purgeDataFrom(). We can keep it that way. Thanks, Jun On Mon, Jan 23, 2017 at 4:24 PM, Dong Lin wrote: > Hi all, > > When I am implementing the patch, I realized that the current usage of > "lo

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836678#comment-15836678 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipien

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836677#comment-15836677 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipien

[jira] [Updated] (KAFKA-4693) Consumer subscription change during rebalance causes exception

[ https://issues.apache.org/jira/browse/KAFKA-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-4693: --- Component/s: consumer > Consumer subscription change during rebalance causes exception > -

[jira] [Resolved] (KAFKA-4673) Python VerifiableConsumer service has thread-safety bug for event_handlers

[ https://issues.apache.org/jira/browse/KAFKA-4673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-4673. -- Resolution: Fixed Fix Version/s: 0.10.2.0 0.10.1.2

[jira] [Commented] (KAFKA-4673) Python VerifiableConsumer service has thread-safety bug for event_handlers

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

[GitHub] kafka pull request #2427: KAFKA-4673: Fix thread-safety of Python Verifiable...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2427 --- 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-4693) Consumer subscription change during rebalance causes exception

Jason Gustafson created KAFKA-4693: -- Summary: Consumer subscription change during rebalance causes exception Key: KAFKA-4693 URL: https://issues.apache.org/jira/browse/KAFKA-4693 Project: Kafka

[jira] [Commented] (KAFKA-4144) Allow per stream/table timestamp extractor

[ https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836638#comment-15836638 ] Matthias J. Sax commented on KAFKA-4144: [~jeyhunkarimov] I don't understand this:

[jira] [Comment Edited] (KAFKA-4144) Allow per stream/table timestamp extractor

[ https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836328#comment-15836328 ] Jeyhun Karimov edited comment on KAFKA-4144 at 1/24/17 8:58 PM:

Trying to understand design decision about producer ack and min.insync.replicas

Hi everybody I am trying to understand why Kafka let each individual producer, on a connection per connection basis, choose the tradeoff between availability and durability, honoring min.insync.replicas value only if producer uses ack=all. I mean, for a single topic, cluster administrators can't

[jira] [Commented] (KAFKA-4547) Consumer.position returns incorrect results for Kafka 0.10.1.0 client

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

[GitHub] kafka pull request #2431: KAFKA-4547 (0.10.1 hotfix): Avoid unnecessary offs...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/2431 KAFKA-4547 (0.10.1 hotfix): Avoid unnecessary offset commit that could lead to an invalid offset position if partition is paused You can merge this pull request into a Git repository by run

[jira] [Updated] (KAFKA-4687) InvalidTopicException is possible for topic colliding with itself when concurrently created

[ https://issues.apache.org/jira/browse/KAFKA-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4687: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 2425

[jira] [Commented] (KAFKA-4687) InvalidTopicException is possible for topic colliding with itself when concurrently created

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

[GitHub] kafka pull request #2425: KAFKA-4687: Fix InvalidTopicException due to topic...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2425 --- 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] [Commented] (KAFKA-4548) Add CompatibilityTest to verify that individual features are supported or not by the broker we're connecting to

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

[jira] [Updated] (KAFKA-4548) Add CompatibilityTest to verify that individual features are supported or not by the broker we're connecting to

[ https://issues.apache.org/jira/browse/KAFKA-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4548: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 2262

[GitHub] kafka pull request #2262: KAFKA-4548: Add CompatibilityTest to verify that i...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2262 --- 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-3896) Unstable test KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations

[ https://issues.apache.org/jira/browse/KAFKA-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3896. -- Resolution: Fixed Fix Version/s: (was: 0.10.1.0) 0.10.2.0

[jira] [Commented] (KAFKA-3894) LogCleaner thread crashes if not even one segment can fit in the offset map

[ https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836543#comment-15836543 ] Vincent Rischmann commented on KAFKA-3894: -- No not all logs, just the 000

[jira] [Commented] (KAFKA-3896) Unstable test KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations

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

[GitHub] kafka pull request #2405: KAFKA-3896: Fix KStreamRepartitionJoinTest

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2405 --- 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] [Commented] (KAFKA-3894) LogCleaner thread crashes if not even one segment can fit in the offset map

[ https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836524#comment-15836524 ] William Yu commented on KAFKA-3894: --- [~m...@vrischmann.me] Thanks for the quick reply. D

[jira] [Commented] (KAFKA-3894) LogCleaner thread crashes if not even one segment can fit in the offset map

[ https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836495#comment-15836495 ] Vincent Rischmann commented on KAFKA-3894: -- I had the exact same bug, didn't real

Re: [DISCUSS] KIP-114: KTable materialization and improved semantics

That not what I meant by "huge impact". I refer to the actions related to materialize a KTable: creating a RocksDB store and a changelog topic -- users should be aware about runtime implication and this is better expressed by an explicit method call, rather than implicitly triggered by using a dif

Re: [DISCUSS] KIP-84: Support SASL/SCRAM mechanisms

Thanks, Ismael. Just curious, why does it not make sense to do bcrypt it in the context of SCRAM? On Mon, Jan 23, 2017 at 3:54 PM, Ismael Juma wrote: > Hi Roger, > > SCRAM uses the PBKDF2 mechanism, here's a comparison between PBKDF2 and > bcrypt: > > http://security.stackexchange.com/questions

[jira] [Commented] (KAFKA-3894) LogCleaner thread crashes if not even one segment can fit in the offset map

[ https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836473#comment-15836473 ] William Yu commented on KAFKA-3894: --- I know this bug is resolved, but we just encountere

Re: [DISCUSS] KIP-113: Support replicas movement between log directories

Hey Alexey, Thanks. I think we agreed that the suggested solution doesn't work in general for kafka users. To answer your questions: 1. I agree we need quota to rate limit replica movement when a broker is moving a "leader" replica. I will come up with solution, probably re-use the config of repl

[GitHub] kafka pull request #2337: MINOR: rework JavaDoc for windowing related public...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2337 --- 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] [Updated] (KAFKA-4691) ProducerInterceptor.onSend() is called after key and value are serialized

[ https://issues.apache.org/jira/browse/KAFKA-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Lemma updated KAFKA-4691: --- Reviewer: Anna Povzner > ProducerInterceptor.onSend() is called after key and value are serial

[GitHub] kafka pull request #2430: MINOR: close state store in CachingSessionStoreTes...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2430 MINOR: close state store in CachingSessionStoreTest close the sessions store in `@After` to release rocksdb resources. You can merge this pull request into a Git repository by running: $ git pull

Re: [VOTE] KIP-48 Support for delegation tokens as an authentication mechanism

Hi Jun, Thanks for the review. Sorry for the delayed response. Please see the replies inline. > 101. DelegationTokenRequest/DelegationTokenResponse > 101.1 I am wondering if renewer should be principalType + name to match > what we have in kafka-acls tool? > Yes, renewer should be principalType

[GitHub] kafka pull request #2429: KAFKA-4677: Avoid unnecessary task movement across...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2429 KAFKA-4677: Avoid unnecessary task movement across threads during rebalance Makes task assignment more sticky by preferring to assign tasks to clients that had previously had the task as active task. I

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

See

[DISCUSS]- JIRA ISSUE KAFKA-4566 : Can't Symlink to Kafka bins

Hi, The bug deals with the problem one encounters in case if the script 'kafka-console-consumer.sh' is executed through a symlink which could be placed on a different location on disk The initial suggestion provided in the bug was to make changes in the below line exec $(dirname $0)/kafka-run-c

Jenkins build is back to normal : kafka-0.10.2-jdk7 #26

See

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

See

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

See Changes: [ismael] KAFKA-4576; Log segments close to max size break on fetch -- [...truncated 28698 lines...] org.apache.kafka.common.security.scram.ScramCredentialUtilsTest > generateCreden

[GitHub] kafka pull request #918: Add expected Error Codes to ProduceResponse documen...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/918 --- 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 enabl

Re: [DISCUSS] KIP-113: Support replicas movement between log directories

23.01.2017, 22:11, "Dong Lin" : > Thanks. Please see my comment inline. > > On Mon, Jan 23, 2017 at 6:45 AM, Alexey Ozeritsky > wrote: > >>  13.01.2017, 22:29, "Dong Lin" : >>  > Hey Alexey, >>  > >>  > Thanks for your review and the alternative approach. Here is my >>  > understanding of your p

[GitHub] kafka pull request #2424: KAFKA-4688: The Docker image should contain versio...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2424 --- 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

[GitHub] kafka pull request #2304: kafka-4576: Log segments close to max size break o...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2304 --- 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

  1   2   >