[jira] [Updated] (KAFKA-1694) kafka command line and centralized operations
[ https://issues.apache.org/jira/browse/KAFKA-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-1694: - Description: https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Command+Line+and+Related+Improvements was: https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Command+Line+and+Related+Improvements Assignee: Andrii Biletskyi +1 multiple admin request/response messages > kafka command line and centralized operations > - > > Key: KAFKA-1694 > URL: https://issues.apache.org/jira/browse/KAFKA-1694 > Project: Kafka > Issue Type: Bug >Reporter: Joe Stein >Assignee: Andrii Biletskyi >Priority: Critical > Fix For: 0.8.3 > > Attachments: KAFKA-1772_1802_1775_1774_v2.patch > > > https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Command+Line+and+Related+Improvements -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-1817) AdminUtils.createTopic vs kafka-topics.sh --create with partitions
[ https://issues.apache.org/jira/browse/KAFKA-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-1817: - Fix Version/s: 0.8.3 I added this as a sub ticket to the command line refactoring so we do this there. > AdminUtils.createTopic vs kafka-topics.sh --create with partitions > -- > > Key: KAFKA-1817 > URL: https://issues.apache.org/jira/browse/KAFKA-1817 > Project: Kafka > Issue Type: Sub-task >Affects Versions: 0.8.2 > Environment: debian linux current version up to date >Reporter: Jason Kania > Fix For: 0.8.3 > > > When topics are created using AdminUtils.createTopic in code, no partitions > folder is created The zookeeper shell shows this. > ls /brokers/topics/foshizzle > [] > However, when kafka-topics.sh --create is run, the partitions folder is > created: > ls /brokers/topics/foshizzle > [partitions] > The unfortunately useless error message "KeeperErrorCode = NoNode for > /brokers/topics/periodicReading/partitions" makes it unclear what to do. When > the topics are listed via kafka-topics.sh, they appear to have been created > fine. It would be good if the exception was wrapped by Kafka to suggested > looking in the zookeeper shell so a person didn't have to dig around to > understand what the meaning of this path is... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-1817) AdminUtils.createTopic vs kafka-topics.sh --create with partitions
[ https://issues.apache.org/jira/browse/KAFKA-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-1817: - Issue Type: Sub-task (was: Bug) Parent: KAFKA-1694 > AdminUtils.createTopic vs kafka-topics.sh --create with partitions > -- > > Key: KAFKA-1817 > URL: https://issues.apache.org/jira/browse/KAFKA-1817 > Project: Kafka > Issue Type: Sub-task >Affects Versions: 0.8.2 > Environment: debian linux current version up to date >Reporter: Jason Kania > Fix For: 0.8.3 > > > When topics are created using AdminUtils.createTopic in code, no partitions > folder is created The zookeeper shell shows this. > ls /brokers/topics/foshizzle > [] > However, when kafka-topics.sh --create is run, the partitions folder is > created: > ls /brokers/topics/foshizzle > [partitions] > The unfortunately useless error message "KeeperErrorCode = NoNode for > /brokers/topics/periodicReading/partitions" makes it unclear what to do. When > the topics are listed via kafka-topics.sh, they appear to have been created > fine. It would be good if the exception was wrapped by Kafka to suggested > looking in the zookeeper shell so a person didn't have to dig around to > understand what the meaning of this path is... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KAFKA-1694) kafka command line and centralized operations
[ https://issues.apache.org/jira/browse/KAFKA-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14245282#comment-14245282 ] Andrii Biletskyi commented on KAFKA-1694: - [~junrao]: Thank you for you comments. I agree with all you remarks, we also think about breaking AdminRequest into separate requests as a preferable solution. I created and uploaded this patch to see whether we go at least right direction in building shell for admin requests, as I understand there are no major concerns for now about the structure/approach so I'll submit this all with patch review tool and we can follow our usual procedure. > kafka command line and centralized operations > - > > Key: KAFKA-1694 > URL: https://issues.apache.org/jira/browse/KAFKA-1694 > Project: Kafka > Issue Type: Bug >Reporter: Joe Stein >Assignee: Andrii Biletskyi >Priority: Critical > Fix For: 0.8.3 > > Attachments: KAFKA-1772_1802_1775_1774_v2.patch > > > https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Command+Line+and+Related+Improvements -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-1815) ServerShutdownTest fails in trunk.
[ https://issues.apache.org/jira/browse/KAFKA-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1815: --- Assignee: Anatoly Fayngelerin (was: Chris Cope) Thanks, updated the assignee to Anatoly. > ServerShutdownTest fails in trunk. > -- > > Key: KAFKA-1815 > URL: https://issues.apache.org/jira/browse/KAFKA-1815 > Project: Kafka > Issue Type: Bug >Reporter: Anatoly Fayngelerin >Assignee: Anatoly Fayngelerin >Priority: Minor > Fix For: 0.8.3 > > Attachments: shutdown_test_fix.patch > > > I ran into these failures consistently when trying to build Kafka locally: > kafka.server.ServerShutdownTest > testCleanShutdown FAILED > java.lang.NullPointerException > at > kafka.server.ServerShutdownTest$$anonfun$verifyNonDaemonThreadsStatus$2.apply(ServerShutdownTest.scala:147) > at > kafka.server.ServerShutdownTest$$anonfun$verifyNonDaemonThreadsStatus$2.apply(ServerShutdownTest.scala:147) > at > scala.collection.TraversableOnce$$anonfun$count$1.apply(TraversableOnce.scala:114) > at > scala.collection.TraversableOnce$$anonfun$count$1.apply(TraversableOnce.scala:113) > at > scala.collection.IndexedSeqOptimized$class.foreach(IndexedSeqOptimized.scala:33) > at scala.collection.mutable.ArrayOps$ofRef.foreach(ArrayOps.scala:105) > at > scala.collection.TraversableOnce$class.count(TraversableOnce.scala:113) > at scala.collection.mutable.ArrayOps$ofRef.count(ArrayOps.scala:105) > at > kafka.server.ServerShutdownTest.verifyNonDaemonThreadsStatus(ServerShutdownTest.scala:147) > at > kafka.server.ServerShutdownTest.testCleanShutdown(ServerShutdownTest.scala:101) > kafka.server.ServerShutdownTest > testCleanShutdownWithDeleteTopicEnabled > FAILED > java.lang.NullPointerException > at > kafka.server.ServerShutdownTest$$anonfun$verifyNonDaemonThreadsStatus$2.apply(ServerShutdownTest.scala:147) > at > kafka.server.ServerShutdownTest$$anonfun$verifyNonDaemonThreadsStatus$2.apply(ServerShutdownTest.scala:147) > at > scala.collection.TraversableOnce$$anonfun$count$1.apply(TraversableOnce.scala:114) > at > scala.collection.TraversableOnce$$anonfun$count$1.apply(TraversableOnce.scala:113) > at > scala.collection.IndexedSeqOptimized$class.foreach(IndexedSeqOptimized.scala:33) > at scala.collection.mutable.ArrayOps$ofRef.foreach(ArrayOps.scala:105) > at > scala.collection.TraversableOnce$class.count(TraversableOnce.scala:113) > at scala.collection.mutable.ArrayOps$ofRef.count(ArrayOps.scala:105) > at > kafka.server.ServerShutdownTest.verifyNonDaemonThreadsStatus(ServerShutdownTest.scala:147) > at > kafka.server.ServerShutdownTest.testCleanShutdownWithDeleteTopicEnabled(ServerShutdownTest.scala:114) > kafka.server.ServerShutdownTest > testCleanShutdownAfterFailedStartup FAILED > java.lang.NullPointerException > at > kafka.server.ServerShutdownTest$$anonfun$verifyNonDaemonThreadsStatus$2.apply(ServerShutdownTest.scala:147) > at > kafka.server.ServerShutdownTest$$anonfun$verifyNonDaemonThreadsStatus$2.apply(ServerShutdownTest.scala:147) > at > scala.collection.TraversableOnce$$anonfun$count$1.apply(TraversableOnce.scala:114) > at > scala.collection.TraversableOnce$$anonfun$count$1.apply(TraversableOnce.scala:113) > at > scala.collection.IndexedSeqOptimized$class.foreach(IndexedSeqOptimized.scala:33) > at scala.collection.mutable.ArrayOps$ofRef.foreach(ArrayOps.scala:105) > at > scala.collection.TraversableOnce$class.count(TraversableOnce.scala:113) > at scala.collection.mutable.ArrayOps$ofRef.count(ArrayOps.scala:105) > at > kafka.server.ServerShutdownTest.verifyNonDaemonThreadsStatus(ServerShutdownTest.scala:147) > at > kafka.server.ServerShutdownTest.testCleanShutdownAfterFailedStartup(ServerShutdownTest.scala:141) > It looks like Jenkins also had issues with these tests: > https://builds.apache.org/job/Kafka-trunk/351/console > I would like to provide a patch that fixes this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
