[
https://issues.apache.org/jira/browse/KAFKA-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-331.
-
Resolution: Incomplete
recurrent produce errors
Key: KAFKA
[
https://issues.apache.org/jira/browse/KAFKA-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-157.
-
Resolution: Fixed
Message may be delivered to incorrect partition incase of semantic
partitioning
[
https://issues.apache.org/jira/browse/KAFKA-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-5.
---
Resolution: Invalid (was: Unresolved)
Continuous log flusher
--
Key
[
https://issues.apache.org/jira/browse/KAFKA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-168.
-
Resolution: Won't Fix
Support locality in consumer partition assignment algorithm
[
https://issues.apache.org/jira/browse/KAFKA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-1.
---
Resolution: Invalid (was: Unresolved)
The log4j appender still uses the SyncProducer API
[
https://issues.apache.org/jira/browse/KAFKA-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-1239.
--
Resolution: Fixed
New producer checklist
--
Key: KAFKA-1239
[
https://issues.apache.org/jira/browse/KAFKA-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-1655.
--
Resolution: Invalid
Allow high performance SimpleConsumer use cases to still work with new Kafka
0.9
Jay Kreps created KAFKA-1930:
Summary: Move server over to new metrics library
Key: KAFKA-1930
URL: https://issues.apache.org/jira/browse/KAFKA-1930
Project: Kafka
Issue Type: Improvement
Jay Kreps created KAFKA-1929:
Summary: Convert core kafka module to use the errors in
org.apache.kafka.common.errors
Key: KAFKA-1929
URL: https://issues.apache.org/jira/browse/KAFKA-1929
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310972#comment-14310972
]
Jay Kreps commented on KAFKA-1804:
--
The remaining issue is the lack of logging. However
[
https://issues.apache.org/jira/browse/KAFKA-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310982#comment-14310982
]
Jay Kreps commented on KAFKA-1638:
--
[~junrao] is this still happening? I haven't seen
[
https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-881.
-
Resolution: Won't Fix
Closing due to ancientness.
Kafka broker not respecting log.roll.hours
[
https://issues.apache.org/jira/browse/KAFKA-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-864.
-
Resolution: Duplicate
I think this is being pursued on another ticket.
bin/kafka-gen-reassignment.sh
[
https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-493.
-
Resolution: Incomplete
High CPU usage on inactive server
[
https://issues.apache.org/jira/browse/KAFKA-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14311042#comment-14311042
]
Jay Kreps commented on KAFKA-1831:
--
The new producer returns RecordMetadata on each
[
https://issues.apache.org/jira/browse/KAFKA-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-1831.
--
Resolution: Fixed
I think the new producer fixes this, reopen if you disagree.
Producer does
[
https://issues.apache.org/jira/browse/KAFKA-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-1709.
--
Resolution: Invalid
This didn't turn out to be a deadlock.
[New Java Producer Potential Deadlock
[
https://issues.apache.org/jira/browse/KAFKA-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-1587.
--
Resolution: Won't Fix
Possible Memory Leak when we use Kafka 8.0 Producer for sending messages
[
https://issues.apache.org/jira/browse/KAFKA-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310961#comment-14310961
]
Jay Kreps commented on KAFKA-936:
-
[~junrao] Does this issue still exist?
Kafka Metrics
[
https://issues.apache.org/jira/browse/KAFKA-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310973#comment-14310973
]
Jay Kreps commented on KAFKA-1408:
--
[~junrao], [~dmitrybugaychenko] is this still active
[
https://issues.apache.org/jira/browse/KAFKA-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-1416:
-
Labels: newbie (was: )
Unify sendMessages/getMessages in unit tests
[
https://issues.apache.org/jira/browse/KAFKA-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-867.
-
Resolution: Incomplete
No follow-up.
producer transaction issue when metrics lib not correct
[
https://issues.apache.org/jira/browse/KAFKA-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-865.
-
Resolution: Duplicate
Mavenize and separate the client
[
https://issues.apache.org/jira/browse/KAFKA-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-715.
-
Resolution: Duplicate
NumberFormatException in PartitionStateInfo
[
https://issues.apache.org/jira/browse/KAFKA-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-711.
-
Resolution: Invalid
NPE in TRUNK broker
---
Key: KAFKA-711
[
https://issues.apache.org/jira/browse/KAFKA-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-662.
-
Resolution: Fixed
Create testcases for unclean shut down
[
https://issues.apache.org/jira/browse/KAFKA-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-663.
-
Resolution: Won't Fix
Not under active development.
Add deploy feature to System Test
[
https://issues.apache.org/jira/browse/KAFKA-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-321.
-
Resolution: Fixed
Remove dead brokers from ProducerPool
[
https://issues.apache.org/jira/browse/KAFKA-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-299.
-
Resolution: Fixed
Change broker request and response to use Seqs rather than Array
[
https://issues.apache.org/jira/browse/KAFKA-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-260.
-
Resolution: Won't Fix
Add audit trail to kafka
Key: KAFKA-260
[
https://issues.apache.org/jira/browse/KAFKA-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-665.
-
Resolution: Fixed
We solved this by making the response queue unbounded. When the request queue
is full
[
https://issues.apache.org/jira/browse/KAFKA-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-904.
-
Resolution: Duplicate
ClientUtils throws SocketTimeOut in client side at high load
[
https://issues.apache.org/jira/browse/KAFKA-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310986#comment-14310986
]
Jay Kreps commented on KAFKA-948:
-
[~junrao] Can this be closed?
ISR list in LeaderAndISR
[
https://issues.apache.org/jira/browse/KAFKA-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14311002#comment-14311002
]
Jay Kreps commented on KAFKA-783:
-
[~nehanarkhede] Still a problem?
Preferred replica
[
https://issues.apache.org/jira/browse/KAFKA-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-185.
-
Resolution: Invalid
The files in the kafka\clients\csharp\src\Kafka\Kafka.Client\cfg folder
[
https://issues.apache.org/jira/browse/KAFKA-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-178.
-
Resolution: Invalid
Simplify the brokerinfo argument to the producer-perf-test.sh
[
https://issues.apache.org/jira/browse/KAFKA-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-1827.
--
Resolution: Won't Fix
Yeah this is interesting but currently out of scope.
Optimistic Locking when
Jay Kreps created KAFKA-1928:
Summary: Move kafka.network over to using the network classes in
org.apache.kafka.common.network
Key: KAFKA-1928
URL: https://issues.apache.org/jira/browse/KAFKA-1928
[
https://issues.apache.org/jira/browse/KAFKA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-479.
-
Resolution: Invalid
I think we decided this was a java bug.
ZK EPoll taking 100% CPU usage with Kafka
[
https://issues.apache.org/jira/browse/KAFKA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-1926:
-
Description:
There is currently a lot of duplication between the Utils class in common and
the one
[
https://issues.apache.org/jira/browse/KAFKA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-1926:
-
Labels: newbie (was: )
Replace kafka.utils.Utils with o.a.k.common.utils.Utils
[
https://issues.apache.org/jira/browse/KAFKA-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310955#comment-14310955
]
Jay Kreps commented on KAFKA-1155:
--
[~nehanarkhede] is this still a problem? Seems like
[
https://issues.apache.org/jira/browse/KAFKA-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-1145.
--
Resolution: Won't Fix
Closing since no follow-up.
Broker fail to sync after restart
[
https://issues.apache.org/jira/browse/KAFKA-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-1132.
--
Resolution: Won't Fix
Reduce size and amount of server access logs
[
https://issues.apache.org/jira/browse/KAFKA-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310963#comment-14310963
]
Jay Kreps commented on KAFKA-902:
-
This could be accomplished by just adding +/-5
[
https://issues.apache.org/jira/browse/KAFKA-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-1423.
--
Resolution: Fixed
Fix Version/s: 0.8.2
Updating partition count clears topic configuration
[
https://issues.apache.org/jira/browse/KAFKA-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310994#comment-14310994
]
Jay Kreps commented on KAFKA-1044:
--
This would be nice to do. If anyone wants to take
[
https://issues.apache.org/jira/browse/KAFKA-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-1050.
--
Resolution: Fixed
I think both of these are done on other tickets.
Support for no data loss mode
[
https://issues.apache.org/jira/browse/KAFKA-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-744.
-
Resolution: Invalid
Ancient.
Bad response time for fetch request
[
https://issues.apache.org/jira/browse/KAFKA-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-406.
-
Resolution: Won't Fix
Gzipped payload is a fully wrapped Message (with headers), not just payload
[
https://issues.apache.org/jira/browse/KAFKA-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-430.
-
Resolution: Won't Fix
Improve the waitUntilLeaderIsElectedOrChanged function in TestUtils class
[
https://issues.apache.org/jira/browse/KAFKA-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-436.
-
Resolution: Fixed
This should be fixed as part of the response size issues being done for the new
[
https://issues.apache.org/jira/browse/KAFKA-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-650.
-
Resolution: Fixed
Create a testcase for Migration Tool with hundreds of topics
[
https://issues.apache.org/jira/browse/KAFKA-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-760.
-
Resolution: Fixed
building a version other than 2.8.0 with package breaks scripts when running
them
[
https://issues.apache.org/jira/browse/KAFKA-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14311041#comment-14311041
]
Jay Kreps commented on KAFKA-1897:
--
[~navina] WRT your suggestions:
1. Isn't this what
[
https://issues.apache.org/jira/browse/KAFKA-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14311044#comment-14311044
]
Jay Kreps commented on KAFKA-1925:
--
Ha ha, that is terrible! :-)
+1
We'll figure out
[
https://issues.apache.org/jira/browse/KAFKA-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-1791.
--
Resolution: Cannot Reproduce
Corrupt index after safe shutdown and restart
[
https://issues.apache.org/jira/browse/KAFKA-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-1765.
--
Resolution: Fixed
slf4j binding conflict in slf4j-log4j12 and kafka-assembly
[
https://issues.apache.org/jira/browse/KAFKA-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-1808.
--
Resolution: Invalid
SimpleConsumer not working as expected
[
https://issues.apache.org/jira/browse/KAFKA-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-1767.
--
Resolution: Incomplete
No follow-up.
/admin/reassign_partitions deleted before reassignment completes
[
https://issues.apache.org/jira/browse/KAFKA-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-778.
-
Resolution: Won't Fix
New producer probably has new problems :-)
Fix unclear exceptions when
[
https://issues.apache.org/jira/browse/KAFKA-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-754.
-
Resolution: Fixed
Disable log4j logging in command line tools
[
https://issues.apache.org/jira/browse/KAFKA-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-735.
-
Resolution: Incomplete
No follow-up.
Add looping and JSON output for ConsumerOffsetChecker
[
https://issues.apache.org/jira/browse/KAFKA-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-476.
-
Resolution: Fixed
change Pool to use Option
--
Key: KAFKA-476
[
https://issues.apache.org/jira/browse/KAFKA-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-652.
-
Resolution: Fixed
Create testcases for clean shut-down
[
https://issues.apache.org/jira/browse/KAFKA-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-660.
-
Resolution: Fixed
Change (topic, partition) tuples to TopicAndPartition
[
https://issues.apache.org/jira/browse/KAFKA-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-1820.
--
Resolution: Invalid
Kafka Leader not found for Topic and Partition
[
https://issues.apache.org/jira/browse/KAFKA-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14311038#comment-14311038
]
Jay Kreps commented on KAFKA-1794:
--
[~navina] This is intentional. The whole config def
.
On Thu, Feb 05, 2015 at 06:17:44PM -0500, Joe Stein wrote:
+1
On Thu, Feb 5, 2015 at 6:16 PM, Neha Narkhede
n...@confluent.io javascript:;
wrote:
Sounds good.
On Thu, Feb 5, 2015 at 2:35 PM, Jay Kreps
jay.kr
[
https://issues.apache.org/jira/browse/KAFKA-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14310590#comment-14310590
]
Jay Kreps commented on KAFKA-1865:
--
A key aspect of this that isn't obvious is that flush
to this?
On Sun, Jan 18, 2015 at 10:31:08AM -0800, Jay Kreps wrote:
Great! Sounds like everyone is on the same page
- I created a template page to make things easier. If you do
Tools-Copy
on this page you can just fill in the italic portions with your
details.
- I retrofitted
if
there is a reasonable objection.
On Thu, Feb 05, 2015 at 06:17:44PM -0500, Joe Stein wrote:
+1
On Thu, Feb 5, 2015 at 6:16 PM, Neha Narkhede n...@confluent.io wrote:
Sounds good.
On Thu, Feb 5, 2015 at 2:35 PM, Jay Kreps jay.kr...@gmail.com wrote:
None on my part.
-Jay
Jay Kreps created KAFKA-1919:
Summary: Metadata request issued with no backoff in new producer
if there are no topics
Key: KAFKA-1919
URL: https://issues.apache.org/jira/browse/KAFKA-1919
Project: Kafka
on we also want to have unit
test for it, that¹s why it becomes a separate util class and we have unit
test in UtilsTest.scala.
-Jiangjie (Becket) Qin
On 2/3/15, 9:15 PM, Jay Kreps jay.kr...@gmail.com wrote:
How come we added this? Is it better than the linked list in java and
scala? Also
[
https://issues.apache.org/jira/browse/KAFKA-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-1919:
-
Affects Version/s: 0.8.2
Metadata request issued with no backoff in new producer if there are no topics
- the scaladocs seem to indicate that the doubly linked lists are
deprecated as of 2.11
Joel
On Wednesday, February 4, 2015, Jay Kreps jay.kr...@gmail.com wrote:
Hey Jiangjie,
Both the scala and java doubly linked lists allow O(1) deletion--it isn't
obvious because the api is slightly different from
[
https://issues.apache.org/jira/browse/KAFKA-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14306332#comment-14306332
]
Jay Kreps commented on KAFKA-1760:
--
Actually shameful to say but I'm not sure
[
https://issues.apache.org/jira/browse/KAFKA-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14306357#comment-14306357
]
Jay Kreps commented on KAFKA-1919:
--
Here is what I think is happening: in 0.8.1
[
https://issues.apache.org/jira/browse/KAFKA-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-1919:
-
Attachment: KAFKA-1919-v1.patch
Metadata request issued with no backoff in new producer
I just committed the checkstyle patch (KAFKA-1915). This will do the
checkstyle evaluation when you run the unit tests and error on style
inconsistencies. It can be hard to say which checks are more trouble than
they are worth or are two pedantic. Let's give this a try and see if it is
annoying or
How come we added this? Is it better than the linked list in java and
scala? Also it was added with only one test which is actually put inside
UtilsTest.scala which is meant to house tests for Utils.scala.
-Jay
[
https://issues.apache.org/jira/browse/KAFKA-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-1915:
-
Attachment: KAFKA-1915_2015-02-03_09:17:34.patch
Integrate checkstyle for java code
:
https://reviews.apache.org/r/30547/#review70712
---
On Feb. 3, 2015, 5:48 a.m., Jay Kreps wrote:
---
This is an automatically generated e-mail. To reply, visit:
https
/java/kafka/examples/SimpleConsumerDemo.java
c79192c5c195d4c3a7facf1be8f503478b6cc809
Diff: https://reviews.apache.org/r/30547/diff/
Testing
---
Thanks,
Jay Kreps
Jay Kreps created KAFKA-1915:
Summary: Integrate checkstyle for java code
Key: KAFKA-1915
URL: https://issues.apache.org/jira/browse/KAFKA-1915
Project: Kafka
Issue Type: Improvement
Yay!
-Jay
On Mon, Feb 2, 2015 at 2:23 PM, Neha Narkhede n...@confluent.io wrote:
Great! Thanks Jun for helping with the release and everyone involved for
your contributions.
On Mon, Feb 2, 2015 at 1:32 PM, Joe Stein joe.st...@stealth.ly wrote:
Huzzah!
Thanks Jun for preparing the
[
https://issues.apache.org/jira/browse/KAFKA-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14302796#comment-14302796
]
Jay Kreps commented on KAFKA-1915:
--
Created reviewboard https://reviews.apache.org/r
/
Testing
---
Thanks,
Jay Kreps
[
https://issues.apache.org/jira/browse/KAFKA-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-1915:
-
Status: Patch Available (was: Open)
Integrate checkstyle for java code
[
https://issues.apache.org/jira/browse/KAFKA-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-1915:
-
Attachment: KAFKA-1915.patch
Integrate checkstyle for java code
You may already know this but the producer doesn't require a complete list
of brokers in its config, it just requires the connection info for one
active broker which it uses to discover the rest of the brokers. We allow
you to specify multiple urls here for failover in cases where you aren't
using
[
https://issues.apache.org/jira/browse/KAFKA-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14300251#comment-14300251
]
Jay Kreps commented on KAFKA-1910:
--
I guess the real question is how to slice it up. Big
Jay Kreps created KAFKA-1912:
Summary: Create a simple request re-routing facility
Key: KAFKA-1912
URL: https://issues.apache.org/jira/browse/KAFKA-1912
Project: Kafka
Issue Type: Improvement
, Jeff Holoman wrote:
Maybe I'm in the minority here, but I actually don't think there should be
a default for this param and you should be required to explicitly set this.
On Thu, Jan 29, 2015 at 5:43 AM, Jay Kreps boredandr...@gmail.com wrote:
On Jan. 29, 2015, 6:50 a.m., Gwen Shapira
/#comment115739
ditto
Not sure this stuff is actually here for review...may still be a work in
progress. Overall this structure of code makes a ton of sense to me. Left some
minor comments.
- Jay Kreps
On Feb. 1, 2015, 2:45 a.m., Guozhang Wang wrote
[
https://issues.apache.org/jira/browse/KAFKA-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296710#comment-14296710
]
Jay Kreps commented on KAFKA-1760:
--
Updated reviewboard https://reviews.apache.org/r
to set
log.dir=${KAFKA_HOME}/data, we will end up forcing this value as the log.dir
even when the user has intentionally specified a different path for the data
logs.
Let me know if I misunderstood your suggestion.
Jay Kreps wrote:
I think you are right that --override won't
ac15d34425795d5be20c51b01fa1108bdcd66583
Diff: https://reviews.apache.org/r/27799/diff/
Testing
---
Thanks,
Jay Kreps
://reviews.apache.org/r/27799/#review68693
---
On Jan. 23, 2015, 9:15 p.m., Jay Kreps wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r
On Jan. 29, 2015, 6:50 a.m., Gwen Shapira wrote:
We added --override option to KafkaServer that allows overriding default
configuration from commandline.
I believe that just changing the shell script to include --override
log.dir=${KAFKA_HOME}/data
may be enough?
overriding
801 - 900 of 2091 matches
Mail list logo
