[jira] [Commented] (KAFKA-4144) Allow per stream/table timestamp extractor

[ https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837350#comment-15837350 ] Jeyhun Karimov commented on KAFKA-4144: --- Thanks for clarification. I got the point. > Allow per

[jira] [Updated] (KAFKA-4695) Can't start Kafka server after Blue Screen

[ https://issues.apache.org/jira/browse/KAFKA-4695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Tippenhauer updated KAFKA-4695: - Description: When I get a blue screen (my laptop does that quite often) I can't start my

[jira] [Updated] (KAFKA-4695) Can't start Kafka server after Blue Screen

[ https://issues.apache.org/jira/browse/KAFKA-4695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Tippenhauer updated KAFKA-4695: - Description: When I get a blue screen (my laptop does that quite often) I can't start my

[jira] [Updated] (KAFKA-4695) Can't start Kafka server after Blue Screen

[ https://issues.apache.org/jira/browse/KAFKA-4695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Tippenhauer updated KAFKA-4695: - Description: When I get a blue screen (my laptop does that quite often) I can't start my

[jira] [Created] (KAFKA-4695) Can't start Kafka server after Blue Screen

Kevin Tippenhauer created KAFKA-4695: Summary: Can't start Kafka server after Blue Screen Key: KAFKA-4695 URL: https://issues.apache.org/jira/browse/KAFKA-4695 Project: Kafka Issue Type:

[DISCUSS] KIP-115: Enforce offsets.topic.replication.factor

Hey everyone. I made a bug-fix KIP-115 to enforce offsets.topic.replication.factor: https://cwiki.apache.org/confluence/display/KAFKA/KIP-115%3A+Enforce+offsets.topic.replication.factor Comments are welcome. - Onur

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837793#comment-15837793 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

Re: [DISCUSS] KIP-110: Add Codec for ZStandard Compression

Is there more discussion to be had on this KIP, or should it be taken to a vote? On Mon, Jan 16, 2017 at 6:37 AM Dongjin Lee wrote: > I updated KIP-110 with JMH-measured benchmark results. Please have a review > when you are free. (The overall result is not different yet.) >

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837792#comment-15837792 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837519#comment-15837519 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837518#comment-15837518 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[jira] [Updated] (KAFKA-4596) KIP-73 rebalance throttling breaks on plans for specific partitions

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

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

See Changes: [ismael] KAFKA-4596; Throttled reassignment should support partial JSON file -- [...truncated 4126 lines...] kafka.integration.SaslPlaintextTopicMetadataTest >

[jira] [Updated] (KAFKA-4636) Per listener security setting overrides (KIP-103)

[ https://issues.apache.org/jira/browse/KAFKA-4636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4636: --- Status: Patch Available (was: In Progress) > Per listener security setting overrides (KIP-103) >

[jira] [Commented] (KAFKA-4596) KIP-73 rebalance throttling breaks on plans for specific partitions

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

[jira] [Created] (KAFKA-4696) Streams standby task assignment should be state-store aware

Damian Guy created KAFKA-4696: - Summary: Streams standby task assignment should be state-store aware Key: KAFKA-4696 URL: https://issues.apache.org/jira/browse/KAFKA-4696 Project: Kafka Issue

[GitHub] kafka pull request #2433: Update kafka-run-class.bat

GitHub user jonfreedman opened a pull request: https://github.com/apache/kafka/pull/2433 Update kafka-run-class.bat handle existing classpath with spaces list each lib dependency individually You can merge this pull request into a Git repository by running: $ git pull

Re: [VOTE] KIP-104: Granular Sensors for Streams

Just FYI: between feature freeze and code freeze we realised that the name of a method didn't match its Javadoc and implementation, so changed addLatencySensor -> addLatencyAndThroughputSensor in the KIP and code. Thanks Eno > On 11 Jan 2017, at 08:10, Eno Thereska

[GitHub] kafka pull request #2399: KAFKA-4596: Throttled Replica Reassignment Error

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2399 --- 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-4113) Allow KTable bootstrap

[ https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837764#comment-15837764 ] Mitch Seymour commented on KAFKA-4113: -- [~guozhang] Yes that is perfect. I haven't had a chance to

[jira] [Updated] (KAFKA-2000) Delete consumer offsets from kafka once the topic is deleted

[ https://issues.apache.org/jira/browse/KAFKA-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated KAFKA-2000: -- Resolution: Fixed Fix Version/s: (was: 0.10.2.0)

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837994#comment-15837994 ] Ismael Juma commented on KAFKA-3959: Either way, it's too late for 0.10.2.0. I'll move it to 0.10.3.0

[jira] [Updated] (KAFKA-3266) List/Alter Acls - protocol and server side implementation

[ https://issues.apache.org/jira/browse/KAFKA-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3266: --- Fix Version/s: (was: 0.10.2.0) 0.10.3.0 > List/Alter Acls - protocol and

[jira] [Updated] (KAFKA-3264) Mark the old Scala consumer and related classes as deprecated

[ https://issues.apache.org/jira/browse/KAFKA-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3264: --- Fix Version/s: (was: 0.10.2.0) 0.10.3.0 > Mark the old Scala consumer and

[jira] [Commented] (KAFKA-3300) Calculate the initial/max size of offset index files and reduce the memory footprint for memory mapped index files.

[ https://issues.apache.org/jira/browse/KAFKA-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838069#comment-15838069 ] Ismael Juma commented on KAFKA-3300: This was deemed not necessary if I recall correctly. If that's

[jira] [Updated] (KAFKA-1923) Negative offsets in replication-offset-checkpoint file

[ https://issues.apache.org/jira/browse/KAFKA-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1923: --- Fix Version/s: (was: 0.10.2.0) 0.10.3.0 > Negative offsets in

[jira] [Updated] (KAFKA-4487) Tests should be run in Jenkins with INFO or DEBUG level

[ https://issues.apache.org/jira/browse/KAFKA-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4487: --- Fix Version/s: (was: 0.10.2.0) 0.10.3.0 > Tests should be run in Jenkins with

[jira] [Commented] (KAFKA-1923) Negative offsets in replication-offset-checkpoint file

[ https://issues.apache.org/jira/browse/KAFKA-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838086#comment-15838086 ] Ismael Juma commented on KAFKA-1923: [~ewencp], moved to 0.10.3.0 since we don't know how this can

[jira] [Commented] (KAFKA-3989) Add JMH module for Benchmarks

[ https://issues.apache.org/jira/browse/KAFKA-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838056#comment-15838056 ] Ismael Juma commented on KAFKA-3989: Too late for 0.10.2.0, so aiming for 0.10.3.0. > Add JMH module

[jira] [Updated] (KAFKA-2000) Delete consumer offsets from kafka once the topic is deleted

[ https://issues.apache.org/jira/browse/KAFKA-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated KAFKA-2000: -- Fix Version/s: 0.10.2.0 > Delete consumer offsets from kafka once the topic is

Re: [DISCUSS] KIP-110: Add Codec for ZStandard Compression

So far the discussion was around the performance characteristics of the new compression algorithm. Another area that is important and is not covered in the KIP is the compatibility implications. For example, what happens if a consumer that doesn't support zstd tries to consume a topic compressed

[jira] [Updated] (KAFKA-3987) Allow configuration of the hash algorithm used by the LogCleaner's offset map

[ https://issues.apache.org/jira/browse/KAFKA-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3987: --- Labels: needs-kip (was: ) > Allow configuration of the hash algorithm used by the LogCleaner's

[jira] [Commented] (KAFKA-3987) Allow configuration of the hash algorithm used by the LogCleaner's offset map

[ https://issues.apache.org/jira/browse/KAFKA-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837969#comment-15837969 ] Ismael Juma commented on KAFKA-3987: Removed "fix version" as this needs a KIP. > Allow configuration

[jira] [Updated] (KAFKA-3987) Allow configuration of the hash algorithm used by the LogCleaner's offset map

[ https://issues.apache.org/jira/browse/KAFKA-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3987: --- Priority: Major (was: Minor) > Allow configuration of the hash algorithm used by the LogCleaner's

[jira] [Updated] (KAFKA-3987) Allow configuration of the hash algorithm used by the LogCleaner's offset map

[ https://issues.apache.org/jira/browse/KAFKA-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3987: --- Fix Version/s: (was: 0.10.2.0) > Allow configuration of the hash algorithm used by the

[jira] [Updated] (KAFKA-4474) Poor kafka-streams throughput

[ https://issues.apache.org/jira/browse/KAFKA-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres Gomez Ferrer updated KAFKA-4474: --- Attachment: kafka-streams-bug-1.png Example Architecture > Poor kafka-streams

[jira] [Commented] (KAFKA-4474) Poor kafka-streams throughput

[ https://issues.apache.org/jira/browse/KAFKA-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838055#comment-15838055 ] Andres Gomez Ferrer commented on KAFKA-4474: Hi all, I investigated more on this issue and I

[jira] [Commented] (KAFKA-4242) Re-enable committing offsets in consumer's unsubscribe() when auto commit is enabled

[ https://issues.apache.org/jira/browse/KAFKA-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838052#comment-15838052 ] Ismael Juma commented on KAFKA-4242: I removed the "fix version" since this depends on KAFKA-3491,

[jira] [Updated] (KAFKA-3989) Add JMH module for Benchmarks

[ https://issues.apache.org/jira/browse/KAFKA-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3989: --- Fix Version/s: (was: 0.10.2.0) 0.10.3.0 > Add JMH module for Benchmarks >

[jira] [Updated] (KAFKA-4242) Re-enable committing offsets in consumer's unsubscribe() when auto commit is enabled

[ https://issues.apache.org/jira/browse/KAFKA-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4242: --- Fix Version/s: (was: 0.10.2.0) > Re-enable committing offsets in consumer's unsubscribe() when

[jira] [Comment Edited] (KAFKA-4474) Poor kafka-streams throughput

[ https://issues.apache.org/jira/browse/KAFKA-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838055#comment-15838055 ] Andres Gomez Ferrer edited comment on KAFKA-4474 at 1/25/17 4:31 PM: -

[jira] [Updated] (KAFKA-3554) Generate actual data with specific compression ratio and add multi-thread support in the ProducerPerformance tool.

[ https://issues.apache.org/jira/browse/KAFKA-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3554: --- Fix Version/s: (was: 0.10.2.0) 0.10.3.0 > Generate actual data with specific

[jira] [Updated] (KAFKA-3333) Client Partitioner - Round Robin

[ https://issues.apache.org/jira/browse/KAFKA-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-: --- Labels: needs-kip (was: ) > Client Partitioner - Round Robin > > >

[jira] [Updated] (KAFKA-3203) Add UnknownCodecException and UnknownMagicByteException to error mapping

[ https://issues.apache.org/jira/browse/KAFKA-3203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3203: --- Fix Version/s: (was: 0.10.2.0) > Add UnknownCodecException and UnknownMagicByteException to error

[jira] [Updated] (KAFKA-3203) Add UnknownCodecException and UnknownMagicByteException to error mapping

[ https://issues.apache.org/jira/browse/KAFKA-3203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3203: --- Fix Version/s: 0.10.3.0 > Add UnknownCodecException and UnknownMagicByteException to error mapping >

[jira] [Commented] (KAFKA-4631) Refresh consumer metadata more frequently for unknown subscribed topics

[ https://issues.apache.org/jira/browse/KAFKA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837964#comment-15837964 ] Ismael Juma commented on KAFKA-4631: Are we still aiming to have this done by this Friday (code

[jira] [Updated] (KAFKA-3947) kafka-reassign-partitions.sh should support dumping current assignment

[ https://issues.apache.org/jira/browse/KAFKA-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3947: --- Fix Version/s: (was: 0.10.2.0) > kafka-reassign-partitions.sh should support dumping current

[jira] [Updated] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3959: --- Fix Version/s: (was: 0.10.2.0) 0.10.3.0 > __consumer_offsets wrong number of

[GitHub] kafka pull request #1850: KAFKA-2000: Delete topic should also delete consum...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1850 --- 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-3436) Speed up controlled shutdown.

[ https://issues.apache.org/jira/browse/KAFKA-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3436: --- Fix Version/s: (was: 0.10.2.0) 0.10.3.0 > Speed up controlled shutdown. >

[jira] [Updated] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3959: --- Labels: needs-kip reliability (was: reliability) > __consumer_offsets wrong number of replicas at

[jira] [Commented] (KAFKA-2000) Delete consumer offsets from kafka once the topic is deleted

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

[jira] [Commented] (KAFKA-3234) Minor documentation edits: clarify minISR; some topic-level configs are missing

[ https://issues.apache.org/jira/browse/KAFKA-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838075#comment-15838075 ] Ismael Juma commented on KAFKA-3234: Removed "fix version" for now. > Minor documentation edits:

[jira] [Updated] (KAFKA-3234) Minor documentation edits: clarify minISR; some topic-level configs are missing

[ https://issues.apache.org/jira/browse/KAFKA-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3234: --- Fix Version/s: (was: 0.10.2.0) > Minor documentation edits: clarify minISR; some topic-level

[jira] [Updated] (KAFKA-3155) Transient Failure in kafka.api.PlaintextProducerSendTest.testFlush

[ https://issues.apache.org/jira/browse/KAFKA-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3155: --- Fix Version/s: (was: 0.10.2.0) 0.10.3.0 > Transient Failure in

[jira] [Comment Edited] (KAFKA-3987) Allow configuration of the hash algorithm used by the LogCleaner's offset map

[ https://issues.apache.org/jira/browse/KAFKA-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837969#comment-15837969 ] Ismael Juma edited comment on KAFKA-3987 at 1/25/17 4:00 PM: - Removed "fix

[jira] [Updated] (KAFKA-4474) Poor kafka-streams throughput

[ https://issues.apache.org/jira/browse/KAFKA-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres Gomez Ferrer updated KAFKA-4474: --- Attachment: kafka-streams-bug-2.png > Poor kafka-streams throughput >

[jira] [Issue Comment Deleted] (KAFKA-4474) Poor kafka-streams throughput

[ https://issues.apache.org/jira/browse/KAFKA-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres Gomez Ferrer updated KAFKA-4474: --- Comment: was deleted (was: Example Architecture) > Poor kafka-streams throughput >

[jira] [Updated] (KAFKA-3333) Client Partitioner - Round Robin

[ https://issues.apache.org/jira/browse/KAFKA-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-: --- Fix Version/s: (was: 0.10.2.0) > Client Partitioner - Round Robin >

[jira] [Commented] (KAFKA-3333) Client Partitioner - Round Robin

[ https://issues.apache.org/jira/browse/KAFKA-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838064#comment-15838064 ] Ismael Juma commented on KAFKA-: This falls under "Any change that impacts the public interfaces

[jira] [Commented] (KAFKA-4691) ProducerInterceptor.onSend() is called after key and value are serialized

[ https://issues.apache.org/jira/browse/KAFKA-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838829#comment-15838829 ] Anna Povzner commented on KAFKA-4691: - I agree with [~mjsax] about not changing KafkaProducer API.

Re: [DISCUSS] KIP-115: Enforce offsets.topic.replication.factor

An important question is if this needs to wait for a major release or not. Ismael On Thu, Jan 26, 2017 at 12:19 AM, Ismael Juma wrote: > +1 from me too. > > Ismael > > On Thu, Jan 26, 2017 at 12:07 AM, Ewen Cheslack-Postava > wrote: > >> +1 >> >> Since

Re: [VOTE] KIP-115: Enforce offsets.topic.replication.factor

+1 On Wed, Jan 25, 2017 at 4:37 PM, Ismael Juma wrote: > +1 (binding) > > Ismael > > On Thu, Jan 26, 2017 at 12:34 AM, Onur Karaman < > onurkaraman.apa...@gmail.com > > wrote: > > > I'd like to start the vote for KIP-115: Enforce > > offsets.topic.replication.factor > > > >

[GitHub] kafka pull request #2434: KAFKA-4698: VerifyError in kafka/client/ClientUtil...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2434 KAFKA-4698: VerifyError in kafka/client/ClientUtils due to -target:jvm-1.7 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka

[jira] [Commented] (KAFKA-4698) `-target:jvm-1.7` in scalaCompileOptions seems to cause java.lang.VerifyError when loading kafka/client/ClientUtils

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

Re: [VOTE] KIP-115: Enforce offsets.topic.replication.factor

+1 On Wed, Jan 25, 2017 at 4:39 PM, Dong Lin wrote: > +1 > > On Wed, Jan 25, 2017 at 4:37 PM, Ismael Juma wrote: > > > +1 (binding) > > > > Ismael > > > > On Thu, Jan 26, 2017 at 12:34 AM, Onur Karaman < > > onurkaraman.apa...@gmail.com > > > wrote: > >

[jira] [Updated] (KAFKA-4698) `-target:jvm-1.7` in scalaCompileOptions seems to cause java.lang.VerifyError when loading kafka/client/ClientUtils

[ https://issues.apache.org/jira/browse/KAFKA-4698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4698: --- Status: Patch Available (was: Open) > `-target:jvm-1.7` in scalaCompileOptions seems to cause

[jira] [Commented] (KAFKA-3806) Adjust default values of log.retention.hours and offsets.retention.minutes

[ https://issues.apache.org/jira/browse/KAFKA-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838918#comment-15838918 ] Jeff Widman commented on KAFKA-3806: Too often people not super familiar with Kafka don't realize the

[jira] [Updated] (KAFKA-4698) `-target:jvm-1.7` in scalaCompileOptions seems to cause java.lang.VerifyError when loading kafka/client/ClientUtils

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

[GitHub] kafka pull request #2434: KAFKA-4698: VerifyError in kafka/client/ClientUtil...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2434 --- 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-4698) `-target:jvm-1.7` in scalaCompileOptions seems to cause java.lang.VerifyError when loading kafka/client/ClientUtils

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

[jira] [Updated] (KAFKA-4698) `-target:jvm-1.7` in scalaCompileOptions seems to cause java.lang.VerifyError when loading kafka/client/ClientUtils

[ https://issues.apache.org/jira/browse/KAFKA-4698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Heisterkamp updated KAFKA-4698: - Description: When we updated to kafka 2.11-0.10.1.1 from 2.11-0.8.2.2 we started getting

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

See Changes: [wangguoz] KAFKA-3502: KStreamTestDriver needs to be closed after the test case [wangguoz] HOTFIX: KIP-104 follow-up: remove duplicated per-processor-node -- [...truncated 8440

[jira] [Comment Edited] (KAFKA-4691) ProducerInterceptor.onSend() is called after key and value are serialized

[ https://issues.apache.org/jira/browse/KAFKA-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838657#comment-15838657 ] Francesco Lemma edited comment on KAFKA-4691 at 1/25/17 9:56 PM: - [~mjsax]

[jira] [Updated] (KAFKA-4698) `-target:jvm-1.7` in scalaCompileOptions seems to cause java.lang.VerifyError when loading kafka/client/ClientUtils

[ https://issues.apache.org/jira/browse/KAFKA-4698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4698: --- Fix Version/s: 0.10.2.0 > `-target:jvm-1.7` in scalaCompileOptions seems to cause

[jira] [Assigned] (KAFKA-4698) `-target:jvm-1.7` in scalaCompileOptions seems to cause java.lang.VerifyError when loading kafka/client/ClientUtils

[ https://issues.apache.org/jira/browse/KAFKA-4698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-4698: -- Assignee: Ismael Juma > `-target:jvm-1.7` in scalaCompileOptions seems to cause

[jira] [Commented] (KAFKA-4691) ProducerInterceptor.onSend() is called after key and value are serialized

[ https://issues.apache.org/jira/browse/KAFKA-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838744#comment-15838744 ] Matthias J. Sax commented on KAFKA-4691: I see. Understood now. Seems to be a fair change. But I

Re: [DISCUSS] KIP-115: Enforce offsets.topic.replication.factor

+1 from me. The current behavior seems both surprising and dangerous. -Jason On Wed, Jan 25, 2017 at 3:58 PM, Onur Karaman wrote: > Hey everyone. > > I made a bug-fix KIP-115 to enforce offsets.topic.replication.factor: >

Re: [DISCUSS] KIP-115: Enforce offsets.topic.replication.factor

+1 from me too. Ismael On Thu, Jan 26, 2017 at 12:07 AM, Ewen Cheslack-Postava wrote: > +1 > > Since this is an unusual one, I think it's worth pointing out that the KIP > notes it is really a bug fix, but since it has compatibility implications > the KIP was worth it. It

Re: [DISCUSS] KIP-115: Enforce offsets.topic.replication.factor

+1 On Wed, Jan 25, 2017 at 4:22 PM, Ismael Juma wrote: > An important question is if this needs to wait for a major release or not. > > Ismael > > On Thu, Jan 26, 2017 at 12:19 AM, Ismael Juma wrote: > > > +1 from me too. > > > > Ismael > > > > On Thu, Jan

[jira] [Commented] (KAFKA-4691) ProducerInterceptor.onSend() is called after key and value are serialized

[ https://issues.apache.org/jira/browse/KAFKA-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838896#comment-15838896 ] Matthias J. Sax commented on KAFKA-4691: You should now have permission to assign to yourself. I

Re: [DISCUSS] KIP-115: Enforce offsets.topic.replication.factor

As a user, I'd personally rather see this land sooner rather than waiting for a major release... As long as it fails noisily if I don't have enough brokers when it tries to create the topic, then it's easy enough to solve... On Wed, Jan 25, 2017 at 4:22 PM, Ismael Juma wrote:

[VOTE] KIP-115: Enforce offsets.topic.replication.factor

I'd like to start the vote for KIP-115: Enforce offsets.topic.replication.factor https://cwiki.apache.org/confluence/display/KAFKA/KIP-115%3A+Enforce+offsets.topic.replication.factor - Onur

Re: [VOTE] KIP-115: Enforce offsets.topic.replication.factor

+1 (binding) Ismael On Thu, Jan 26, 2017 at 12:34 AM, Onur Karaman wrote: > I'd like to start the vote for KIP-115: Enforce > offsets.topic.replication.factor > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- >

[jira] [Commented] (KAFKA-4691) ProducerInterceptor.onSend() is called after key and value are serialized

[ https://issues.apache.org/jira/browse/KAFKA-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838245#comment-15838245 ] Matthias J. Sax commented on KAFKA-4691: I am not sure, if we can fix this soon. The problem is,

[jira] [Commented] (KAFKA-4631) Refresh consumer metadata more frequently for unknown subscribed topics

[ https://issues.apache.org/jira/browse/KAFKA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838184#comment-15838184 ] Jason Gustafson commented on KAFKA-4631: Perhaps it is not critical since we got KAFKA-4633? >

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838302#comment-15838302 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

Hey Colin, Good point! Yeah we have actually considered and tested this solution, which we call one-broker-per-disk. It would work and should require no major change in Kafka as compared to this JBOD KIP. So it would be a good short term solution. But it has a few drawbacks which makes it less

[jira] [Created] (KAFKA-4698) `-target:jvm-1.7` in scalaCompileOptions seems to cause java.lang.VerifyError when loading kafka/client/ClientUtils

Chris Heisterkamp created KAFKA-4698: Summary: `-target:jvm-1.7` in scalaCompileOptions seems to cause java.lang.VerifyError when loading kafka/client/ClientUtils Key: KAFKA-4698 URL:

Re: [DISCUSS] KIP-115: Enforce offsets.topic.replication.factor

+1 Since this is an unusual one, I think it's worth pointing out that the KIP notes it is really a bug fix, but since it has compatibility implications the KIP was worth it. It was a sort of intentional bug, but confusing and dangerous. Seems important to fix this ASAP since people are hitting

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838740#comment-15838740 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[jira] [Commented] (KAFKA-4691) ProducerInterceptor.onSend() is called after key and value are serialized

[ https://issues.apache.org/jira/browse/KAFKA-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838864#comment-15838864 ] Francesco Lemma commented on KAFKA-4691: Thanks [~mjsax] and [~apovzner]. Your points make

[jira] [Commented] (KAFKA-4691) ProducerInterceptor.onSend() is called after key and value are serialized

[ https://issues.apache.org/jira/browse/KAFKA-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838657#comment-15838657 ] Francesco Lemma commented on KAFKA-4691: [~mjsax] This issue is not related to dynamic routing.

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838724#comment-15838724 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[GitHub] kafka pull request #2436: HOTFIX: Consumer offsets not properly loaded on co...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/2436 HOTFIX: Consumer offsets not properly loaded on coordinator failover You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka

Re: [DISCUSS] KIP-115: Enforce offsets.topic.replication.factor

> On Jan 25, 2017, at 9:26 PM, Joel Koshy wrote: > > already voted, but one thing worth considering (since this KIP speaks of > *enforcement*) is desired behavior if the topic already exists and the > config != existing RF. > Yeah, I'm curious about this too. -James >

[jira] [Updated] (KAFKA-4699) Transient Failure PlaintextConsumerTest.testInterceptros

[ https://issues.apache.org/jira/browse/KAFKA-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-4699: --- Assignee: Ismael Juma (was: Jason Gustafson) > Transient Failure

[jira] [Commented] (KAFKA-4699) Transient Failure PlaintextConsumerTest.testInterceptros

[ https://issues.apache.org/jira/browse/KAFKA-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15839364#comment-15839364 ] Jason Gustafson commented on KAFKA-4699: Actually, it is an assertion on the behavior of the

Re: [VOTE] KIP-115: Enforce offsets.topic.replication.factor

+1 > On Jan 25, 2017, at 9:48 PM, Ewen Cheslack-Postava wrote: > > +1 > > On Wed, Jan 25, 2017 at 9:23 PM, Joel Koshy wrote: > >> +1 >> >> >> On Wed, Jan 25, 2017 at 4:41 PM, Jason Gustafson >> wrote: >> >>> +1 >>> >>> On Wed,

[jira] [Commented] (KAFKA-4578) Upgrade notes for 0.10.2.0

[ https://issues.apache.org/jira/browse/KAFKA-4578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15839378#comment-15839378 ] Ismael Juma commented on KAFKA-4578: Yes, I was planning to submit this one today. > Upgrade notes

  1   2   >