[jira] [Updated] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3442: --- Reviewer: Jun Rao > FetchResponse size exceeds max.partition.fetch.bytes > ---

[jira] [Updated] (KAFKA-3428) Remove metadata sync bottleneck from mirrormaker's producer

[ https://issues.apache.org/jira/browse/KAFKA-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3428: --- Fix Version/s: (was: 0.10.0.0) 0.10.0.1 > Remove metadata sync bottleneck from

[jira] [Commented] (KAFKA-3428) Remove metadata sync bottleneck from mirrormaker's producer

[ https://issues.apache.org/jira/browse/KAFKA-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206112#comment-15206112 ] Ismael Juma commented on KAFKA-3428: Given that the first RC for 0.10.0.0 has gone out

RE: [VOTE] 0.10.0.0 RC0

I would like KAFKA-3296 to be looked at for 0.10, this is causing us significant issues in our testing. There's a comment in the bug that this is possibly caused by KAFKA-3215, but that was fixed in 0.9, and KAFKA-3296 is reproducible in 0.9, so it could be a regression. SimonC -Original M

[jira] [Created] (KAFKA-3445) ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit

Ryan P created KAFKA-3445: - Summary: ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit Key: KAFKA-3445 URL: https://issues.apache.org/jira/browse/KAFKA-3445 Project: Kafka Issue

[jira] [Work stopped] (KAFKA-3038) Speeding up partition reassignment after broker failure

[ https://issues.apache.org/jira/browse/KAFKA-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3038 stopped by Eno Thereska. --- > Speeding up partition reassignment after broker failure > ---

[jira] [Created] (KAFKA-3446) SIGSEGV (0xb) Crash - libjvm.so / JVM_FindSignal

Tobias Feldhaus created KAFKA-3446: -- Summary: SIGSEGV (0xb) Crash - libjvm.so / JVM_FindSignal Key: KAFKA-3446 URL: https://issues.apache.org/jira/browse/KAFKA-3446 Project: Kafka Issue Type

[jira] [Updated] (KAFKA-3446) SIGSEGV (0xb) Crash - libjvm.so / JVM_FindSignal

[ https://issues.apache.org/jira/browse/KAFKA-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Feldhaus updated KAFKA-3446: --- Environment: FreeBSD 10.2, OpenJDK (build 1.8.0_72-b15) (was: FreeBSD 10.2, OpenJDK ) > SIGS

[jira] [Commented] (KAFKA-3446) SIGSEGV (0xb) Crash - libjvm.so / JVM_FindSignal

[ https://issues.apache.org/jira/browse/KAFKA-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206202#comment-15206202 ] Ismael Juma commented on KAFKA-3446: This probably unrelated to Kafka, see: https://fo

[jira] [Commented] (KAFKA-3446) SIGSEGV (0xb) Crash - libjvm.so / JVM_FindSignal

[ https://issues.apache.org/jira/browse/KAFKA-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206214#comment-15206214 ] Tobias Feldhaus commented on KAFKA-3446: We are running the newest Version of Open

[jira] [Commented] (KAFKA-3446) SIGSEGV (0xb) Crash - libjvm.so / JVM_FindSignal

[ https://issues.apache.org/jira/browse/KAFKA-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206205#comment-15206205 ] Tobias Feldhaus commented on KAFKA-3446: We are running the newest Version of Open

[jira] [Issue Comment Deleted] (KAFKA-3446) SIGSEGV (0xb) Crash - libjvm.so / JVM_FindSignal

[ https://issues.apache.org/jira/browse/KAFKA-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Feldhaus updated KAFKA-3446: --- Comment: was deleted (was: We are running the newest Version of OpenJDK8 and FreeBSD 10.2 "Fr

[jira] [Commented] (KAFKA-3446) SIGSEGV (0xb) Crash - libjvm.so / JVM_FindSignal

[ https://issues.apache.org/jira/browse/KAFKA-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206248#comment-15206248 ] Ismael Juma commented on KAFKA-3446: That link was just one example. The kind of error

[jira] [Updated] (KAFKA-3446) SIGSEGV (0xb) Crash - libjvm.so / JVM_FindSignal

[ https://issues.apache.org/jira/browse/KAFKA-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Feldhaus updated KAFKA-3446: --- Environment: FreeBSD 10.2, OpenJDK (build 1.8.0_72-b15), Scala 2.11.7 (was: FreeBSD 10.2, Ope

[jira] [Updated] (KAFKA-3445) ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit

[ https://issues.apache.org/jira/browse/KAFKA-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P updated KAFKA-3445: -- Attachment: KAFKA-3445.patch Adding a variable for TASKS_MIN_CONFIG is probably a bit of overkill but that can

[jira] [Updated] (KAFKA-3445) ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit

[ https://issues.apache.org/jira/browse/KAFKA-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P updated KAFKA-3445: -- Description: I'll be the first to admit this is a bit nit picky but any property marked with Importance.HIGH sh

[jira] [Updated] (KAFKA-3445) ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit

[ https://issues.apache.org/jira/browse/KAFKA-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P updated KAFKA-3445: -- Description: I'll be the first to admit this is a bit nit picky any property marked with Importance.HIGH should

[jira] [Commented] (KAFKA-1173) Using Vagrant to get up and running with Apache Kafka

[ https://issues.apache.org/jira/browse/KAFKA-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206680#comment-15206680 ] Stefan Gower commented on KAFKA-1173: - Thanks. Will retry. Stefan From: Ewen Ch

[jira] [Commented] (KAFKA-3409) Mirror maker hangs indefinitely due to commit

[ https://issues.apache.org/jira/browse/KAFKA-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206717#comment-15206717 ] Jason Gustafson commented on KAFKA-3409: Assigning to myself. [~singhashish] Feel

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206723#comment-15206723 ] Jun Rao commented on KAFKA-3442: There is another tricky issue to think through. If a clie

[jira] [Assigned] (KAFKA-3435) Remove `Unstable` annotation from new Java Consumer

[ https://issues.apache.org/jira/browse/KAFKA-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke reassigned KAFKA-3435: -- Assignee: Grant Henke > Remove `Unstable` annotation from new Java Consumer > -

[jira] [Assigned] (KAFKA-3409) Mirror maker hangs indefinitely due to commit

[ https://issues.apache.org/jira/browse/KAFKA-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-3409: -- Assignee: Jason Gustafson > Mirror maker hangs indefinitely due to commit > --

[jira] [Commented] (KAFKA-3432) Cluster.update() thread-safety

[ https://issues.apache.org/jira/browse/KAFKA-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206721#comment-15206721 ] Guozhang Wang commented on KAFKA-3432: -- I think an additional option is to change `up

[jira] [Commented] (KAFKA-3435) Remove `Unstable` annotation from new Java Consumer

[ https://issues.apache.org/jira/browse/KAFKA-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206733#comment-15206733 ] ASF GitHub Bot commented on KAFKA-3435: --- GitHub user granthenke opened a pull reques

[jira] [Updated] (KAFKA-3435) Remove `Unstable` annotation from new Java Consumer

[ https://issues.apache.org/jira/browse/KAFKA-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3435: --- Status: Patch Available (was: Open) > Remove `Unstable` annotation from new Java Consumer > -

[GitHub] kafka pull request: KAFKA-3435: Remove `Unstable` annotation from ...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/1113 KAFKA-3435: Remove `Unstable` annotation from new Java Consumer You can merge this pull request into a Git repository by running: $ git pull https://github.com/granthenke/kafka remove-unsta

[jira] [Commented] (KAFKA-3210) Using asynchronous calls through the raw ZK API in ZkUtils

[ https://issues.apache.org/jira/browse/KAFKA-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206771#comment-15206771 ] Grant Henke commented on KAFKA-3210: [~fpj] I would be curious on your thoughts on oth

[jira] [Updated] (KAFKA-3441) 0.10.0 documentation still says "0.9.0"

[ https://issues.apache.org/jira/browse/KAFKA-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3441: --- Fix Version/s: 0.10.0.0 > 0.10.0 documentation still says "0.9.0" > --

[jira] [Updated] (KAFKA-3441) 0.10.0 documentation still says "0.9.0"

[ https://issues.apache.org/jira/browse/KAFKA-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3441: --- Affects Version/s: 0.10.0.0 > 0.10.0 documentation still says "0.9.0" > --

[jira] [Work started] (KAFKA-3409) Mirror maker hangs indefinitely due to commit

[ https://issues.apache.org/jira/browse/KAFKA-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3409 started by Jason Gustafson. -- > Mirror maker hangs indefinitely due to commit > --

[jira] [Updated] (KAFKA-3445) ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit

[ https://issues.apache.org/jira/browse/KAFKA-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P updated KAFKA-3445: -- Status: Patch Available (was: Open) > ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit > -

[jira] [Assigned] (KAFKA-3441) 0.10.0 documentation still says "0.9.0"

[ https://issues.apache.org/jira/browse/KAFKA-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke reassigned KAFKA-3441: -- Assignee: Grant Henke > 0.10.0 documentation still says "0.9.0" > -

[jira] [Assigned] (KAFKA-3437) We don't need sitedocs package for every scala version

[ https://issues.apache.org/jira/browse/KAFKA-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke reassigned KAFKA-3437: -- Assignee: Grant Henke > We don't need sitedocs package for every scala version > --

[jira] [Updated] (KAFKA-3437) We don't need sitedocs package for every scala version

[ https://issues.apache.org/jira/browse/KAFKA-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3437: --- Fix Version/s: 0.10.0.1 > We don't need sitedocs package for every scala version > ---

[jira] [Updated] (KAFKA-3437) We don't need sitedocs package for every scala version

[ https://issues.apache.org/jira/browse/KAFKA-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3437: --- Affects Version/s: 0.9.0.0 > We don't need sitedocs package for every scala version >

[jira] [Updated] (KAFKA-3438) Rack Aware Replica Reassignment should warn of overloaded brokers

[ https://issues.apache.org/jira/browse/KAFKA-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3438: --- Affects Version/s: 0.10.0.0 > Rack Aware Replica Reassignment should warn of overloaded brokers >

[jira] [Updated] (KAFKA-3438) Rack Aware Replica Reassignment should warn of overloaded brokers

[ https://issues.apache.org/jira/browse/KAFKA-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3438: --- Fix Version/s: 0.10.0.1 > Rack Aware Replica Reassignment should warn of overloaded brokers >

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206790#comment-15206790 ] Dana Powers commented on KAFKA-3442: yes, kafka-python uses the same check for partial

[jira] [Assigned] (KAFKA-3301) CommonClientConfigs.METRICS_SAMPLE_WINDOW_MS_DOC is incorrect

[ https://issues.apache.org/jira/browse/KAFKA-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke reassigned KAFKA-3301: -- Assignee: Grant Henke > CommonClientConfigs.METRICS_SAMPLE_WINDOW_MS_DOC is incorrect > --

[jira] [Commented] (KAFKA-3409) Mirror maker hangs indefinitely due to commit

[ https://issues.apache.org/jira/browse/KAFKA-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206800#comment-15206800 ] Ashish K Singh commented on KAFKA-3409: --- [~hachikuji] there is a trivial patch, htt

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206808#comment-15206808 ] Jiangjie Qin commented on KAFKA-3442: - [~junrao] Yes, this is a known issue when the o

[jira] [Commented] (KAFKA-3409) Mirror maker hangs indefinitely due to commit

[ https://issues.apache.org/jira/browse/KAFKA-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206820#comment-15206820 ] Jason Gustafson commented on KAFKA-3409: [~singhashish] Thanks! The thing that's b

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206838#comment-15206838 ] Magnus Edenhill commented on KAFKA-3442: librdkafka silently ignores partial messa

[jira] [Commented] (KAFKA-3301) CommonClientConfigs.METRICS_SAMPLE_WINDOW_MS_DOC is incorrect

[ https://issues.apache.org/jira/browse/KAFKA-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206866#comment-15206866 ] ASF GitHub Bot commented on KAFKA-3301: --- GitHub user granthenke opened a pull reques

[GitHub] kafka pull request: KAFKA-3301: CommonClientConfigs.METRICS_SAMPLE...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/1114 KAFKA-3301: CommonClientConfigs.METRICS_SAMPLE_WINDOW_MS_DOC is incor… …rect You can merge this pull request into a Git repository by running: $ git pull https://github.com/granthenke/ka

[jira] [Updated] (KAFKA-3301) CommonClientConfigs.METRICS_SAMPLE_WINDOW_MS_DOC is incorrect

[ https://issues.apache.org/jira/browse/KAFKA-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3301: --- Status: Patch Available (was: Open) > CommonClientConfigs.METRICS_SAMPLE_WINDOW_MS_DOC is incorrect

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206867#comment-15206867 ] Jun Rao commented on KAFKA-3442: [~becket_qin], it's probably better if we keep supporting

Jenkins job for 0.10.0

Hi Team Kafka, Just a quick update - I've created a Jenkins job to test the 0.10.0 branch, to make sure we don't accidentally break it :) I know our tests have been all over the place recently, so this may not be as useful as it should be - but it is worth taking a look at the tests to make sure

[jira] [Comment Edited] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206808#comment-15206808 ] Jiangjie Qin edited comment on KAFKA-3442 at 3/22/16 5:42 PM: --

[jira] [Updated] (KAFKA-3426) Improve protocol type errors when invalid sizes are received

[ https://issues.apache.org/jira/browse/KAFKA-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3426: --- Affects Version/s: 0.9.0.0 > Improve protocol type errors when invalid sizes are received > --

[jira] [Assigned] (KAFKA-3417) Invalid characters in config properties not being validated?

[ https://issues.apache.org/jira/browse/KAFKA-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke reassigned KAFKA-3417: -- Assignee: Grant Henke > Invalid characters in config properties not being validated? >

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206876#comment-15206876 ] Dana Powers commented on KAFKA-3442: [~junrao] Actually I meant adding the error code

[jira] [Resolved] (KAFKA-3367) Delete topic dont delete the complete log from kafka

[ https://issues.apache.org/jira/browse/KAFKA-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KAFKA-3367. Resolution: Not A Problem > Delete topic dont delete the complete log from kafka > -

[jira] [Updated] (KAFKA-3347) Configure java to prefer ipv4

[ https://issues.apache.org/jira/browse/KAFKA-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3347: --- Status: Patch Available (was: Open) > Configure java to prefer ipv4 > - >

[jira] [Updated] (KAFKA-3347) Configure java to prefer ipv4

[ https://issues.apache.org/jira/browse/KAFKA-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3347: --- Assignee: Jeremy Custenborder > Configure java to prefer ipv4 > - > >

[jira] [Commented] (KAFKA-3210) Using asynchronous calls through the raw ZK API in ZkUtils

[ https://issues.apache.org/jira/browse/KAFKA-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206935#comment-15206935 ] Flavio Junqueira commented on KAFKA-3210: - [~granthenke] my main goal here is to h

[jira] [Commented] (KAFKA-3296) All consumer reads hang indefinately

[ https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206956#comment-15206956 ] Jun Rao commented on KAFKA-3296: [~thecoop1984], it's a bit weird that that the controller

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206990#comment-15206990 ] Jiangjie Qin commented on KAFKA-3442: - I am thinking about the same thing if we want t

[GitHub] kafka pull request: KAFKA-3435: Remove `Unstable` annotation from ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1113 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-3435) Remove `Unstable` annotation from new Java Consumer

[ https://issues.apache.org/jira/browse/KAFKA-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207030#comment-15207030 ] ASF GitHub Bot commented on KAFKA-3435: --- Github user asfgit closed the pull request

[jira] [Updated] (KAFKA-3435) Remove `Unstable` annotation from new Java Consumer

[ https://issues.apache.org/jira/browse/KAFKA-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3435: Resolution: Fixed Fix Version/s: 0.10.1.0 Status: Resolved (was: Patch Available)

[GitHub] kafka pull request: MINOR: Remove the very misleading comment line...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/793 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207068#comment-15207068 ] Dana Powers commented on KAFKA-3442: I think old clients might work better if the sing

[GitHub] kafka pull request: KAFKA-3426; Improve protocol type errors when ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1100 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-3426) Improve protocol type errors when invalid sizes are received

[ https://issues.apache.org/jira/browse/KAFKA-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207121#comment-15207121 ] ASF GitHub Bot commented on KAFKA-3426: --- Github user asfgit closed the pull request

[jira] [Updated] (KAFKA-3426) Improve protocol type errors when invalid sizes are received

[ https://issues.apache.org/jira/browse/KAFKA-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3426: Resolution: Fixed Fix Version/s: 0.10.0.0 0.10.1.0 Status: Resol

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207127#comment-15207127 ] Jiangjie Qin commented on KAFKA-3442: - [~dana.powers] I think we all agree that having

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207142#comment-15207142 ] Dana Powers commented on KAFKA-3442: sounds good to me! > FetchResponse size exceeds

Build failed in Jenkins: kafka-0.10-jdk7 #2

See Changes: [cshapi] KAFKA-3435: Remove `Unstable` annotation from new Java Consumer [cshapi] MINOR: Remove the very misleading comment lines -- [...truncated 3119 lines...] kafka.log.BrokerCompre

[GitHub] kafka pull request: KAFKA-3319: improve session timeout broker/cli...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1106 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-3319) Improve session timeout broker and client configuration documentation

[ https://issues.apache.org/jira/browse/KAFKA-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207182#comment-15207182 ] ASF GitHub Bot commented on KAFKA-3319: --- Github user asfgit closed the pull request

[jira] [Resolved] (KAFKA-3319) Improve session timeout broker and client configuration documentation

[ https://issues.apache.org/jira/browse/KAFKA-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3319. -- Resolution: Fixed Fix Version/s: 0.10.0.0 Issue resolved by pull request 1106 [https://gi

[GitHub] kafka pull request: KAFKA-3219: Fix long topic name validation

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/898 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

[jira] [Commented] (KAFKA-3219) Long topic names mess up broker topic state

[ https://issues.apache.org/jira/browse/KAFKA-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207185#comment-15207185 ] ASF GitHub Bot commented on KAFKA-3219: --- Github user asfgit closed the pull request

[jira] [Updated] (KAFKA-3219) Long topic names mess up broker topic state

[ https://issues.apache.org/jira/browse/KAFKA-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3219: Resolution: Fixed Fix Version/s: 0.10.0.0 Status: Resolved (was: Patch Available)

Build failed in Jenkins: kafka-trunk-jdk8 #468

See Changes: [cshapi] KAFKA-3435: Remove `Unstable` annotation from new Java Consumer [cshapi] MINOR: Remove the very misleading comment lines -- [...truncated 5378 lines...] kafka.log.BrokerCom

[jira] [Commented] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207225#comment-15207225 ] Jason Gustafson commented on KAFKA-3177: [~becket_qin] Were you planning to submit

[GitHub] kafka pull request: KAFKA-3409: handle CommitFailedException in Mi...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1115 KAFKA-3409: handle CommitFailedException in MirrorMaker You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-3409 Alternativ

[jira] [Commented] (KAFKA-3409) Mirror maker hangs indefinitely due to commit

[ https://issues.apache.org/jira/browse/KAFKA-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207240#comment-15207240 ] ASF GitHub Bot commented on KAFKA-3409: --- GitHub user hachikuji opened a pull request

Build failed in Jenkins: kafka-trunk-jdk7 #1136

See Changes: [cshapi] KAFKA-3435: Remove `Unstable` annotation from new Java Consumer [cshapi] MINOR: Remove the very misleading comment lines [cshapi] KAFKA-3426; Improve protocol type errors when invalid sizes are received --

Build failed in Jenkins: kafka-0.10-jdk7 #3

See Changes: [cshapi] KAFKA-3426; Improve protocol type errors when invalid sizes are received -- [...truncated 5446 lines...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[1] PASSED

[GitHub] kafka pull request: KAFKA-3435: Follow up to fix checkstyle

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/1116 KAFKA-3435: Follow up to fix checkstyle You can merge this pull request into a Git repository by running: $ git pull https://github.com/ewencp/kafka kafka-3435-follow-up Alternatively you can

[jira] [Commented] (KAFKA-3435) Remove `Unstable` annotation from new Java Consumer

[ https://issues.apache.org/jira/browse/KAFKA-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207315#comment-15207315 ] ASF GitHub Bot commented on KAFKA-3435: --- GitHub user ewencp opened a pull request:

[GitHub] kafka pull request: KAFKA-3435: Follow up to fix checkstyle

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1116 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-3435) Remove `Unstable` annotation from new Java Consumer

[ https://issues.apache.org/jira/browse/KAFKA-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207319#comment-15207319 ] ASF GitHub Bot commented on KAFKA-3435: --- Github user asfgit closed the pull request

Build failed in Jenkins: kafka-trunk-jdk7 #1137

See Changes: [wangguoz] KAFKA-3319: improve session timeout broker/client config documentation [cshapi] KAFKA-3219: Fix long topic name validation -- [...truncated 3517 lines...] kafka.log.Br

[DISCUSS] KIP-51 - List Connectors REST API

Hi all, It was pointed out that we've been playing a bit fast and loose with API additions in Kafka. I think it's worth discussing a lighter weight process for APIs that are still marked unstable, but for the time being we'll add KIPs before adjusting these APIs. To that end, I'd like to discuss

Re: [DISCUSS] KIP-51 - List Connectors REST API

Hey Ewen, Just a quick question. It looks like we're returning a simple array containing the classnames. Would it make sense to return a set of objects instead? For example: [ { "class": "org.apache.kafka.connect.file.FileStreamSourceConnector"}, { "class": "org.apache.kafka.connect.file.File

Re: [DISCUSS] KIP-51 - List Connectors REST API

Yeah, we can do that. Not sure what we might want to add there, but makes sense to keep things flexible. Updated the KIP text to reflect this. -Ewen On Tue, Mar 22, 2016 at 2:51 PM, Jason Gustafson wrote: > Hey Ewen, > > Just a quick question. It looks like we're returning a simple array > cont

Build failed in Jenkins: kafka-trunk-jdk8 #469

See Changes: [cshapi] KAFKA-3426; Improve protocol type errors when invalid sizes are [wangguoz] KAFKA-3319: improve session timeout broker/client config documentation [cshapi] KAFKA-3219: Fix long topic name validation

[GitHub] kafka pull request: KAFKA-3301: CommonClientConfigs.METRICS_SAMPLE...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1114 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Updated] (KAFKA-3301) CommonClientConfigs.METRICS_SAMPLE_WINDOW_MS_DOC is incorrect

[ https://issues.apache.org/jira/browse/KAFKA-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3301: --- Resolution: Fixed Fix Version/s: (was: 0.10.1.0) 0.10.0.0 Status: Reso

[jira] [Commented] (KAFKA-3301) CommonClientConfigs.METRICS_SAMPLE_WINDOW_MS_DOC is incorrect

[ https://issues.apache.org/jira/browse/KAFKA-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207396#comment-15207396 ] ASF GitHub Bot commented on KAFKA-3301: --- Github user asfgit closed the pull request

Jenkins build is back to normal : kafka-0.10-jdk7 #4

See

[jira] [Commented] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207431#comment-15207431 ] Jiangjie Qin commented on KAFKA-3177: - [~hachikuji] It would be great if you can help.

Build failed in Jenkins: kafka-trunk-jdk8 #470

See Changes: [cshapi] KAFKA-3435: Follow up to fix checkstyle -- [...truncated 1621 lines...] kafka.consumer.ZookeeperConsumerConnectorTest > testConsumerDecoder PASSED kafka.consumer.Zookeeper

[VOTE] KIP-51 - List Connectors REST API

Since it's pretty minimal, we'd like to squeeze it into 0.10 if possible, and VOTE threads take 3 days, it was suggested it might make sense to just kick off voting on this KIP immediately (and restart it if someone raises an issue). Feel free to object and comment in the DISCUSS thread if you feel

Re: [VOTE] KIP-51 - List Connectors REST API

+1 (non-binding) On Tue, Mar 22, 2016 at 3:46 PM, Ewen Cheslack-Postava wrote: > Since it's pretty minimal, we'd like to squeeze it into 0.10 if possible, > and VOTE threads take 3 days, it was suggested it might make sense to just > kick off voting on this KIP immediately (and restart it if som

Re: [VOTE] KIP-51 - List Connectors REST API

+1 Straight forward enough and can't possibly break anything. On Tue, Mar 22, 2016 at 3:46 PM, Ewen Cheslack-Postava wrote: > Since it's pretty minimal, we'd like to squeeze it into 0.10 if possible, > and VOTE threads take 3 days, it was suggested it might make sense to just > kick off voting

Re: [VOTE] KIP-51 - List Connectors REST API

+1 On Tue, Mar 22, 2016 at 3:54 PM, Gwen Shapira wrote: > +1 > > Straight forward enough and can't possibly break anything. > > On Tue, Mar 22, 2016 at 3:46 PM, Ewen Cheslack-Postava > wrote: > > > Since it's pretty minimal, we'd like to squeeze it into 0.10 if possible, > > and VOTE threads ta

  1   2   >