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

[ https://issues.apache.org/jira/browse/KAFKA-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede reassigned KAFKA-1063: Assignee: Neha Narkhede > run log cleanup at startup > -- > >

[jira] [Closed] (KAFKA-1121) DumpLogSegments tool should print absolute file name to report inconsistencies

[ https://issues.apache.org/jira/browse/KAFKA-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede closed KAFKA-1121. > DumpLogSegments tool should print absolute file name to report inconsistencies >

[jira] [Resolved] (KAFKA-1121) DumpLogSegments tool should print absolute file name to report inconsistencies

[ https://issues.apache.org/jira/browse/KAFKA-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede resolved KAFKA-1121. -- Resolution: Fixed > DumpLogSegments tool should print absolute file name to report inconsistenc

[jira] [Created] (KAFKA-1122) Kafka can log giant log lines

Jason Rosenberg created KAFKA-1122: -- Summary: Kafka can log giant log lines Key: KAFKA-1122 URL: https://issues.apache.org/jira/browse/KAFKA-1122 Project: Kafka Issue Type: Bug Affects V

Re: Review Request 15248: DumpLogSegments should print absolute file path while printing errors

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15248/#review28238 --- Ship it! Ship It! - Neha Narkhede On Nov. 5, 2013, 10:08 p.m., S

Re: Review Request 15248: DumpLogSegments should print absolute file path while printing errors

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15248/#review28234 --- Ship it! core/src/main/scala/kafka/tools/DumpLogSegments.scala

Re: Review Request 15201: tool for checking the consistency among replicas

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15201/#review28162 --- core/src/main/scala/kafka/tools/ReplicaVerificationTool.scala

[jira] [Commented] (KAFKA-1121) DumpLogSegments tool should print absolute file name to report inconsistencies

[ https://issues.apache.org/jira/browse/KAFKA-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814308#comment-13814308 ] Swapnil Ghike commented on KAFKA-1121: -- Created reviewboard https://reviews.apache.or

[jira] [Updated] (KAFKA-1121) DumpLogSegments tool should print absolute file name to report inconsistencies

[ https://issues.apache.org/jira/browse/KAFKA-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Ghike updated KAFKA-1121: - Attachment: KAFKA-1121.patch > DumpLogSegments tool should print absolute file name to report inc

Review Request 15248: DumpLogSegments should print absolute file path while printing errors

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15248/ --- Review request for kafka. Bugs: KAFKA-1121 https://issues.apache.org/jira/b

[jira] [Updated] (KAFKA-1121) DumpLogSegments tool should print absolute file name to report inconsistencies

[ https://issues.apache.org/jira/browse/KAFKA-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Ghike updated KAFKA-1121: - Fix Version/s: 0.8.1 > DumpLogSegments tool should print absolute file name to report inconsisten

[jira] [Updated] (KAFKA-1121) DumpLogSegments tool should print absolute file name to report inconsistencies

[ https://issues.apache.org/jira/browse/KAFKA-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Ghike updated KAFKA-1121: - Affects Version/s: 0.8 > DumpLogSegments tool should print absolute file name to report inconsist

[jira] [Created] (KAFKA-1121) DumpLogSegments tool should print absolute file name to report inconsistencies

Swapnil Ghike created KAFKA-1121: Summary: DumpLogSegments tool should print absolute file name to report inconsistencies Key: KAFKA-1121 URL: https://issues.apache.org/jira/browse/KAFKA-1121 Project:

[jira] [Closed] (KAFKA-1118) /solr/select/ returned fields

[ https://issues.apache.org/jira/browse/KAFKA-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede closed KAFKA-1118. > /solr/select/ returned fields > - > > Key: KAFKA-1118 >

[jira] [Resolved] (KAFKA-1118) /solr/select/ returned fields

[ https://issues.apache.org/jira/browse/KAFKA-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] antoine s resolved KAFKA-1118. -- Resolution: Invalid > /solr/select/ returned fields > - > >

[jira] [Commented] (KAFKA-1118) /solr/select/ returned fields

[ https://issues.apache.org/jira/browse/KAFKA-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814220#comment-13814220 ] antoine s commented on KAFKA-1118: -- yes solr. not sure how i ended up here.. sorry > /so

[jira] [Updated] (KAFKA-1116) Need to upgrade sbt-assembly to compile on scala 2.10.2

[ https://issues.apache.org/jira/browse/KAFKA-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kane Kim updated KAFKA-1116: Fix Version/s: 0.8.1 0.8 Labels: build (was: ) Affects Versio

[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 ] Guozhang Wang updated KAFKA-1112: - Attachment: KAFKA-1112.out > broker can not start itself after kafka is killed with -9 >

[jira] [Updated] (KAFKA-1116) Need to upgrade sbt-assembly to compile on scala 2.10.2

[ https://issues.apache.org/jira/browse/KAFKA-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kane Kim updated KAFKA-1116: Attachment: kafka-1116-scala.2.10.2.patch Upgrading sbt-assembly > Need to upgrade sbt-assembly to compile

[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=13814134#comment-13814134 ] Guozhang Wang commented on KAFKA-1112: -- Attached another stack trace with more debugg

[jira] [Reopened] (KAFKA-1116) Need to upgrade sbt-assembly to compile on scala 2.10.2

[ https://issues.apache.org/jira/browse/KAFKA-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kane Kim reopened KAFKA-1116: - Attaching a patch > Need to upgrade sbt-assembly to compile on scala 2.10.2 > --

[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: - Assignee: Jay Kreps (was: Guozhang Wang) > broker can not start itself after kafka is killed wit

[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=13814110#comment-13814110 ] Neha Narkhede commented on KAFKA-1112: -- Stack trace - [2013-11-01 17:46:02,685] INFO

Re: Review Request 15201: tool for checking the consistency among replicas

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15201/#review28186 --- core/src/main/scala/kafka/tools/ReplicaVerificationTool.scala

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

Jun Rao created KAFKA-1120: -- Summary: Controller could miss a broker state change Key: KAFKA-1120 URL: https://issues.apache.org/jira/browse/KAFKA-1120 Project: Kafka Issue Type: Bug Comp

[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=13814096#comment-13814096 ] Jun Rao commented on KAFKA-1120: The root cause of this issue is that the controller misse

[jira] [Reopened] (KAFKA-1119) Kafka 0.8.1 overwrites previous per topic config changes

[ https://issues.apache.org/jira/browse/KAFKA-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede reopened KAFKA-1119: -- Yes, removing overrides is an issue today. I like option #1 where no value means delete the per-to

[jira] [Updated] (KAFKA-1119) Kafka 0.8.1 overwrites previous per topic config changes

[ https://issues.apache.org/jira/browse/KAFKA-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1119: - Priority: Critical (was: Blocker) > Kafka 0.8.1 overwrites previous per topic config changes > -

[jira] [Commented] (KAFKA-1118) /solr/select/ returned fields

[ https://issues.apache.org/jira/browse/KAFKA-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813971#comment-13813971 ] Jun Rao commented on KAFKA-1118: Is this created by mistake? This seems like a solr jira.

Re: [VOTE] Apache Kafka Release 0.8.0 - Candidate 2

+1. Verified quickstart and unit tests. Thanks, Jun On Sun, Nov 3, 2013 at 5:55 PM, Joe Stein wrote: > Hello, > > This is the second candidate for release of Apache Kafka 0.8.0. The only > change to this release candidate from the last is that this builds against > Java 6 as expected. > > R

[jira] [Updated] (KAFKA-1109) Need to fix GC log configuration code, not able to override KAFKA_GC_LOG_OPTS

[ https://issues.apache.org/jira/browse/KAFKA-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Kolodrevskiy updated KAFKA-1109: --- Affects Version/s: 0.8.1 > Need to fix GC log configuration code, not able to overrid