[jira] [Resolved] (KAFKA-414) Evaluate mmap-based writes for Log implementation

[ https://issues.apache.org/jira/browse/KAFKA-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-414. - Resolution: Won't Fix > Evaluate mmap-based writes for Log implementation >

[jira] [Comment Edited] (KAFKA-1955) Explore disk-based buffering in new Kafka Producer

[ https://issues.apache.org/jira/browse/KAFKA-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043494#comment-16043494 ] Jay Kreps edited comment on KAFKA-1955 at 6/8/17 9:43 PM: -- I think the patch I

[jira] [Comment Edited] (KAFKA-1955) Explore disk-based buffering in new Kafka Producer

[ https://issues.apache.org/jira/browse/KAFKA-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043494#comment-16043494 ] Jay Kreps edited comment on KAFKA-1955 at 6/8/17 9:41 PM: -- I think the patch I

[jira] [Commented] (KAFKA-1955) Explore disk-based buffering in new Kafka Producer

[ https://issues.apache.org/jira/browse/KAFKA-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043494#comment-16043494 ] Jay Kreps commented on KAFKA-1955: -- I think the patch I submitted was kind of a cool hack, but after

[jira] [Resolved] (KAFKA-1941) Timeout connections in the clients

[ https://issues.apache.org/jira/browse/KAFKA-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1941. -- Resolution: Duplicate Yes, I think this is resolved by KAFKA-1282. > Timeout connections in the

[jira] [Comment Edited] (KAFKA-4113) Allow KTable bootstrap

[ https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456296#comment-15456296 ] Jay Kreps edited comment on KAFKA-4113 at 9/1/16 6:52 PM: -- Don't you get this

[jira] [Comment Edited] (KAFKA-4113) Allow KTable bootstrap

[ https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456296#comment-15456296 ] Jay Kreps edited comment on KAFKA-4113 at 9/1/16 6:51 PM: -- Don't you get this

[jira] [Commented] (KAFKA-4113) Allow KTable bootstrap

[ https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456296#comment-15456296 ] Jay Kreps commented on KAFKA-4113: -- Don't you get this naturally out of the message timestamps and the

[jira] [Created] (KAFKA-4094) Fix importance labels for Kafka Server config

Jay Kreps created KAFKA-4094: Summary: Fix importance labels for Kafka Server config Key: KAFKA-4094 URL: https://issues.apache.org/jira/browse/KAFKA-4094 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-2063) Bound fetch response size

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15400224#comment-15400224 ] Jay Kreps commented on KAFKA-2063: -- Makes sense on both counts--I have no real opinion, just thought I'd

[jira] [Commented] (KAFKA-2063) Bound fetch response size

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399909#comment-15399909 ] Jay Kreps commented on KAFKA-2063: -- [~benstopford] 1. I guess the question is how do you load balance

[jira] [Commented] (KAFKA-3990) Kafka New Producer may raise an OutOfMemoryError

[ https://issues.apache.org/jira/browse/KAFKA-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15398283#comment-15398283 ] Jay Kreps commented on KAFKA-3990: -- [~hachikuji] But the response format is dictated by the producer

[jira] [Commented] (KAFKA-3824) Docs indicate auto.commit breaks at least once delivery but that is incorrect

[ https://issues.apache.org/jira/browse/KAFKA-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15344548#comment-15344548 ] Jay Kreps commented on KAFKA-3824: -- [~beez] Sorry for not following up sooner. I think the reason for

[jira] [Created] (KAFKA-3824) Docs indicate auto.commit breaks at least once delivery but that is incorrect

Jay Kreps created KAFKA-3824: Summary: Docs indicate auto.commit breaks at least once delivery but that is incorrect Key: KAFKA-3824 URL: https://issues.apache.org/jira/browse/KAFKA-3824 Project: Kafka

[jira] [Commented] (KAFKA-3803) JsonConverter deserialized Struct containing bytes field does not return true for equals()

[ https://issues.apache.org/jira/browse/KAFKA-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324743#comment-15324743 ] Jay Kreps commented on KAFKA-3803: -- FWIW, past experience with giving users ByteBuffer has been pretty

[jira] [Commented] (KAFKA-3811) Introduce Kafka Streams metrics recording levels

[ https://issues.apache.org/jira/browse/KAFKA-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324669#comment-15324669 ] Jay Kreps commented on KAFKA-3811: -- I'm not wild about introducing these levels in an ad hoc way in Kafka

[jira] [Commented] (KAFKA-3753) Add size() to the StateStore interface for metrics reporting

[ https://issues.apache.org/jira/browse/KAFKA-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323324#comment-15323324 ] Jay Kreps commented on KAFKA-3753: -- I think size is a bit ambiguous, it could mean the number of bytes

[jira] [Commented] (KAFKA-3788) Potential message lost when switching to new segment

[ https://issues.apache.org/jira/browse/KAFKA-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321156#comment-15321156 ] Jay Kreps commented on KAFKA-3788: -- You are correct--unix doesn't guarantee either the ordering or writes

[jira] [Commented] (KAFKA-3775) Throttle maximum number of tasks assigned to a single KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314721#comment-15314721 ] Jay Kreps commented on KAFKA-3775: -- I'd have to agree I think this is a memory management problem I think

[jira] [Commented] (KAFKA-3777) Extract the LRU cache out of RocksDBStore

[ https://issues.apache.org/jira/browse/KAFKA-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313382#comment-15313382 ] Jay Kreps commented on KAFKA-3777: -- Probably everyone already knows but just want to capture a couple of

[jira] [Commented] (KAFKA-3769) KStream job spending 60% of time writing metrics

[ https://issues.apache.org/jira/browse/KAFKA-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309288#comment-15309288 ] Jay Kreps commented on KAFKA-3769: -- Nice catch. > KStream job spending 60% of time writing metrics >

[jira] [Commented] (KAFKA-3732) Add an auto accept option to kafka-acls.sh

[ https://issues.apache.org/jira/browse/KAFKA-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15292095#comment-15292095 ] Jay Kreps commented on KAFKA-3732: -- Is the right fix to add an option here. I mean, this is unix, the

[jira] [Commented] (KAFKA-3511) Provide built-in aggregators sum() and avg() in Kafka Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15290440#comment-15290440 ] Jay Kreps commented on KAFKA-3511: -- It just seems really weird to bake one or two aggregates into the

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252152#comment-15252152 ] Jay Kreps commented on KAFKA-3565: -- Oh yeah, I think the critical question is what is the bottleneck? In

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252139#comment-15252139 ] Jay Kreps commented on KAFKA-3565: -- [~becket_qin] Yeah I think you are saying something like "previously

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252069#comment-15252069 ] Jay Kreps commented on KAFKA-3565: -- [~ijuma] Yeah your data eliminates my guess. If the problem were the

[jira] [Comment Edited] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15248198#comment-15248198 ] Jay Kreps edited comment on KAFKA-3565 at 4/19/16 5:11 PM: --- I think

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15248198#comment-15248198 ] Jay Kreps commented on KAFKA-3565: -- I think [~becket_qin] noted a good possible explanation. The dominate

[jira] [Commented] (KAFKA-3522) Consider adding version information into rocksDB storage format

[ https://issues.apache.org/jira/browse/KAFKA-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229388#comment-15229388 ] Jay Kreps commented on KAFKA-3522: -- I think you could potentially just write some version file on startup

[jira] [Commented] (KAFKA-3511) Provide built-in aggregators sum() and avg() in Kafka Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227096#comment-15227096 ] Jay Kreps commented on KAFKA-3511: -- The issue is that there are dozens of common aggregation functions,

[jira] [Commented] (KAFKA-3499) byte[] should not be used as Map key nor Set member

[ https://issues.apache.org/jira/browse/KAFKA-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15224768#comment-15224768 ] Jay Kreps commented on KAFKA-3499: -- Yeah, gotcha, that would be totally broken. > byte[] should not be

[jira] [Comment Edited] (KAFKA-3499) byte[] should not be used as Map key nor Set member

[ https://issues.apache.org/jira/browse/KAFKA-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15224741#comment-15224741 ] Jay Kreps edited comment on KAFKA-3499 at 4/4/16 6:27 PM: -- I think this problem

[jira] [Commented] (KAFKA-3499) byte[] should not be used as Map key nor Set member

[ https://issues.apache.org/jira/browse/KAFKA-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15224741#comment-15224741 ] Jay Kreps commented on KAFKA-3499: -- I think this problem is more general than byte[] since lots of things

[jira] [Commented] (KAFKA-3456) In-house KafkaMetric misreports metrics when periodically observed

[ https://issues.apache.org/jira/browse/KAFKA-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15211302#comment-15211302 ] Jay Kreps commented on KAFKA-3456: -- I think the tradeoff is between getting a current estimate and using

[jira] [Comment Edited] (KAFKA-3262) Make KafkaStreams debugging friendly

[ https://issues.apache.org/jira/browse/KAFKA-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159545#comment-15159545 ] Jay Kreps edited comment on KAFKA-3262 at 2/23/16 7:58 PM: --- This is a good

[jira] [Commented] (KAFKA-3262) Make KafkaStreams debugging friendly

[ https://issues.apache.org/jira/browse/KAFKA-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159545#comment-15159545 ] Jay Kreps commented on KAFKA-3262: -- This is a good catch, I ran into this issue too. Another issue is

[jira] [Commented] (KAFKA-3197) Producer can send message out of order even when in flight request is set to 1.

[ https://issues.apache.org/jira/browse/KAFKA-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131451#comment-15131451 ] Jay Kreps commented on KAFKA-3197: -- Would it be better to treat this more as a bug than a configurable

[jira] [Commented] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15124537#comment-15124537 ] Jay Kreps commented on KAFKA-3174: -- This is a great find. It looks like it did become an intrinsic in 1.8

[jira] [Commented] (KAFKA-1464) Add a throttling option to the Kafka replication tool

[ https://issues.apache.org/jira/browse/KAFKA-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121706#comment-15121706 ] Jay Kreps commented on KAFKA-1464: -- Another issue this raises is that a partition might have a natural

[jira] [Commented] (KAFKA-1464) Add a throttling option to the Kafka replication tool

[ https://issues.apache.org/jira/browse/KAFKA-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121691#comment-15121691 ] Jay Kreps commented on KAFKA-1464: -- I agree that the key difference is in-sync vs out-of-sync replicas.

[jira] [Commented] (KAFKA-2076) Add an API to new consumer to allow user get high watermark of partitions.

[ https://issues.apache.org/jira/browse/KAFKA-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15115762#comment-15115762 ] Jay Kreps commented on KAFKA-2076: -- I think that makes sense. Is there other per-partition metadata

[jira] [Created] (KAFKA-3142) Improve error message in kstreams

Jay Kreps created KAFKA-3142: Summary: Improve error message in kstreams Key: KAFKA-3142 URL: https://issues.apache.org/jira/browse/KAFKA-3142 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-3137) Delete tombstones in log compacted topics may never get removed.

[ https://issues.apache.org/jira/browse/KAFKA-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113222#comment-15113222 ] Jay Kreps commented on KAFKA-3137: -- We maintain the modification timestamp from the original file in the

[jira] [Commented] (KAFKA-3115) Remove locking in metrics package

[ https://issues.apache.org/jira/browse/KAFKA-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15107827#comment-15107827 ] Jay Kreps commented on KAFKA-3115: -- [~ijuma] It showed up as a heavy hitter in hprof profiling when we

[jira] [Created] (KAFKA-3115) Remove locking in metrics package

Jay Kreps created KAFKA-3115: Summary: Remove locking in metrics package Key: KAFKA-3115 URL: https://issues.apache.org/jira/browse/KAFKA-3115 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-3044) Consumer.poll doesnot return messages when poll interval is less

[ https://issues.apache.org/jira/browse/KAFKA-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073212#comment-15073212 ] Jay Kreps commented on KAFKA-3044: -- +1 on the doc change, let's not try to make the contract of poll()

[jira] [Commented] (KAFKA-3027) Kafka metrics can be stale if there is no new update

[ https://issues.apache.org/jira/browse/KAFKA-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15067445#comment-15067445 ] Jay Kreps commented on KAFKA-3027: -- The window should advance either when an update comes or when the

[jira] [Commented] (KAFKA-3015) Improve JBOD data balancing

[ https://issues.apache.org/jira/browse/KAFKA-3015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065455#comment-15065455 ] Jay Kreps commented on KAFKA-3015: -- [~guozhang] Yeah the original proposal and patch actually always

[jira] [Commented] (KAFKA-3006) Make collection default container type for sequences in the consumer API

[ https://issues.apache.org/jira/browse/KAFKA-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064502#comment-15064502 ] Jay Kreps commented on KAFKA-3006: -- [~gwenshap] Yeah I suppose you're right, I was thinking you'd end up

[jira] [Created] (KAFKA-3015) Improve JBOD data balancing

Jay Kreps created KAFKA-3015: Summary: Improve JBOD data balancing Key: KAFKA-3015 URL: https://issues.apache.org/jira/browse/KAFKA-3015 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-3006) Make collection default container type for sequences in the consumer API

[ https://issues.apache.org/jira/browse/KAFKA-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15063121#comment-15063121 ] Jay Kreps commented on KAFKA-3006: -- Hmm, does it make sense to do it both ways? I get that maybe ideally

[jira] [Commented] (KAFKA-2991) Improve collection type consistency in KafkaConsumer API

[ https://issues.apache.org/jira/browse/KAFKA-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15059130#comment-15059130 ] Jay Kreps commented on KAFKA-2991: -- Sucks we didn't catch this in our reviews, changing it now will break

[jira] [Commented] (KAFKA-2967) Move Kafka documentation to ReStructuredText

[ https://issues.apache.org/jira/browse/KAFKA-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051348#comment-15051348 ] Jay Kreps commented on KAFKA-2967: -- [~ewencp] Cool, can we see what the output would look like for

[jira] [Commented] (KAFKA-2967) Move Kafka documentation to ReStructuredText

[ https://issues.apache.org/jira/browse/KAFKA-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15049105#comment-15049105 ] Jay Kreps commented on KAFKA-2967: -- +0 We've been through a few rounds of this and doc changes tend to

[jira] [Comment Edited] (KAFKA-2967) Move Kafka documentation to ReStructuredText

[ https://issues.apache.org/jira/browse/KAFKA-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15049105#comment-15049105 ] Jay Kreps edited comment on KAFKA-2967 at 12/9/15 6:14 PM: --- +0 We've been

[jira] [Created] (KAFKA-2956) Upgrade section of the docs is still a bit anemic

Jay Kreps created KAFKA-2956: Summary: Upgrade section of the docs is still a bit anemic Key: KAFKA-2956 URL: https://issues.apache.org/jira/browse/KAFKA-2956 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-2953) Kafka documentation is really wise

[ https://issues.apache.org/jira/browse/KAFKA-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15045398#comment-15045398 ] Jay Kreps commented on KAFKA-2953: -- I like that this bug's title says "wise" instead of "wide. Favorite

[jira] [Comment Edited] (KAFKA-2953) Kafka documentation is really wise

[ https://issues.apache.org/jira/browse/KAFKA-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15045398#comment-15045398 ] Jay Kreps edited comment on KAFKA-2953 at 12/7/15 6:30 PM: --- I like that this

[jira] [Created] (KAFKA-2950) Performance regression in producer

Jay Kreps created KAFKA-2950: Summary: Performance regression in producer Key: KAFKA-2950 URL: https://issues.apache.org/jira/browse/KAFKA-2950 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-2939) Make AbstractConfig.logUnused() tunable for clients

[ https://issues.apache.org/jira/browse/KAFKA-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15036977#comment-15036977 ] Jay Kreps commented on KAFKA-2939: -- That was the whole point of the original implementation. Looking at

[jira] [Commented] (KAFKA-2580) Kafka Broker keeps file handles open for all log files (even if its not written to/read from)

[ https://issues.apache.org/jira/browse/KAFKA-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985696#comment-14985696 ] Jay Kreps commented on KAFKA-2580: -- [~vinothchandar] All I'm saying is that you have to kind of do some

[jira] [Commented] (KAFKA-2528) Quota Performance Evaluation

[ https://issues.apache.org/jira/browse/KAFKA-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985697#comment-14985697 ] Jay Kreps commented on KAFKA-2528: -- [~lindong] Great! > Quota Performance Evaluation >

[jira] [Commented] (KAFKA-2702) ConfigDef toHtmlTable() sorts in a way that is a bit confusing

[ https://issues.apache.org/jira/browse/KAFKA-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14979782#comment-14979782 ] Jay Kreps commented on KAFKA-2702: -- Originally the presence or absence of a default indicated whether

[jira] [Commented] (KAFKA-2702) ConfigDef toHtmlTable() sorts in a way that is a bit confusing

[ https://issues.apache.org/jira/browse/KAFKA-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14979786#comment-14979786 ] Jay Kreps commented on KAFKA-2702: -- Also note that the check against NO_DEFAULT_VALUE isn't a check

[jira] [Commented] (KAFKA-2674) ConsumerRebalanceListener.onPartitionsRevoked() is not called on consumer close

[ https://issues.apache.org/jira/browse/KAFKA-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14979433#comment-14979433 ] Jay Kreps commented on KAFKA-2674: -- [~hachikuji] I don't have a ton to add. I think I added that class,

[jira] [Commented] (KAFKA-2702) ConfigDef toHtmlTable() sorts in a way that is a bit confusing

[ https://issues.apache.org/jira/browse/KAFKA-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14979554#comment-14979554 ] Jay Kreps commented on KAFKA-2702: -- Aren't things without default required? That rationale for that order

[jira] [Commented] (KAFKA-2472) Fix kafka ssl configs to not throw warnings

[ https://issues.apache.org/jira/browse/KAFKA-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14965348#comment-14965348 ] Jay Kreps commented on KAFKA-2472: -- [~gwenshap] This should work with plugins too. The config helper code

[jira] [Commented] (KAFKA-2580) Kafka Broker keeps file handles open for all log files (even if its not written to/read from)

[ https://issues.apache.org/jira/browse/KAFKA-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14964382#comment-14964382 ] Jay Kreps commented on KAFKA-2580: -- Yeah as [~toddpalino] says it is totally not graceful--it's a hard

[jira] [Commented] (KAFKA-2671) Enable starting Kafka server with a Properties object

[ https://issues.apache.org/jira/browse/KAFKA-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14964394#comment-14964394 ] Jay Kreps commented on KAFKA-2671: -- The use case for embedding Kafka is to make it work with existing

[jira] [Commented] (KAFKA-2580) Kafka Broker keeps file handles open for all log files (even if its not written to/read from)

[ https://issues.apache.org/jira/browse/KAFKA-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14963632#comment-14963632 ] Jay Kreps commented on KAFKA-2580: -- 10TB of space with 1GB segment files means about 10k FDs (though

[jira] [Comment Edited] (KAFKA-2580) Kafka Broker keeps file handles open for all log files (even if its not written to/read from)

[ https://issues.apache.org/jira/browse/KAFKA-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14963632#comment-14963632 ] Jay Kreps edited comment on KAFKA-2580 at 10/19/15 5:21 PM: 10TB of space with

[jira] [Commented] (KAFKA-2419) Allow certain Sensors to be garbage collected after inactivity

[ https://issues.apache.org/jira/browse/KAFKA-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14959543#comment-14959543 ] Jay Kreps commented on KAFKA-2419: -- It would be preferable to not need additional threads--we put

[jira] [Comment Edited] (KAFKA-2419) Allow certain Sensors to be garbage collected after inactivity

[ https://issues.apache.org/jira/browse/KAFKA-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14959543#comment-14959543 ] Jay Kreps edited comment on KAFKA-2419 at 10/15/15 8:19 PM: It would be

[jira] [Commented] (KAFKA-2397) leave group request

[ https://issues.apache.org/jira/browse/KAFKA-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14957550#comment-14957550 ] Jay Kreps commented on KAFKA-2397: -- Dunno if we closed the loop on the approach. [~onurkaraman] Yeah the

[jira] [Commented] (KAFKA-2592) Stop Writing the Change-log in store.put() / delete() for Non-transactional Store

[ https://issues.apache.org/jira/browse/KAFKA-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14933603#comment-14933603 ] Jay Kreps commented on KAFKA-2592: -- I think the impl strategy that Samza has is pretty good, it keeps an

[jira] [Commented] (KAFKA-2592) Stop Writing the Change-log in store.put() / delete() for Non-transactional Store

[ https://issues.apache.org/jira/browse/KAFKA-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14933673#comment-14933673 ] Jay Kreps commented on KAFKA-2592: -- That is generally true for all output, though, right? Not more true

[jira] [Commented] (KAFKA-2276) Initial patch for KIP-25

[ https://issues.apache.org/jira/browse/KAFKA-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14741225#comment-14741225 ] Jay Kreps commented on KAFKA-2276: -- [~granders] This is common code so it should go under

[jira] [Comment Edited] (KAFKA-2528) Quota Performance Evaluation

[ https://issues.apache.org/jira/browse/KAFKA-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14739660#comment-14739660 ] Jay Kreps edited comment on KAFKA-2528 at 9/10/15 9:44 PM: --- Yeah, sorry separate

[jira] [Commented] (KAFKA-2528) Quota Performance Evaluation

[ https://issues.apache.org/jira/browse/KAFKA-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14739660#comment-14739660 ] Jay Kreps commented on KAFKA-2528: -- Yeah, sorry separate thought. What I'm trying to figure out is how

[jira] [Commented] (KAFKA-2528) Quota Performance Evaluation

[ https://issues.apache.org/jira/browse/KAFKA-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14739917#comment-14739917 ] Jay Kreps commented on KAFKA-2528: -- Yeah that makes sense. So if that were the case the artifact would go

[jira] [Commented] (KAFKA-2528) Quota Performance Evaluation

[ https://issues.apache.org/jira/browse/KAFKA-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14739420#comment-14739420 ] Jay Kreps commented on KAFKA-2528: -- This is a great evaluation. It looks from the results like there must

[jira] [Commented] (KAFKA-2528) Quota Performance Evaluation

[ https://issues.apache.org/jira/browse/KAFKA-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14739493#comment-14739493 ] Jay Kreps commented on KAFKA-2528: -- I mention it because I have had to implement that kind of throttling

[jira] [Commented] (KAFKA-2528) Quota Performance Evaluation

[ https://issues.apache.org/jira/browse/KAFKA-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14739585#comment-14739585 ] Jay Kreps commented on KAFKA-2528: -- I guess my expectation is that if I run a producer perf test or

[jira] [Resolved] (KAFKA-2523) New consumer doesn't check magic version

[ https://issues.apache.org/jira/browse/KAFKA-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-2523. -- Resolution: Duplicate > New consumer doesn't check magic version >

[jira] [Created] (KAFKA-2523) New consumer doesn't check magic version

Jay Kreps created KAFKA-2523: Summary: New consumer doesn't check magic version Key: KAFKA-2523 URL: https://issues.apache.org/jira/browse/KAFKA-2523 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-2510) Prevent broker from re-replicating / losing data due to disk misconfiguration

[ https://issues.apache.org/jira/browse/KAFKA-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732096#comment-14732096 ] Jay Kreps commented on KAFKA-2510: -- @gwen I think maybe I'm confused. The discussion in the ticket is all

[jira] [Comment Edited] (KAFKA-2510) Prevent broker from re-replicating / losing data due to disk misconfiguration

[ https://issues.apache.org/jira/browse/KAFKA-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732096#comment-14732096 ] Jay Kreps edited comment on KAFKA-2510 at 9/5/15 8:23 PM: -- [~gwenshap] I think

[jira] [Commented] (KAFKA-2397) leave group request

[ https://issues.apache.org/jira/browse/KAFKA-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14731052#comment-14731052 ] Jay Kreps commented on KAFKA-2397: -- Couple thoughts: 1. [~hachikuji] Does this need to be in the next

[jira] [Commented] (KAFKA-2397) leave group request

[ https://issues.apache.org/jira/browse/KAFKA-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14731091#comment-14731091 ] Jay Kreps commented on KAFKA-2397: -- [~hachikuji] Makes sense. > leave group request >

[jira] [Commented] (KAFKA-2510) Prevent broker from re-replicating / losing data due to disk misconfiguration

[ https://issues.apache.org/jira/browse/KAFKA-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14731497#comment-14731497 ] Jay Kreps commented on KAFKA-2510: -- I actually think we shouldn't prevent this. In our replication model

[jira] [Comment Edited] (KAFKA-2510) Prevent broker from re-replicating / losing data due to disk misconfiguration

[ https://issues.apache.org/jira/browse/KAFKA-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14731497#comment-14731497 ] Jay Kreps edited comment on KAFKA-2510 at 9/4/15 9:56 PM: -- I actually think we

[jira] [Commented] (KAFKA-2496) New consumer from trunk doesn't work with 0.8.2.1 brokers

[ https://issues.apache.org/jira/browse/KAFKA-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726448#comment-14726448 ] Jay Kreps commented on KAFKA-2496: -- The first response is expected. The group management feature didn't

[jira] [Commented] (KAFKA-2486) New consumer performance

[ https://issues.apache.org/jira/browse/KAFKA-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14723615#comment-14723615 ] Jay Kreps commented on KAFKA-2486: -- I don't think we need to do anything special for the 0 wait time

[jira] [Commented] (KAFKA-2486) New consumer performance

[ https://issues.apache.org/jira/browse/KAFKA-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14724079#comment-14724079 ] Jay Kreps commented on KAFKA-2486: -- Where does this leave perf for the new consumer vs old? Maybe that's

[jira] [Commented] (KAFKA-2486) New consumer performance

[ https://issues.apache.org/jira/browse/KAFKA-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14724448#comment-14724448 ] Jay Kreps commented on KAFKA-2486: -- [~ewencp] Nightly will be awesome! I think what I am asking is more

[jira] [Commented] (KAFKA-2486) New consumer performance

[ 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}

[jira] [Commented] (KAFKA-2486) New consumer performance

[ 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

[jira] [Commented] (KAFKA-2486) New consumer performance

[ 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

[jira] [Commented] (KAFKA-2486) New consumer performance

[ 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

[jira] [Commented] (KAFKA-2367) Add Copycat runtime data API

[ https://issues.apache.org/jira/browse/KAFKA-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14712472#comment-14712472 ] Jay Kreps commented on KAFKA-2367: -- On unions: they were kind of a disaster at LinkedIn.

  1   2   3   4   5   6   7   8   9   10   >