Is kafka mesos framework still supported? Is there any official kafka docker images?

Hi guys, I found kafka mesos framework on https://github.com/mesos/kafka. Is it still maintained? Is there any official kafka docker images available? Thanks, Jared, (??) Software developer Interested in open source software, big data, Linux

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

See Changes: [harsha] KAFKA-4345; Run decktape test for each pull request -- [...truncated 12505 lines...] ^

[jira] [Created] (KAFKA-4440) Make producer RecordMetadata non-final

Rajini Sivaram created KAFKA-4440: - Summary: Make producer RecordMetadata non-final Key: KAFKA-4440 URL: https://issues.apache.org/jira/browse/KAFKA-4440 Project: Kafka Issue Type: Improvemen

[GitHub] kafka pull request #2165: KAFKA-4440: Make producer RecordMetadata non-final

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/2165 KAFKA-4440: Make producer RecordMetadata non-final You can merge this pull request into a Git repository by running: $ git pull https://github.com/rajinisivaram/kafka KAFKA-4440 Alterna

[jira] [Commented] (KAFKA-4440) Make producer RecordMetadata non-final

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

Re: [DISCUSS] 0.10.1.1 Plan

Can we add KAFKA-4440 and KAFKA-4250 to the the list? They make ProducerRecord/ConsumerRecord/RecordMetadata non-final so that they can be extended. The changes have minimal impact on the codebase, but will really help when implementing other producers/consumers. It is not a bug-fix, but if we are

[jira] [Updated] (KAFKA-4405) Kafka consumer improperly send prefetch request

[ https://issues.apache.org/jira/browse/KAFKA-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ysysberserk updated KAFKA-4405: --- Description: Now kafka consumer has added max.poll.records to limit the count of messages return by p

Re: [DISCUSS] 0.10.1.1 Plan

Hi Rajini, I think we should avoid making changes like that in patch releases as it means that code that compiles with 0.10.1.1 may not compile with 0.10.1.0. Since we now have frequent time based releases, I think it makes sense for patch releases to only include bug fixes and test stability fixe

Re: [DISCUSS] 0.10.1.1 Plan

Hi Ismael, OK, I do agree with you. At the moment, our code wraps these three classes since they can't be extended. I recently noticed that two of the three are now non-final in trunk. If all three were made non-final, we would like to extend them, According to the Java specification: *Changing

[jira] [Commented] (KAFKA-4406) Add support for custom Java Security Providers in configuration

[ https://issues.apache.org/jira/browse/KAFKA-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15693153#comment-15693153 ] Magnus Reftel commented on KAFKA-4406: -- I'd be glad to write one if there's interest.

[GitHub] kafka pull request #2127: KAFKA-4384: ReplicaFetcherThread stopped after Rep...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2127 --- 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-4384) ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted message

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

[jira] [Updated] (KAFKA-4384) ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted message

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

[jira] [Updated] (KAFKA-4384) ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted message

[ https://issues.apache.org/jira/browse/KAFKA-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4384: --- Assignee: Jun He > ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted > mes

[DISCUSS] KIP-94: Session Windows

Hi all, I would like to start the discussion on KIP-94: https://cwiki.apache.org/confluence/display/KAFKA/KIP-94+Session+Windows Thanks, Damian

[jira] [Created] (KAFKA-4441) Kafka Monitoring is incorrect during rapid topic creation and deletion

Tom Crayford created KAFKA-4441: --- Summary: Kafka Monitoring is incorrect during rapid topic creation and deletion Key: KAFKA-4441 URL: https://issues.apache.org/jira/browse/KAFKA-4441 Project: Kafka

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

See Changes: [ismael] KAFKA-4384; ReplicaFetcherThread stops after ReplicaFetcherThread -- [...truncated 12181 lines...] org.apache.kafka.common.record.RecordTest > testChecksum[190] PASSED org

[jira] [Work started] (KAFKA-3452) Support session windows besides time interval windows

[ https://issues.apache.org/jira/browse/KAFKA-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3452 started by Damian Guy. - > Support session windows besides time interval windows > -

[jira] [Updated] (KAFKA-3452) Support session windows besides time interval windows

[ https://issues.apache.org/jira/browse/KAFKA-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-3452: -- Description: The Streams DSL currently does not provide session window as in the DataFlow model. We hav

[jira] [Updated] (KAFKA-3452) Support session windows

[ https://issues.apache.org/jira/browse/KAFKA-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-3452: -- Summary: Support session windows (was: Support session windows besides time interval windows) > Suppor

[GitHub] kafka pull request #2166: KAFKA-3452: Support session windows

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2166 KAFKA-3452: Support session windows Add support for SessionWindows based on design detailed in https://cwiki.apache.org/confluence/display/KAFKA/KIP-94+Session+Windows. This includes refactoring of

[jira] [Commented] (KAFKA-3452) Support session windows

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

Jenkins build is back to normal : kafka-trunk-jdk7 #1710

See

Re: [DISCUSS] 0.10.1.1 Plan

+1 it would be nice, and as is less restrive would not cause any issue. Saying that agree this is a fix build not a feature build. Sent using OWA for iPhone From: Rajini Sivaram Sent: Thursday, November 24, 2016 12:17:13 PM To: dev@kafka.apache.org Subjec

Reply to Camberwell agent

If you haven't sent the repose yet, please use this one: Hi , Thanks for the update. Ideally we want tenants don't have animals in the property. But if you have already allowed tenants to have the doc in the property, there is no reason why tenants cannot have the cats. Please address to the

[jira] [Commented] (KAFKA-4434) KafkaProducer configuration is logged twice

[ https://issues.apache.org/jira/browse/KAFKA-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15694561#comment-15694561 ] kevin.chen commented on KAFKA-4434: --- can I work on this issue? > KafkaProducer config

Re: [DISCUSS] KIP-93: Improve invalid timestamp handling in Kafka Streams

What I meant is that, for some changes (e.g. say we change the auto-repartition behavior that caused using different name conventions, or some changes that involve changing the underlying state store names, etc) the existing internal state including the stores and topics will probably not valid. So

[jira] [Created] (KAFKA-4442) Controller should grab lock when it is being initialized to avoid race condition

Dong Lin created KAFKA-4442: --- Summary: Controller should grab lock when it is being initialized to avoid race condition Key: KAFKA-4442 URL: https://issues.apache.org/jira/browse/KAFKA-4442 Project: Kafka

[GitHub] kafka pull request #2167: KAFKA-4442; Controller should grab lock when it is...

GitHub user lindong28 opened a pull request: https://github.com/apache/kafka/pull/2167 KAFKA-4442; Controller should grab lock when it is being initialized to avoid race condition You can merge this pull request into a Git repository by running: $ git pull https://github.com/

[jira] [Commented] (KAFKA-4442) Controller should grab lock when it is being initialized to avoid race condition

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

[jira] [Created] (KAFKA-4443) Controller should send UpdateMetadataRequest prior to LeaderAndIsrRequest during failover

Dong Lin created KAFKA-4443: --- Summary: Controller should send UpdateMetadataRequest prior to LeaderAndIsrRequest during failover Key: KAFKA-4443 URL: https://issues.apache.org/jira/browse/KAFKA-4443 Project

[jira] [Created] (KAFKA-4444) Aggregate requests sent from controller to broker during controlled shutdown

Dong Lin created KAFKA-: --- Summary: Aggregate requests sent from controller to broker during controlled shutdown Key: KAFKA- URL: https://issues.apache.org/jira/browse/KAFKA- Project: Kafka

Re: A strange controller log in Kafka 0.9.0.1

Does broker 100 keeps acting as the controller afterwards? What you observe is possible and should be transient since "unsubscribeChildChanges" on ZkClient and listener fired procedure are executed on different threads and they are not strictly synchronized. But if you continuously see broker 100's

[GitHub] kafka pull request #2169: KAFKA-4415; Reduce time to create and send Metadat...

GitHub user lindong28 opened a pull request: https://github.com/apache/kafka/pull/2169 KAFKA-4415; Reduce time to create and send MetadataUpdateRequest You can merge this pull request into a Git repository by running: $ git pull https://github.com/lindong28/kafka KAFKA-4415-2n

[GitHub] kafka pull request #2168: KAFKA-4443; Controller should send UpdateMetadataR...

GitHub user lindong28 opened a pull request: https://github.com/apache/kafka/pull/2168 KAFKA-4443; Controller should send UpdateMetadataRequest prior to LeaderAndIsrRequest during failover You can merge this pull request into a Git repository by running: $ git pull https://gi

[jira] [Commented] (KAFKA-4415) Reduce time to create and send MetadataUpdateRequest

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

[jira] [Commented] (KAFKA-4443) Controller should send UpdateMetadataRequest prior to LeaderAndIsrRequest during failover

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

[jira] [Created] (KAFKA-4445) PreferredLeaderElectionCommand should query zk only once per topic

Dong Lin created KAFKA-4445: --- Summary: PreferredLeaderElectionCommand should query zk only once per topic Key: KAFKA-4445 URL: https://issues.apache.org/jira/browse/KAFKA-4445 Project: Kafka Issue

[GitHub] kafka pull request #2170: KAFKA-4445; PreferredLeaderElectionCommand should ...

GitHub user lindong28 opened a pull request: https://github.com/apache/kafka/pull/2170 KAFKA-4445; PreferredLeaderElectionCommand should query zookeeper only once per topic You can merge this pull request into a Git repository by running: $ git pull https://github.com/lindong

[jira] [Commented] (KAFKA-4445) PreferredLeaderElectionCommand should query zk only once per topic

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

Re: [DISCUSS] KIP-93: Improve invalid timestamp handling in Kafka Streams

That does make sense. But KIP-93 does not change anything like this, so there is nothing to mention, IMHO. Or do you mean, the KIP should include that the change is backward compatible with this regard? -Matthias On 11/24/16 5:31 PM, Guozhang Wang wrote: > What I meant is that, for some change