[jira] [Commented] (KAFKA-5358) Consumer perf tool should count rebalance time separately

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

[jira] [Commented] (KAFKA-5358) Consumer perf tool should count rebalance time separately

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

[jira] [Commented] (KAFKA-5731) Connect WorkerSinkTask out of order offset commit can lead to inconsistent state

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

[jira] [Commented] (KAFKA-5603) Streams should not abort transaction when closing zombie task

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

[jira] [Commented] (KAFKA-5768) Upgrade ducktape version to 0.7.0, and use new kill_java_processes

[ https://issues.apache.org/jira/browse/KAFKA-5768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137689#comment-16137689 ] Colin P. McCabe commented on KAFKA-5768: https://github.com/apache/kafka/pull/3721 > Upgrade

[jira] [Commented] (KAFKA-3705) Support non-key joining in KTable

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

[jira] [Updated] (KAFKA-2590) KIP-28: Kafka Streams Checklist

[ https://issues.apache.org/jira/browse/KAFKA-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2590: - Fix Version/s: 0.11.0.0 > KIP-28: Kafka Streams Checklist > --- > >

[jira] [Updated] (KAFKA-4125) Provide low-level Processor API meta data in DSL layer

[ https://issues.apache.org/jira/browse/KAFKA-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4125: - Issue Type: New Feature (was: Sub-task) Parent: (was: KAFKA-2590) > Provide

[jira] [Updated] (KAFKA-5731) Connect WorkerSinkTask out of order offset commit can lead to inconsistent state

[ https://issues.apache.org/jira/browse/KAFKA-5731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-5731: - Fix Version/s: 0.10.2.2 > Connect WorkerSinkTask out of order offset commit can

[jira] [Resolved] (KAFKA-2590) KIP-28: Kafka Streams Checklist

[ https://issues.apache.org/jira/browse/KAFKA-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-2590. -- Resolution: Fixed Assignee: Guozhang Wang > KIP-28: Kafka Streams Checklist >

[jira] [Updated] (KAFKA-3429) Remove Serdes needed for repartitioning in KTable stateful operations

[ https://issues.apache.org/jira/browse/KAFKA-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3429: - Issue Type: Improvement (was: Sub-task) Parent: (was: KAFKA-2590) > Remove Serdes

[jira] [Updated] (KAFKA-4113) Allow KTable bootstrap

[ https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4113: - Issue Type: New Feature (was: Sub-task) Parent: (was: KAFKA-2590) > Allow KTable

[jira] [Updated] (KAFKA-3429) Remove Serdes needed for repartitioning in KTable stateful operations

[ https://issues.apache.org/jira/browse/KAFKA-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3429: - Labels: api (was: api newbie++) > Remove Serdes needed for repartitioning in KTable stateful

[jira] [Updated] (KAFKA-5768) Upgrade ducktape version to 0.7.0, and use new kill_java_processes

[ https://issues.apache.org/jira/browse/KAFKA-5768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-5768: --- Description: Upgrade the ducktape version to 0.7.0. Use the new {{kill_java_processes}}

[jira] [Created] (KAFKA-5768) Upgrade ducktape version to 0.7.0, and use new kill_java_processes

Colin P. McCabe created KAFKA-5768: -- Summary: Upgrade ducktape version to 0.7.0, and use new kill_java_processes Key: KAFKA-5768 URL: https://issues.apache.org/jira/browse/KAFKA-5768 Project: Kafka

[jira] [Commented] (KAFKA-5603) Streams should not abort transaction when closing zombie task

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

[jira] [Commented] (KAFKA-5767) Kafka server should halt if IBP < 1.0.0 and there is log directory failure

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

[jira] [Commented] (KAFKA-5731) Connect WorkerSinkTask out of order offset commit can lead to inconsistent state

[ https://issues.apache.org/jira/browse/KAFKA-5731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137610#comment-16137610 ] Randall Hauch commented on KAFKA-5731: -- [~hachikuji] or [~ewencp]: I've reopened the issue so this

[jira] [Commented] (KAFKA-5731) Connect WorkerSinkTask out of order offset commit can lead to inconsistent state

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

[jira] [Created] (KAFKA-5767) Kafka server should halt if IBP < 1.0.0 and there is log directory failure

Dong Lin created KAFKA-5767: --- Summary: Kafka server should halt if IBP < 1.0.0 and there is log directory failure Key: KAFKA-5767 URL: https://issues.apache.org/jira/browse/KAFKA-5767 Project: Kafka

[jira] [Assigned] (KAFKA-5156) Options for handling exceptions in streams

[ https://issues.apache.org/jira/browse/KAFKA-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-5156: -- Assignee: Matthias J. Sax (was: Eno Thereska) > Options for handling exceptions in

[jira] [Commented] (KAFKA-3473) Add controller channel manager request queue time metric.

[ https://issues.apache.org/jira/browse/KAFKA-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137320#comment-16137320 ] Ismael Juma commented on KAFKA-3473: [~omkreddy], we added metrics for the controller channel queue

[jira] [Commented] (KAFKA-3473) Add controller channel manager request queue time metric.

[ https://issues.apache.org/jira/browse/KAFKA-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137281#comment-16137281 ] Manikumar commented on KAFKA-3473: -- @ijuma Is this covered in KAFKA-5135/KIP-143? > Add controller

[jira] [Resolved] (KAFKA-3653) expose the queue size in ControllerChannelManager

[ https://issues.apache.org/jira/browse/KAFKA-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3653. -- Resolution: Fixed Fixed in KAFKA-5135/KIP-143 > expose the queue size in ControllerChannelManager >

[jira] [Resolved] (KAFKA-3800) java client can`t poll msg

[ https://issues.apache.org/jira/browse/KAFKA-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3800. -- Resolution: Cannot Reproduce Please reopen if the issue still exists. > java client can`t poll msg

[jira] [Resolved] (KAFKA-3927) kafka broker config docs issue

[ https://issues.apache.org/jira/browse/KAFKA-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3927. -- Resolution: Later Yes, These changes are done in KAFKA-615. Please reopen if the issue still exists.

[jira] [Comment Edited] (KAFKA-5749) Refactor SessionStore hierarchy

[ https://issues.apache.org/jira/browse/KAFKA-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137226#comment-16137226 ] Andrey Dyachkov edited comment on KAFKA-5749 at 8/22/17 7:13 PM: -

[jira] [Commented] (KAFKA-5749) Refactor SessionStore hierarchy

[ https://issues.apache.org/jira/browse/KAFKA-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137226#comment-16137226 ] Andrey Dyachkov commented on KAFKA-5749: [~miguno] It would be very nice if someone will guide me

[jira] [Commented] (KAFKA-5732) Kafka 0.11 Consumer.Poll() hangs for consumer.subscribe()

[ https://issues.apache.org/jira/browse/KAFKA-5732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137222#comment-16137222 ] Ramkumar commented on KAFKA-5732: - I found if this points to old data log directory (which had Kafka 0.8

[jira] [Created] (KAFKA-5766) Very high CPU-load of consumer when broker is down

Sebastian Bernauer created KAFKA-5766: - Summary: Very high CPU-load of consumer when broker is down Key: KAFKA-5766 URL: https://issues.apache.org/jira/browse/KAFKA-5766 Project: Kafka

[jira] [Resolved] (KAFKA-4823) Creating Kafka Producer on application running on Java older version

[ https://issues.apache.org/jira/browse/KAFKA-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4823. -- Resolution: Won't Fix Kafka Dropped support for Java 1.6 from 0.9 release. You can try Rest

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

[ https://issues.apache.org/jira/browse/KAFKA-5765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5765: - Fix Version/s: 1.0.0 > Move merge() from StreamsBuilder to KStream >

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

[ https://issues.apache.org/jira/browse/KAFKA-5765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137146#comment-16137146 ] Guozhang Wang commented on KAFKA-5765: -- Sounds reasonable to me. > Move merge() from StreamsBuilder

[jira] [Commented] (KAFKA-5152) Kafka Streams keeps restoring state after shutdown is initiated during startup

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

[jira] [Comment Edited] (KAFKA-5696) SourceConnector does not commit offset on rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137100#comment-16137100 ] Oleg Kuznetsov edited comment on KAFKA-5696 at 8/22/17 5:56 PM: [~rhauch]

[jira] [Commented] (KAFKA-5696) SourceConnector does not commit offset on rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137100#comment-16137100 ] Oleg Kuznetsov commented on KAFKA-5696: --- [~rhauch] Is it possible to add waiting all the task to

[jira] [Assigned] (KAFKA-5547) Return topic authorization failed if no topic describe access

[ https://issues.apache.org/jira/browse/KAFKA-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-5547: Assignee: Manikumar > Return topic authorization failed if no topic describe access >

[jira] [Updated] (KAFKA-5603) Streams should not abort transaction when closing zombie task

[ https://issues.apache.org/jira/browse/KAFKA-5603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5603: --- Fix Version/s: (was: 0.11.0.2) 0.11.0.1 > Streams should not abort

[jira] [Commented] (KAFKA-5749) Refactor SessionStore hierarchy

[ https://issues.apache.org/jira/browse/KAFKA-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137085#comment-16137085 ] Michael Noll commented on KAFKA-5749: - Thanks for wanting to contribute, Andrey! Perhaps you could

[jira] [Resolved] (KAFKA-5401) Kafka Over TLS Error - Failed to send SSL Close message - Broken Pipe

[ https://issues.apache.org/jira/browse/KAFKA-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5401. -- Resolution: Duplicate > Kafka Over TLS Error - Failed to send SSL Close message - Broken Pipe >

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

[ 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-5765) Move merge() from StreamsBuilder to KStream

Matthias J. Sax created KAFKA-5765: -- Summary: Move merge() from StreamsBuilder to KStream Key: KAFKA-5765 URL: https://issues.apache.org/jira/browse/KAFKA-5765 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-5758) Reassigning a topic's partitions can adversely impact other topics

[ https://issues.apache.org/jira/browse/KAFKA-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136984#comment-16136984 ] David van Geest commented on KAFKA-5758: Awesome, Option 3 makes sense to me. Sorry for not

[jira] [Assigned] (KAFKA-5762) Refactor AdminClient to use LogContext

[ https://issues.apache.org/jira/browse/KAFKA-5762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kamal Chandraprakash reassigned KAFKA-5762: --- Assignee: Kamal Chandraprakash > Refactor AdminClient to use LogContext >

[jira] [Commented] (KAFKA-5758) Reassigning a topic's partitions can adversely impact other topics

[ https://issues.apache.org/jira/browse/KAFKA-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136959#comment-16136959 ] Ismael Juma commented on KAFKA-5758: Option 3 is a normal pattern for the Kafka protocol (since APIs

[jira] [Commented] (KAFKA-5758) Reassigning a topic's partitions can adversely impact other topics

[ https://issues.apache.org/jira/browse/KAFKA-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136980#comment-16136980 ] Ismael Juma commented on KAFKA-5758: Yes. > Reassigning a topic's partitions can adversely impact

[jira] [Commented] (KAFKA-5696) SourceConnector does not commit offset on rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136976#comment-16136976 ] Randall Hauch commented on KAFKA-5696: -- [~olkuznsmith], adding, updating, or removing a connector

[jira] [Commented] (KAFKA-5758) Reassigning a topic's partitions can adversely impact other topics

[ https://issues.apache.org/jira/browse/KAFKA-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136974#comment-16136974 ] David van Geest commented on KAFKA-5758: Ah OK. So Option 3 still returns data for the other

[jira] [Updated] (KAFKA-5748) Fix console producer to set timestamp and partition

[ https://issues.apache.org/jira/browse/KAFKA-5748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5748: --- Fix Version/s: (was: 0.11.0.1) 1.0.0 > Fix console producer to set timestamp

[jira] [Commented] (KAFKA-5758) Reassigning a topic's partitions can adversely impact other topics

[ https://issues.apache.org/jira/browse/KAFKA-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136933#comment-16136933 ] David van Geest commented on KAFKA-5758: [~ijuma], thanks for the response! I'm not sure I

[jira] [Updated] (KAFKA-5465) FetchResponse v0 does not return any messages when max_bytes smaller than v2 message set

[ https://issues.apache.org/jira/browse/KAFKA-5465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5465: --- Fix Version/s: (was: 0.11.0.1) > FetchResponse v0 does not return any messages when max_bytes

[jira] [Updated] (KAFKA-5681) jarAll does not build all scala versions anymore.

[ https://issues.apache.org/jira/browse/KAFKA-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5681: --- Fix Version/s: (was: 0.11.0.1) > jarAll does not build all scala versions anymore. >

[jira] [Created] (KAFKA-5764) KafkaShortnamer should allow for case inensitive matches

Ryan P created KAFKA-5764: - Summary: KafkaShortnamer should allow for case inensitive matches Key: KAFKA-5764 URL: https://issues.apache.org/jira/browse/KAFKA-5764 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-5752) Delete topic and re-create topic immediate will delete the new topic's timeindex

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

[jira] [Resolved] (KAFKA-4856) Calling KafkaProducer.close() from multiple threads may cause spurious error

[ https://issues.apache.org/jira/browse/KAFKA-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4856. Resolution: Fixed Fix Version/s: 1.0.0 0.11.0.1 > Calling

[jira] [Commented] (KAFKA-4856) Calling KafkaProducer.close() from multiple threads may cause spurious error

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

[jira] [Comment Edited] (KAFKA-5153) KAFKA Cluster : 0.10.2.0 : Servers Getting disconnected : Service Impacting

[ https://issues.apache.org/jira/browse/KAFKA-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136769#comment-16136769 ] Arpan edited comment on KAFKA-5153 at 8/22/17 1:10 PM: --- Hi [~arthurk] - Not sure yet

[jira] [Commented] (KAFKA-5153) KAFKA Cluster : 0.10.2.0 : Servers Getting disconnected : Service Impacting

[ https://issues.apache.org/jira/browse/KAFKA-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136769#comment-16136769 ] Arpan commented on KAFKA-5153: -- Hi [~arthurk] - Not sure yet what is the solution and we are also stuck and

[jira] [Assigned] (KAFKA-2254) The shell script should be optimized , even kafka-run-class.sh has a syntax error.

[ https://issues.apache.org/jira/browse/KAFKA-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-2254: Assignee: Manikumar > The shell script should be optimized , even kafka-run-class.sh has a syntax

[jira] [Assigned] (KAFKA-4856) Calling KafkaProducer.close() from multiple threads may cause spurious error

[ https://issues.apache.org/jira/browse/KAFKA-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-4856: Assignee: Manikumar > Calling KafkaProducer.close() from multiple threads may cause spurious error

[jira] [Created] (KAFKA-5763) Refactor NetworkClient to use LogContext

Ismael Juma created KAFKA-5763: -- Summary: Refactor NetworkClient to use LogContext Key: KAFKA-5763 URL: https://issues.apache.org/jira/browse/KAFKA-5763 Project: Kafka Issue Type: Improvement

[jira] [Created] (KAFKA-5762) Refactor AdminClient to use LogContext

Ismael Juma created KAFKA-5762: -- Summary: Refactor AdminClient to use LogContext Key: KAFKA-5762 URL: https://issues.apache.org/jira/browse/KAFKA-5762 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-5758) Reassigning a topic's partitions can adversely impact other topics

[ https://issues.apache.org/jira/browse/KAFKA-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136708#comment-16136708 ] Ismael Juma commented on KAFKA-5758: [~junrao], what do you think we should do in this case? Option 1

[jira] [Updated] (KAFKA-5758) Reassigning a topic's partitions can adversely impact other topics

[ https://issues.apache.org/jira/browse/KAFKA-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5758: --- Fix Version/s: (was: 0.11.0.1) > Reassigning a topic's partitions can adversely impact other

[jira] [Comment Edited] (KAFKA-5758) Reassigning a topic's partitions can adversely impact other topics

[ https://issues.apache.org/jira/browse/KAFKA-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136702#comment-16136702 ] Ismael Juma edited comment on KAFKA-5758 at 8/22/17 12:28 PM: -- [~dwvangeest],

[jira] [Commented] (KAFKA-5758) Reassigning a topic's partitions can adversely impact other topics

[ https://issues.apache.org/jira/browse/KAFKA-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136702#comment-16136702 ] Ismael Juma commented on KAFKA-5758: [~dwvangeest], looks like a good fine. We should not be failing

[jira] [Updated] (KAFKA-5758) Reassigning a topic's partitions can adversely impact other topics

[ https://issues.apache.org/jira/browse/KAFKA-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5758: --- Fix Version/s: 1.0.0 0.11.0.1 > Reassigning a topic's partitions can adversely

[jira] [Updated] (KAFKA-5758) Reassigning a topic's partitions can adversely impact other topics

[ https://issues.apache.org/jira/browse/KAFKA-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5758: --- Labels: reliability (was: ) > Reassigning a topic's partitions can adversely impact other topics >

[jira] [Updated] (KAFKA-5720) In Jenkins, kafka.api.SaslSslAdminClientIntegrationTest failed with org.apache.kafka.common.errors.TimeoutException

[ https://issues.apache.org/jira/browse/KAFKA-5720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5720: --- Fix Version/s: 1.0.0 > In Jenkins, kafka.api.SaslSslAdminClientIntegrationTest failed with >

[jira] [Commented] (KAFKA-5342) Distinguish abortable failures in transactional producer

[ https://issues.apache.org/jira/browse/KAFKA-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136686#comment-16136686 ] Ismael Juma commented on KAFKA-5342: [~hachikuji], do you think you can submit the PR today? >

[jira] [Commented] (KAFKA-5749) Refactor SessionStore hierarchy

[ https://issues.apache.org/jira/browse/KAFKA-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136644#comment-16136644 ] Damian Guy commented on KAFKA-5749: --- Sorry [~adyachkov] these tasks i've assigned to myself as the are

[jira] [Assigned] (KAFKA-5686) Documentation inconsistency on the "Compression"

[ https://issues.apache.org/jira/browse/KAFKA-5686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-5686: Assignee: Manikumar > Documentation inconsistency on the "Compression" >

[jira] [Resolved] (KAFKA-5751) Kafka cannot start; corrupted index file(s)

[ https://issues.apache.org/jira/browse/KAFKA-5751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5751. -- Resolution: Duplicate > Kafka cannot start; corrupted index file(s) >

[jira] [Assigned] (KAFKA-5714) Allow whitespaces in the principal name

[ https://issues.apache.org/jira/browse/KAFKA-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reassigned KAFKA-5714: Assignee: (was: Manikumar) > Allow whitespaces in the principal name >

[jira] [Commented] (KAFKA-5689) Refactor WindowStore hierarchy so that Metered Store is the outermost store

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

[jira] [Updated] (KAFKA-5503) Idempotent producer ignores shutdown while fetching ProducerId

[ https://issues.apache.org/jira/browse/KAFKA-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5503: --- Fix Version/s: (was: 0.11.0.2, 1.0.0) 0.11.0.2 1.0.0 >

[jira] [Updated] (KAFKA-5503) Idempotent producer ignores shutdown while fetching ProducerId

[ https://issues.apache.org/jira/browse/KAFKA-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5503: --- Fix Version/s: (was: 0.11.0.1) 0.11.0.2, 1.0.0 > Idempotent producer ignores

[jira] [Assigned] (KAFKA-5752) Delete topic and re-create topic immediate will delete the new topic's timeindex

[ https://issues.apache.org/jira/browse/KAFKA-5752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-5752: -- Assignee: Manikumar > Delete topic and re-create topic immediate will delete the new topic's

[jira] [Created] (KAFKA-5761) Serializer API should support ByteBuffer

Bhaskar Gollapudi created KAFKA-5761: Summary: Serializer API should support ByteBuffer Key: KAFKA-5761 URL: https://issues.apache.org/jira/browse/KAFKA-5761 Project: Kafka Issue Type:

[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: 1.0.0 > KerberosLogin refresh time bug and other improvements >

[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.2 > KerberosLogin refresh time bug and

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

[ 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: