[jira] [Assigned] (KAFKA-347) change number of partitions of a topic online
[ https://issues.apache.org/jira/browse/KAFKA-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriram Subramanian reassigned KAFKA-347: Assignee: Sriram Subramanian change number of partitions of a topic online - Key: KAFKA-347 URL: https://issues.apache.org/jira/browse/KAFKA-347 Project: Kafka Issue Type: Improvement Components: core Affects Versions: 0.8 Reporter: Jun Rao Assignee: Sriram Subramanian Labels: features Fix For: 0.8.1 We will need an admin tool to change the number of partitions of a topic online. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Kafka 0.8.0 Beta 1 (Candidate 1)
a few last details I left it last night hopefully later today/tonight/tomorrow. want to make sure all the maven changes are correct for publishing. On Wed, Jun 19, 2013 at 11:51 AM, Jun Rao jun...@gmail.com wrote: Hi, Joe, When do you plan to cut an RC2 for vote? Thanks, Jun On Mon, Jun 17, 2013 at 4:58 AM, Joe Stein crypt...@gmail.com wrote: Hey folks, I am going to vote -1 on this this release. I know, I know, I know I prepared it but I was working for hours and hours last night going through so many facets even working on it to deploy into our own shakedown (pre-production) environment and it hit me! We are not voting on all the artifacts we need for this release, its different than 0.7.X and has to be prepared that way for vote. so one thing I want to change in src is SNAPSHOT to beta1 and will create JIRA can commit once we get +1 on patch. also for the -bin distribution folks should be able to just download and run the quick start and ./kafka-server-start.sh ../config/server.properties should just start without any other class files, etc. but I will prepare that also and sign it and put up in the second candidate vote any other feedback for the second candidate release please let me know On Thu, Jun 13, 2013 at 5:41 PM, Joe Stein crypt...@gmail.com wrote: Hello, this is the first candidate release for Kafka 0.8.0 Beta 1 This release fixes the following issues http://people.apache.org/~joestein/kafka-0.8.0-beta1-candidate1/RELEASE_NOTES.html *** Please download, test and vote by Sunday June, 16th, 9pm PST Release artifacts: http://people.apache.org/~joestein/kafka-0.8.0-beta1-candidate1/ The tag to be voted upon (off the 0.8 branch): https://git-wip-us.apache.org/repos/asf?p=kafka.git;a=tag;h=refs/tags/0.8.0-beta1 Kafka's KEYS file containing PGP keys we use to sign the release: http://svn.apache.org/repos/asf/kafka/KEYS -- /* Joe Stein http://www.linkedin.com/in/charmalloc Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop */ -- /* Joe Stein http://www.linkedin.com/in/charmalloc Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop */ -- /* Joe Stein http://www.linkedin.com/in/charmalloc Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop */
[jira] [Created] (KAFKA-947) isr-expiration-thread may block LeaderAndIsr request for a relatively long period
Jun Rao created KAFKA-947: - Summary: isr-expiration-thread may block LeaderAndIsr request for a relatively long period Key: KAFKA-947 URL: https://issues.apache.org/jira/browse/KAFKA-947 Project: Kafka Issue Type: Bug Components: core Affects Versions: 0.8.1 Reporter: Jun Rao Assignee: Jun Rao If there are lots of partitions whose isr needs to be shrank, isr-expiration-thread will hold a long lock on leaderPartitionsLock, which will delay LeaderAndIsr requests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-947) isr-expiration-thread may block LeaderAndIsr request for a relatively long period
[ https://issues.apache.org/jira/browse/KAFKA-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-947: -- Status: Patch Available (was: Open) Attach a patch. isr-expiration-thread may block LeaderAndIsr request for a relatively long period -- Key: KAFKA-947 URL: https://issues.apache.org/jira/browse/KAFKA-947 Project: Kafka Issue Type: Bug Components: core Affects Versions: 0.8.1 Reporter: Jun Rao Assignee: Jun Rao Attachments: kafka-947.patch If there are lots of partitions whose isr needs to be shrank, isr-expiration-thread will hold a long lock on leaderPartitionsLock, which will delay LeaderAndIsr requests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-947) isr-expiration-thread may block LeaderAndIsr request for a relatively long period
[ https://issues.apache.org/jira/browse/KAFKA-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-947: -- Attachment: kafka-947.patch isr-expiration-thread may block LeaderAndIsr request for a relatively long period -- Key: KAFKA-947 URL: https://issues.apache.org/jira/browse/KAFKA-947 Project: Kafka Issue Type: Bug Components: core Affects Versions: 0.8.1 Reporter: Jun Rao Assignee: Jun Rao Attachments: kafka-947.patch If there are lots of partitions whose isr needs to be shrank, isr-expiration-thread will hold a long lock on leaderPartitionsLock, which will delay LeaderAndIsr requests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-944) the pom output from publish and publish-local is not accurate
[ https://issues.apache.org/jira/browse/KAFKA-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-944: Status: Patch Available (was: Open) the pom output from publish and publish-local is not accurate - Key: KAFKA-944 URL: https://issues.apache.org/jira/browse/KAFKA-944 Project: Kafka Issue Type: Bug Affects Versions: 0.8 Reporter: Joe Stein Assignee: Joe Stein Priority: Critical Fix For: 0.8 Attachments: KAFKA-944.patch the groupId in the publish-local and publish output is wrong its groupIdorg.apache/groupId and should be groupIdorg.apache.kafka/groupId per https://issues.apache.org/jira/browse/INFRA-6399 also, I think we should be adding this http://www.apache.org/dev/publishing-maven-artifacts.html#adjust-maven maybe some other things going through it over again -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-947) isr-expiration-thread may block LeaderAndIsr request for a relatively long period
[ https://issues.apache.org/jira/browse/KAFKA-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688719#comment-13688719 ] Joel Koshy commented on KAFKA-947: -- +1 thanks for the patch! isr-expiration-thread may block LeaderAndIsr request for a relatively long period -- Key: KAFKA-947 URL: https://issues.apache.org/jira/browse/KAFKA-947 Project: Kafka Issue Type: Bug Components: core Affects Versions: 0.8.1 Reporter: Jun Rao Assignee: Jun Rao Attachments: kafka-947.patch If there are lots of partitions whose isr needs to be shrank, isr-expiration-thread will hold a long lock on leaderPartitionsLock, which will delay LeaderAndIsr requests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-944) the pom output from publish and publish-local is not accurate
[ https://issues.apache.org/jira/browse/KAFKA-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-944: Resolution: Fixed Status: Resolved (was: Patch Available) the pom output from publish and publish-local is not accurate - Key: KAFKA-944 URL: https://issues.apache.org/jira/browse/KAFKA-944 Project: Kafka Issue Type: Bug Affects Versions: 0.8 Reporter: Joe Stein Assignee: Joe Stein Priority: Critical Fix For: 0.8 Attachments: KAFKA-944.patch the groupId in the publish-local and publish output is wrong its groupIdorg.apache/groupId and should be groupIdorg.apache.kafka/groupId per https://issues.apache.org/jira/browse/INFRA-6399 also, I think we should be adding this http://www.apache.org/dev/publishing-maven-artifacts.html#adjust-maven maybe some other things going through it over again -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KAFKA-948) ISR list in LeaderAndISR path not updated for partitions when Broker (which is not leader) is down
Dibyendu Bhattacharya created KAFKA-948: --- Summary: ISR list in LeaderAndISR path not updated for partitions when Broker (which is not leader) is down Key: KAFKA-948 URL: https://issues.apache.org/jira/browse/KAFKA-948 Project: Kafka Issue Type: Bug Components: controller Affects Versions: 0.8 Reporter: Dibyendu Bhattacharya Assignee: Neha Narkhede When the broker which is the leader for a partition is down, the ISR list in the LeaderAndISR path is updated. But if the broker , which is not a leader of the partition is down, the ISR list is not getting updated. This is an issues because ISR list contains the stale entry. This issue I found in kafka-0.8.0-beta1-candidate1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
