[jira] [Updated] (KAFKA-3721) UpdateMetadataRequest V2 should be in API version 0.10.0-IV1

[ https://issues.apache.org/jira/browse/KAFKA-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3721: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 1400 [https:

[jira] [Created] (KAFKA-3755) tightening the offset check in ReplicaFetcherThread

Jun Rao created KAFKA-3755: -- Summary: tightening the offset check in ReplicaFetcherThread Key: KAFKA-3755 URL: https://issues.apache.org/jira/browse/KAFKA-3755 Project: Kafka Issue Type: Improvement

[jira] [Created] (KAFKA-3762) Log.loadSegments() should log the message in exception

Jun Rao created KAFKA-3762: -- Summary: Log.loadSegments() should log the message in exception Key: KAFKA-3762 URL: https://issues.apache.org/jira/browse/KAFKA-3762 Project: Kafka Issue Type: Improvem

[jira] [Commented] (KAFKA-3689) ERROR Processor got uncaught exception. (kafka.network.Processor)

[ https://issues.apache.org/jira/browse/KAFKA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15303301#comment-15303301 ] Jun Rao commented on KAFKA-3689: Hmm, interesting. I assume that all the errors are for th

[jira] [Resolved] (KAFKA-3682) ArrayIndexOutOfBoundsException thrown by SkimpyOffsetMap.get() when full

[ https://issues.apache.org/jira/browse/KAFKA-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-3682. Resolution: Fixed Fix Version/s: 0.10.1.0 Issue resolved by pull request 1352 [https://github.com/apa

[jira] [Commented] (KAFKA-3755) tightening the offset check in ReplicaFetcherThread

[ https://issues.apache.org/jira/browse/KAFKA-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313028#comment-15313028 ] Jun Rao commented on KAFKA-3755: [~imandhan], we can just add a unit test that calls log.a

[jira] [Updated] (KAFKA-3689) ERROR Processor got uncaught exception. (kafka.network.Processor)

[ https://issues.apache.org/jira/browse/KAFKA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3689: --- Attachment: kafka-3689-instrumentation.patch [~buvana.rama...@nokia.com], our current logging doesn't tell you

[jira] [Commented] (KAFKA-3693) Race condition between highwatermark-checkpoint thread and handleLeaderAndIsrRequest at broker start-up

[ https://issues.apache.org/jira/browse/KAFKA-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313234#comment-15313234 ] Jun Rao commented on KAFKA-3693: [~maysamyabandeh], the logic in KafkaController.shutdownB

[jira] [Commented] (KAFKA-3693) Race condition between highwatermark-checkpoint thread and handleLeaderAndIsrRequest at broker start-up

[ https://issues.apache.org/jira/browse/KAFKA-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313441#comment-15313441 ] Jun Rao commented on KAFKA-3693: [~maysamyabandeh], yes, I agree it would be better if the

[jira] [Commented] (KAFKA-3693) Race condition between highwatermark-checkpoint thread and handleLeaderAndIsrRequest at broker start-up

[ https://issues.apache.org/jira/browse/KAFKA-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15315086#comment-15315086 ] Jun Rao commented on KAFKA-3693: Hmm, if broker 16 was down at 06:17:02,012, it shouldn't

[jira] [Commented] (KAFKA-3693) Race condition between highwatermark-checkpoint thread and handleLeaderAndIsrRequest at broker start-up

[ https://issues.apache.org/jira/browse/KAFKA-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15316652#comment-15316652 ] Jun Rao commented on KAFKA-3693: Yes, if the controller detects that a broker is down, it

[jira] [Commented] (KAFKA-3693) Race condition between highwatermark-checkpoint thread and handleLeaderAndIsrRequest at broker start-up

[ https://issues.apache.org/jira/browse/KAFKA-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318753#comment-15318753 ] Jun Rao commented on KAFKA-3693: [~maysam], when broker 16 completes the shutdown, the con

[jira] [Commented] (KAFKA-1211) Hold the produce request with ack > 1 in purgatory until replicas' HW has larger than the produce offset

[ https://issues.apache.org/jira/browse/KAFKA-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318799#comment-15318799 ] Jun Rao commented on KAFKA-1211: This is still an issue. It can cause data loss if the lea

[jira] [Commented] (KAFKA-3806) Adjust default values of log.retention.hours and offsets.retention.minutes

[ https://issues.apache.org/jira/browse/KAFKA-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320931#comment-15320931 ] Jun Rao commented on KAFKA-3806: offsets.retention.minutes is designed to handle the case

[jira] [Commented] (KAFKA-3806) Adjust default values of log.retention.hours and offsets.retention.minutes

[ https://issues.apache.org/jira/browse/KAFKA-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321710#comment-15321710 ] Jun Rao commented on KAFKA-3806: [~wushujames], committing offsets on every poll is likely

[jira] [Commented] (KAFKA-3806) Adjust default values of log.retention.hours and offsets.retention.minutes

[ https://issues.apache.org/jira/browse/KAFKA-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323521#comment-15323521 ] Jun Rao commented on KAFKA-3806: [~dwatzke], I think the original intention is that consum

[jira] [Commented] (KAFKA-3693) Race condition between highwatermark-checkpoint thread and handleLeaderAndIsrRequest at broker start-up

[ https://issues.apache.org/jira/browse/KAFKA-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323675#comment-15323675 ] Jun Rao commented on KAFKA-3693: [~maysamyabandeh], the controller detects broker failure

[jira] [Commented] (KAFKA-1120) Controller could miss a broker state change

[ https://issues.apache.org/jira/browse/KAFKA-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325496#comment-15325496 ] Jun Rao commented on KAFKA-1120: A better way is probably for the controller to store the

[jira] [Commented] (KAFKA-3693) Race condition between highwatermark-checkpoint thread and handleLeaderAndIsrRequest at broker start-up

[ https://issues.apache.org/jira/browse/KAFKA-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325510#comment-15325510 ] Jun Rao commented on KAFKA-3693: [~maysamyabandeh], thanks for confirming this. The root o

[jira] [Created] (KAFKA-3827) log.message.format.version should default to inter.broker.protocol.version

Jun Rao created KAFKA-3827: -- Summary: log.message.format.version should default to inter.broker.protocol.version Key: KAFKA-3827 URL: https://issues.apache.org/jira/browse/KAFKA-3827 Project: Kafka

[jira] [Commented] (KAFKA-3693) Race condition between highwatermark-checkpoint thread and handleLeaderAndIsrRequest at broker start-up

[ https://issues.apache.org/jira/browse/KAFKA-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15332684#comment-15332684 ] Jun Rao commented on KAFKA-3693: [~maysamyabandeh], that by itself may not be a bad idea.

[jira] [Resolved] (KAFKA-3755) tightening the offset check in ReplicaFetcherThread

[ https://issues.apache.org/jira/browse/KAFKA-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-3755. Resolution: Not A Problem As notes in the PR, looks like Log.append() already has that check. See https://g

[jira] [Updated] (KAFKA-3868) New producer metric record-size-avg does not provide average record size as advertised

[ https://issues.apache.org/jira/browse/KAFKA-3868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3868: --- Assignee: (was: Jun Rao) > New producer metric record-size-avg does not provide average record size as >

[jira] [Commented] (KAFKA-3827) log.message.format.version should default to inter.broker.protocol.version

[ https://issues.apache.org/jira/browse/KAFKA-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15340549#comment-15340549 ] Jun Rao commented on KAFKA-3827: [~ewencp], [~ijuma], the issue is that log.message.format

[jira] [Commented] (KAFKA-3868) New producer metric record-size-avg does not provide average record size as advertised

[ https://issues.apache.org/jira/browse/KAFKA-3868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15340565#comment-15340565 ] Jun Rao commented on KAFKA-3868: One caveat is that record() requires synchronization. So,

[jira] [Commented] (KAFKA-1429) Yet another deadlock in controller shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343716#comment-15343716 ] Jun Rao commented on KAFKA-1429: [~pengwei], yes, it's a real bug. Thanks for finding and

[jira] [Commented] (KAFKA-3915) LogCleaner IO buffers do not account for potential size difference due to message format change

[ https://issues.apache.org/jira/browse/KAFKA-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353396#comment-15353396 ] Jun Rao commented on KAFKA-3915: [~twbecker], thanks for reporting this. Keeping the old

[jira] [Commented] (KAFKA-3810) replication of internal topics should not be limited by replica.fetch.max.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354011#comment-15354011 ] Jun Rao commented on KAFKA-3810: [~onurkaraman], [~becket_qin], thanks for the patch. I ha

[jira] [Commented] (KAFKA-3252) compression type for a topic should be used during log compaction

[ https://issues.apache.org/jira/browse/KAFKA-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354083#comment-15354083 ] Jun Rao commented on KAFKA-3252: [~omkreddy], sorry for creating the duplicated jira. I to

[jira] [Commented] (KAFKA-3915) LogCleaner IO buffers do not account for potential size difference due to message format change

[ https://issues.apache.org/jira/browse/KAFKA-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354183#comment-15354183 ] Jun Rao commented on KAFKA-3915: The writeBuffer is set to maxMessageSize. We can't really

[jira] [Commented] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355393#comment-15355393 ] Jun Rao commented on KAFKA-3919: [~BigAndy], thanks for reporting and investigating this.

[jira] [Commented] (KAFKA-3915) LogCleaner IO buffers do not account for potential size difference due to message format change

[ https://issues.apache.org/jira/browse/KAFKA-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357996#comment-15357996 ] Jun Rao commented on KAFKA-3915: Yes, we could choose to only keep the old message format

[jira] [Commented] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362865#comment-15362865 ] Jun Rao commented on KAFKA-3919: [~BigAndy], thanks for the investigation and the addition

[jira] [Commented] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365046#comment-15365046 ] Jun Rao commented on KAFKA-3919: [~BigAndy], yes, you are right. We actually do index base

[jira] [Commented] (KAFKA-3894) Log Cleaner thread crashes and never restarts

[ https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15366339#comment-15366339 ] Jun Rao commented on KAFKA-3894: [~wushujames], this is slightly different from KAFKA-3810

[jira] [Commented] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367781#comment-15367781 ] Jun Rao commented on KAFKA-3919: [~BigAndy], yes, the fix could be involved and we haven't

[jira] [Created] (KAFKA-3939) add new consumer metrics in docs

Jun Rao created KAFKA-3939: -- Summary: add new consumer metrics in docs Key: KAFKA-3939 URL: https://issues.apache.org/jira/browse/KAFKA-3939 Project: Kafka Issue Type: Task Components: con

[jira] [Created] (KAFKA-3940) Log should check the return value of dir.mkdirs()

Jun Rao created KAFKA-3940: -- Summary: Log should check the return value of dir.mkdirs() Key: KAFKA-3940 URL: https://issues.apache.org/jira/browse/KAFKA-3940 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-3940) Log should check the return value of dir.mkdirs()

[ https://issues.apache.org/jira/browse/KAFKA-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3940: --- Labels: newbie (was: ) > Log should check the return value of dir.mkdirs() >

[jira] [Commented] (KAFKA-3940) Log should check the return value of dir.mkdirs()

[ https://issues.apache.org/jira/browse/KAFKA-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368315#comment-15368315 ] Jun Rao commented on KAFKA-3940: Also, instead of using File.mkdirs(), it may be better to

[jira] [Updated] (KAFKA-3163) KIP-33 - Add a time based log index to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3163: --- Attachment: 00113931.timeindex 00113931.log Also, I ran the following

[jira] [Updated] (KAFKA-3111) java.lang.ArithmeticException: / by zero in ConsumerPerformance

[ https://issues.apache.org/jira/browse/KAFKA-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3111: --- Resolution: Fixed Fix Version/s: 0.10.1.0 Status: Resolved (was: Patch Available) Issue res

[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&focusedCommentId=15371583#comment-15371583 ] Jun Rao commented on KAFKA-1464: Currently, our leader balancing logic happens automatical

[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&focusedCommentId=15372039#comment-15372039 ] Jun Rao commented on KAFKA-1464: The controller does leader balancing. So, auto.leader.reb

[jira] [Commented] (KAFKA-3940) Log should check the return value of dir.mkdirs()

[ https://issues.apache.org/jira/browse/KAFKA-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372146#comment-15372146 ] Jun Rao commented on KAFKA-3940: [~imandhan], we don't need to change dir to Files. We jus

[jira] [Updated] (KAFKA-2945) CreateTopic - protocol and server side implementation

[ https://issues.apache.org/jira/browse/KAFKA-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2945: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 1489 [https:

[jira] [Commented] (KAFKA-2205) Generalize TopicConfigManager to handle multiple entity configs

[ https://issues.apache.org/jira/browse/KAFKA-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375527#comment-15375527 ] Jun Rao commented on KAFKA-2205: [~thesquelched], thanks for reporting that. Do you want t

[jira] [Created] (KAFKA-3996) ByteBufferMessageSet.writeTo() should be non-blocking

Jun Rao created KAFKA-3996: -- Summary: ByteBufferMessageSet.writeTo() should be non-blocking Key: KAFKA-3996 URL: https://issues.apache.org/jira/browse/KAFKA-3996 Project: Kafka Issue Type: Bug A

[jira] [Commented] (KAFKA-3996) ByteBufferMessageSet.writeTo() should be non-blocking

[ https://issues.apache.org/jira/browse/KAFKA-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394755#comment-15394755 ] Jun Rao commented on KAFKA-3996: To address this issue, we will need to get rid of the whi

[jira] [Updated] (KAFKA-3689) Exception when attempting to decrease connection count for address with no connections

[ https://issues.apache.org/jira/browse/KAFKA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3689: --- Assignee: (was: Jun Rao) > Exception when attempting to decrease connection count for address with no > c

[jira] [Updated] (KAFKA-3996) ByteBufferMessageSet.writeTo() should be non-blocking

[ https://issues.apache.org/jira/browse/KAFKA-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3996: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 1669 [https:

[jira] [Updated] (KAFKA-3924) Data loss due to halting when LEO is larger than leader's LEO

[ https://issues.apache.org/jira/browse/KAFKA-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3924: --- Resolution: Fixed Fix Version/s: 0.10.0.1 Status: Resolved (was: Patch Available) Issue res

[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&focusedCommentId=15402263#comment-15402263 ] Jun Rao commented on KAFKA-2063: [~nepal], thanks for the proposal. For a), which server

[jira] [Commented] (KAFKA-1211) Hold the produce request with ack > 1 in purgatory until replicas' HW has larger than the produce offset

[ https://issues.apache.org/jira/browse/KAFKA-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402622#comment-15402622 ] Jun Rao commented on KAFKA-1211: The following is a draft proposal. [~fpj], does that look

[jira] [Commented] (KAFKA-4009) Data corruption or EIO leads to data loss

[ https://issues.apache.org/jira/browse/KAFKA-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402740#comment-15402740 ] Jun Rao commented on KAFKA-4009: [~aganesan], thanks for reporting this. In your test, did

[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&focusedCommentId=15404147#comment-15404147 ] Jun Rao commented on KAFKA-2063: For #3, the main reason for people to customize partition

[jira] [Commented] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15404314#comment-15404314 ] Jun Rao commented on KAFKA-3042: Thinking about this a bit more. An alternative approach i

[jira] [Commented] (KAFKA-1211) Hold the produce request with ack > 1 in purgatory until replicas' HW has larger than the produce offset

[ https://issues.apache.org/jira/browse/KAFKA-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15404404#comment-15404404 ] Jun Rao commented on KAFKA-1211: [~fpj], for #1 and #2, there are a couple scenarios that

[jira] [Commented] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15404901#comment-15404901 ] Jun Rao commented on KAFKA-3042: [~onurkaraman], there are a couple of things. 1. Current

[jira] [Assigned] (KAFKA-3875) Transient test failure: kafka.api.SslProducerSendTest.testSendNonCompressedMessageWithCreateTime

[ https://issues.apache.org/jira/browse/KAFKA-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao reassigned KAFKA-3875: -- Assignee: Jun Rao > Transient test failure: > kafka.api.SslProducerSendTest.testSendNonCompressedMessa

[jira] [Commented] (KAFKA-3875) Transient test failure: kafka.api.SslProducerSendTest.testSendNonCompressedMessageWithCreateTime

[ https://issues.apache.org/jira/browse/KAFKA-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406737#comment-15406737 ] Jun Rao commented on KAFKA-3875: I took a look at this and found a few things. 1. The Ill

[jira] [Commented] (KAFKA-1211) Hold the produce request with ack > 1 in purgatory until replicas' HW has larger than the produce offset

[ https://issues.apache.org/jira/browse/KAFKA-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406915#comment-15406915 ] Jun Rao commented on KAFKA-1211: [~fpj], very good questions. 1. Yes, the idea is for the

[jira] [Commented] (KAFKA-3894) Log Cleaner thread crashes and never restarts

[ https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406970#comment-15406970 ] Jun Rao commented on KAFKA-3894: [~tcrayford-heroku], I chatted with [~jkreps] on this a b

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407964#comment-15407964 ] Jun Rao commented on KAFKA-3665: [~Ryan P], is SNI really relevant here? According to Raji

[jira] [Commented] (KAFKA-4009) Data corruption or EIO leads to data loss

[ https://issues.apache.org/jira/browse/KAFKA-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407990#comment-15407990 ] Jun Rao commented on KAFKA-4009: Thanks for the info. Then, N1 only discovered the issue d

[jira] [Created] (KAFKA-4019) LogCleaner should grow read/write buffer to max message size for the topic

Jun Rao created KAFKA-4019: -- Summary: LogCleaner should grow read/write buffer to max message size for the topic Key: KAFKA-4019 URL: https://issues.apache.org/jira/browse/KAFKA-4019 Project: Kafka

[jira] [Created] (KAFKA-4021) system tests need to enable trace level logging for controller and state-change log

Jun Rao created KAFKA-4021: -- Summary: system tests need to enable trace level logging for controller and state-change log Key: KAFKA-4021 URL: https://issues.apache.org/jira/browse/KAFKA-4021 Project: Kafka

[jira] [Commented] (KAFKA-3518) Transient failure in ReplicationTest.test_replication_with_broker_failure with ConsumerTimeoutException

[ https://issues.apache.org/jira/browse/KAFKA-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15408726#comment-15408726 ] Jun Rao commented on KAFKA-3518: Took a look at the log. The following are my findings. >

[jira] [Resolved] (KAFKA-3518) Transient failure in ReplicationTest.test_replication_with_broker_failure with ConsumerTimeoutException

[ https://issues.apache.org/jira/browse/KAFKA-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-3518. Resolution: Cannot Reproduce Closing the jira since it's likely fixed by KAFKA-3670. > Transient failure in

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410268#comment-15410268 ] Jun Rao commented on KAFKA-3665: [~Ryan P], thanks for the explanation. In the common case

[jira] [Commented] (KAFKA-1211) Hold the produce request with ack > 1 in purgatory until replicas' HW has larger than the produce offset

[ https://issues.apache.org/jira/browse/KAFKA-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412111#comment-15412111 ] Jun Rao commented on KAFKA-1211: [~fpj], yes, the idea is to always first write the new LG

[jira] [Commented] (KAFKA-1211) Hold the produce request with ack > 1 in purgatory until replicas' HW has larger than the produce offset

[ https://issues.apache.org/jira/browse/KAFKA-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412133#comment-15412133 ] Jun Rao commented on KAFKA-1211: [~fpj], for (a), this is because the leader needs to firs

[jira] [Commented] (KAFKA-3556) Improve group coordinator metrics

[ https://issues.apache.org/jira/browse/KAFKA-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412416#comment-15412416 ] Jun Rao commented on KAFKA-3556: It would also be useful to add metrics on the consumer si

[jira] [Commented] (KAFKA-2039) Update Scala to 2.10.5 and 2.11.6

[ https://issues.apache.org/jira/browse/KAFKA-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14382124#comment-14382124 ] Jun Rao commented on KAFKA-2039: Thanks for the patch. We will also need to change the sca

[jira] [Commented] (KAFKA-1595) Remove deprecated and slower scala JSON parser from kafka.consumer.TopicCount

[ https://issues.apache.org/jira/browse/KAFKA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14383111#comment-14383111 ] Jun Rao commented on KAFKA-1595: [~ijuma], we probably need to do a poll on the dev/user m

[jira] [Commented] (KAFKA-1634) Improve semantics of timestamp in OffsetCommitRequests and update documentation

[ https://issues.apache.org/jira/browse/KAFKA-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14383117#comment-14383117 ] Jun Rao commented on KAFKA-1634: Also, could you also update the protocol wiki (https://c

[jira] [Commented] (KAFKA-1546) Automate replica lag tuning

[ https://issues.apache.org/jira/browse/KAFKA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14384406#comment-14384406 ] Jun Rao commented on KAFKA-1546: Since the broker has moved to ConfigDef, we can generate

[jira] [Updated] (KAFKA-2044) Support requests and responses from o.a.k.common in KafkaApis

[ https://issues.apache.org/jira/browse/KAFKA-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2044: --- Resolution: Fixed Fix Version/s: 0.8.3 Status: Resolved (was: Patch Available) +1 for the l

[jira] [Commented] (KAFKA-1634) Improve semantics of timestamp in OffsetCommitRequests and update documentation

[ https://issues.apache.org/jira/browse/KAFKA-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385848#comment-14385848 ] Jun Rao commented on KAFKA-1634: Perhaps, we can do KAFKA-1841 together with KAFKA-2068. T

[jira] [Commented] (KAFKA-2068) Replace OffsetCommit Request/Response with org.apache.kafka.common.requests equivalent

[ https://issues.apache.org/jira/browse/KAFKA-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385850#comment-14385850 ] Jun Rao commented on KAFKA-2068: We may want to consider if it's better to do KAFKA-1841 t

[jira] [Commented] (KAFKA-1809) Refactor brokers to allow listening on multiple ports and IPs

[ https://issues.apache.org/jira/browse/KAFKA-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385906#comment-14385906 ] Jun Rao commented on KAFKA-1809: Thanks for the latest patch. Reviewed. Could you also pro

[jira] [Commented] (KAFKA-1546) Automate replica lag tuning

[ https://issues.apache.org/jira/browse/KAFKA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389322#comment-14389322 ] Jun Rao commented on KAFKA-1546: For the doc change, do we need to make the following chan

[jira] [Created] (KAFKA-2081) testUncleanLeaderElectionEnabledByTopicOverride transient failure

Jun Rao created KAFKA-2081: -- Summary: testUncleanLeaderElectionEnabledByTopicOverride transient failure Key: KAFKA-2081 URL: https://issues.apache.org/jira/browse/KAFKA-2081 Project: Kafka Issue Ty

[jira] [Updated] (KAFKA-2039) Update Scala to 2.10.5 and 2.11.6

[ https://issues.apache.org/jira/browse/KAFKA-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2039: --- Resolution: Fixed Fix Version/s: 0.8.3 Assignee: Ismael Juma Status: Resolved (was:

[jira] [Updated] (KAFKA-2013) benchmark test for the purgatory

[ https://issues.apache.org/jira/browse/KAFKA-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2013: --- Resolution: Fixed Fix Version/s: 0.8.3 Status: Resolved (was: Patch Available) Thanks for t

[jira] [Created] (KAFKA-2086) testRoundRobinPartitionAssignor transient failure

Jun Rao created KAFKA-2086: -- Summary: testRoundRobinPartitionAssignor transient failure Key: KAFKA-2086 URL: https://issues.apache.org/jira/browse/KAFKA-2086 Project: Kafka Issue Type: Sub-task

[jira] [Commented] (KAFKA-2078) Getting Selector [WARN] Error in I/O with host java.io.EOFException

[ https://issues.apache.org/jira/browse/KAFKA-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14391970#comment-14391970 ] Jun Rao commented on KAFKA-2078: Do you see ZK session timeout on the broker? With large m

[jira] [Updated] (KAFKA-2016) RollingBounceTest takes long

[ https://issues.apache.org/jira/browse/KAFKA-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2016: --- Resolution: Fixed Assignee: Ted Malaska Status: Resolved (was: Patch Available) Thanks for the

[jira] [Commented] (KAFKA-1961) Looks like its possible to delete _consumer_offsets topic

[ https://issues.apache.org/jira/browse/KAFKA-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393886#comment-14393886 ] Jun Rao commented on KAFKA-1961: [~ted.m], thanks for the patch. Just added a minor commen

[jira] [Created] (KAFKA-2089) MetadataTest transient failure

Jun Rao created KAFKA-2089: -- Summary: MetadataTest transient failure Key: KAFKA-2089 URL: https://issues.apache.org/jira/browse/KAFKA-2089 Project: Kafka Issue Type: Sub-task Affects Versions: 0

[jira] [Commented] (KAFKA-1809) Refactor brokers to allow listening on multiple ports and IPs

[ https://issues.apache.org/jira/browse/KAFKA-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395251#comment-14395251 ] Jun Rao commented on KAFKA-1809: The latest patch looks good to me. Left a few comments on

[jira] [Resolved] (KAFKA-1303) metadata request in the new producer can be delayed

[ https://issues.apache.org/jira/browse/KAFKA-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-1303. Resolution: Won't Fix I think this is less of an issue given that we have max.in.flight.requests.per.connec

[jira] [Commented] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395985#comment-14395985 ] Jun Rao commented on KAFKA-2082: [~sriharsha], the reason why ReplicaFetcherManager doesn'

[jira] [Commented] (KAFKA-2078) Getting Selector [WARN] Error in I/O with host java.io.EOFException

[ https://issues.apache.org/jira/browse/KAFKA-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395993#comment-14395993 ] Jun Rao commented on KAFKA-2078: I thought that you were reporting a producer side issue.

[jira] [Commented] (KAFKA-1293) Mirror maker housecleaning

[ https://issues.apache.org/jira/browse/KAFKA-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14396274#comment-14396274 ] Jun Rao commented on KAFKA-1293: [~mwarhaftig], granted wiki permission to you. > Mirror

[jira] [Updated] (KAFKA-1005) kafka.perf.ConsumerPerformance not shutting down consumer

[ https://issues.apache.org/jira/browse/KAFKA-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1005: --- Assignee: paul mackles > kafka.perf.ConsumerPerformance not shutting down consumer > -

[jira] [Updated] (KAFKA-2050) Avoid calling .size() on java.util.ConcurrentLinkedQueue

[ https://issues.apache.org/jira/browse/KAFKA-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2050: --- Assignee: Tim Brooks (was: Jay Kreps) > Avoid calling .size() on java.util.ConcurrentLinkedQueue > --

[jira] [Updated] (KAFKA-2002) It does not work when kafka_mx4jenable is false

[ https://issues.apache.org/jira/browse/KAFKA-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2002: --- Assignee: Yaguo Zhou (was: Jay Kreps) > It does not work when kafka_mx4jenable is false > ---

[jira] [Updated] (KAFKA-2024) Cleaner can generate unindexable log segments

[ https://issues.apache.org/jira/browse/KAFKA-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2024: --- Assignee: Rajini Sivaram > Cleaner can generate unindexable log segments > ---

[jira] [Updated] (KAFKA-1996) Scaladoc error: unknown tag parameter

[ https://issues.apache.org/jira/browse/KAFKA-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1996: --- Assignee: Yaguo Zhou > Scaladoc error: unknown tag parameter > - > >

<    1   2   3   4   5   6   7   8   9   10   >