[jira] [Commented] (KAFKA-5376) Transactions: Concurrent transactional consumer reads aborted messages

[ https://issues.apache.org/jira/browse/KAFKA-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16036170#comment-16036170 ] Jason Gustafson commented on KAFKA-5376: [~apurva] Please post the log data from one of the

[jira] [Commented] (KAFKA-5368) Kafka Streams skipped-records-rate sensor produces nonzero values when the timestamps are valid

[ https://issues.apache.org/jira/browse/KAFKA-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16036169#comment-16036169 ] Matthias J. Sax commented on KAFKA-5368: I actually think, we should add an integration test here.

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

What I don't understand is this: > From there on its the easiest way forward: fix, redeploy, start => done If you have many producers that work fine and a new "bad" producer starts up and writes bad data into your input topic, your Streams app dies but all your producers, including the bad one,

[GitHub] kafka pull request #3231: KAFKA-5364: ensurePartitionAdded does not handle p...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3231 KAFKA-5364: ensurePartitionAdded does not handle pending partitions in abortable error state You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-5364) Producer attempts to send transactional messages before adding partitions to transaction

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

Re: Sink Processor definition

I think "sink" it the correct term here. It means that we write to a topic. Processors, that don't have downstream nodes are called "terminal operation" (at least in the DSL). Thus, a sink is also a "terminal operation" but not the other way round. So the docs are not optimal, as they put the

[jira] [Commented] (KAFKA-4325) Improve processing of late records for window operations

[ https://issues.apache.org/jira/browse/KAFKA-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16036135#comment-16036135 ] Matthias J. Sax commented on KAFKA-4325: I assume yes. \cc [~guozhang] > Improve processing of

[jira] [Commented] (KAFKA-5070) org.apache.kafka.streams.errors.LockException: task [0_18] Failed to lock the state directory: /opt/rocksdb/pulse10/0_18

[ https://issues.apache.org/jira/browse/KAFKA-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16036134#comment-16036134 ] Matthias J. Sax commented on KAFKA-5070: It's unclear to me how increasing poll time (ie,

[jira] [Updated] (KAFKA-5377) Kafka server process crashing due to access violation (caused by log cleaner)

[ https://issues.apache.org/jira/browse/KAFKA-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus B updated KAFKA-5377: Description: We are running Kafka in a 2 x broker cluster configuration on Windows, and overall it has

[jira] [Updated] (KAFKA-5377) Kafka server process crashing due to access violation (caused by log cleaner)

[ https://issues.apache.org/jira/browse/KAFKA-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus B updated KAFKA-5377: Summary: Kafka server process crashing due to access violation (caused by log cleaner) (was: Kafka process

Re: [DISCUSS] KIP-165: Extend Interactive Queries for return latest update timestamp per key

Hi Matthias, Thanks for comments. - why do you only consider get() and not range() and all() ? The corresponding jira concentrates on single key lookups. Moreover, I could not find a use-case to include range queries to return records with timestamp. However, theoritically we can include

[jira] [Created] (KAFKA-5377) Kafka process crashing due to access violation

Markus Bergman created KAFKA-5377: - Summary: Kafka process crashing due to access violation Key: KAFKA-5377 URL: https://issues.apache.org/jira/browse/KAFKA-5377 Project: Kafka Issue Type:

[GitHub] kafka pull request #3230: KAFKA-5355: Test cases to ensure isolation level p...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3230 KAFKA-5355: Test cases to ensure isolation level propagated in delayed fetch You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka

[jira] [Created] (KAFKA-5376) Transactions: Concurrent transactional consumer reads aborted messages

Apurva Mehta created KAFKA-5376: --- Summary: Transactions: Concurrent transactional consumer reads aborted messages Key: KAFKA-5376 URL: https://issues.apache.org/jira/browse/KAFKA-5376 Project: Kafka

[jira] [Created] (KAFKA-5375) Transactions: Concurrent transactional consumer loses messages when there are broker bounces

Apurva Mehta created KAFKA-5375: --- Summary: Transactions: Concurrent transactional consumer loses messages when there are broker bounces Key: KAFKA-5375 URL: https://issues.apache.org/jira/browse/KAFKA-5375

[jira] [Updated] (KAFKA-5375) Transactions: Concurrent transactional consumer loses messages when there are broker bounces

[ https://issues.apache.org/jira/browse/KAFKA-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5375: Labels: exactly-once (was: ) > Transactions: Concurrent transactional consumer loses messages when

[jira] [Commented] (KAFKA-5364) Producer attempts to send transactional messages before adding partitions to transaction

[ https://issues.apache.org/jira/browse/KAFKA-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16036092#comment-16036092 ] Apurva Mehta commented on KAFKA-5364: - I am leaving the fix version as 0.11.0.0 for now. But since PR

[jira] [Reopened] (KAFKA-5364) Producer attempts to send transactional messages before adding partitions to transaction

[ https://issues.apache.org/jira/browse/KAFKA-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reopened KAFKA-5364: - > Producer attempts to send transactional messages before adding partitions to > transaction >

[jira] [Updated] (KAFKA-5364) Producer attempts to send transactional messages before adding partitions to transaction

[ https://issues.apache.org/jira/browse/KAFKA-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5364: Attachment: KAFKA-5364.tar.gz This has recurred once in more than 2 dozen runs after 3202 was

[jira] [Commented] (KAFKA-5347) OutOfSequence error should be fatal

[ https://issues.apache.org/jira/browse/KAFKA-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16036089#comment-16036089 ] Apurva Mehta commented on KAFKA-5347: - I think this can be punted to a bug fix release. This is a

Re: [VOTE] KIP-113 - Support replicas movement between log directories

Hey Joel, Thanks much for the review! I have updated the KIP to address all your comments. Please find the diff here . Regards, Dong On Sat, Jun 3, 2017 at 11:43 AM, Joel Koshy

[jira] [Updated] (KAFKA-5347) OutOfSequence error should be fatal

[ https://issues.apache.org/jira/browse/KAFKA-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5347: Fix Version/s: 0.11.0.1 > OutOfSequence error should be fatal > ---

Re: [VOTE] KIP-113 - Support replicas movement between log directories

+1 Few additional comments (most of which we discussed offline): - This was summarized in the “discuss” thread, but it is worth recording in the KIP itself that the LEO in DescribeDirsResponse is useful to measure progress of the move. - num.replica.move.threads defaults to #

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

See

[GitHub] kafka pull request #3229: MINOR: (docs) add missing word

GitHub user mihbor opened a pull request: https://github.com/apache/kafka/pull/3229 MINOR: (docs) add missing word You can merge this pull request into a Git repository by running: $ git pull https://github.com/mihbor/kafka patch-9 Alternatively you can review and apply

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

See Changes: [ismael] KAFKA-5374; Set allow auto topic creation to false when requesting node [ismael] KAFKA-5019; Upgrades notes for idempotent/transactional features and new

[jira] [Resolved] (KAFKA-5098) KafkaProducer.send() blocks and generates TimeoutException if topic name has illegal char

[ https://issues.apache.org/jira/browse/KAFKA-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5098. Resolution: Fixed Fix Version/s: 0.11.0.0 Issue resolved by pull request 3223

[GitHub] kafka pull request #3223: KAFKA-5098: KafkaProducer.send() should validate t...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3223 --- 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-4291) TopicCommand --describe shows topics marked for deletion as under-replicated and unavailable (KIP-137)

[ https://issues.apache.org/jira/browse/KAFKA-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4291: --- Resolution: Fixed Status: Resolved (was: Patch Available) > TopicCommand --describe shows

[jira] [Commented] (KAFKA-4913) creating a window store with one segment throws division by zero error

[ https://issues.apache.org/jira/browse/KAFKA-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035902#comment-16035902 ] Ismael Juma commented on KAFKA-4913: Is this still planned for 0.11.0.0? > creating a window store

[jira] [Commented] (KAFKA-4291) TopicCommand --describe shows topics marked for deletion as under-replicated and unavailable (KIP-137)

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

[GitHub] kafka pull request #2011: KAFKA-4291: TopicCommand --describe shows topics m...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2011 --- 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 #3228: MINOR: (docs) in section, not at section

GitHub user mihbor opened a pull request: https://github.com/apache/kafka/pull/3228 MINOR: (docs) in section, not at section See https://english.stackexchange.com/questions/158981/at-this-section-vs-in-this-section and

Re: [DISCUSS] KIP-147: Add missing type parameters to StateStoreSupplier factories and KGroupedStream/Table methods

I agree maintaining backwards-compatibility here adds a lot of overhead. I haven't so far found a way to reconcile these elegantly. Whichever way we go it's better to take the pain sooner rather than later. Kafka 0.11.0.0 (through KAFKA-5045

Re: Sink Processor definition

Yes, I think the key distinction, from the point of view of that documentation section, is that it doesn't have downstream processors. On 03/06/17 09:48, Damian Guy wrote: Hi Michal, In this case Sink Processor is really referring to a SinkNode that can only produce to a kafka topic. Maybe

Re: Sink Processor definition

Hi Michal, In this case Sink Processor is really referring to a SinkNode that can only produce to a kafka topic. Maybe the terminology is incorrect as strictly speaking a processor that writes data to anything could be considered a Sink Processor. On Sat, 3 Jun 2017 at 09:23 Michal Borowiecki

[GitHub] kafka pull request #3227: MINOR: fix quotes for consistent rendering

GitHub user mihbor opened a pull request: https://github.com/apache/kafka/pull/3227 MINOR: fix quotes for consistent rendering “ as opposed to " don't render consistently across browsers. On current Kafka website they render correctly in Firefox but not Chrome

Re: [DISCUSS] KIP-147: Add missing type parameters to StateStoreSupplier factories and KGroupedStream/Table methods

Hmm, i guess this won't work due to adding the additional to the StateStoreSupplier params on reduce, count, aggregate etc. On Sat, 3 Jun 2017 at 09:06 Damian Guy wrote: > Hi Michal, > > Thanks for the KIP - is there a way we can do this without having to > introduce

[jira] [Updated] (KAFKA-5371) SyncProducerTest.testReachableServer has become flaky

[ https://issues.apache.org/jira/browse/KAFKA-5371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5371: --- Issue Type: Test (was: Bug) > SyncProducerTest.testReachableServer has become flaky >

[jira] [Updated] (KAFKA-5371) SyncProducerTest.testReachableServer has become flaky

[ https://issues.apache.org/jira/browse/KAFKA-5371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5371: --- Assignee: Ismael Juma (was: Apurva Mehta) Fix Version/s: 0.11.0.0 Status: Patch

Sink Processor definition

Hi all, Streams docs say: * *Sink Processor*: A sink processor is a special type of stream processor that does not have down-stream processors. It sends any received records from its up-stream processors to a specified Kafka topic. Would a processor that doesn't produce to a

[GitHub] kafka pull request #3225: KAFKA-5371: Increase request timeout for producer ...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3225 KAFKA-5371: Increase request timeout for producer used by testReachableServer 500ms is low for a shared Jenkins environment. You can merge this pull request into a Git repository by running: $

[jira] [Commented] (KAFKA-5371) SyncProducerTest.testReachableServer has become flaky

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

[GitHub] kafka pull request #3224: MINOR: mention IQ use-case in the Overview

GitHub user mihbor opened a pull request: https://github.com/apache/kafka/pull/3224 MINOR: mention IQ use-case in the Overview You can merge this pull request into a Git repository by running: $ git pull https://github.com/mihbor/kafka patch-5 Alternatively you can review

Re: [VOTE] KIP-117: Add a public AdminClient API for Kafka admin operations

Hi Colin, Thanks for the feedback. Regarding the behaviour for brokers older than 0.11.0, I had gone for the Javadoc note because it made it possible to avoid the inefficiency of getting all topics for users who have disabled auto topic creation. After some thought and discussion, I agree that

Re: [DISCUSS] KIP-147: Add missing type parameters to StateStoreSupplier factories and KGroupedStream/Table methods

Hi Michal, Thanks for the KIP - is there a way we can do this without having to introduce the new Typed.. Interfaces, overloaded methods etc? Is it possible that we just need to provide a couple of new methods on PersistentKeyValueFactory for windowed and sessionWindowed to return interfaces like

[jira] [Updated] (KAFKA-3096) Leader is not set to -1 when it is shutdown if followers are down

[ https://issues.apache.org/jira/browse/KAFKA-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3096: --- Fix Version/s: 0.11.1.0 > Leader is not set to -1 when it is shutdown if followers are down >

[jira] [Updated] (KAFKA-3143) inconsistent state in ZK when all replicas are dead

[ https://issues.apache.org/jira/browse/KAFKA-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3143: --- Fix Version/s: 0.11.1.0 > inconsistent state in ZK when all replicas are dead >

[jira] [Updated] (KAFKA-3866) KerberosLogin refresh time bug and other improvements

[ https://issues.apache.org/jira/browse/KAFKA-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3866: --- Fix Version/s: (was: 0.11.0.1) 0.11.0.0 > KerberosLogin refresh time bug and

[jira] [Assigned] (KAFKA-3881) Remove the replacing logic from "." to "_" in Fetcher

[ https://issues.apache.org/jira/browse/KAFKA-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-3881: -- Assignee: (was: Ismael Juma) > Remove the replacing logic from "." to "_" in Fetcher >

[jira] [Assigned] (KAFKA-4503) Expose the log dir for a partition as a metric

[ https://issues.apache.org/jira/browse/KAFKA-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-4503: -- Assignee: (was: Ismael Juma) > Expose the log dir for a partition as a metric >

[jira] [Commented] (KAFKA-5031) Additional validation in validateMessagesAndAssignOffsets

[ https://issues.apache.org/jira/browse/KAFKA-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035884#comment-16035884 ] Ismael Juma commented on KAFKA-5031: If we don't add this validation now, we may not be able to add it

[jira] [Updated] (KAFKA-5031) Additional validation in validateMessagesAndAssignOffsets

[ https://issues.apache.org/jira/browse/KAFKA-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5031: --- Priority: Critical (was: Major) > Additional validation in validateMessagesAndAssignOffsets >

[jira] [Updated] (KAFKA-5214) KafkaAdminClient#apiVersions should return a public class

[ https://issues.apache.org/jira/browse/KAFKA-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5214: --- Priority: Blocker (was: Major) > KafkaAdminClient#apiVersions should return a public class >

[jira] [Updated] (KAFKA-5214) KafkaAdminClient#apiVersions should return a public class

[ https://issues.apache.org/jira/browse/KAFKA-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5214: --- Fix Version/s: 0.11.0.0 > KafkaAdminClient#apiVersions should return a public class >

[jira] [Updated] (KAFKA-5325) Connection Lose during Kafka Kerberos Renewal process

[ https://issues.apache.org/jira/browse/KAFKA-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5325: --- Status: Patch Available (was: Open) > Connection Lose during Kafka Kerberos Renewal process >

[jira] [Updated] (KAFKA-5325) Connection Lose during Kafka Kerberos Renewal process

[ https://issues.apache.org/jira/browse/KAFKA-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5325: --- Fix Version/s: 0.11.0.0 > Connection Lose during Kafka Kerberos Renewal process >

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

See

[jira] [Updated] (KAFKA-5355) Broker returns messages beyond "latest stable offset" to transactional consumer in read_committed mode

[ https://issues.apache.org/jira/browse/KAFKA-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5355: --- Status: In Progress (was: Patch Available) > Broker returns messages beyond "latest stable offset"

[jira] [Updated] (KAFKA-5355) Broker returns messages beyond "latest stable offset" to transactional consumer in read_committed mode

[ https://issues.apache.org/jira/browse/KAFKA-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5355: --- Status: Patch Available (was: Open) > Broker returns messages beyond "latest stable offset" to

[jira] [Commented] (KAFKA-5347) OutOfSequence error should be fatal

[ https://issues.apache.org/jira/browse/KAFKA-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035883#comment-16035883 ] Ismael Juma commented on KAFKA-5347: [~apurva] [~hachikuji] This issue has no "Fix version". Is it

[jira] [Updated] (KAFKA-4815) Idempotent/transactional Producer Checklist (KIP-98)

[ https://issues.apache.org/jira/browse/KAFKA-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4815: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Idempotent/transactional Producer

[jira] [Commented] (KAFKA-5021) Update Message Delivery Semantics section to take into account KIP-98

[ https://issues.apache.org/jira/browse/KAFKA-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035879#comment-16035879 ] Ismael Juma commented on KAFKA-5021: Since this is a website update, it doesn't have to block the

[jira] [Updated] (KAFKA-5021) Update Message Delivery Semantics section to take into account KIP-98

[ https://issues.apache.org/jira/browse/KAFKA-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5021: --- Priority: Critical (was: Blocker) > Update Message Delivery Semantics section to take into account

[jira] [Updated] (KAFKA-5020) Update protocol documentation to mention message format v2

[ https://issues.apache.org/jira/browse/KAFKA-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5020: --- Priority: Critical (was: Blocker) > Update protocol documentation to mention message format v2 >

[jira] [Assigned] (KAFKA-5098) KafkaProducer.send() blocks and generates TimeoutException if topic name has illegal char

[ https://issues.apache.org/jira/browse/KAFKA-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-5098: - Assignee: huxihx > KafkaProducer.send() blocks and generates TimeoutException if topic name has >

[GitHub] kafka pull request #3223: KAFKA-5098: KafkaProducer.send() should validate t...

GitHub user huxihx opened a pull request: https://github.com/apache/kafka/pull/3223 KAFKA-5098: KafkaProducer.send() should validate topic name before sending KafkaProducer.send() should check topic name before sending the record. You can merge this pull request into a Git

[jira] [Commented] (KAFKA-5098) KafkaProducer.send() blocks and generates TimeoutException if topic name has illegal char

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

[jira] [Commented] (KAFKA-5262) Can't find some consumer group information

[ https://issues.apache.org/jira/browse/KAFKA-5262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035865#comment-16035865 ] huxihx commented on KAFKA-5262: --- Does your client code commit offsets? Besides, a complete output for

[jira] [Commented] (KAFKA-5296) Unable to write to some partitions of newly created topic in 10.2

[ https://issues.apache.org/jira/browse/KAFKA-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035862#comment-16035862 ] huxihx commented on KAFKA-5296: --- [~asaikia] Do you mean directories for some partitions could always fail to