[jira] [Created] (KAFKA-5592) Connection with plain client to SSL-secured broker causes OOM

2017-07-14 Thread JIRA
Marcin Łuczyński created KAFKA-5592: --- Summary: Connection with plain client to SSL-secured broker causes OOM Key: KAFKA-5592 URL: https://issues.apache.org/jira/browse/KAFKA-5592 Project: Kafka

[jira] [Commented] (KAFKA-4107) Support offset reset capability in Kafka Connect

2017-07-10 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16080346#comment-16080346 ] Sönke Liebau commented on KAFKA-4107: - Sounds good to me. I'll investigate the issue a little

[jira] [Updated] (KAFKA-5625) Invalid subscription data may cause streams app to throw BufferUnderflowException

2017-07-21 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-5625: - Affects Version/s: 0.11.0.0 Component/s: streams > Invalid subscription data may ca

[jira] [Created] (KAFKA-5625) Invalid subscription data may cause streams app to throw BufferUnderflowException

2017-07-21 Thread JIRA
Xavier Léauté created KAFKA-5625: Summary: Invalid subscription data may cause streams app to throw BufferUnderflowException Key: KAFKA-5625 URL: https://issues.apache.org/jira/browse/KAFKA-5625

[jira] [Commented] (KAFKA-5563) Clarify handling of connector name in config

2017-07-21 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096076#comment-16096076 ] Sönke Liebau commented on KAFKA-5563: - Alright, I'll prepare a PR to introduce this check once [2755

[jira] [Assigned] (KAFKA-4827) Kafka connect: error with special characters in connector name

2017-07-27 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau reassigned KAFKA-4827: --- Assignee: Sönke Liebau > Kafka connect: error with special characters in connector n

[jira] [Commented] (KAFKA-4827) Kafka connect: error with special characters in connector name

2017-07-27 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103087#comment-16103087 ] Sönke Liebau commented on KAFKA-4827: - All true :) I'll create a dedicated jira and kick off

[jira] [Assigned] (KAFKA-5637) Document compatibility and release policies

2017-07-27 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau reassigned KAFKA-5637: --- Assignee: Sönke Liebau > Document compatibility and release polic

[jira] [Assigned] (KAFKA-5563) Clarify handling of connector name in config

2017-07-27 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau reassigned KAFKA-5563: --- Assignee: Sönke Liebau > Clarify handling of connector name in con

[jira] [Updated] (KAFKA-5637) Document compatibility and release policies

2017-07-27 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau updated KAFKA-5637: Description: We should document our compatibility and release policies in one place so that people

[jira] [Commented] (KAFKA-5546) Lost data when the leader is disconnected.

2017-07-01 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071252#comment-16071252 ] Björn Eriksson commented on KAFKA-5546: --- Hi [~mihbor], I've updated the test to use {{acks=all

[jira] [Created] (KAFKA-5546) Lost data when the leader is disconnected.

2017-06-30 Thread JIRA
Björn Eriksson created KAFKA-5546: - Summary: Lost data when the leader is disconnected. Key: KAFKA-5546 URL: https://issues.apache.org/jira/browse/KAFKA-5546 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-4107) Support offset reset capability in Kafka Connect

2017-07-04 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073478#comment-16073478 ] Sönke Liebau commented on KAFKA-4107: - [~hachikuji] any updates on whether this is still needed? I

[jira] [Commented] (KAFKA-4827) Kafka connect: error with special characters in connector name

2017-07-06 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076052#comment-16076052 ] Sönke Liebau commented on KAFKA-4827: - There is a few more special characters that cause similar

[jira] [Created] (KAFKA-5563) Clarify handling of connector name in config

2017-07-06 Thread JIRA
Sönke Liebau created KAFKA-5563: --- Summary: Clarify handling of connector name in config Key: KAFKA-5563 URL: https://issues.apache.org/jira/browse/KAFKA-5563 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-5546) Temporary loss of availability data when the leader is disconnected

2017-08-06 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16115735#comment-16115735 ] Björn Eriksson commented on KAFKA-5546: --- Hi Jason, No, {{ifdown}} means that the connection won't

[jira] [Updated] (KAFKA-5546) Temporary loss of availability data when the leader is disconnected

2017-08-04 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Björn Eriksson updated KAFKA-5546: -- Affects Version/s: 0.11.0.0 Environment: docker, failing-network Description

[jira] [Updated] (KAFKA-5546) Temporary loss of availability data when the leader is disconnected

2017-08-04 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Björn Eriksson updated KAFKA-5546: -- Attachment: (was: kafka-failure-log.txt) > Temporary loss of availability data w

[jira] [Created] (KAFKA-5742) Support passing ZK chroot in system tests

2017-08-16 Thread JIRA
Xavier Léauté created KAFKA-5742: Summary: Support passing ZK chroot in system tests Key: KAFKA-5742 URL: https://issues.apache.org/jira/browse/KAFKA-5742 Project: Kafka Issue Type: Test

[jira] [Assigned] (KAFKA-5742) Support passing ZK chroot in system tests

2017-08-16 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-5742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté reassigned KAFKA-5742: Assignee: Xavier Léauté > Support passing ZK chroot in system te

[jira] [Commented] (KAFKA-5765) Move merge() from StreamsBuilder to KStream

2017-08-22 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-5765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137081#comment-16137081 ] Xavier Léauté commented on KAFKA-5765: -- I have a small request when it comes to merge(). The current

[jira] [Created] (KAFKA-5966) Support ByteBuffer serialization in Kafka Streams

2017-09-22 Thread JIRA
Xavier Léauté created KAFKA-5966: Summary: Support ByteBuffer serialization in Kafka Streams Key: KAFKA-5966 URL: https://issues.apache.org/jira/browse/KAFKA-5966 Project: Kafka Issue Type

[jira] [Created] (KAFKA-5959) NPE in NetworkClient

2017-09-21 Thread JIRA
Xavier Léauté created KAFKA-5959: Summary: NPE in NetworkClient Key: KAFKA-5959 URL: https://issues.apache.org/jira/browse/KAFKA-5959 Project: Kafka Issue Type: Bug Components

[jira] [Commented] (KAFKA-4972) Kafka 0.10.0 Found a corrupted index file during Kafka broker startup

2017-09-18 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169681#comment-16169681 ] Julius Žaromskis commented on KAFKA-4972: - There's a bunch of warning msgs in my log file, kafka

[jira] [Comment Edited] (KAFKA-4972) Kafka 0.10.0 Found a corrupted index file during Kafka broker startup

2017-09-18 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169681#comment-16169681 ] Julius Žaromskis edited comment on KAFKA-4972 at 9/18/17 7:22 AM

[jira] [Created] (KAFKA-5895) Update readme to reflect that Gradle 2 is no longer good enough

2017-09-14 Thread JIRA
Matthias Weßendorf created KAFKA-5895: - Summary: Update readme to reflect that Gradle 2 is no longer good enough Key: KAFKA-5895 URL: https://issues.apache.org/jira/browse/KAFKA-5895 Project

[jira] [Updated] (KAFKA-5895) Gradle 3.0+ is needed on the build

2017-09-14 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf updated KAFKA-5895: -- Summary: Gradle 3.0+ is needed on the build (was: Update readme to reflect that Gradle

[jira] [Commented] (KAFKA-4950) ConcurrentModificationException when iterating over Kafka Metrics

2017-09-19 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172134#comment-16172134 ] Sébastien Launay commented on KAFKA-4950: - I am also getting such an error sporadically when using

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

2017-10-06 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16195250#comment-16195250 ] Håkon Åmdal commented on KAFKA-4477: [~mlesyk] It seems like we're also experiencing the same issues

[jira] [Commented] (KAFKA-5637) Document compatibility and release policies

2017-10-05 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16192779#comment-16192779 ] Sönke Liebau commented on KAFKA-5637: - Apologies for letting this slide for so long, I had a medical

[jira] [Updated] (KAFKA-5708) Update Jackson dependencies (from 2.8.5 to 2.9.x)

2017-09-08 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Stojadinović updated KAFKA-5708: -- Description: -In addition to update: remove deprecated version forcing for 'jackson

[jira] [Commented] (KAFKA-1324) Debian packaging

2017-08-24 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139931#comment-16139931 ] Martin Schröder commented on KAFKA-1324: bq. I think we can leave packaging out of Kafka itself

[jira] [Commented] (KAFKA-4741) Memory leak in RecordAccumulator.append

2017-08-22 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136549#comment-16136549 ] Julius Žaromskis commented on KAFKA-4741: - I'm having this problem: https://stackoverflow.com

[jira] [Comment Edited] (KAFKA-5649) Producer is being closed generating ssl exception

2017-08-25 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142275#comment-16142275 ] Tomasz Sosiński edited comment on KAFKA-5649 at 8/25/17 9:48 PM

[jira] [Commented] (KAFKA-5649) Producer is being closed generating ssl exception

2017-08-25 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142275#comment-16142275 ] Tomasz Sosiński commented on KAFKA-5649: Do you use Kafka or Spark on docker? > Producer is be

[jira] [Commented] (KAFKA-5772) Improve Util classes

2017-08-23 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-5772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138460#comment-16138460 ] Matthias Weßendorf commented on KAFKA-5772: --- As requested by [~rhauch], for this PR: https

[jira] [Created] (KAFKA-5772) Improve Util classes

2017-08-23 Thread JIRA
Matthias Weßendorf created KAFKA-5772: - Summary: Improve Util classes Key: KAFKA-5772 URL: https://issues.apache.org/jira/browse/KAFKA-5772 Project: Kafka Issue Type: Improvement

[jira] [Created] (KAFKA-5836) Kafka Streams - API for specifying internal stream name on join

2017-09-05 Thread JIRA
Lovro Pandžić created KAFKA-5836: Summary: Kafka Streams - API for specifying internal stream name on join Key: KAFKA-5836 URL: https://issues.apache.org/jira/browse/KAFKA-5836 Project: Kafka

[jira] [Created] (KAFKA-6104) Add unit tests for ClusterConnectionStates

2017-10-22 Thread JIRA
Sönke Liebau created KAFKA-6104: --- Summary: Add unit tests for ClusterConnectionStates Key: KAFKA-6104 URL: https://issues.apache.org/jira/browse/KAFKA-6104 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-4827) Kafka connect: error with special characters in connector name

2017-11-10 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau updated KAFKA-4827: Fix Version/s: (was: 0.11.0.2) (was: 0.10.2.2

[jira] [Commented] (KAFKA-4827) Kafka connect: error with special characters in connector name

2017-11-10 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16247275#comment-16247275 ] Sönke Liebau commented on KAFKA-4827: - In this particular case the issue was probably a non encoded

[jira] [Commented] (KAFKA-6168) Connect Schema comparison is slow for large schemas

2017-11-14 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252532#comment-16252532 ] Loïc Monney commented on KAFKA-6168: Hello [~rhauch], First, thank you very much for creating

[jira] [Commented] (KAFKA-5563) Clarify handling of connector name in config

2017-11-24 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265038#comment-16265038 ] Sönke Liebau commented on KAFKA-5563: - [~ewencp] can you take a look at the changes when you get

[jira] [Resolved] (KAFKA-6257) KafkaConsumer was hung when bootstrap servers was not existed

2017-11-28 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau resolved KAFKA-6257. - Resolution: Duplicate Closing this as duplicate since no contradicting information was added

[jira] [Created] (KAFKA-6389) Expose transaction metrics via JMX

2017-12-20 Thread JIRA
Florent Ramière created KAFKA-6389: -- Summary: Expose transaction metrics via JMX Key: KAFKA-6389 URL: https://issues.apache.org/jira/browse/KAFKA-6389 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-5563) Clarify handling of connector name in config

2017-11-17 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256744#comment-16256744 ] Sönke Liebau commented on KAFKA-5563: - As KAFKA-4930 is approaching a stable state I looked

[jira] [Commented] (KAFKA-414) Evaluate mmap-based writes for Log implementation

2017-11-16 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255509#comment-16255509 ] Sönke Liebau commented on KAFKA-414: True, I was looking at the index file code, sorry for the mixup

[jira] [Resolved] (KAFKA-381) Changes made by a request do not affect following requests in the same packet.

2017-11-16 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau resolved KAFKA-381. Resolution: Not A Bug I think we can safely close this issue, the behavior was sufficiently

[jira] [Commented] (KAFKA-517) Ensure that we escape the metric names if they include user strings

2017-11-17 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256991#comment-16256991 ] Sönke Liebau commented on KAFKA-517: A recent [commit|https://github.com/apache/kafka/commit

[jira] [Commented] (KAFKA-4827) Kafka connect: error with special characters in connector name

2017-11-10 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16247658#comment-16247658 ] Sönke Liebau commented on KAFKA-4827: - Sure, feel free to reassign! > Kafka connect: er

[jira] [Comment Edited] (KAFKA-4827) Kafka connect: error with special characters in connector name

2017-11-10 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16247658#comment-16247658 ] Sönke Liebau edited comment on KAFKA-4827 at 11/10/17 4:16 PM: --- Sure, feel

[jira] [Commented] (KAFKA-6177) kafka-mirror-maker.sh RecordTooLargeException

2017-11-13 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16249639#comment-16249639 ] Rémi REY commented on KAFKA-6177: - Hello all, Anyone to acknowledge this ticket please ? Thank you

[jira] [Resolved] (KAFKA-1130) "log.dirs" is a confusing property name

2017-11-20 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau resolved KAFKA-1130. - Resolution: Won't Fix Due to the age of the last comment on this issue and the fact

[jira] [Commented] (KAFKA-6234) Transient failure in kafka.api.AdminClientIntegrationTest.testLogStartOffsetCheckpoint

2017-11-19 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16258826#comment-16258826 ] Sönke Liebau commented on KAFKA-6234: - Is the 1 second timeout in that relevant to what is being

[jira] [Commented] (KAFKA-6234) Transient failure in kafka.api.AdminClientIntegrationTest.testLogStartOffsetCheckpoint

2017-11-19 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16258851#comment-16258851 ] Sönke Liebau commented on KAFKA-6234: - I've run a few tests and looked at the value that the 1s

[jira] [Created] (KAFKA-6238) Issues with protocol version when applying a rolling upgrade to 1.0.0

2017-11-20 Thread JIRA
Diego Louzán created KAFKA-6238: --- Summary: Issues with protocol version when applying a rolling upgrade to 1.0.0 Key: KAFKA-6238 URL: https://issues.apache.org/jira/browse/KAFKA-6238 Project: Kafka

[jira] [Commented] (KAFKA-679) Phabricator for code review

2017-11-17 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257000#comment-16257000 ] Sönke Liebau commented on KAFKA-679: Is there still any activity in this direction ongoing or pending

[jira] [Issue Comment Deleted] (KAFKA-4) Confusing Error mesage from producer when no kafka brokers are available

2017-11-16 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau updated KAFKA-4: - Comment: was deleted (was: Better error message introduced by fix for KAFKA-5179) > Confusing Error mes

[jira] [Resolved] (KAFKA-4) Confusing Error mesage from producer when no kafka brokers are available

2017-11-16 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau resolved KAFKA-4. -- Resolution: Fixed (was: Unresolved) > Confusing Error mesage from producer when no kafka brok

[jira] [Commented] (KAFKA-414) Evaluate mmap-based writes for Log implementation

2017-11-16 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255038#comment-16255038 ] Sönke Liebau commented on KAFKA-414: The switch to using MappedByteBuffers was made as part of KAFKA

[jira] [Commented] (KAFKA-4) Confusing Error mesage from producer when no kafka brokers are available

2017-11-16 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254981#comment-16254981 ] Sönke Liebau commented on KAFKA-4: -- Better error message introduced by fix for KAFKA-5179 > Confusing Er

[jira] [Comment Edited] (KAFKA-4) Confusing Error mesage from producer when no kafka brokers are available

2017-11-16 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254975#comment-16254975 ] Sönke Liebau edited comment on KAFKA-4 at 11/16/17 9:10 AM: Current error message

[jira] [Updated] (KAFKA-4) Confusing Error mesage from producer when no kafka brokers are available

2017-11-16 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau updated KAFKA-4: - Fix Version/s: 0.11.0.0 > Confusing Error mesage from producer when no kafka brokers are availa

[jira] [Commented] (KAFKA-6163) Broker should fail fast on startup if an error occurs while loading logs

2017-11-03 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16237984#comment-16237984 ] Xavier Léauté commented on KAFKA-6163: -- [~ijuma] in this case it was a different fatal error

[jira] [Commented] (KAFKA-6164) ClientQuotaManager threads prevent shutdown when encountering an error loading logs

2017-11-03 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16237977#comment-16237977 ] Xavier Léauté commented on KAFKA-6164: -- [~ted_yu] that's certainly an option assuming we don't care

[jira] [Updated] (KAFKA-6177) kafka-mirror-maker.sh RecordTooLargeException

2017-11-06 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rémi REY updated KAFKA-6177: Description: Hi all, I am facing an issue with kafka-mirror-maker.sh. We have 2 kafka clusters

[jira] [Updated] (KAFKA-6177) kafka-mirror-maker.sh RecordTooLargeException

2017-11-06 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rémi REY updated KAFKA-6177: Attachment: server.properties Source kafka cluster config file sample. > kafka-mirror-maker

[jira] [Created] (KAFKA-6177) kafka-mirror-maker.sh RecordTooLargeException

2017-11-06 Thread JIRA
Rémi REY created KAFKA-6177: --- Summary: kafka-mirror-maker.sh RecordTooLargeException Key: KAFKA-6177 URL: https://issues.apache.org/jira/browse/KAFKA-6177 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-6177) kafka-mirror-maker.sh RecordTooLargeException

2017-11-06 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rémi REY updated KAFKA-6177: Description: Hi all, I am facing an issue with kafka-mirror-maker.sh. We have 2 kafka clusters

[jira] [Updated] (KAFKA-6178) Broker is listed as only ISR for all partitions it is leader of

2017-11-06 Thread AS (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] AS updated KAFKA-6178: -- Description: We're running a 15 broker cluster on windows machines, and one of the brokers, 10, is the only ISR on all

[jira] [Updated] (KAFKA-6178) Broker is listed as only ISR for all partitions it is leader of

2017-11-06 Thread AS (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] AS updated KAFKA-6178: -- Description: We're running a 15 broker cluster on windows machines, and one of the brokers, 10, is the only ISR on all

[jira] [Updated] (KAFKA-6178) Broker is listed as only ISR for all partitions it is leader of

2017-11-06 Thread AS (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] AS updated KAFKA-6178: -- Description: We're running a 15 broker cluster on windows machines, and one of the brokers, 10, is the only ISR on all

[jira] [Created] (KAFKA-6178) Broker is listed as only ISR for all partitions it is leader of

2017-11-06 Thread AS (JIRA)
AS created KAFKA-6178: - Summary: Broker is listed as only ISR for all partitions it is leader of Key: KAFKA-6178 URL: https://issues.apache.org/jira/browse/KAFKA-6178 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-6178) Broker is listed as only ISR for all partitions it is leader of

2017-11-06 Thread AS (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] AS updated KAFKA-6178: -- Description: We're running a 15 broker cluster on windows machines, and one of the brokers, 10, is the only ISR on all

[jira] [Updated] (KAFKA-6159) Link to upgrade docs in 1.0.0 release notes is broken

2017-11-02 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Schröder updated KAFKA-6159: --- Summary: Link to upgrade docs in 1.0.0 release notes is broken (was: Link to upgrade docs

[jira] [Updated] (KAFKA-6159) Link to upgrade docs in 1.0.0 release notes is broken

2017-11-02 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Schröder updated KAFKA-6159: --- Description: The release notes for 1.0.0 (https://dist.apache.org/repos/dist/release/kafka

[jira] [Created] (KAFKA-6159) Link to upgrade docs in 100 release notes is broken

2017-11-02 Thread JIRA
Martin Schröder created KAFKA-6159: -- Summary: Link to upgrade docs in 100 release notes is broken Key: KAFKA-6159 URL: https://issues.apache.org/jira/browse/KAFKA-6159 Project: Kafka Issue

[jira] [Updated] (KAFKA-6159) Link to upgrade docs in 1.0.0 release notes is broken

2017-11-02 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Schröder updated KAFKA-6159: --- Labels: release-notes (was: ) > Link to upgrade docs in 1.0.0 release notes is bro

[jira] [Updated] (KAFKA-6163) Broker should fail fast on startup if an error occurs while loading logs

2017-11-02 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-6163: - Affects Version/s: 1.0.0 > Broker should fail fast on startup if an error occurs while load

[jira] [Created] (KAFKA-6163) Broker should fail fast on startup if an error occurs while loading logs

2017-11-02 Thread JIRA
Xavier Léauté created KAFKA-6163: Summary: Broker should fail fast on startup if an error occurs while loading logs Key: KAFKA-6163 URL: https://issues.apache.org/jira/browse/KAFKA-6163 Project

[jira] [Created] (KAFKA-6164) ClientQuotaManager threads prevent shutdown when encountering an error loading logs

2017-11-02 Thread JIRA
Xavier Léauté created KAFKA-6164: Summary: ClientQuotaManager threads prevent shutdown when encountering an error loading logs Key: KAFKA-6164 URL: https://issues.apache.org/jira/browse/KAFKA-6164

[jira] [Assigned] (KAFKA-6163) Broker should fail fast on startup if an error occurs while loading logs

2017-11-06 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté reassigned KAFKA-6163: Assignee: Xavier Léauté > Broker should fail fast on startup if an error occurs wh

[jira] [Created] (KAFKA-6311) Expose Kafka cluster ID in Connect REST API

2017-12-05 Thread JIRA
Xavier Léauté created KAFKA-6311: Summary: Expose Kafka cluster ID in Connect REST API Key: KAFKA-6311 URL: https://issues.apache.org/jira/browse/KAFKA-6311 Project: Kafka Issue Type

[jira] [Commented] (KAFKA-6294) ZkClient is not joining it's event thread during an interrupt

2017-12-01 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16275011#comment-16275011 ] Buğra Gedik commented on KAFKA-6294: I guess this will happen if an interrupt is received while

[jira] [Resolved] (KAFKA-6114) kafka Java API Consumer and producer Offset value comparison?

2017-10-25 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau resolved KAFKA-6114. - Resolution: Invalid Assignee: Sönke Liebau > kafka Java API Consumer and producer Off

[jira] [Commented] (KAFKA-6114) kafka Java API Consumer and producer Offset value comparison?

2017-10-25 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16218651#comment-16218651 ] Sönke Liebau commented on KAFKA-6114: - Hi [~jvnath], I've responded to your [question

[jira] [Comment Edited] (KAFKA-4767) KafkaProducer is not joining its IO thread properly

2017-10-24 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16217695#comment-16217695 ] Buğra Gedik edited comment on KAFKA-4767 at 10/24/17 9:03 PM: -- Any progress

[jira] [Commented] (KAFKA-4767) KafkaProducer is not joining its IO thread properly

2017-10-24 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16217695#comment-16217695 ] Buğra Gedik commented on KAFKA-4767: Any progress on restoring the interrupt state of the current

[jira] [Created] (KAFKA-6868) BufferUnderflowException in client when querying consumer group information

2018-05-04 Thread JIRA
Xavier Léauté created KAFKA-6868: Summary: BufferUnderflowException in client when querying consumer group information Key: KAFKA-6868 URL: https://issues.apache.org/jira/browse/KAFKA-6868 Project

[jira] [Updated] (KAFKA-6868) BufferUnderflowException in client when querying consumer group information

2018-05-04 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-6868: - Description: Exceptions get thrown when describing consumer group or querying group offsets from

[jira] [Updated] (KAFKA-6868) BufferUnderflowException in client when querying consumer group information

2018-05-04 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-6868: - Description: Exceptions get thrown when describing consumer group or querying group offsets from

[jira] [Updated] (KAFKA-6868) BufferUnderflowException in client when querying consumer group information

2018-05-04 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-6868: - Description: Exceptions get thrown when describing consumer group or querying group offsets from

[jira] [Commented] (KAFKA-6689) Kafka not release .deleted file.

2018-05-07 Thread A (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465823#comment-16465823 ] A commented on KAFKA-6689: -- [~huxi_2b]   Thank you for your suggestion. After I have upgrade the Broker

[jira] [Created] (KAFKA-6901) Kafka crashes when trying to delete segment when retetention time is reached

2018-05-14 Thread JIRA
Grégory R. created KAFKA-6901: - Summary: Kafka crashes when trying to delete segment when retetention time is reached Key: KAFKA-6901 URL: https://issues.apache.org/jira/browse/KAFKA-6901 Project: Kafka

[jira] [Commented] (KAFKA-6729) KTable should use user source topics if possible and not create changelog topic

2018-05-14 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16474793#comment-16474793 ] Xavier Léauté commented on KAFKA-6729: -- [~vvcephei] it's not just a performance regression

[jira] [Updated] (KAFKA-6901) Kafka crashes when trying to delete segment when retetention time is reached

2018-05-17 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégory R. updated KAFKA-6901: -- Attachment: 20180517 - ProcessExplorer after the crash.png > Kafka crashes when trying to del

[jira] [Updated] (KAFKA-6901) Kafka crashes when trying to delete segment when retetention time is reached

2018-05-17 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégory R. updated KAFKA-6901: -- Priority: Major (was: Critical) > Kafka crashes when trying to delete segment when retetention t

[jira] [Updated] (KAFKA-6901) Kafka crashes when trying to delete segment when retetention time is reached

2018-05-17 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-6901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégory R. updated KAFKA-6901: -- Attachment: 20180517 - ProcessExplorer before the crash.png > Kafka crashes when trying to del

[jira] [Commented] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

2018-05-17 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479130#comment-16479130 ] Grégory R. commented on KAFKA-1194: --- This issue is reproduced with kafka 1.1.0 > The kafka bro

[jira] [Commented] (KAFKA-7070) KafkaConsumer#committed might unexpectedly shift consumer offset

2018-06-18 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16516318#comment-16516318 ] Jan Lukavský commented on KAFKA-7070: - Hi, sorry, my bad. I should have tried to create the test case

  1   2   3   4   5   6   7   8   9   10   >