[jira] [Updated] (KAFKA-2318) replica manager repeatedly tries to fetch from partitions already moved during controlled shutdown

[ https://issues.apache.org/jira/browse/KAFKA-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Rosenberg updated KAFKA-2318: --- Description: Using version 0.8.2.1. During a controlled shutdown, it seems like the left-hand

[jira] [Commented] (KAFKA-2231) Deleting a topic fails

[ https://issues.apache.org/jira/browse/KAFKA-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617601#comment-14617601 ] James G. Haberly commented on KAFKA-2231: - I deleted just one topic and tried to s

[jira] [Created] (KAFKA-2319) After controlled shutdown: IllegalStateException: Kafka scheduler has not been started

Jason Rosenberg created KAFKA-2319: -- Summary: After controlled shutdown: IllegalStateException: Kafka scheduler has not been started Key: KAFKA-2319 URL: https://issues.apache.org/jira/browse/KAFKA-2319

Re: Build failed in Jenkins: KafkaPreCommit #138

Ewen, We did have at least one successful run ( https://builds.apache.org/job/Kafka-trunk/526/console) after the rat patch. Perhaps you can file an Apache infra ticket to figure out why other runs fail? Thanks, Jun On Tue, Jul 7, 2015 at 11:16 AM, Ewen Cheslack-Postava wrote: > Is there a way

Re: Review Request 36030: Patch for KAFKA-972

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36030/#review90843 --- Thanks for the patch. Saw the following transient unit test failure.

Re: Review Request 35791: Patch for KAFKA-2298

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35791/#review90847 --- Ship it! Ship It! - Joel Koshy On June 24, 2015, 8 p.m., Dong Li

request forwarding in Kafka?

Hi Kafka folks, I'm investigating about using Kafka as a data ingress endpoint for our analytic service. In our scenario, Kafka cluster is behind NLB which has a public IP, and the data source service is under another public IP. Basically the data source service cannot access Kafka cluster nodes

Re: Review Request 34554: Patch for KAFKA-2205

> On July 7, 2015, 2:18 a.m., Jun Rao wrote: > > Thanks for the patch. A few more comments below. > > > > 1. The patch doesn't apply. Could you rebase? > > 2. Also, we need the logic to read all existing client configs. Is that in > > a separate jira? 1. Will do. 2. Hey Jun - I didn't understa

[jira] [Commented] (KAFKA-2205) Generalize TopicConfigManager to handle multiple entity configs

[ https://issues.apache.org/jira/browse/KAFKA-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617845#comment-14617845 ] Aditya A Auradkar commented on KAFKA-2205: -- Updated reviewboard https://reviews.a

Re: Review Request 34554: Patch for KAFKA-2205

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34554/ --- (Updated July 8, 2015, 2:12 a.m.) Review request for kafka and Joel Koshy. Bu

[jira] [Updated] (KAFKA-2205) Generalize TopicConfigManager to handle multiple entity configs

[ https://issues.apache.org/jira/browse/KAFKA-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya A Auradkar updated KAFKA-2205: - Attachment: KAFKA-2205_2015-07-07_19:12:15.patch > Generalize TopicConfigManager to handle

Re: Review Request 34554: Patch for KAFKA-2205

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34554/ --- (Updated July 8, 2015, 2:13 a.m.) Review request for kafka and Joel Koshy. Bu

[jira] [Commented] (KAFKA-2205) Generalize TopicConfigManager to handle multiple entity configs

[ https://issues.apache.org/jira/browse/KAFKA-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617849#comment-14617849 ] Aditya Auradkar commented on KAFKA-2205: [~junrao] - Addressed your comments. Can

[jira] [Commented] (KAFKA-2308) New producer + Snappy face un-compression errors after broker restart

[ https://issues.apache.org/jira/browse/KAFKA-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617878#comment-14617878 ] Gwen Shapira commented on KAFKA-2308: - Thanks for your comments, [~guozhang]. Closing

Review Request 36290: Patch for KAFKA-2308

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

[jira] [Updated] (KAFKA-2308) New producer + Snappy face un-compression errors after broker restart

[ https://issues.apache.org/jira/browse/KAFKA-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2308: Status: Patch Available (was: Open) > New producer + Snappy face un-compression errors after broker

[jira] [Updated] (KAFKA-2308) New producer + Snappy face un-compression errors after broker restart

[ https://issues.apache.org/jira/browse/KAFKA-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2308: Attachment: KAFKA-2308.patch > New producer + Snappy face un-compression errors after broker restart

[jira] [Commented] (KAFKA-2308) New producer + Snappy face un-compression errors after broker restart

[ https://issues.apache.org/jira/browse/KAFKA-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617887#comment-14617887 ] Gwen Shapira commented on KAFKA-2308: - Created reviewboard https://reviews.apache.org/

[jira] [Comment Edited] (KAFKA-2308) New producer + Snappy face un-compression errors after broker restart

[ https://issues.apache.org/jira/browse/KAFKA-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617878#comment-14617878 ] Gwen Shapira edited comment on KAFKA-2308 at 7/8/15 2:54 AM: -

Build failed in Jenkins: KafkaPreCommit #140

See Changes: [jjkoshy] KAFKA-2298; Client Selector can drop connections on InvalidReceiveException without notifying NetworkClient; reviewed by Jason Gustafson and Joel Koshy -- Started by an SCM

Build failed in Jenkins: Kafka-trunk #531

See Changes: [jjkoshy] KAFKA-2298; Client Selector can drop connections on InvalidReceiveException without notifying NetworkClient; reviewed by Jason Gustafson and Joel Koshy -- Started by an SCM ch

[jira] [Commented] (KAFKA-2308) New producer + Snappy face un-compression errors after broker restart

[ https://issues.apache.org/jira/browse/KAFKA-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617949#comment-14617949 ] Gwen Shapira commented on KAFKA-2308: - Actually, looks likely that it is Snappy (even

Re: Build failed in Jenkins: KafkaPreCommit #138

You can reproduce the rat failure by running: ./gradlew clean && gradlew test If you run gradlew test again it does not report any error. build.gradle uses Grgit to expand the gitignore files to exclude. For a clean build, the build directory does not exist (yet). So it is not excluded by rat.

Jenkins build is back to normal : Kafka-trunk #532

See

Re: Build failed in Jenkins: KafkaPreCommit #138

> explicitly specify an exclude for build/rat/rat-report.xml (btw, I went ahead with a trivial commit for the above - let me know if there are any concerns) On Tue, Jul 07, 2015 at 09:44:27PM -0700, Joel Koshy wrote: > You can reproduce the rat failure by running: ./gradlew clean && > gradlew tes

Build failed in Jenkins: KafkaPreCommit #141

See Changes: [jjkoshy] Trivial commit - explicitly exclude build/rat-report.xml from rat check -- Started by an SCM change Building remotely on ubuntu3 (Ubuntu ubuntu legacy-ubuntu) in workspace

[jira] [Commented] (KAFKA-2310) Add config to prevent broker becoming controller

[ https://issues.apache.org/jira/browse/KAFKA-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14618034#comment-14618034 ] Joe Stein commented on KAFKA-2310: -- Hey [~jjkoshy] I had suggested to Andrii that it migh

Re: Build failed in Jenkins: KafkaPreCommit #138

Ah, that makes sense, thanks for finding that. We could alternatively use build/** to avoid everything under build, or include a more complete list via .gitignore instead (although that would have to be done carefully since the pattern matching works differently). Unfortunately grgit is required to

Re: Review Request 36030: Patch for KAFKA-972

> On July 8, 2015, 12:52 a.m., Jun Rao wrote: > > Thanks for the patch. Saw the following transient unit test failure. > > > > kafka.integration.TopicMetadataTest > > > testIsrAfterBrokerShutDownAndJoinsBack FAILED > > junit.framework.AssertionFailedError: Topic metadata is not correctly >

[jira] [Updated] (KAFKA-972) MetadataRequest returns stale list of brokers

[ https://issues.apache.org/jira/browse/KAFKA-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-972: - Attachment: KAFKA-972_2015-07-07_23:24:13.patch > MetadataRequest returns stale list of brokers > -

Re: Review Request 36030: Patch for KAFKA-972

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36030/ --- (Updated July 8, 2015, 6:24 a.m.) Review request for kafka. Bugs: KAFKA-972

[jira] [Commented] (KAFKA-972) MetadataRequest returns stale list of brokers

[ https://issues.apache.org/jira/browse/KAFKA-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14618050#comment-14618050 ] Ashish K Singh commented on KAFKA-972: -- Updated reviewboard https://reviews.apache.org

<    1   2