[jira] [Commented] (KAFKA-510) broker needs to know the replication factor per partition

[ https://issues.apache.org/jira/browse/KAFKA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473843#comment-13473843 ] Yang Ye commented on KAFKA-510: --- thanks for the comments. The new one is ready and will be su

[jira] [Commented] (KAFKA-548) remove partition from ProducerRequestPartitionData and FetchResponsePartitionData

[ https://issues.apache.org/jira/browse/KAFKA-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473842#comment-13473842 ] Yang Ye commented on KAFKA-548: --- Yeah, that's incomplete. I didn't notice when I submit the f

[jira] [Commented] (KAFKA-548) remove partition from ProducerRequestPartitionData and FetchResponsePartitionData

[ https://issues.apache.org/jira/browse/KAFKA-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473840#comment-13473840 ] Neha Narkhede commented on KAFKA-548: - Thanks for the patch. Few review comments - 1.

[jira] [Commented] (KAFKA-537) expose clientId and correlationId in ConsumerConfig

[ https://issues.apache.org/jira/browse/KAFKA-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473835#comment-13473835 ] Yang Ye commented on KAFKA-537: --- To enable special consumer to fetch from any replica, we don

[jira] [Commented] (KAFKA-530) kafka.server.KafkaApis: kafka.common.OffsetOutOfRangeException

[ https://issues.apache.org/jira/browse/KAFKA-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473834#comment-13473834 ] Neha Narkhede commented on KAFKA-530: - John, do you still see this issue on the latest

[jira] [Commented] (KAFKA-537) expose clientId and correlationId in ConsumerConfig

[ https://issues.apache.org/jira/browse/KAFKA-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473833#comment-13473833 ] Neha Narkhede commented on KAFKA-537: - Agree with Jay here. I assume this is to enable

[jira] [Commented] (KAFKA-560) Garbage Collect obsolete topics

[ https://issues.apache.org/jira/browse/KAFKA-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473829#comment-13473829 ] Neha Narkhede commented on KAFKA-560: - OffsetRequest will not give you the time, but th

[jira] [Commented] (KAFKA-557) Replica fetch thread doesn't need to recompute message id

[ https://issues.apache.org/jira/browse/KAFKA-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473822#comment-13473822 ] Neha Narkhede commented on KAFKA-557: - 1.2 Understand, but that's what we've been follo

[jira] [Commented] (KAFKA-506) Store logical offset in log

[ https://issues.apache.org/jira/browse/KAFKA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473821#comment-13473821 ] Neha Narkhede commented on KAFKA-506: - +1. Looks good and thanks for addressing the lat

[jira] [Updated] (KAFKA-557) Replica fetch thread doesn't need to recompute message id

[ https://issues.apache.org/jira/browse/KAFKA-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-557: Attachment: KAFKA-557.patch > Replica fetch thread doesn't need to recompute message id > --

[jira] [Commented] (KAFKA-557) Replica fetch thread doesn't need to recompute message id

[ https://issues.apache.org/jira/browse/KAFKA-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473790#comment-13473790 ] Jay Kreps commented on KAFKA-557: - 1.1 Fixed 1.2 The long lines are due to use of String.fo

[jira] [Updated] (KAFKA-565) update download page for 0.7.2 download

[ https://issues.apache.org/jira/browse/KAFKA-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-565: Attachment: KAFKA-538.patch > update download page for 0.7.2 download >

[jira] [Updated] (KAFKA-565) update download page for 0.7.2 download

[ https://issues.apache.org/jira/browse/KAFKA-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-565: Status: Patch Available (was: Open) pending dist availability and mirror updates > update

[jira] [Created] (KAFKA-565) update download page for 0.7.2 download

Joe Stein created KAFKA-565: --- Summary: update download page for 0.7.2 download Key: KAFKA-565 URL: https://issues.apache.org/jira/browse/KAFKA-565 Project: Kafka Issue Type: Task Report

Re: [VOTE] Release Kafka 0.7.2-incubating (Candidate 5)

[3] +1 (binding) Alan, Jakob, Chris [1] +1 (non-binding) Jun [1] 0 (binding) Owen) [0] -1 the vote passes IPMC and with the PPMC vote already passsed [3] +1 (binding) Jun, Neha, Chris [1] +1 (non-binding) Joel [0] 0 [0] -1 0.7.2 is ready to ship i will push the release to the origin server a

[jira] [Commented] (KAFKA-510) broker needs to know the replication factor per partition

[ https://issues.apache.org/jira/browse/KAFKA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473746#comment-13473746 ] Neha Narkhede commented on KAFKA-510: - 1. ControllerChannelManager Wrap the long line

[jira] [Updated] (KAFKA-267) Enhance ProducerPerformance to generate unique random Long value for payload

[ https://issues.apache.org/jira/browse/KAFKA-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Ye updated KAFKA-267: -- Attachment: kafka-267-v3.patch rebase on kafka 42 > Enhance ProducerPerformance to generate un

[jira] [Commented] (KAFKA-557) Replica fetch thread doesn't need to recompute message id

[ https://issues.apache.org/jira/browse/KAFKA-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473728#comment-13473728 ] Neha Narkhede commented on KAFKA-557: - 1. Log 1.1 Typos in description of analyzeAndVa

[jira] [Updated] (KAFKA-510) broker needs to know the replication factor per partition

[ https://issues.apache.org/jira/browse/KAFKA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Ye updated KAFKA-510: -- Attachment: kafka_510_v8.diff rebase from kafka 42 and apply Neha's advices > broker needs to

[jira] [Commented] (KAFKA-562) Non-failure System Test Log Segment File Checksums mismatched

[ https://issues.apache.org/jira/browse/KAFKA-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473719#comment-13473719 ] Jay Kreps commented on KAFKA-562: - So the proposed fix for this is to special case appends

[jira] [Commented] (KAFKA-557) Replica fetch thread doesn't need to recompute message id

[ https://issues.apache.org/jira/browse/KAFKA-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473716#comment-13473716 ] Jay Kreps commented on KAFKA-557: - I verified that this fixes KAFKA-562 >

[jira] [Updated] (KAFKA-506) Store logical offset in log

[ https://issues.apache.org/jira/browse/KAFKA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-506: Attachment: KAFKA-506-neha-post-review-v2.patch This patch is identical to the previous Neha related patch e

[jira] [Resolved] (KAFKA-492) Sometimes the python system test framework doesn't terminate all running processes

[ https://issues.apache.org/jira/browse/KAFKA-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung resolved KAFKA-492. - Resolution: Fixed Changes committed in KAFKA-502. Mark this Fixed. > Sometimes the python

[jira] [Resolved] (KAFKA-507) Shut down ZK last to avoid hanging brokers running processes

[ https://issues.apache.org/jira/browse/KAFKA-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung resolved KAFKA-507. - Resolution: Fixed Changes committed in KAFKA-502. Mark this Fixed. > Shut down ZK last to

[jira] [Resolved] (KAFKA-484) Move log settings in the beginning of system_test_runner.py to an external log properties file

[ https://issues.apache.org/jira/browse/KAFKA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung resolved KAFKA-484. - Resolution: Fixed Changes committed in KAFKA-502. Mark this Fixed. > Move log settings in

[jira] [Resolved] (KAFKA-503) Support "testcase_to_run" or "testcase_to_skip"

[ https://issues.apache.org/jira/browse/KAFKA-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung resolved KAFKA-503. - Resolution: Fixed Changes committed in KAFKA-502. Mark this Fixed. > Support "testcase_to

[jira] [Resolved] (KAFKA-488) Port Mirroring System Test to this python system test framework

[ https://issues.apache.org/jira/browse/KAFKA-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung resolved KAFKA-488. - Resolution: Fixed (Testcase_5001) Changes committed in KAFKA-502. Mark this Fixed. > Port

[jira] [Resolved] (KAFKA-447) Message replication with failures and multiple partitions and log segments

[ https://issues.apache.org/jira/browse/KAFKA-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung resolved KAFKA-447. - Resolution: Fixed Changes committed in KAFKA-502. Mark this Fixed. > Message replication

[jira] [Resolved] (KAFKA-448) Message replication with failures and varied replication factor

[ https://issues.apache.org/jira/browse/KAFKA-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung resolved KAFKA-448. - Resolution: Fixed Changes committed in KAFKA-502. Mark this Fixed. > Message replication

[jira] [Resolved] (KAFKA-444) Simple message replication test with multiple partitions and log segments

[ https://issues.apache.org/jira/browse/KAFKA-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung resolved KAFKA-444. - Resolution: Fixed Changes committed in KAFKA-502. Mark this Fixed. > Simple message repli

[jira] [Resolved] (KAFKA-446) Message replication with failures and varied producer acks

[ https://issues.apache.org/jira/browse/KAFKA-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung resolved KAFKA-446. - Resolution: Fixed Changes committed in KAFKA-502. Mark this Fixed. > Message replication

[jira] [Resolved] (KAFKA-445) Message replication with failures

[ https://issues.apache.org/jira/browse/KAFKA-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung resolved KAFKA-445. - Resolution: Fixed Changes committed in KAFKA-502. Mark this Fixed. > Message replication

[jira] [Resolved] (KAFKA-442) Simple message replication test with varied producer acks

[ https://issues.apache.org/jira/browse/KAFKA-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung resolved KAFKA-442. - Resolution: Fixed Changes committed in KAFKA-502. Mark this Fixed. > Simple message repli

[jira] [Resolved] (KAFKA-443) Simple message replication test with multiple partitions

[ https://issues.apache.org/jira/browse/KAFKA-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung resolved KAFKA-443. - Resolution: Fixed Changes committed in KAFKA-502. Mark this Fixed. > Simple message repli

[jira] [Resolved] (KAFKA-441) Simple message replication test

[ https://issues.apache.org/jira/browse/KAFKA-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung resolved KAFKA-441. - Resolution: Fixed Changes committed in KAFKA-502. Mark this Fixed. > Simple message repli

[jira] [Updated] (KAFKA-557) Replica fetch thread doesn't need to recompute message id

[ https://issues.apache.org/jira/browse/KAFKA-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-557: Attachment: KAFKA-557.patch Attached is a patch that makes offset assignment by the log optional. This is a

[jira] [Updated] (KAFKA-502) Simplify setup / initialization in replication_basic_test.py

[ https://issues.apache.org/jira/browse/KAFKA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung updated KAFKA-502: Resolution: Fixed Status: Resolved (was: Patch Available) > Simplify setup / initialization in

[jira] [Updated] (KAFKA-42) Support rebalancing the partitions with replication

[ https://issues.apache.org/jira/browse/KAFKA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-42: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed this > Su

[jira] [Commented] (KAFKA-562) Non-failure System Test Log Segment File Checksums mismatched

[ https://issues.apache.org/jira/browse/KAFKA-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473463#comment-13473463 ] Jay Kreps commented on KAFKA-562: - Okay, this is not a bug exactly, I was mistaken. Here is

[jira] [Commented] (KAFKA-562) Non-failure System Test Log Segment File Checksums mismatched

[ https://issues.apache.org/jira/browse/KAFKA-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473426#comment-13473426 ] Jay Kreps commented on KAFKA-562: - Yeah, this is definitely a real problem that is leading

[jira] [Commented] (KAFKA-267) Enhance ProducerPerformance to generate unique random Long value for payload

[ https://issues.apache.org/jira/browse/KAFKA-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473382#comment-13473382 ] Jun Rao commented on KAFKA-267: --- Can't find a revision that I can apply the patch cleanly. Co

[jira] [Commented] (KAFKA-42) Support rebalancing the partitions with replication

[ https://issues.apache.org/jira/browse/KAFKA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473379#comment-13473379 ] Neha Narkhede commented on KAFKA-42: I fear I might end up rebasing incorrectly and volu

[jira] [Commented] (KAFKA-510) broker needs to know the replication factor per partition

[ https://issues.apache.org/jira/browse/KAFKA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473376#comment-13473376 ] Neha Narkhede commented on KAFKA-510: - This JIRA would have been much easier to work on

[jira] [Commented] (KAFKA-510) broker needs to know the replication factor per partition

[ https://issues.apache.org/jira/browse/KAFKA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473373#comment-13473373 ] Jun Rao commented on KAFKA-510: --- Unfortunately, the jira module that we use is no-reopen on c

[jira] [Commented] (KAFKA-510) broker needs to know the replication factor per partition

[ https://issues.apache.org/jira/browse/KAFKA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473369#comment-13473369 ] Neha Narkhede commented on KAFKA-510: - I can't seem to be able to reopen this JIRA. Jun

[jira] [Commented] (KAFKA-42) Support rebalancing the partitions with replication

[ https://issues.apache.org/jira/browse/KAFKA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473359#comment-13473359 ] Jun Rao commented on KAFKA-42: -- +1 on the patch. Still see AdminTest.testResumePartitionReassi

[jira] [Commented] (KAFKA-42) Support rebalancing the partitions with replication

[ https://issues.apache.org/jira/browse/KAFKA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473354#comment-13473354 ] Neha Narkhede commented on KAFKA-42: This is blocking work on KAFKA-43, if no one has ob

[jira] [Updated] (KAFKA-564) Wildcard-based topic consumption should assign partitions to threads uniformly

[ https://issues.apache.org/jira/browse/KAFKA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-564: - Description: Right now, if when a client uses createMessageStreamsByFilter and specifies 'n' streams (thr

[jira] [Commented] (KAFKA-510) broker needs to know the replication factor per partition

[ https://issues.apache.org/jira/browse/KAFKA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473350#comment-13473350 ] Neha Narkhede commented on KAFKA-510: - Thanks for patch v7, here are few review comment

[jira] [Created] (KAFKA-564) Wildcard-based topic consumption should assign partitions to threads uniformly

Joel Koshy created KAFKA-564: Summary: Wildcard-based topic consumption should assign partitions to threads uniformly Key: KAFKA-564 URL: https://issues.apache.org/jira/browse/KAFKA-564 Project: Kafka

[jira] [Closed] (KAFKA-563) KafkaScheduler shutdown in ZookeeperConsumerConnector should check for config.autocommit

[ https://issues.apache.org/jira/browse/KAFKA-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-563. - > KafkaScheduler shutdown in ZookeeperConsumerConnector should check for > config.autocommit > --

[jira] [Resolved] (KAFKA-563) KafkaScheduler shutdown in ZookeeperConsumerConnector should check for config.autocommit

[ https://issues.apache.org/jira/browse/KAFKA-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-563. --- Resolution: Fixed Committed a trivial fix to 0.8. > KafkaScheduler shutdown in ZookeeperConsu

[jira] [Commented] (KAFKA-550) Wildcarded consumption is single-threaded

[ https://issues.apache.org/jira/browse/KAFKA-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473346#comment-13473346 ] Jun Rao commented on KAFKA-550: --- Could you open a separate jira for improving partition assig

[jira] [Closed] (KAFKA-510) broker needs to know the replication factor per partition

[ https://issues.apache.org/jira/browse/KAFKA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-510. - > broker needs to know the replication factor per partition >

[jira] [Resolved] (KAFKA-510) broker needs to know the replication factor per partition

[ https://issues.apache.org/jira/browse/KAFKA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-510. --- Resolution: Fixed Thanks for patch v7. Committed to 0.8 with the following minor refactoring. ControllerBroke

Re: Build failed in Jenkins: Kafka-trunk #149

PrimitiveApiTest failed while checking consumer iterators. Haven't seen this error in a while. On Tue, Oct 9, 2012 at 7:10 PM, Apache Jenkins Server wrote: > See > > Changes: > > [jjkoshy] Fix wildcard consumption to work with greater than o

[jira] [Closed] (KAFKA-553) confusing reference to zk.connect in config/producer.properties

[ https://issues.apache.org/jira/browse/KAFKA-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-553. - > confusing reference to zk.connect in config/producer.properties > --

[jira] [Updated] (KAFKA-553) confusing reference to zk.connect in config/producer.properties

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

[jira] [Updated] (KAFKA-553) confusing reference to zk.connect in config/producer.properties

[ https://issues.apache.org/jira/browse/KAFKA-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yazgoo updated KAFKA-553: - Attachment: kafka_553_v1.diff In config/producer.properties 1. removing references to zookeeper 2. changing the d

[jira] [Updated] (KAFKA-553) confusing reference to zk.connect in config/producer.properties

[ https://issues.apache.org/jira/browse/KAFKA-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yazgoo updated KAFKA-553: - Comment: was deleted (was: 1. removing references to zookeeper 2. changing the description of broker.list) >

[jira] [Updated] (KAFKA-553) confusing reference to zk.connect in config/producer.properties

[ https://issues.apache.org/jira/browse/KAFKA-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yazgoo updated KAFKA-553: - Status: Patch Available (was: Open) 1. removing references to zookeeper 2. changing the description of broker.lis

[jira] [Updated] (KAFKA-553) confusing reference to zk.connect in config/producer.properties

[ https://issues.apache.org/jira/browse/KAFKA-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yazgoo updated KAFKA-553: - Status: Open (was: Patch Available) > confusing reference to zk.connect in config/producer.properties > -

[jira] [Updated] (KAFKA-553) confusing reference to zk.connect in config/producer.properties

[ https://issues.apache.org/jira/browse/KAFKA-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yazgoo updated KAFKA-553: - Status: Patch Available (was: Open) Remove references to zookeeper from config/producer.properties change the bro

[jira] [Updated] (KAFKA-553) confusing reference to zk.connect in config/producer.properties

[ https://issues.apache.org/jira/browse/KAFKA-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yazgoo updated KAFKA-553: - Comment: was deleted (was: Remove references to zookeeper from config/producer.properties change the broker.list d