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

See Changes: [wangguoz] MINOR: Fix ProcessorTopologyTestDriver to support multiple source topics [me] KAFKA-4042: Contain connector & task start/stop failures within the -- [...truncated

Re: Batch Expired

Are any requests at all making it? That is a pretty big timeout. However, I noticed if there is no connections made to broker, you can still get batch expiry. On Fri, Aug 26, 2016 at 6:32 AM, Ghosh, Achintya (Contractor) < achintya_gh...@comcast.com> wrote: > Hi there, > > What is the

[jira] [Resolved] (KAFKA-73) SyncProducer sends messages to invalid partitions without complaint

[ https://issues.apache.org/jira/browse/KAFKA-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dru Panchal resolved KAFKA-73. -- Resolution: Duplicate > SyncProducer sends messages to invalid partitions without complaint >

[jira] [Commented] (KAFKA-73) SyncProducer sends messages to invalid partitions without complaint

[ https://issues.apache.org/jira/browse/KAFKA-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15440101#comment-15440101 ] Dru Panchal commented on KAFKA-73: -- Marking this JIRA closed as the bug was solved with KAFKA-49. >

[jira] [Assigned] (KAFKA-73) SyncProducer sends messages to invalid partitions without complaint

[ https://issues.apache.org/jira/browse/KAFKA-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dru Panchal reassigned KAFKA-73: Assignee: Dru Panchal > SyncProducer sends messages to invalid partitions without complaint >

[jira] [Resolved] (KAFKA-156) Messages should not be dropped when brokers are unavailable

[ https://issues.apache.org/jira/browse/KAFKA-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dru Panchal resolved KAFKA-156. --- Resolution: Duplicate Fix Version/s: 0.10.1.0 > Messages should not be dropped when brokers are

[jira] [Commented] (KAFKA-156) Messages should not be dropped when brokers are unavailable

[ https://issues.apache.org/jira/browse/KAFKA-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15440079#comment-15440079 ] Dru Panchal commented on KAFKA-156: --- This JIRA is duplicated by KAFKA-789 which has provided the

[jira] [Assigned] (KAFKA-156) Messages should not be dropped when brokers are unavailable

[ https://issues.apache.org/jira/browse/KAFKA-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dru Panchal reassigned KAFKA-156: - Assignee: Dru Panchal > Messages should not be dropped when brokers are unavailable >

[jira] [Resolved] (KAFKA-2) a restful producer API

[ https://issues.apache.org/jira/browse/KAFKA-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dru Panchal resolved KAFKA-2. - Resolution: Information Provided (was: Unresolved) > a restful producer API > -- > >

[jira] [Assigned] (KAFKA-2) a restful producer API

[ https://issues.apache.org/jira/browse/KAFKA-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dru Panchal reassigned KAFKA-2: --- Assignee: Dru Panchal > a restful producer API > -- > > Key:

[jira] [Commented] (KAFKA-2) a restful producer API

[ https://issues.apache.org/jira/browse/KAFKA-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15440061#comment-15440061 ] Dru Panchal commented on KAFKA-2: - [~anandriyer] I would like to resolve this JIRA because the Kafka REST

[jira] [Commented] (KAFKA-3094) Kafka process 100% CPU when no message in topic

[ https://issues.apache.org/jira/browse/KAFKA-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15440050#comment-15440050 ] Dru Panchal commented on KAFKA-3094: [~oazabir] Do you still experience this issue have you been able

Jenkins build is back to normal : kafka-trunk-jdk8 #849

See

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

See Changes: [wangguoz] MINOR: Include request header in exception when correlation of -- [...truncated 12219 lines...] org.apache.kafka.streams.processor.internals.MinTimestampTrackerTest >

[jira] [Commented] (KAFKA-4020) Kafka consumer stop taking messages from kafka server

[ https://issues.apache.org/jira/browse/KAFKA-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15440016#comment-15440016 ] Dru Panchal commented on KAFKA-4020: [~shawnhe] What stopped working? Please provide more details. Did

[jira] [Commented] (KAFKA-4026) consumer block

[ https://issues.apache.org/jira/browse/KAFKA-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439982#comment-15439982 ] Dru Panchal commented on KAFKA-4026: [~imperio] So far I've tried setting up a 0.8.1.1 environment

Build failed in Jenkins: kafka-0.10.0-jdk7 #196

See Changes: [wangguoz] MINOR: Include request header in exception when correlation of -- [...truncated 5370 lines...] org.apache.kafka.clients.consumer.internals.ConsumerCoordinatorTest >

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

See Changes: [wangguoz] MINOR: Fix ProcessorTopologyTestDriver to support multiple source topics -- [...truncated 7298 lines...] kafka.log.LogTest >

[jira] [Resolved] (KAFKA-4042) DistributedHerder thread can die because of connector & task lifecycle exceptions

[ https://issues.apache.org/jira/browse/KAFKA-4042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-4042. -- Resolution: Fixed Issue resolved by pull request 1778

[jira] [Commented] (KAFKA-4042) DistributedHerder thread can die because of connector & task lifecycle exceptions

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

[GitHub] kafka pull request #1778: KAFKA-4042: Contain connector & task start/stop fa...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1778 --- 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-1981) Make log compaction point configurable

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

[GitHub] kafka pull request #1494: KAFKA-1981 Make log compaction point configurable

Github user ewasserman closed the pull request at: https://github.com/apache/kafka/pull/1494 --- 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-1981) Make log compaction point configurable

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

[GitHub] kafka pull request #1794: KAFKA-1981 Make log compaction point configurable

GitHub user ewasserman opened a pull request: https://github.com/apache/kafka/pull/1794 KAFKA-1981 Make log compaction point configurable Now uses LogSegment.largestTimestamp to determine age of segment's messages. You can merge this pull request into a Git repository by running:

[jira] [Updated] (KAFKA-4065) Missing Property in ProducerConfig.java - KafkaProducer API 0.9.0.0

[ https://issues.apache.org/jira/browse/KAFKA-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dru Panchal updated KAFKA-4065: --- Summary: Missing Property in ProducerConfig.java - KafkaProducer API 0.9.0.0 (was: Property missing

[jira] [Comment Edited] (KAFKA-4076) Kafka broker shuts down due to irrecoverable IO error

[ https://issues.apache.org/jira/browse/KAFKA-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439798#comment-15439798 ] Dru Panchal edited comment on KAFKA-4076 at 8/26/16 8:43 PM: - [~anyun] I can

[jira] [Commented] (KAFKA-4076) Kafka broker shuts down due to irrecoverable IO error

[ https://issues.apache.org/jira/browse/KAFKA-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439798#comment-15439798 ] Dru Panchal commented on KAFKA-4076: [~anyun] I can confirm [~omkreddy]'s analysis on this having

[jira] [Commented] (KAFKA-3129) Console producer issue when request-required-acks=0

[ https://issues.apache.org/jira/browse/KAFKA-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439764#comment-15439764 ] Vahid Hashemian commented on KAFKA-3129: [~cotedm] Thanks for looking into this. I think if we are

[jira] [Created] (KAFKA-4092) retention.bytes should not be allowed to be less than segment.bytes

Dustin Cote created KAFKA-4092: -- Summary: retention.bytes should not be allowed to be less than segment.bytes Key: KAFKA-4092 URL: https://issues.apache.org/jira/browse/KAFKA-4092 Project: Kafka

[GitHub] kafka pull request #1782: MINOR: Fix ProcessorTopologyTestDriver to support ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1782 --- 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-3129) Console producer issue when request-required-acks=0

[ https://issues.apache.org/jira/browse/KAFKA-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439670#comment-15439670 ] Dustin Cote commented on KAFKA-3129: What I'm seeing is that we are faking the callback

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

See Changes: [wangguoz] MINOR: Include request header in exception when correlation of -- [...truncated 4916 lines...] kafka.utils.ZkUtilsTest > testSuccessfulConditionalDeletePath PASSED

[jira] [Resolved] (KAFKA-3993) Console producer drops data

[ https://issues.apache.org/jira/browse/KAFKA-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dustin Cote resolved KAFKA-3993. Resolution: Duplicate Marking this a duplicate of KAFKA-3129. The workaround here is to set acks=1

[jira] [Created] (KAFKA-4091) Unable to produce or consume on any topic

Avi Chopra created KAFKA-4091: - Summary: Unable to produce or consume on any topic Key: KAFKA-4091 URL: https://issues.apache.org/jira/browse/KAFKA-4091 Project: Kafka Issue Type: Bug

[GitHub] kafka pull request #1793: MINOR: Include request header in exception when co...

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

Kafka KIP meeting Aug 30 at 11:00am PST

Hi, Everyone., We plan to have a Kafka KIP meeting this coming Tuesday at 11:00am PST. If you plan to attend but haven't received an invite, please let me know. The following is the tentative agenda. Agenda: KIP-48: delegation tokens Thanks, Jun

Re: Queryable state client read guarantees

Hi Mikael, Very good question. You are correct about the desired semantics. The semantic of case (a) depends on the local store as you mention. For case (b), the final check is always performed again on get(), and if the store has disappeared between the lookup and get, the user will get an

[jira] [Assigned] (KAFKA-4089) KafkaProducer raises Batch Expired exception

[ https://issues.apache.org/jira/browse/KAFKA-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumant Tambe reassigned KAFKA-4089: --- Assignee: Sumant Tambe (was: Dong Lin) > KafkaProducer raises Batch Expired exception >

Re: Using SSL port without specifying security protocol causes OOM on 0.9.0.1 and 0.10.0.1

Thank you for explaining that, it makes sense. -Jaikiran On Friday 26 August 2016 09:02 PM, Rajini Sivaram wrote: When a port is configured for SSL, broker expects SSL handshake messages before any Kafka requests are sent. But since the client is using PLAINTEXT on an SSL port, the client is

Re: Using SSL port without specifying security protocol causes OOM on 0.9.0.1 and 0.10.0.1

When a port is configured for SSL, broker expects SSL handshake messages before any Kafka requests are sent. But since the client is using PLAINTEXT on an SSL port, the client is interpreting SSL handshake protocol messages as Kafka requests. Hence the size (300MB) being allocated doesn't really

Queryable state client read guarantees

Hi, I've tried to understand the implementation and APIs from KIP-67 and would like to know the possible semantics for read requests from a client perspective. As a developer of a queryable state client, the access semantics I would like to have (I think...) is one where subsequent reads always

[jira] [Commented] (KAFKA-4081) Consumer API consumer new interface commitSyn does not verify the validity of offset

[ https://issues.apache.org/jira/browse/KAFKA-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439258#comment-15439258 ] Mickael Maison commented on KAFKA-4081: --- The same happens with 0.10.0.1. Looking at the offset

[jira] [Commented] (KAFKA-4090) JVM runs into OOM if (Java) client uses a SSL port without setting the security protocol

[ https://issues.apache.org/jira/browse/KAFKA-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439247#comment-15439247 ] jaikiran pai commented on KAFKA-4090: - Mailing list discussion is here

Re: Using SSL port without specifying security protocol causes OOM on 0.9.0.1 and 0.10.0.1

Hi Rajini, Just filed a JIRA as suggested https://issues.apache.org/jira/browse/KAFKA-4090. More comments inline. On Friday 26 August 2016 07:53 PM, Rajini Sivaram wrote: Jaikiran, At the moment there is no client-side configuration parameter to restrict the maximum request size on

[jira] [Created] (KAFKA-4090) JVM runs into OOM if (Java) client uses a SSL port without setting the security protocol

jaikiran pai created KAFKA-4090: --- Summary: JVM runs into OOM if (Java) client uses a SSL port without setting the security protocol Key: KAFKA-4090 URL: https://issues.apache.org/jira/browse/KAFKA-4090

Re: Using SSL port without specifying security protocol causes OOM on 0.9.0.1 and 0.10.0.1

Jaikiran, At the moment there is no client-side configuration parameter to restrict the maximum request size on clients. On the broker side, "socket.request.max.bytes" restricts the maximum buffer size allocated, protecting the broker from badly behaved or misconfigured clients. A KIP would be

[GitHub] kafka pull request #1793: MINOR: Include request header in exception when co...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1793 MINOR: Include request header in exception when correlation of request/response fails You can merge this pull request into a Git repository by running: $ git pull

Re: Using SSL port without specifying security protocol causes OOM on 0.9.0.1 and 0.10.0.1

Yes, please file a JIRA. On Fri, Aug 26, 2016 at 2:28 PM, Jaikiran Pai wrote: > We have been using Kafka 0.9.0.1 (server and Java client libraries). So > far we had been using it with plaintext transport but recently have been > considering upgrading to using SSL. It

Batch Expired

Hi there, What is the recommended Producer setting for Producer as I see a lot of Batch Expired exception even though I put request.timeout=6. Producer settings: acks=1 retries=3 batch.size=16384 linger.ms=5 buffer.memory=33554432 request.timeout.ms=6 timeout.ms=6 Thanks Achintya

Using SSL port without specifying security protocol causes OOM on 0.9.0.1 and 0.10.0.1

We have been using Kafka 0.9.0.1 (server and Java client libraries). So far we had been using it with plaintext transport but recently have been considering upgrading to using SSL. It mostly works except that a mis-configured producer (and even consumer) causes a hard to relate OutOfMemory

Re: [DISCUSS] KIP-76: Improve Kafka Streams Join Semantics

Thanks Bill. We will need to start an dedicated voting thread though. -Matthias On 08/26/2016 03:10 PM, Bill Bejeck wrote: > +1 > > On Fri, Aug 26, 2016 at 8:12 AM, Matthias J. Sax > wrote: > >> If there is no further feedback, I would like to start the voting process.

Re: [DISCUSS] KIP-76: Improve Kafka Streams Join Semantics

+1 On Fri, Aug 26, 2016 at 8:12 AM, Matthias J. Sax wrote: > If there is no further feedback, I would like to start the voting process. > > -Matthias > > On 08/19/2016 12:18 PM, Matthias J. Sax wrote: > > Hi, > > > > we have created KIP-76: Improve Kafka Streams Join

Re: [VOTE] KIP-63: Unify store and downstream caching in streams

+1 On Thu, Aug 25, 2016 at 11:45 AM, Matthias J. Sax wrote: > +1 > > On 08/25/2016 04:22 PM, Damian Guy wrote: > > +1 > > > > On Thu, 25 Aug 2016 at 11:57 Eno Thereska > wrote: > > > >> Hi folks, > >> > >> We'd like to start the vote for KIP-63.

Re: [DISCUSS] KIP-76: Improve Kafka Streams Join Semantics

If there is no further feedback, I would like to start the voting process. -Matthias On 08/19/2016 12:18 PM, Matthias J. Sax wrote: > Hi, > > we have created KIP-76: Improve Kafka Streams Join Semantics > >

[jira] [Commented] (KAFKA-2170) 10 LogTest cases failed for file.renameTo failed under windows

[ https://issues.apache.org/jira/browse/KAFKA-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438668#comment-15438668 ] Harald Kirsch commented on KAFKA-2170: -- Tried to added the patches. Since I had the 1757 in already,

[GitHub] kafka pull request #1792: KAFKA-3595: window stores use compact,delete confi...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/1792 KAFKA-3595: window stores use compact,delete config for changelogs changelogs of window stores now configure cleanup.policy=compact,delete with retention.ms set to window maintainMs +

[jira] [Commented] (KAFKA-3595) Add capability to specify replication compact option for stream store

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

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

See Changes: [cshapi] MINOR: Update Kafka configuration documentation to use kafka-configs.… [cshapi] KAFKA-4052: Allow passing properties file to ProducerPerformance [cshapi] KAFKA-4070: implement Connect Struct.toString() [cshapi]

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

See Changes: [cshapi] KAFKA-3742: (FIX) Can't run bin/connect-*.sh with -daemon flag [cshapi] MINOR: doc changes for QueueTimeMs JMX metrics. [cshapi] MINOR: Update MirrorMaker docs to remove multiple --consumer.config