[jira] [Commented] (KAFKA-1004) Handle topic event for trivial whitelist topic filters

[ https://issues.apache.org/jira/browse/KAFKA-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742351#comment-13742351 ] Jun Rao commented on KAFKA-1004: Thanks for the patch. That looks good. However, shouldn't

[jira] [Commented] (KAFKA-1004) Handle topic event for trivial whitelist topic filters

[ https://issues.apache.org/jira/browse/KAFKA-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742386#comment-13742386 ] Jun Rao commented on KAFKA-1004: Looks good to me. Joel, do you want to take another look?

[jira] [Commented] (KAFKA-992) Double Check on Broker Registration to Avoid False NodeExist Exception

[ https://issues.apache.org/jira/browse/KAFKA-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742837#comment-13742837 ] Jun Rao commented on KAFKA-992: --- Thanks for patch v14. Committed to 0.8.

[jira] [Commented] (KAFKA-649) Cleanup log4j logging

[ https://issues.apache.org/jira/browse/KAFKA-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13743888#comment-13743888 ] Jun Rao commented on KAFKA-649: --- Thanks for patch v6. Committed to 0.8.

[jira] [Commented] (KAFKA-990) Fix ReassignPartitionCommand and improve usability

[ https://issues.apache.org/jira/browse/KAFKA-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13743930#comment-13743930 ] Jun Rao commented on KAFKA-990: --- Thanks for patch v2. A few more comments. 2.1 I think it's

[jira] [Resolved] (KAFKA-1017) High number of open file handles in 0.8 producer

[ https://issues.apache.org/jira/browse/KAFKA-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-1017. Resolution: Fixed Fix Version/s: 0.8 Good patch. +1. Committed to 0.8. High

[jira] [Commented] (KAFKA-955) After a leader change, messages sent with ack=0 are lost

[ https://issues.apache.org/jira/browse/KAFKA-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13747692#comment-13747692 ] Jun Rao commented on KAFKA-955: --- Magnus, thanks for your comment. What you suggested is

[jira] [Commented] (KAFKA-975) Leader not local for partition when partition is leader (kafka.common.NotLeaderForPartitionException)

[ https://issues.apache.org/jira/browse/KAFKA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13748630#comment-13748630 ] Jun Rao commented on KAFKA-975: --- Could you describe how to reproduce the issue?

[jira] [Commented] (KAFKA-1012) Implement an Offset Manager and hook offset requests to it

[ https://issues.apache.org/jira/browse/KAFKA-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750580#comment-13750580 ] Jun Rao commented on KAFKA-1012: Thanks for the patch. This looks promising. Some

[jira] [Resolved] (KAFKA-677) Retention process gives exception if an empty segment is chosen for collection

[ https://issues.apache.org/jira/browse/KAFKA-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-677. --- Resolution: Cannot Reproduce No longer see this. Close it for now. Retention process gives

[jira] [Closed] (KAFKA-677) Retention process gives exception if an empty segment is chosen for collection

[ https://issues.apache.org/jira/browse/KAFKA-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-677. - Retention process gives exception if an empty segment is chosen for collection

[jira] [Assigned] (KAFKA-1029) Zookeeper leader election stuck in ephemeral node retry loop

[ https://issues.apache.org/jira/browse/KAFKA-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao reassigned KAFKA-1029: -- Assignee: Sam Meder (was: Neha Narkhede) Zookeeper leader election stuck in ephemeral node retry

[jira] [Assigned] (KAFKA-995) Enforce that the value for replica.fetch.max.bytes is always = the value for message.max.bytes

[ https://issues.apache.org/jira/browse/KAFKA-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao reassigned KAFKA-995: - Assignee: Sam Meder Enforce that the value for replica.fetch.max.bytes is always = the value for

[jira] [Resolved] (KAFKA-1031) Little modification to the stop script to be able to kill the proper process

[ https://issues.apache.org/jira/browse/KAFKA-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-1031. Resolution: Fixed Fix Version/s: 0.8 Assignee: Vladislav Pernin Thanks for the patch.

[jira] [Created] (KAFKA-1038) fetch response should use empty messageset instead of null when handling errors

Jun Rao created KAFKA-1038: -- Summary: fetch response should use empty messageset instead of null when handling errors Key: KAFKA-1038 URL: https://issues.apache.org/jira/browse/KAFKA-1038 Project: Kafka

[jira] [Updated] (KAFKA-1038) fetch response should use empty messageset instead of null when handling errors

[ https://issues.apache.org/jira/browse/KAFKA-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1038: --- Status: Patch Available (was: Open) fetch response should use empty messageset instead of null when

[jira] [Updated] (KAFKA-1038) fetch response should use empty messageset instead of null when handling errors

[ https://issues.apache.org/jira/browse/KAFKA-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1038: --- Attachment: kafka-1038.patch Attach a patch. fetch response should use empty messageset

[jira] [Commented] (KAFKA-1038) fetch response should use empty messageset instead of null when handling errors

[ https://issues.apache.org/jira/browse/KAFKA-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756685#comment-13756685 ] Jun Rao commented on KAFKA-1038: This patch only fixes the response for the fetch request.

[jira] [Commented] (KAFKA-955) After a leader change, messages sent with ack=0 are lost

[ https://issues.apache.org/jira/browse/KAFKA-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756692#comment-13756692 ] Jun Rao commented on KAFKA-955: --- Thanks for patch v7. A couple of more comments. 70. There

[jira] [Commented] (KAFKA-1011) Decompression and re-compression on MirrorMaker could result in messages being dropped in the pipeline

[ https://issues.apache.org/jira/browse/KAFKA-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756703#comment-13756703 ] Jun Rao commented on KAFKA-1011: Thanks for the patch. Not sure if it works correctly

[jira] [Closed] (KAFKA-937) ConsumerFetcherThread can deadlock

[ https://issues.apache.org/jira/browse/KAFKA-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-937. - Thanks for the review. Committed the delta patch to 0.8, after fixing the logging.

[jira] [Commented] (KAFKA-1039) kafka return acks but not logging while sending messages with compression

[ https://issues.apache.org/jira/browse/KAFKA-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13757444#comment-13757444 ] Jun Rao commented on KAFKA-1039: Could you describe how to reproduce the issue?

[jira] [Commented] (KAFKA-1039) kafka return acks but not logging while sending messages with compression

[ https://issues.apache.org/jira/browse/KAFKA-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13757803#comment-13757803 ] Jun Rao commented on KAFKA-1039: It this the same problem as kafka-1037 when snappy jar is

[jira] [Closed] (KAFKA-1039) kafka return acks but not logging while sending messages with compression

[ https://issues.apache.org/jira/browse/KAFKA-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-1039. -- kafka return acks but not logging while sending messages with compression

[jira] [Resolved] (KAFKA-1039) kafka return acks but not logging while sending messages with compression

[ https://issues.apache.org/jira/browse/KAFKA-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-1039. Resolution: Duplicate Close this since it's a duplicate of kafka-1037. kafka return acks

[jira] [Updated] (KAFKA-1035) Add message-send-max-retries and retry-backoff-ms options to console producer

[ https://issues.apache.org/jira/browse/KAFKA-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1035: --- Resolution: Fixed Assignee: Rajasekar Elango (was: Jun Rao) Status: Resolved (was: Patch

[jira] [Closed] (KAFKA-1035) Add message-send-max-retries and retry-backoff-ms options to console producer

[ https://issues.apache.org/jira/browse/KAFKA-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-1035. -- Add message-send-max-retries and retry-backoff-ms options to console producer

[jira] [Resolved] (KAFKA-953) Remove release-zip from README we are not releasing with it

[ https://issues.apache.org/jira/browse/KAFKA-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-953. --- Resolution: Fixed We actually do support the release-zip target, as well as release-tar.

[jira] [Updated] (KAFKA-1042) Fix segment flush logic

[ https://issues.apache.org/jira/browse/KAFKA-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1042: --- Affects Version/s: (was: 0.8) 0.8.1 Fix Version/s: (was: 0.8) This is

[jira] [Updated] (KAFKA-960) Upgrade Metrics to 3.x

[ https://issues.apache.org/jira/browse/KAFKA-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-960: -- Affects Version/s: (was: 0.8) 0.8.1 Fix Version/s: (was: 0.8) This is

[jira] [Updated] (KAFKA-984) Avoid a full rebalance in cases when a new topic is discovered but container/broker set stay the same

[ https://issues.apache.org/jira/browse/KAFKA-984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-984: -- Fix Version/s: (was: 0.8) 0.8.1 Since the changes are relative large and subtle, we

[jira] [Updated] (KAFKA-995) Enforce that the value for replica.fetch.max.bytes is always = the value for message.max.bytes

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

[jira] [Updated] (KAFKA-997) Provide a strict verification mode when reading configuration properties

[ https://issues.apache.org/jira/browse/KAFKA-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-997: -- Affects Version/s: (was: 0.8) Fix Version/s: (was: 0.8) 0.8.1 Since this

[jira] [Created] (KAFKA-1052) integrate add-partitions command into topicCommand

Jun Rao created KAFKA-1052: -- Summary: integrate add-partitions command into topicCommand Key: KAFKA-1052 URL: https://issues.apache.org/jira/browse/KAFKA-1052 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-1051) merge from 0.8 da4512174b6f7c395ffe053a86d2c6bb19d2538a to trunk

[ https://issues.apache.org/jira/browse/KAFKA-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1051: --- Attachment: kafka-1051.patch Attach a patch for review. Somehow, couldn't publish a reviewboard because of

[jira] [Commented] (KAFKA-970) ./sbt +package rebuilds the Hadoop consumer jar N times with the same output file

[ https://issues.apache.org/jira/browse/KAFKA-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13764540#comment-13764540 ] Jun Rao commented on KAFKA-970: --- This affects the following jars.

[jira] [Commented] (KAFKA-1051) merge from 0.8 da4512174b6f7c395ffe053a86d2c6bb19d2538a to trunk

[ https://issues.apache.org/jira/browse/KAFKA-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13764503#comment-13764503 ] Jun Rao commented on KAFKA-1051: Will leave this jira un-closed for a few days in case

[jira] [Updated] (KAFKA-1051) merge from 0.8 da4512174b6f7c395ffe053a86d2c6bb19d2538a to trunk

[ https://issues.apache.org/jira/browse/KAFKA-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1051: --- Resolution: Fixed Status: Resolved (was: Patch Available) Since all merge conflicts are easy to

[jira] [Commented] (KAFKA-1046) Added support for Scala 2.10 builds while maintaining compatibility with 2.8.x

[ https://issues.apache.org/jira/browse/KAFKA-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13764544#comment-13764544 ] Jun Rao commented on KAFKA-1046: Chris, I merged everything in 0.8 before your change to

[jira] [Created] (KAFKA-1051) merge from 0.8 da4512174b6f7c395ffe053a86d2c6bb19d2538a to trunk

Jun Rao created KAFKA-1051: -- Summary: merge from 0.8 da4512174b6f7c395ffe053a86d2c6bb19d2538a to trunk Key: KAFKA-1051 URL: https://issues.apache.org/jira/browse/KAFKA-1051 Project: Kafka Issue

[jira] [Updated] (KAFKA-1051) merge from 0.8 da4512174b6f7c395ffe053a86d2c6bb19d2538a to trunk

[ https://issues.apache.org/jira/browse/KAFKA-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1051: --- Status: Patch Available (was: Open) merge from 0.8 da4512174b6f7c395ffe053a86d2c6bb19d2538a to trunk

[jira] [Commented] (KAFKA-1051) merge from 0.8 da4512174b6f7c395ffe053a86d2c6bb19d2538a to trunk

[ https://issues.apache.org/jira/browse/KAFKA-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13765141#comment-13765141 ] Jun Rao commented on KAFKA-1051: There's a problem in generating a reviewboard with this

[jira] [Commented] (KAFKA-925) Add optional partition key override in producer

[ https://issues.apache.org/jira/browse/KAFKA-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13765591#comment-13765591 ] Jun Rao commented on KAFKA-925: --- Thanks for the post commit patch. Looks good. +1.

[jira] [Commented] (KAFKA-1008) Unmap before resizing

[ https://issues.apache.org/jira/browse/KAFKA-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13765579#comment-13765579 ] Jun Rao commented on KAFKA-1008: Thanks for the patch. Reviewed patch v7 for 0.8. Looks

[jira] [Updated] (KAFKA-923) Improve controller failover latency

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

[jira] [Updated] (KAFKA-1020) Remove getAllReplicasOnBroker from KafkaController

[ https://issues.apache.org/jira/browse/KAFKA-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1020: --- Fix Version/s: 0.8.1 Remove getAllReplicasOnBroker from KafkaController

[jira] [Commented] (KAFKA-998) Producer should not retry on non-recoverable error codes

[ https://issues.apache.org/jira/browse/KAFKA-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13765633#comment-13765633 ] Jun Rao commented on KAFKA-998: --- Thanks for the patch. Looks good overall. Just one comment:

[jira] [Commented] (KAFKA-948) ISR list in LeaderAndISR path not updated for partitions when Broker (which is not leader) is down

[ https://issues.apache.org/jira/browse/KAFKA-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13766575#comment-13766575 ] Jun Rao commented on KAFKA-948: --- Is this still happening in 0.8? ISR list

[jira] [Resolved] (KAFKA-973) Messages From Producer Not being Partitioned

[ https://issues.apache.org/jira/browse/KAFKA-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-973. --- Resolution: Not A Problem Messages From Producer Not being Partitioned

[jira] [Updated] (KAFKA-972) MetadataRequest returns stale list of brokers

[ https://issues.apache.org/jira/browse/KAFKA-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-972: -- Fix Version/s: (was: 0.8) Could you describe how to reproduce this? MetadataRequest

[jira] [Commented] (KAFKA-975) Leader not local for partition when partition is leader (kafka.common.NotLeaderForPartitionException)

[ https://issues.apache.org/jira/browse/KAFKA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13766567#comment-13766567 ] Jun Rao commented on KAFKA-975: --- Any error in the controller and state-change log?

[jira] [Updated] (KAFKA-1040) ConsumerConfig and ProducerConfig do work in the Constructor

[ https://issues.apache.org/jira/browse/KAFKA-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1040: --- Fix Version/s: 0.8.1 ConsumerConfig and ProducerConfig do work in the Constructor

[jira] [Updated] (KAFKA-1046) Added support for Scala 2.10 builds while maintaining compatibility with 2.8.x

[ https://issues.apache.org/jira/browse/KAFKA-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1046: --- Fix Version/s: 0.8 Added support for Scala 2.10 builds while maintaining compatibility with 2.8.x

[jira] [Commented] (KAFKA-1036) Unable to rename replication offset checkpoint in windows

[ https://issues.apache.org/jira/browse/KAFKA-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13766549#comment-13766549 ] Jun Rao commented on KAFKA-1036: Hmm, not sure how to patch this since we close the writer

[jira] [Updated] (KAFKA-1044) change log4j to slf4j

[ https://issues.apache.org/jira/browse/KAFKA-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1044: --- Fix Version/s: 0.9 change log4j to slf4j -- Key: KAFKA-1044

[jira] [Updated] (KAFKA-1046) Added support for Scala 2.10 builds while maintaining compatibility with 2.8.x

[ https://issues.apache.org/jira/browse/KAFKA-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1046: --- Status: Patch Available (was: Open) Added support for Scala 2.10 builds while maintaining

[jira] [Commented] (KAFKA-956) High-level consumer fails to check topic metadata response for errors

[ https://issues.apache.org/jira/browse/KAFKA-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13766581#comment-13766581 ] Jun Rao commented on KAFKA-956: --- This can probably be fixed as part of kafka-1030.

[jira] [Updated] (KAFKA-1027) Add documentation for system tests

[ https://issues.apache.org/jira/browse/KAFKA-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1027: --- Fix Version/s: (was: 0.8) 0.8.1 Add documentation for system tests

[jira] [Updated] (KAFKA-946) Kafka Hadoop Consumer fails when verifying message checksum

[ https://issues.apache.org/jira/browse/KAFKA-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-946: -- Fix Version/s: 0.8 Kafka Hadoop Consumer fails when verifying message checksum

[jira] [Updated] (KAFKA-1041) Number of file handles increases indefinitely in producer if broker host is unresolvable

[ https://issues.apache.org/jira/browse/KAFKA-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1041: --- Fix Version/s: 0.8.1 Moving to 0.8.1 since it's not very critical Number of file handles

[jira] [Updated] (KAFKA-1038) fetch response should use empty messageset instead of null when handling errors

[ https://issues.apache.org/jira/browse/KAFKA-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1038: --- Fix Version/s: 0.8 fetch response should use empty messageset instead of null when handling errors

[jira] [Updated] (KAFKA-1038) fetch response should use empty messageset instead of null when handling errors

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

[jira] [Closed] (KAFKA-1038) fetch response should use empty messageset instead of null when handling errors

[ https://issues.apache.org/jira/browse/KAFKA-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-1038. -- fetch response should use empty messageset instead of null when handling errors

[jira] [Commented] (KAFKA-1008) Unmap before resizing

[ https://issues.apache.org/jira/browse/KAFKA-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13774698#comment-13774698 ] Jun Rao commented on KAFKA-1008: Sorry, I missed that comment. +1 on v8.

[jira] [Closed] (KAFKA-975) Leader not local for partition when partition is leader (kafka.common.NotLeaderForPartitionException)

[ https://issues.apache.org/jira/browse/KAFKA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-975. - Leader not local for partition when partition is leader (kafka.common.NotLeaderForPartitionException)

[jira] [Resolved] (KAFKA-975) Leader not local for partition when partition is leader (kafka.common.NotLeaderForPartitionException)

[ https://issues.apache.org/jira/browse/KAFKA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-975. --- Resolution: Not A Problem Assignee: (was: Neha Narkhede) Carl, thanks for the update. Could you

[jira] [Commented] (KAFKA-946) Kafka Hadoop Consumer fails when verifying message checksum

[ https://issues.apache.org/jira/browse/KAFKA-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13774707#comment-13774707 ] Jun Rao commented on KAFKA-946: --- Sorry for not looking at this earlier. I think that we can

[jira] [Updated] (KAFKA-946) Kafka Hadoop Consumer fails when verifying message checksum

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

[jira] [Closed] (KAFKA-946) Kafka Hadoop Consumer fails when verifying message checksum

[ https://issues.apache.org/jira/browse/KAFKA-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-946. - Kafka Hadoop Consumer fails when verifying message checksum

[jira] [Commented] (KAFKA-1065) IO exception on windows when high throughput of messages

[ https://issues.apache.org/jira/browse/KAFKA-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13776426#comment-13776426 ] Jun Rao commented on KAFKA-1065: Could you try the patch in

[jira] [Commented] (KAFKA-998) Producer should not retry on non-recoverable error codes

[ https://issues.apache.org/jira/browse/KAFKA-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13778883#comment-13778883 ] Jun Rao commented on KAFKA-998: --- Jason, This patch just won't retry sending the data when

[jira] [Commented] (KAFKA-998) Producer should not retry on non-recoverable error codes

[ https://issues.apache.org/jira/browse/KAFKA-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13779636#comment-13779636 ] Jun Rao commented on KAFKA-998: --- My feeling is that it may not be very easy to do a quick

[jira] [Created] (KAFKA-1068) OfflinePartitionCount metrics may be incorrect after the controller failover

Jun Rao created KAFKA-1068: -- Summary: OfflinePartitionCount metrics may be incorrect after the controller failover Key: KAFKA-1068 URL: https://issues.apache.org/jira/browse/KAFKA-1068 Project: Kafka

[jira] [Updated] (KAFKA-1068) OfflinePartitionCount metrics may be incorrect after the controller failover

[ https://issues.apache.org/jira/browse/KAFKA-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1068: --- Attachment: KAFKA-1068.patch OfflinePartitionCount metrics may be incorrect after the controller failover

[jira] [Commented] (KAFKA-1068) OfflinePartitionCount metrics may be incorrect after the controller failover

[ https://issues.apache.org/jira/browse/KAFKA-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13781530#comment-13781530 ] Jun Rao commented on KAFKA-1068: Created reviewboard https://reviews.apache.org/r/14399/

[jira] [Updated] (KAFKA-1068) OfflinePartitionCount metrics may be incorrect after the controller failover

[ https://issues.apache.org/jira/browse/KAFKA-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1068: --- Status: Patch Available (was: Open) OfflinePartitionCount metrics may be incorrect after the controller

[jira] [Resolved] (KAFKA-1065) IO exception on windows when high throughput of messages

[ https://issues.apache.org/jira/browse/KAFKA-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-1065. Resolution: Duplicate Close this since it duplicates kafka-1008. IO exception on windows when high

[jira] [Created] (KAFKA-1071) The random partition selected in DefaultEventHandler is not random across producer instances

Jun Rao created KAFKA-1071: -- Summary: The random partition selected in DefaultEventHandler is not random across producer instances Key: KAFKA-1071 URL: https://issues.apache.org/jira/browse/KAFKA-1071

[jira] [Commented] (KAFKA-1071) The random partition selected in DefaultEventHandler is not random across producer instances

[ https://issues.apache.org/jira/browse/KAFKA-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13784816#comment-13784816 ] Jun Rao commented on KAFKA-1071: Thanks for the patch. Would it be better to just get a

[jira] [Updated] (KAFKA-1071) The random partition selected in DefaultEventHandler is not random across producer instances

[ https://issues.apache.org/jira/browse/KAFKA-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1071: --- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for patch v2. +1. Committed to

[jira] [Commented] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13786295#comment-13786295 ] Jun Rao commented on KAFKA-881: --- Thanks for the patch. I am not sure if the patch works

[jira] [Created] (KAFKA-1073) CheckReassignmentStatus is broken

Jun Rao created KAFKA-1073: -- Summary: CheckReassignmentStatus is broken Key: KAFKA-1073 URL: https://issues.apache.org/jira/browse/KAFKA-1073 Project: Kafka Issue Type: Bug Components:

[jira] [Commented] (KAFKA-1073) CheckReassignmentStatus is broken

[ https://issues.apache.org/jira/browse/KAFKA-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13786649#comment-13786649 ] Jun Rao commented on KAFKA-1073: Created reviewboard https://reviews.apache.org/r/14496/

[jira] [Updated] (KAFKA-1073) CheckReassignmentStatus is broken

[ https://issues.apache.org/jira/browse/KAFKA-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1073: --- Attachment: KAFKA-1073.patch CheckReassignmentStatus is broken -

[jira] [Updated] (KAFKA-1073) CheckReassignmentStatus is broken

[ https://issues.apache.org/jira/browse/KAFKA-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1073: --- Status: Patch Available (was: Open) CheckReassignmentStatus is broken -

[jira] [Created] (KAFKA-1074) Reassign partitions should delete the old replicas from disk

Jun Rao created KAFKA-1074: -- Summary: Reassign partitions should delete the old replicas from disk Key: KAFKA-1074 URL: https://issues.apache.org/jira/browse/KAFKA-1074 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-1073) CheckReassignmentStatus is broken

[ https://issues.apache.org/jira/browse/KAFKA-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1073: --- Attachment: KAFKA-1073_2013-10-05_11:02:45.patch CheckReassignmentStatus is broken

[jira] [Updated] (KAFKA-1076) system tests in 0.8 are broken due to wrong log4j config

[ https://issues.apache.org/jira/browse/KAFKA-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1076: --- Status: Patch Available (was: Open) system tests in 0.8 are broken due to wrong log4j config

[jira] [Commented] (KAFKA-1076) system tests in 0.8 are broken due to wrong log4j config

[ https://issues.apache.org/jira/browse/KAFKA-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13787287#comment-13787287 ] Jun Rao commented on KAFKA-1076: Created reviewboard https://reviews.apache.org/r/14511/

[jira] [Updated] (KAFKA-1076) system tests in 0.8 are broken due to wrong log4j config

[ https://issues.apache.org/jira/browse/KAFKA-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1076: --- Attachment: KAFKA-1076.patch system tests in 0.8 are broken due to wrong log4j config

[jira] [Commented] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13787655#comment-13787655 ] Jun Rao commented on KAFKA-881: --- How about the following: In log, maintaining an

[jira] [Updated] (KAFKA-1076) system tests in 0.8 are broken due to wrong log4j config

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

[jira] [Closed] (KAFKA-1076) system tests in 0.8 are broken due to wrong log4j config

[ https://issues.apache.org/jira/browse/KAFKA-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-1076. -- system tests in 0.8 are broken due to wrong log4j config

[jira] [Updated] (KAFKA-1073) CheckReassignmentStatus is broken

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

[jira] [Closed] (KAFKA-1073) CheckReassignmentStatus is broken

[ https://issues.apache.org/jira/browse/KAFKA-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-1073. -- CheckReassignmentStatus is broken - Key: KAFKA-1073

[jira] [Closed] (KAFKA-1075) Consumer will not rebalance upon topic partition change

[ https://issues.apache.org/jira/browse/KAFKA-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-1075. -- Consumer will not rebalance upon topic partition change ---

[jira] [Resolved] (KAFKA-1075) Consumer will not rebalance upon topic partition change

[ https://issues.apache.org/jira/browse/KAFKA-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-1075. Resolution: Fixed Fix Version/s: 0.8 Thanks for the patch. +1 and committed to 0.8. Consumer will

[jira] [Updated] (KAFKA-1067) the default partitioner should be randomizing messages and a new partition for the meta refresh requirements created

[ https://issues.apache.org/jira/browse/KAFKA-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1067: --- Fix Version/s: (was: 0.8) 0.8.1 the default partitioner should be randomizing

[jira] [Updated] (KAFKA-1063) run log cleanup at startup

[ https://issues.apache.org/jira/browse/KAFKA-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1063: --- Fix Version/s: (was: 0.8) 0.8.1 Moving to 0.8.1 since it's a minor issue and there is

[jira] [Updated] (KAFKA-1036) Unable to rename replication offset checkpoint in windows

[ https://issues.apache.org/jira/browse/KAFKA-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1036: --- Affects Version/s: (was: 0.8) 0.8.1 Fix Version/s: (was: 0.8)

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