[
https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481521#comment-14481521
]
Sriharsha Chintalapani commented on KAFKA-2082:
---
[~eapache] [~junrao] These
Aditya Auradkar created KAFKA-2097:
--
Summary: Implement request delays for quota violations
Key: KAFKA-2097
URL: https://issues.apache.org/jira/browse/KAFKA-2097
Project: Kafka
Issue Type:
[
https://issues.apache.org/jira/browse/KAFKA-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Bugaychenko updated KAFKA-2029:
--
Attachment: KAFKA-2029.patch
Improving controlled shutdown for rolling updates
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/32890/
---
Review request for kafka.
Bugs: KAFKA-2029
[
https://issues.apache.org/jira/browse/KAFKA-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481465#comment-14481465
]
Dmitry Bugaychenko commented on KAFKA-2029:
---
Created reviewboard
Hi Jay,
2. At this time, the proposed response format changes are only for
monitoring/informing clients. As Jun mentioned, we get instance level
monitoring in this case since each instance that got throttled will have a
metric confirming the same. Without client level monitoring for this, it's
[
https://issues.apache.org/jira/browse/KAFKA-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481477#comment-14481477
]
Dmitry Bugaychenko commented on KAFKA-2029:
---
Rebased on trunk.
Improving
[
https://issues.apache.org/jira/browse/KAFKA-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481865#comment-14481865
]
Rekha Joshi commented on KAFKA-1621:
Hi.missed updating earlier. everything else was
Rekha Joshi created KAFKA-2098:
--
Summary: Gradle Wrapper Jar gone missing in 0.8.2.1
Key: KAFKA-2098
URL: https://issues.apache.org/jira/browse/KAFKA-2098
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481843#comment-14481843
]
Jun Rao commented on KAFKA-2082:
After step 2), which broker is the new controller? The
[
https://issues.apache.org/jira/browse/KAFKA-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-2043:
---
Resolution: Fixed
Fix Version/s: 0.8.3
Status: Resolved (was: Patch Available)
Thanks for
[
https://issues.apache.org/jira/browse/KAFKA-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481617#comment-14481617
]
Aravind commented on KAFKA-2078:
Yes, I could reproduce this with just 1 broker as well.
[
https://issues.apache.org/jira/browse/KAFKA-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481861#comment-14481861
]
Jun Rao commented on KAFKA-2078:
What kind of network do you have? Do you have any load
[
https://issues.apache.org/jira/browse/KAFKA-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481890#comment-14481890
]
Jun Rao commented on KAFKA-2096:
[~allenxwang], that seems to be a good fix. Do you want
See https://builds.apache.org/job/KafkaPreCommit/59/changes
Changes:
[junrao] kafka-2043; CompressionType is passed in each RecordAccumulator
append; patched by Grant Henke; reviewed by Jun Rao
--
[...truncated 2129 lines...]
[
https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14482042#comment-14482042
]
Sriharsha Chintalapani edited comment on KAFKA-2082 at 4/6/15 10:21 PM:
[
https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481931#comment-14481931
]
Sriharsha Chintalapani commented on KAFKA-2082:
---
[~junrao]
After step 2 I
1. The controller - broker communication doesn't have to be blocking. It
just needs to call a callback on completion of a request. We can leave this
out for now. It just means that we can't run the inter cluster
communication through non-plaintext port until we port this code to the
common network
[
https://issues.apache.org/jira/browse/KAFKA-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14482085#comment-14482085
]
Guozhang Wang commented on KAFKA-2059:
--
I saw this error once out of 100 runs, and on
[
https://issues.apache.org/jira/browse/KAFKA-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-2086.
Resolution: Duplicate
Yes. Closing this one.
testRoundRobinPartitionAssignor transient failure
[
https://issues.apache.org/jira/browse/KAFKA-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-2086.
--
testRoundRobinPartitionAssignor transient failure
-
It seems that everyone is in favor of keeping the docs updated in each jira.
As for the next step, anyone wants to help figure out if it's possible to
move the website to git?
Thanks,
Jun
On Tue, Mar 31, 2015 at 10:03 AM, Gwen Shapira gshap...@cloudera.com
wrote:
+1
On Tue, Mar 31, 2015 at
GitHub user rekhajoshm opened a pull request:
https://github.com/apache/kafka/pull/54
KAFKA-2098: gradle files
gradle files, tiny footprint.lets have it in.thanks
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rekhajoshm/kafka
[
https://issues.apache.org/jira/browse/KAFKA-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481936#comment-14481936
]
ASF GitHub Bot commented on KAFKA-2098:
---
GitHub user rekhajoshm opened a pull
[
https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14482058#comment-14482058
]
Evan Huus commented on KAFKA-2082:
--
What if (in a normally set up cluster) a broker
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31568/#review78668
---
Thanks for the new patch. Now that I understood the logic better, I
Gwen,
That sounds about right to me. I've found that when ports are bound
dynamically, RAII-style greatly simplifies things since if you've bound
them as early as possible, then you'll always be able to get at the port
even if nothing is accept()ing yet.
-Ewen
On Sat, Apr 4, 2015 at 8:27 PM,
[
https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481981#comment-14481981
]
Evan Huus commented on KAFKA-2082:
--
So I guess the producer should not be connecting to
Hi,
I started work on converting core to use common network code and I ran into
two questions that hopefully someone can help me with:
1. BlockingChannel - Looks like the inter-broker communication is mostly
through blocking channel. There's no client equivalent (i.e client code is
all
[
https://issues.apache.org/jira/browse/KAFKA-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14482084#comment-14482084
]
Guozhang Wang commented on KAFKA-1910:
--
[~jjkoshy]:
1. No the error code change was
[
https://issues.apache.org/jira/browse/KAFKA-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14482207#comment-14482207
]
Gwen Shapira commented on KAFKA-1809:
-
Sorry for missing that [~harsha_ch]. I agree
Gwen Shapira created KAFKA-2099:
---
Summary: BrokerEndPoint file, methods and object names should match
Key: KAFKA-2099
URL: https://issues.apache.org/jira/browse/KAFKA-2099
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481962#comment-14481962
]
Guozhang Wang commented on KAFKA-2086:
--
Is this a duplicate of KAFKA-2056?
[
https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14482042#comment-14482042
]
Sriharsha Chintalapani commented on KAFKA-2082:
---
[~eapache]
I think the
On March 24, 2015, 10:46 p.m., Guozhang Wang wrote:
core/src/main/scala/kafka/server/AbstractFetcherThread.scala, lines 81-86
https://reviews.apache.org/r/31366/diff/2/?file=898415#file898415line81
Jun has a comment about the case when all partitions gets inactive,
which is
On April 1, 2015, 6:46 p.m., Jun Rao wrote:
core/src/main/scala/kafka/utils/timer/Timer.scala, lines 44-45
https://reviews.apache.org/r/31568/diff/2/?file=901427#file901427line44
Could we use inLock() where applicable?
Yasuhiro Matsuda wrote:
I don't like to have a closure
[
https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14482134#comment-14482134
]
Guozhang Wang commented on KAFKA-2082:
--
[~eapache] the problem you described is
Gianmarco,
I browse through your paper (congrats for the ICDE publication BTW!), and
here are some questions / comments on the algorithm:
1. One motivation of enabling key-based partitioned in Kafka is to achieve
per-key ordering, i.e. with all messages with the same key sent to the same
[
https://issues.apache.org/jira/browse/KAFKA-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira resolved KAFKA-2098.
-
Resolution: Won't Fix
Gradle Wrapper Jar gone missing in 0.8.2.1
[
https://issues.apache.org/jira/browse/KAFKA-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481979#comment-14481979
]
Gwen Shapira commented on KAFKA-2098:
-
I believe it was deliberately removed, since we
[
https://issues.apache.org/jira/browse/KAFKA-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14482198#comment-14482198
]
Sriharsha Chintalapani commented on KAFKA-1809:
---
[~gwenshap] I apologize for
As for 4, if we are going to reuse the purgatory class are we going to just
use the produce / fetch purgatory objects or we are going to create a new
throttle purgatory object? If we go with the first option then I think
Jun's concern is valid such that some produce / fetch requests will have
many
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/32866/#review79084
---
Thanks for the patch. A few comments below. Also, could you rebase?
[
https://issues.apache.org/jira/browse/KAFKA-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-2099:
---
Resolution: Fixed
Fix Version/s: 0.8.3
Status: Resolved (was: Patch Available)
Thanks for
[
https://issues.apache.org/jira/browse/KAFKA-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyukjin Kwon resolved KAFKA-2094.
-
Resolution: Not A Problem
Fix Version/s: 0.8.2.0
This is the issue caused by not setting
Hey Aditya,
2. I kind of buy it, but I really like to understand the details of the use
case before we make protocol changes. What changes are you proposing in the
clients for monitoring and how would that be used?
-Jay
On Mon, Apr 6, 2015 at 10:36 AM, Aditya Auradkar
Here's a wild guess:
An app developer included a Kafka Producer in his app, and is not happy
with the throughput. He doesn't have visibility into the brokers since they
are owned by a different team. Obviously the first instinct of a developer
who knows that throttling exists is to blame
[
https://issues.apache.org/jira/browse/KAFKA-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14482537#comment-14482537
]
Fangmin Lv commented on KAFKA-2059:
---
Every run takes 30 seconds on my machine. I've run
[
https://issues.apache.org/jira/browse/KAFKA-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-2099:
Status: Patch Available (was: Open)
BrokerEndPoint file, methods and object names should match
[
https://issues.apache.org/jira/browse/KAFKA-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-2099:
Attachment: KAFKA-2099.patch
BrokerEndPoint file, methods and object names should match
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/32913/
---
Review request for kafka.
Bugs: KAFKA-2099
[
https://issues.apache.org/jira/browse/KAFKA-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14482296#comment-14482296
]
Gwen Shapira commented on KAFKA-2099:
-
Created reviewboard
This is great survey for understanding which part still needs improvement,
thanks Gwen!
On Mon, Mar 30, 2015 at 12:27 PM, Gwen Shapira gshap...@cloudera.com
wrote:
I was planning on doing a re-poll about a month after every release :)
Maybe it can be part of the release activity.
Gwen
On
[
https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14482301#comment-14482301
]
Evan Huus commented on KAFKA-2082:
--
OK, that all makes sense. Some follow-up questions:
[
https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14482302#comment-14482302
]
Evan Huus commented on KAFKA-2082:
--
OK, that all makes sense. Some follow-up questions:
[
https://issues.apache.org/jira/browse/KAFKA-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14482363#comment-14482363
]
Gwen Shapira commented on KAFKA-2099:
-
Thanks for quick review [~junrao] and
[
https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14482361#comment-14482361
]
Sriharsha Chintalapani commented on KAFKA-2082:
---
[~guozhang]
1. This case is
[
https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14482421#comment-14482421
]
Evan Huus commented on KAFKA-2082:
--
1. Then why does broker3 continue to spam logs? (I
[
https://issues.apache.org/jira/browse/KAFKA-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14482316#comment-14482316
]
Sriharsha Chintalapani commented on KAFKA-2099:
---
Thanks [~gwenshap]
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31850/#review79063
---
Thanks for the patch.
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31850/#review79107
---
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/32913/#review79099
---
Ship it!
Ship It!
- Sriharsha Chintalapani
On April 7, 2015,
[
https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14482343#comment-14482343
]
Guozhang Wang commented on KAFKA-2082:
--
1. when broker-1 registry re-appears on ZK,
See https://builds.apache.org/job/KafkaPreCommit/60/changes
Hi,
These days I have been focus on Kafka 0.8 replication design and found
three replication design proposals from the wiki (according to the document,
the V3 version is used in Kafka 0.8 release).
But the v3 proposal is not complete and is inconsistent with the
release.
Is
[
https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14482494#comment-14482494
]
Sriharsha Chintalapani commented on KAFKA-2082:
---
[~eapache] I was testing
On April 7, 2015, 1:28 a.m., Joel Koshy wrote:
clients/src/main/java/org/apache/kafka/clients/producer/internals/RecordAccumulator.java,
line 362
https://reviews.apache.org/r/31850/diff/5/?file=908540#file908540line362
As you explained offline, the sender does not have access to
[
https://issues.apache.org/jira/browse/KAFKA-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyukjin Kwon updated KAFKA-2094:
Description:
After I create a topic and then remove it (and wait for enough time to
eventually
Hyukjin Kwon created KAFKA-2094:
---
Summary: Kafka does not create topic automatically after deleting
the topic.
Key: KAFKA-2094
URL: https://issues.apache.org/jira/browse/KAFKA-2094
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyukjin Kwon updated KAFKA-2094:
Description:
After I create a topic and then remove it (and wait for enough time to
eventually
[
https://issues.apache.org/jira/browse/KAFKA-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyukjin Kwon updated KAFKA-2094:
Description:
After I create a topic and then remove it (and wait for enough time to
eventually
Run Rao,
Thanks for reviewing it again. What commands do you run to show unused
imports? When I run grandle --daemon test, it did not show these (there
were some warnings, but not unused imports). I thought that would have
shown these things.
Tong Li
OpenStack Kafka Community Development
Hi,
These days I have been focus on Kafka 0.8 replication design and found
three replication design proposals from the wiki (according to the document,
the V3 version is used in Kafka 0.8 release).
But the v3 proposal is not complete and is inconsistent with the
release.
Is
[
https://issues.apache.org/jira/browse/KAFKA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481262#comment-14481262
]
Jun Rao commented on KAFKA-1926:
Typically, IDE (e.g., intellij) shows unused imports.
Yes, the wiki is a bit old. You can find out more about replication in the
following links.
http://kafka.apache.org/documentation.html#replication
http://www.slideshare.net/junrao/kafka-replication-apachecon2013
#1, #2, #8. See the ZK layout in
Sriharsha Chintalapani created KAFKA-2095:
-
Summary: ZKConfig uses hard coded value
zookeeper.session.timeout.ms
Key: KAFKA-2095
URL: https://issues.apache.org/jira/browse/KAFKA-2095
Project:
[
https://issues.apache.org/jira/browse/KAFKA-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani resolved KAFKA-2095.
---
Resolution: Invalid
ZKConfig uses hard coded value
Allen Wang created KAFKA-2096:
-
Summary: Enable keepalive socket option for broker
Key: KAFKA-2096
URL: https://issues.apache.org/jira/browse/KAFKA-2096
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wang updated KAFKA-2096:
--
Summary: Enable keepalive socket option for broker to prevent socket leak
(was: Enable keepalive
79 matches
Mail list logo
