Ewen Cheslack-Postava created KAFKA-2486:
Summary: New consumer performance
Key: KAFKA-2486
URL: https://issues.apache.org/jira/browse/KAFKA-2486
Project: Kafka
Issue Type: Sub-task
Tried bisecting, but turns out things were broken for some time. We really
need some system tests in place to avoid letting even new code break for so
long.
At 49026f11781181c38e9d5edb634be9d27245c961 (May 14th), we went from good
performance - an error due to broker apparently not accepting the
I think we think this proposal addresses 100% of the split brain issues
ever seen in the ZK-based protocol, but I think you think there are still
issues. Can you explain what your thinking of and when you think it would
happen? I want to make sure you aren't assuming client-side=split-brain
Thanks for re-reviewing Joel.
On Fri, Aug 28, 2015 at 2:51 AM -0700, Joel Koshy jjkosh...@gmail.com wrote:
I think we think this proposal addresses 100% of the split brain issues
ever seen in the ZK-based protocol, but I think you think there are still
issues. Can you explain
So I’ve been looking at the SSL performance (which potentially also has an
issue unrelated to this). I’d noticed strange behaviour with poll() on the new
consumer but I wasn’t sure whether this was a bug or a feature. On closer
inspection it seems to arise from ConsumerPerformance relying on a
[
https://issues.apache.org/jira/browse/KAFKA-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14719974#comment-14719974
]
Ben Stopford commented on KAFKA-2486:
-
Switching to:
while(records.isEmpty)
Hi,
I am working on some project which is using Kafka heavilly. Becasue of
the latest API changes, I am forced to use 0.8.3-SNAPSHOT version and
I am releasing this project on my own to my private Maven repository.
I need to make that project public / official and I can not depend on
a SNAPSHOT
[
https://issues.apache.org/jira/browse/KAFKA-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14719295#comment-14719295
]
Ben Stopford commented on KAFKA-2486:
-
The mail thread refers to the user of
Response I got recently
http://mail-archives.apache.org/mod_mbox/kafka-users/201508.mbox/%3cCAFc58G8pvjH_8A0=41dzj5xpe80j+m_skpzadxnog9qxzf1...@mail.gmail.com%3e
On Fri, Aug 28, 2015, 16:46 Stefan Miklosovic mikloso...@gmail.com wrote:
Hi,
I am working on some project which is using Kafka
[
https://issues.apache.org/jira/browse/KAFKA-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14719979#comment-14719979
]
Jay Kreps commented on KAFKA-2486:
--
Hmm, I think it should be
{code}
Recently there was a discussion that 0.8.2.2 will be released soon to
fix the critical issue with compression. Is that still the plan or has
that been shelved?
-Jaikiran
[
https://issues.apache.org/jira/browse/KAFKA-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14720050#comment-14720050
]
Jay Kreps commented on KAFKA-2486:
--
[~guozhang] these are long-poll fetches so if there
[
https://issues.apache.org/jira/browse/KAFKA-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14719963#comment-14719963
]
Jay Kreps commented on KAFKA-2486:
--
Wait, we sleep? That is totally messed up, you can't
[
https://issues.apache.org/jira/browse/KAFKA-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14720040#comment-14720040
]
Guozhang Wang commented on KAFKA-2486:
--
The sleep is introduced in
[
https://issues.apache.org/jira/browse/KAFKA-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14720110#comment-14720110
]
Guozhang Wang commented on KAFKA-2486:
--
OK, there are a few mixed expressions in my
[
https://issues.apache.org/jira/browse/KAFKA-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14720237#comment-14720237
]
Jay Kreps commented on KAFKA-2486:
--
[~guozhang] I interpret you to be saying that even if
[
https://issues.apache.org/jira/browse/KAFKA-2447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14720264#comment-14720264
]
ASF GitHub Bot commented on KAFKA-2447:
---
GitHub user SinghAsDev opened a pull
[
https://issues.apache.org/jira/browse/KAFKA-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh reassigned KAFKA-2487:
-
Assignee: Ashish K Singh
change kafka.examples.Consumer to use the new java consumer
GitHub user SinghAsDev opened a pull request:
https://github.com/apache/kafka/pull/175
KAFKA-2447: Add capability to KafkaLog4jAppender to be able to use SSL
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SinghAsDev/kafka
Jun Rao created KAFKA-2487:
--
Summary: change kafka.examples.Consumer to use the new java
consumer
Key: KAFKA-2487
URL: https://issues.apache.org/jira/browse/KAFKA-2487
Project: Kafka
Issue Type:
[
https://issues.apache.org/jira/browse/KAFKA-2447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-2447:
--
Status: Patch Available (was: Open)
Add capability to KafkaLog4jAppender to be able to use
[
https://issues.apache.org/jira/browse/KAFKA-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14720307#comment-14720307
]
Ashish K Singh commented on KAFKA-2470:
---
I do not think that is an issue as it only
[
https://issues.apache.org/jira/browse/KAFKA-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geoff Anderson reassigned KAFKA-2488:
-
Assignee: Geoff Anderson
System tests: updated console_consumer.py to support new
Geoff Anderson created KAFKA-2488:
-
Summary: System tests: updated console_consumer.py to support new
consumer
Key: KAFKA-2488
URL: https://issues.apache.org/jira/browse/KAFKA-2488
Project: Kafka
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/173
---
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
[
https://issues.apache.org/jira/browse/KAFKA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14720419#comment-14720419
]
Jun Rao commented on KAFKA-2477:
[~hakon], the leader changes will be logged in the
Geoff Anderson created KAFKA-2489:
-
Summary: System tests: update benchmark tests to run with new and
old consumer
Key: KAFKA-2489
URL: https://issues.apache.org/jira/browse/KAFKA-2489
Project: Kafka
GitHub user ijuma reopened a pull request:
https://github.com/apache/kafka/pull/151
KAFKA-2411; remove usage of blocking channel
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ijuma/kafka
[
https://issues.apache.org/jira/browse/KAFKA-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14720799#comment-14720799
]
ASF GitHub Bot commented on KAFKA-2411:
---
GitHub user ijuma reopened a pull request:
[
https://issues.apache.org/jira/browse/KAFKA-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-2411:
---
Status: Patch Available (was: In Progress)
I've updated the PR to use `NetworkClient` instead of
[
https://issues.apache.org/jira/browse/KAFKA-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14720510#comment-14720510
]
ASF GitHub Bot commented on KAFKA-2332:
---
GitHub user lindong28 opened a pull
Another use-case I was thinking of was something like rack-aware
assignment of partitions to clients. This would require some
additional topic metadata to be propagated to and from the coordinator
and you would need some way to resolve conflicts for such strategies.
I think that could be addressed
GitHub user lindong28 opened a pull request:
https://github.com/apache/kafka/pull/176
KAFKA-2332; Add quota metrics to old producer and consumer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lindong28/kafka KAFKA-2332
Yeah I think I brought this up earlier, but I think delete/recreate with
respect to clients will never be right until we introduce the concept of
versioned topics.
On Fri, Aug 28, 2015 at 1:24 PM, Joel Koshy jjkosh...@gmail.com wrote:
Another use-case I was thinking of was something like
I will have some time next week to help roll out an 0.8.2.2 release RC.
Thanks,
Jun
On Fri, Aug 28, 2015 at 8:46 AM, Jaikiran Pai jai.forums2...@gmail.com
wrote:
Recently there was a discussion that 0.8.2.2 will be released soon to fix
the critical issue with compression. Is that still the
Yes, we are still shooting for an 0.8.3 release towards the end of Oct.
Thanks,
Jun
On Fri, Aug 28, 2015 at 7:46 AM, Stefan Miklosovic mikloso...@gmail.com
wrote:
Hi,
I am working on some project which is using Kafka heavilly. Becasue of
the latest API changes, I am forced to use
[
https://issues.apache.org/jira/browse/KAFKA-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14720110#comment-14720110
]
Guozhang Wang edited comment on KAFKA-2486 at 8/28/15 6:31 PM:
See https://builds.apache.org/job/Kafka-trunk/607/changes
Changes:
[cshapi] MINOR: kafkatest add manifest
--
[...truncated 1627 lines...]
kafka.log.LogConfigTest testKafkaConfigToProps PASSED
kafka.log.LogConfigTest testFromPropsInvalid PASSED
From what I understand, the largest number of partitions trick is based
on the assumption that topics can only expand their partitions. What
happens when a topic gets deleted and recreated? This breaks that
assumption.
On Fri, Aug 28, 2015 at 6:33 AM, Neha Narkhede n...@confluent.io wrote:
39 matches
Mail list logo
