[jira] [Created] (KAFKA-6559) Iterate record sets before calling Log.append

Todd Palino created KAFKA-6559: -- Summary: Iterate record sets before calling Log.append Key: KAFKA-6559 URL: https://issues.apache.org/jira/browse/KAFKA-6559 Project: Kafka Issue Type: Improveme

[jira] [Updated] (KAFKA-5056) Shuffling of partitions in old consumer fetch requests removed

[ https://issues.apache.org/jira/browse/KAFKA-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Palino updated KAFKA-5056: --- Summary: Shuffling of partitions in old consumer fetch requests removed (was: Shuffling of partitions

[jira] [Updated] (KAFKA-5056) Shuffling of partitions in old consume fetch requests removed

[ https://issues.apache.org/jira/browse/KAFKA-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Palino updated KAFKA-5056: --- Reviewer: Joel Koshy Status: Patch Available (was: In Progress) > Shuffling of partitions in ol

[jira] [Work started] (KAFKA-5056) Shuffling of partitions in old consume fetch requests removed

[ https://issues.apache.org/jira/browse/KAFKA-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5056 started by Todd Palino. -- > Shuffling of partitions in old consume fetch requests removed > ---

[jira] [Created] (KAFKA-5056) Shuffling of partitions in old consume fetch requests removed

Todd Palino created KAFKA-5056: -- Summary: Shuffling of partitions in old consume fetch requests removed Key: KAFKA-5056 URL: https://issues.apache.org/jira/browse/KAFKA-5056 Project: Kafka Issu

[jira] [Commented] (KAFKA-1342) Slow controlled shutdowns can result in stale shutdown requests

[ https://issues.apache.org/jira/browse/KAFKA-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893728#comment-15893728 ] Todd Palino commented on KAFKA-1342: [~wushujames], I'm not sure about increasing the

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15700938#comment-15700938 ] Todd Palino commented on KAFKA-3959: +1 as well. I think keeping the config/server.pro

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668010#comment-15668010 ] Todd Palino commented on KAFKA-3959: As noted, I just want the config enforced. If RF=

[jira] [Commented] (KAFKA-4050) Allow configuration of the PRNG used for SSL

[ https://issues.apache.org/jira/browse/KAFKA-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15425756#comment-15425756 ] Todd Palino commented on KAFKA-4050: So first off, yes, the thread dump (which [~jjkos

[jira] [Commented] (KAFKA-4050) Allow configuration of the PRNG used for SSL

[ https://issues.apache.org/jira/browse/KAFKA-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15423400#comment-15423400 ] Todd Palino commented on KAFKA-4050: It appears to be called every time something need

[jira] [Created] (KAFKA-4050) Allow configuration of the PRNG used for SSL

Todd Palino created KAFKA-4050: -- Summary: Allow configuration of the PRNG used for SSL Key: KAFKA-4050 URL: https://issues.apache.org/jira/browse/KAFKA-4050 Project: Kafka Issue Type: Improvemen

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420091#comment-15420091 ] Todd Palino commented on KAFKA-3959: If that's the case, then the default should be se

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419365#comment-15419365 ] Todd Palino commented on KAFKA-3959: Agree with Onur 100% here. We've been running int

[jira] [Commented] (KAFKA-3797) Improve security of __consumer_offsets topic

[ https://issues.apache.org/jira/browse/KAFKA-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323930#comment-15323930 ] Todd Palino commented on KAFKA-3797: Obviously we can't do something like that with a

[jira] [Commented] (KAFKA-3797) Improve security of __consumer_offsets topic

[ https://issues.apache.org/jira/browse/KAFKA-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318854#comment-15318854 ] Todd Palino commented on KAFKA-3797: I think the first option is more reasonable, and

[jira] [Commented] (KAFKA-3725) Update documentation with regards to XFS

[ https://issues.apache.org/jira/browse/KAFKA-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312288#comment-15312288 ] Todd Palino commented on KAFKA-3725: I'll take a look at this and put together a PR wi

[jira] [Assigned] (KAFKA-3725) Update documentation with regards to XFS

[ https://issues.apache.org/jira/browse/KAFKA-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Palino reassigned KAFKA-3725: -- Assignee: Todd Palino > Update documentation with regards to XFS >

[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&focusedCommentId=15126292#comment-15126292 ] Todd Palino commented on KAFKA-3174: Yeah, definitely no problems with Java 1.8. We've

[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&focusedCommentId=15065636#comment-15065636 ] Todd Palino commented on KAFKA-3015: [~jkreps] So yes, I'm essentially saying that I w

[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&focusedCommentId=15065239#comment-15065239 ] Todd Palino commented on KAFKA-3015: While this seems good on the surface, it makes it

[jira] [Commented] (KAFKA-2759) Mirror maker can leave gaps of missing messages if the process dies after a partition is reset and before the first offset commit

[ https://issues.apache.org/jira/browse/KAFKA-2759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994590#comment-14994590 ] Todd Palino commented on KAFKA-2759: The thought we had internally on the situation in

[jira] [Commented] (KAFKA-2235) LogCleaner offset map overflow

[ https://issues.apache.org/jira/browse/KAFKA-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14971806#comment-14971806 ] Todd Palino commented on KAFKA-2235: I don't think we can. I have already increased it

[jira] [Commented] (KAFKA-2235) LogCleaner offset map overflow

[ https://issues.apache.org/jira/browse/KAFKA-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14971740#comment-14971740 ] Todd Palino commented on KAFKA-2235: I'm sure [~jjkoshy] will follow along with more d

[jira] [Commented] (KAFKA-2017) Persist Coordinator State for Coordinator Failover

[ https://issues.apache.org/jira/browse/KAFKA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14964228#comment-14964228 ] Todd Palino commented on KAFKA-2017: I think we definitely need to maintain the abilit

[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&focusedCommentId=14964003#comment-14964003 ] Todd Palino commented on KAFKA-2580: It's about as graceful as an OOM, which is to say

[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&focusedCommentId=14963986#comment-14963986 ] Todd Palino commented on KAFKA-2580: I agree with [~jkreps] here, that having a high F

[jira] [Commented] (KAFKA-2017) Persist Coordinator State for Coordinator Failover

[ https://issues.apache.org/jira/browse/KAFKA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960809#comment-14960809 ] Todd Palino commented on KAFKA-2017: Just to throw in my 2 cents here, I don't think t

[jira] [Commented] (KAFKA-1566) Kafka environment configuration (kafka-env.sh)

[ https://issues.apache.org/jira/browse/KAFKA-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708282#comment-14708282 ] Todd Palino commented on KAFKA-1566: This makes a lot of sense. We don't use any of th

[jira] [Commented] (KAFKA-2252) Socket connection closing is logged, but not corresponding opening of socket

[ https://issues.apache.org/jira/browse/KAFKA-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586437#comment-14586437 ] Todd Palino commented on KAFKA-2252: I moved the normal connection closed message to D

[jira] [Assigned] (KAFKA-2175) Reduce server log verbosity at info level

[ https://issues.apache.org/jira/browse/KAFKA-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Palino reassigned KAFKA-2175: -- Assignee: Todd Palino (was: Neha Narkhede) > Reduce server log verbosity at info level > -

[jira] [Updated] (KAFKA-2175) Reduce server log verbosity at info level

[ https://issues.apache.org/jira/browse/KAFKA-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Palino updated KAFKA-2175: --- Attachment: KAFKA-2175.patch > Reduce server log verbosity at info level > ---

[jira] [Updated] (KAFKA-2175) Reduce server log verbosity at info level

[ https://issues.apache.org/jira/browse/KAFKA-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Palino updated KAFKA-2175: --- Status: Patch Available (was: Open) > Reduce server log verbosity at info level > ---

[jira] [Created] (KAFKA-2175) Reduce server log verbosity at info level

Todd Palino created KAFKA-2175: -- Summary: Reduce server log verbosity at info level Key: KAFKA-2175 URL: https://issues.apache.org/jira/browse/KAFKA-2175 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-1342) Slow controlled shutdowns can result in stale shutdown requests

[ https://issues.apache.org/jira/browse/KAFKA-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484278#comment-14484278 ] Todd Palino commented on KAFKA-1342: Bump I think we need to revive this. We have a "

[jira] [Created] (KAFKA-2012) Broker should automatically handle corrupt index files

Todd Palino created KAFKA-2012: -- Summary: Broker should automatically handle corrupt index files Key: KAFKA-2012 URL: https://issues.apache.org/jira/browse/KAFKA-2012 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-1987) Potential race condition in partition creation

Todd Palino created KAFKA-1987: -- Summary: Potential race condition in partition creation Key: KAFKA-1987 URL: https://issues.apache.org/jira/browse/KAFKA-1987 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-1648) Round robin consumer balance throws an NPE when there are no topics

Todd Palino created KAFKA-1648: -- Summary: Round robin consumer balance throws an NPE when there are no topics Key: KAFKA-1648 URL: https://issues.apache.org/jira/browse/KAFKA-1648 Project: Kafka

[jira] [Resolved] (KAFKA-1588) Offset response does not support two requests for the same topic/partition combo

[ https://issues.apache.org/jira/browse/KAFKA-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Palino resolved KAFKA-1588. Resolution: Won't Fix > Offset response does not support two requests for the same topic/partition

[jira] [Commented] (KAFKA-1588) Offset response does not support two requests for the same topic/partition combo

[ https://issues.apache.org/jira/browse/KAFKA-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14114814#comment-14114814 ] Todd Palino commented on KAFKA-1588: I believe that since this involves significant ch

[jira] [Commented] (KAFKA-1588) Offset response does not support two requests for the same topic/partition combo

[ https://issues.apache.org/jira/browse/KAFKA-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105601#comment-14105601 ] Todd Palino commented on KAFKA-1588: Thanks for digging into that [~sriharsha]. I had

[jira] [Commented] (KAFKA-1605) Producer should not require metadata.broker.list

[ https://issues.apache.org/jira/browse/KAFKA-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14104581#comment-14104581 ] Todd Palino commented on KAFKA-1605: There are a lot of concerns with this... 1) We a

[jira] [Commented] (KAFKA-1605) Producer should not require metadata.broker.list

[ https://issues.apache.org/jira/browse/KAFKA-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14104110#comment-14104110 ] Todd Palino commented on KAFKA-1605: Upcoming work for the consumer is going to move c

[jira] [Created] (KAFKA-1599) Change preferred replica election admin command to handle large clusters

Todd Palino created KAFKA-1599: -- Summary: Change preferred replica election admin command to handle large clusters Key: KAFKA-1599 URL: https://issues.apache.org/jira/browse/KAFKA-1599 Project: Kafka

[jira] [Commented] (KAFKA-1588) Offset response does not support two requests for the same topic/partition combo

[ https://issues.apache.org/jira/browse/KAFKA-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096083#comment-14096083 ] Todd Palino commented on KAFKA-1588: When working with this, I am sending my requests

[jira] [Updated] (KAFKA-1588) Offset response does not support two requests for the same topic/partition combo

[ https://issues.apache.org/jira/browse/KAFKA-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Palino updated KAFKA-1588: --- Description: When performing an OffsetRequest, if you request the same topic and partition combinati

[jira] [Created] (KAFKA-1588) Offset response does not support two requests for the same topic/partition combo

Todd Palino created KAFKA-1588: -- Summary: Offset response does not support two requests for the same topic/partition combo Key: KAFKA-1588 URL: https://issues.apache.org/jira/browse/KAFKA-1588 Project: K

[jira] [Commented] (KAFKA-1581) Log cleaner should have an option to ignore messages without keys

[ https://issues.apache.org/jira/browse/KAFKA-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14091622#comment-14091622 ] Todd Palino commented on KAFKA-1581: I suggest that you should just skip any invalid m

[jira] [Commented] (KAFKA-1476) Get a list of consumer groups

[ https://issues.apache.org/jira/browse/KAFKA-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066488#comment-14066488 ] Todd Palino commented on KAFKA-1476: I tend to agree, ~jkreps. We currently have kafka

[jira] [Created] (KAFKA-1440) Per-request tracing

Todd Palino created KAFKA-1440: -- Summary: Per-request tracing Key: KAFKA-1440 URL: https://issues.apache.org/jira/browse/KAFKA-1440 Project: Kafka Issue Type: Improvement Components: c

[jira] [Created] (KAFKA-1276) Provide a list of config overrides available when running kafka.topics

Todd Palino created KAFKA-1276: -- Summary: Provide a list of config overrides available when running kafka.topics Key: KAFKA-1276 URL: https://issues.apache.org/jira/browse/KAFKA-1276 Project: Kafka

[jira] [Commented] (KAFKA-1182) Topic not created if number of live brokers less than # replicas

[ https://issues.apache.org/jira/browse/KAFKA-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903790#comment-13903790 ] Todd Palino commented on KAFKA-1182: I really don't think it needs to be that complica

[jira] [Commented] (KAFKA-1182) Topic not created if number of live brokers less than # replicas

[ https://issues.apache.org/jira/browse/KAFKA-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894781#comment-13894781 ] Todd Palino commented on KAFKA-1182: I'll have to side with Clark on this one. Given a

[jira] [Commented] (KAFKA-1125) Add options to let admin tools block until finish

[ https://issues.apache.org/jira/browse/KAFKA-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889898#comment-13889898 ] Todd Palino commented on KAFKA-1125: I believe an option for each of these tools to ma