[jira] [Commented] (KAFKA-1115) producer performance affected by trace/debug calls

[ https://issues.apache.org/jira/browse/KAFKA-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811827#comment-13811827 ] Guozhang Wang commented on KAFKA-1115: -- Ah got it. Good point. > producer performanc

[jira] [Commented] (KAFKA-1115) producer performance affected by trace/debug calls

[ https://issues.apache.org/jira/browse/KAFKA-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811759#comment-13811759 ] Francois Saint-Jacques commented on KAFKA-1115: --- This is not the problem. Ev

[jira] [Commented] (KAFKA-1115) producer performance affected by trace/debug calls

[ https://issues.apache.org/jira/browse/KAFKA-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811734#comment-13811734 ] Guozhang Wang commented on KAFKA-1115: -- Hi Francois, You can change the logging leve

[jira] [Updated] (KAFKA-1115) producer performance affected by trace/debug calls

[ https://issues.apache.org/jira/browse/KAFKA-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Saint-Jacques updated KAFKA-1115: -- Attachment: producer-performance-fix.patch > producer performance affected by t

[jira] [Updated] (KAFKA-1115) producer performance affected by trace/debug calls

[ https://issues.apache.org/jira/browse/KAFKA-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Saint-Jacques updated KAFKA-1115: -- Status: Open (was: Patch Available) > producer performance affected by trace/d

[jira] [Created] (KAFKA-1115) producer performance affected by trace/debug calls

Francois Saint-Jacques created KAFKA-1115: - Summary: producer performance affected by trace/debug calls Key: KAFKA-1115 URL: https://issues.apache.org/jira/browse/KAFKA-1115 Project: Kafka

[jira] [Updated] (KAFKA-1115) producer performance affected by trace/debug calls

[ https://issues.apache.org/jira/browse/KAFKA-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Saint-Jacques updated KAFKA-1115: -- Status: Patch Available (was: Open) > producer performance affected by trace/d

Re: Review Request 14865: Patch for KAFKA-1097

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/14865/#review28030 --- Ship it! Ship It! - Guozhang Wang On Nov. 1, 2013, 4:55 p.m., Ne

[jira] [Updated] (KAFKA-1112) broker can not start itself after kafka is killed with -9

[ https://issues.apache.org/jira/browse/KAFKA-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1112: - Priority: Critical (was: Major) > broker can not start itself after kafka is killed with -9 > --

[jira] [Updated] (KAFKA-1097) Race condition while reassigning low throughput partition leads to incorrect ISR information in zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1097: - Resolution: Fixed Status: Resolved (was: Patch Available) Thanks a lot for the reviews,

[jira] [Closed] (KAFKA-1097) Race condition while reassigning low throughput partition leads to incorrect ISR information in zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede closed KAFKA-1097. > Race condition while reassigning low throughput partition leads to incorrect > ISR information in zo

[jira] [Updated] (KAFKA-1097) Race condition while reassigning low throughput partition leads to incorrect ISR information in zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1097: - Status: Patch Available (was: In Progress) > Race condition while reassigning low throughput par

[jira] [Work started] (KAFKA-1097) Race condition while reassigning low throughput partition leads to incorrect ISR information in zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-1097 started by Neha Narkhede. > Race condition while reassigning low throughput partition leads to incorrect > ISR information in zookeeper > ---

Re: Review Request 14865: Patch for KAFKA-1097

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/14865/#review28020 --- Ship it! - Jun Rao On Nov. 1, 2013, 4:55 p.m., Neha Narkhede wrot

[jira] [Commented] (KAFKA-1112) broker can not start itself after kafka is killed with -9

[ https://issues.apache.org/jira/browse/KAFKA-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811473#comment-13811473 ] Denis Serduik commented on KAFKA-1112: -- We've also faced with such behavior. Moreover

[jira] [Created] (KAFKA-1114) Add documentation for 0.8.1

Neha Narkhede created KAFKA-1114: Summary: Add documentation for 0.8.1 Key: KAFKA-1114 URL: https://issues.apache.org/jira/browse/KAFKA-1114 Project: Kafka Issue Type: Improvement C

[jira] [Commented] (KAFKA-1113) log.cleanup.interval.mins property should be renamed

[ https://issues.apache.org/jira/browse/KAFKA-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811465#comment-13811465 ] Neha Narkhede commented on KAFKA-1113: -- Filed KAFKA-1114 for adding 0.8.1 documentati

[jira] [Resolved] (KAFKA-1113) log.cleanup.interval.mins property should be renamed

[ https://issues.apache.org/jira/browse/KAFKA-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede resolved KAFKA-1113. -- Resolution: Fixed > log.cleanup.interval.mins property should be renamed >

[jira] [Work started] (KAFKA-1113) log.cleanup.interval.mins property should be renamed

[ https://issues.apache.org/jira/browse/KAFKA-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-1113 started by Neha Narkhede. > log.cleanup.interval.mins property should be renamed > > >

[jira] [Assigned] (KAFKA-1113) log.cleanup.interval.mins property should be renamed

[ https://issues.apache.org/jira/browse/KAFKA-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede reassigned KAFKA-1113: Assignee: Neha Narkhede > log.cleanup.interval.mins property should be renamed > --

[jira] [Updated] (KAFKA-1113) log.cleanup.interval.mins property should be renamed

[ https://issues.apache.org/jira/browse/KAFKA-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1113: - Affects Version/s: (was: 0.8) 0.8.1 > log.cleanup.interval.mins proper

[jira] [Commented] (KAFKA-1097) Race condition while reassigning low throughput partition leads to incorrect ISR information in zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811442#comment-13811442 ] Neha Narkhede commented on KAFKA-1097: -- Updated reviewboard https://reviews.apache.or

[jira] [Updated] (KAFKA-1097) Race condition while reassigning low throughput partition leads to incorrect ISR information in zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1097: - Attachment: KAFKA-1097_2013-11-01_09:55:33.patch > Race condition while reassigning low throughpu

Re: Review Request 14865: Patch for KAFKA-1097

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/14865/ --- (Updated Nov. 1, 2013, 4:55 p.m.) Review request for kafka. Bugs: KAFKA-1097

Re: Review Request 14865: Patch for KAFKA-1097

> On Nov. 1, 2013, 4:33 p.m., Jun Rao wrote: > > core/src/main/scala/kafka/controller/KafkaController.scala, lines 397-398 > > > > > > newReplicas really means the extra replicas in the reassigned replicas. > > So, we

Re: Review Request 14865: Patch for KAFKA-1097

> On Nov. 1, 2013, 4:33 p.m., Jun Rao wrote: > > core/src/main/scala/kafka/controller/KafkaController.scala, lines 383-387 > > > > > > In moveReassignedPartitionLeaderIfRequired(), we call > > partitionStateMachine.ha

[jira] [Updated] (KAFKA-1113) log.cleanup.interval.mins property should be renamed

[ https://issues.apache.org/jira/browse/KAFKA-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Kolodrevskiy updated KAFKA-1113: --- Description: in trunk log.cleanup.interval.mins should be renamed to log.retention.c

[jira] [Updated] (KAFKA-1113) log.cleanup.interval.mins property should be renamed

[ https://issues.apache.org/jira/browse/KAFKA-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Kolodrevskiy updated KAFKA-1113: --- Description: In trunk log.cleanup.interval.mins should be renamed to log.retention.c

[jira] [Created] (KAFKA-1113) log.cleanup.interval.mins property should be renamed

Viktor Kolodrevskiy created KAFKA-1113: -- Summary: log.cleanup.interval.mins property should be renamed Key: KAFKA-1113 URL: https://issues.apache.org/jira/browse/KAFKA-1113 Project: Kafka

[jira] [Assigned] (KAFKA-1112) broker can not start itself after kafka is killed with -9

[ https://issues.apache.org/jira/browse/KAFKA-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-1112: Assignee: Guozhang Wang > broker can not start itself after kafka is killed with -9 > -

Re: Review Request 14865: Patch for KAFKA-1097

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/14865/#review28011 --- core/src/main/scala/kafka/controller/KafkaController.scala

[jira] [Updated] (KAFKA-1112) broker can not start itself after kafka is killed with -9

[ https://issues.apache.org/jira/browse/KAFKA-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1112: - Component/s: log > broker can not start itself after kafka is killed with -9 > --

[jira] [Updated] (KAFKA-1112) broker can not start itself after kafka is killed with -9

[ https://issues.apache.org/jira/browse/KAFKA-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1112: - Affects Version/s: 0.8.1 > broker can not start itself after kafka is killed with -9 > --

[jira] [Created] (KAFKA-1112) broker can not start itself after kafka is killed with -9

Kane Kim created KAFKA-1112: --- Summary: broker can not start itself after kafka is killed with -9 Key: KAFKA-1112 URL: https://issues.apache.org/jira/browse/KAFKA-1112 Project: Kafka Issue Type: Bug

[jira] [Assigned] (KAFKA-1111) Broker prematurely accepts TopicMetadataRequests on startup

[ https://issues.apache.org/jira/browse/KAFKA-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede reassigned KAFKA-: Assignee: Neha Narkhede > Broker prematurely accepts TopicMetadataRequests on startup > ---