[jira] [Updated] (KAFKA-3378) Client blocks forever if SocketChannel connects instantly

[ https://issues.apache.org/jira/browse/KAFKA-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3378: Resolution: Fixed Status: Resolved (was: Patch Available) > Client blocks forever if

[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=15203751#comment-15203751 ] Gwen Shapira commented on KAFKA-1173: - [~ewencp] Does it make sense to copy vagrant instructions to

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

See Changes: [junrao] MINOR: Fix FetchRequest.getErrorResponse for version 1 -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-us1 (Ubuntu

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

See Changes: [junrao] KAFKA-3378; Follow-up to ensure we `finishConnect` for immediately [junrao] MINOR: Fix FetchRequest.getErrorResponse for version 1 -- Started by an SCM change [EnvInject]

[jira] [Commented] (KAFKA-3378) Client blocks forever if SocketChannel connects instantly

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

[GitHub] kafka pull request: KAFKA-3378; Follow-up to ensure we `finishConn...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1103 --- 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

[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=15203615#comment-15203615 ] Maysam Yabandeh commented on KAFKA-3428: I believe volatile variable takes care of the

[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=15203603#comment-15203603 ] Ismael Juma commented on KAFKA-3428: OK, so you mean replacing `synchronized` by `volatile`. That

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

See Changes: [me] MINOR: Add vagrant up wrapper for simple parallel bringup on aws -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H11 (docker

[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=15203578#comment-15203578 ] Maysam Yabandeh commented on KAFKA-3428: Sure. Will do that. bq. By the way, what is the

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

See Changes: [me] MINOR: Add vagrant up wrapper for simple parallel bringup on aws -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-us1

[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=15203573#comment-15203573 ] Ismael Juma commented on KAFKA-3428: By the way, what is the reasoning for stating that

[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=15203572#comment-15203572 ] Ismael Juma commented on KAFKA-3428: Seems like a nice improvement. Since you have the changes

[GitHub] kafka pull request: MINOR: Add vagrant up wrapper for simple paral...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/982 --- 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

[jira] [Updated] (KAFKA-3378) Client blocks forever if SocketChannel connects instantly

[ https://issues.apache.org/jira/browse/KAFKA-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3378: --- Status: Patch Available (was: Reopened) > Client blocks forever if SocketChannel connects instantly

[jira] [Commented] (KAFKA-3378) Client blocks forever if SocketChannel connects instantly

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

[GitHub] kafka pull request: KAFKA-3378; Follow-up to ensure we `finishConn...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1103 KAFKA-3378; Follow-up to ensure we `finishConnect` for immediately connected keys You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka

[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=15203568#comment-15203568 ] Maysam Yabandeh commented on KAFKA-3428: The hardware spec needs an auditing process before shared

[jira] [Reopened] (KAFKA-3378) Client blocks forever if SocketChannel connects instantly

[ https://issues.apache.org/jira/browse/KAFKA-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-3378: > Client blocks forever if SocketChannel connects instantly >

[jira] [Updated] (KAFKA-3431) Move `BrokerEndPoint` from `o.a.k.common` to `o.a.k.common.internals`

[ https://issues.apache.org/jira/browse/KAFKA-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3431: --- Status: Patch Available (was: Open) > Move `BrokerEndPoint` from `o.a.k.common` to

[jira] [Commented] (KAFKA-3431) Move `BrokerEndPoint` from `o.a.k.common` to `o.a.k.common.internals`

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

[GitHub] kafka pull request: KAFKA-3431; Move `BrokerEndPoint` from `o.a.k....

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1102 KAFKA-3431; Move `BrokerEndPoint` from `o.a.k.common` to `o.a.k.common.internals` Also included a minor efficiency improvement in `kafka.cluster.EndPoint`. You can merge this pull request into a Git

[jira] [Created] (KAFKA-3431) Move `BrokerEndPoint` from `o.a.k.common` to `o.a.k.common.internals`

Ismael Juma created KAFKA-3431: -- Summary: Move `BrokerEndPoint` from `o.a.k.common` to `o.a.k.common.internals` Key: KAFKA-3431 URL: https://issues.apache.org/jira/browse/KAFKA-3431 Project: Kafka

[jira] [Resolved] (KAFKA-2970) Both UpdateMetadataRequest.java and LeaderAndIsrRequest.java have an Endpoint class

[ https://issues.apache.org/jira/browse/KAFKA-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2970. Resolution: Duplicate Marking as duplicate of KAFKA-2757. > Both UpdateMetadataRequest.java and

[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=15203558#comment-15203558 ] Ewen Cheslack-Postava commented on KAFKA-1173: -- [~sfgower] Those instructions are out of

[jira] [Created] (KAFKA-3430) Allow users to set key in KTable.toStream() and KStream

Guozhang Wang created KAFKA-3430: Summary: Allow users to set key in KTable.toStream() and KStream Key: KAFKA-3430 URL: https://issues.apache.org/jira/browse/KAFKA-3430 Project: Kafka Issue

[jira] [Created] (KAFKA-3429) Remove Serdes needed for repartitioning in KTable stateful operations

Guozhang Wang created KAFKA-3429: Summary: Remove Serdes needed for repartitioning in KTable stateful operations Key: KAFKA-3429 URL: https://issues.apache.org/jira/browse/KAFKA-3429 Project: Kafka

[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=15203464#comment-15203464 ] Ismael Juma commented on KAFKA-3428: Thanks for the report and interesting analysis. What was the

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

Maysam Yabandeh created KAFKA-3428: -- Summary: Remove metadata sync bottleneck from mirrormaker's producer Key: KAFKA-3428 URL: https://issues.apache.org/jira/browse/KAFKA-3428 Project: Kafka

[jira] [Commented] (KAFKA-3427) broker can return incorrect version of fetch response when the broker hits an unknown exception

[ https://issues.apache.org/jira/browse/KAFKA-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15203370#comment-15203370 ] Aditya Auradkar commented on KAFKA-3427: [~junrao] - Certainly, I can patch 0.9. > broker can

[jira] [Commented] (KAFKA-3427) broker can return incorrect version of fetch response when the broker hits an unknown exception

[ https://issues.apache.org/jira/browse/KAFKA-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15203351#comment-15203351 ] Jun Rao commented on KAFKA-3427: [~aauradkar], do you think you could patch this for the 0.9.0 branch as

[jira] [Commented] (KAFKA-3415) AdminOperationException when altering Topic with same number of partitions

[ https://issues.apache.org/jira/browse/KAFKA-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199909#comment-15199909 ] Ashish K Singh commented on KAFKA-3415: --- I think the tool should be used to bump up partition count,

[jira] [Commented] (KAFKA-3188) Add system test for KIP-31 and KIP-32 - Compatibility Test

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

KStreams Partition Assignment

I'm evaluating whether the KafkaStreams API will be something we can use on my current project. Namely, we want to be able to distribute the consumers on a Mesos/YARN cluster. It's not entirely clear to me in the code what is deciding which partitions get assigned at runtime and whether this is

Re: [DISCUSS] KIP-35 - Retrieve protocol version

I like it. I think the revised KIP-35 approach is simple, easy to understand, and workable. I think it will solve the main problem that I have had, and I assume other 3rd party client devs have had as well, and should open the door to more backwards-compatible drivers and less fracturing of client

[GitHub] kafka pull request: KAFKA-2832: Add a consumer config option to ex...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1082 --- 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

[GitHub] kafka pull request: KAFKA-2832: Add a consumer config option to ex...

GitHub user edoardocomar opened a pull request: https://github.com/apache/kafka/pull/1082 KAFKA-2832: Add a consumer config option to exclude internal topics A new consumer config option 'exclude.internal.topics' was added to allow excluding internal topics when wildcards are

[jira] [Updated] (KAFKA-3417) Invalid characters in config properties not be validated

[ https://issues.apache.org/jira/browse/KAFKA-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Byron Ruth updated KAFKA-3417: -- Summary: Invalid characters in config properties not be validated (was: Invalid characters in config

[jira] [Created] (KAFKA-3415) AdminOperationException when altering Topic with same number of partitions

Gérald Quintana created KAFKA-3415: -- Summary: AdminOperationException when altering Topic with same number of partitions Key: KAFKA-3415 URL: https://issues.apache.org/jira/browse/KAFKA-3415

[jira] [Commented] (KAFKA-3410) Unclean leader election and "Halting because log truncation is not allowed"

[ https://issues.apache.org/jira/browse/KAFKA-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15198550#comment-15198550 ] Gwen Shapira commented on KAFKA-3410: - 1. I'd say "If you just lost all your data on the leader and

Help: Producer with SSL did not work after upgrading the kafka 0.8.2 to Kafka 0.9

Hi folks, We just finished the upgrade from 0.8.2 to 0.9 with the instructions in Kafka web site (that set the protocol version as 0.8.2.x in Kafka server 0.9). After the upgrade, we want to try the producer with SSL endpoint, but never worked. Here's the error: ~/kafka_2.11-0.9.0.0$

[jira] [Commented] (KAFKA-3359) Parallel log-recovery of un-flushed segments on startup

[ https://issues.apache.org/jira/browse/KAFKA-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199544#comment-15199544 ] Vamsi Subhash Achanta commented on KAFKA-3359: -- *bump* Can this be reviewed? > Parallel

[jira] [Updated] (KAFKA-3378) Client blocks forever if SocketChannel connects instantly

[ https://issues.apache.org/jira/browse/KAFKA-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3378: Reviewer: Jun Rao > Client blocks forever if SocketChannel connects instantly >

[jira] [Commented] (KAFKA-3316) Add Connect REST API to list available connector classes

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

[jira] [Updated] (KAFKA-3336) Unify ser/de pair classes into one serde class

[ https://issues.apache.org/jira/browse/KAFKA-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3336: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request

[GitHub] kafka pull request: KAFKA-3397: use -1(latest) as time default val...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1068 --- 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

[jira] [Resolved] (KAFKA-3153) Serializer/Deserializer Registration and Type inference

[ https://issues.apache.org/jira/browse/KAFKA-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3153. -- Resolution: Won't Fix > Serializer/Deserializer Registration and Type inference >

Re: contributors list

Eric, What is your apache id? Guozhang On Tue, Mar 15, 2016 at 8:44 PM, Eric Wasserman wrote: > Kafka Devs, > > I am working on a PR for https://issues.apache.org/jira/browse/KAFKA-1981 > < >

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

See Changes: [cshapi] KAFKA-3328: SimpleAclAuthorizer can lose ACLs with frequent add/remov… -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely

[jira] [Commented] (KAFKA-3260) Increase the granularity of commit for SourceTask

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

[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=15201248#comment-15201248 ] Richard Hillmann commented on KAFKA-3409: - I have an something similar exception, running with two

[jira] [Commented] (KAFKA-3415) AdminOperationException when altering Topic with same number of partitions

[ https://issues.apache.org/jira/browse/KAFKA-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1510#comment-1510 ] Edoardo Comar commented on KAFKA-3415: -- As the user opening the JIRA stated, they use the scripts as

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

See Changes: [cshapi] KAFKA-3328: SimpleAclAuthorizer can lose ACLs with frequent add/remov… -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on

[jira] [Commented] (KAFKA-3328) SimpleAclAuthorizer can lose ACLs with frequent add/remove calls

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

[GitHub] kafka pull request: KAFKA-3328: SimpleAclAuthorizer can lose ACLs ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1006 --- 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

[jira] [Updated] (KAFKA-3328) SimpleAclAuthorizer can lose ACLs with frequent add/remove calls

[ https://issues.apache.org/jira/browse/KAFKA-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3328: Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request

[jira] [Commented] (KAFKA-3400) Topic stop working / can't describe topic

[ https://issues.apache.org/jira/browse/KAFKA-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199839#comment-15199839 ] Ashish K Singh commented on KAFKA-3400: --- Could you provide some details on the error you see. Also

[GitHub] kafka pull request: KAFKA-3188: Compatibility test for old and new...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1059 --- 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

[jira] [Updated] (KAFKA-3330) Truncate log cleaner offset checkpoint if the log is truncated

[ https://issues.apache.org/jira/browse/KAFKA-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3330: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 1009

[GitHub] kafka pull request: MINOR: Fix FetchRequest.getErrorResponse for v...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/1091 MINOR: Fix FetchRequest.getErrorResponse for version 1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/granthenke/kafka fetch-error