[jira] [Created] (KAFKA-6794) Support for incremental replica reassignment

Jason Gustafson created KAFKA-6794: -- Summary: Support for incremental replica reassignment Key: KAFKA-6794 URL: https://issues.apache.org/jira/browse/KAFKA-6794 Project: Kafka Issue Type:

[jira] [Resolved] (KAFKA-6792) Wrong pointer in the link for stream dsl

[ https://issues.apache.org/jira/browse/KAFKA-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-6792. -- Resolution: Fixed Fix Version/s: 1.0.0 > Wrong pointer in the link for stream dsl >

[jira] [Commented] (KAFKA-6514) Add API version as a tag for the RequestsPerSec metric

[ https://issues.apache.org/jira/browse/KAFKA-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439737#comment-16439737 ] ASF GitHub Bot commented on KAFKA-6514: --- hachikuji closed pull request #4506: KAFKA-6514: Add API

[jira] [Assigned] (KAFKA-6361) Fast leader fail over can lead to log divergence between leader and follower

[ https://issues.apache.org/jira/browse/KAFKA-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Povzner reassigned KAFKA-6361: --- Assignee: Anna Povzner (was: Jason Gustafson) > Fast leader fail over can lead to log

[jira] [Updated] (KAFKA-6794) Support for incremental replica reassignment

[ https://issues.apache.org/jira/browse/KAFKA-6794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-6794: --- Description: Say you have a replication factor of 4 and you trigger a reassignment which

[jira] [Commented] (KAFKA-4327) Move Reset Tool from core to streams

[ https://issues.apache.org/jira/browse/KAFKA-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439821#comment-16439821 ] Jorge Quilcate commented on KAFKA-4327: --- Now that

[jira] [Commented] (KAFKA-5975) No response when deleting topics and delete.topic.enable=false

[ https://issues.apache.org/jira/browse/KAFKA-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439572#comment-16439572 ] Mario Molina commented on KAFKA-5975: - What about this fix [~ewencp]? > No response when deleting

[jira] [Comment Edited] (KAFKA-5975) No response when deleting topics and delete.topic.enable=false

[ https://issues.apache.org/jira/browse/KAFKA-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439572#comment-16439572 ] Mario Molina edited comment on KAFKA-5975 at 4/16/18 3:19 PM: -- What about

[jira] [Commented] (KAFKA-6649) ReplicaFetcher stopped after non fatal exception is thrown

[ https://issues.apache.org/jira/browse/KAFKA-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439599#comment-16439599 ] Jason Gustafson commented on KAFKA-6649: [~srinivas.d...@gmail.com] I think those log messages are

[jira] [Created] (KAFKA-6793) Unnecessary warning log message

Anna O created KAFKA-6793: - Summary: Unnecessary warning log message Key: KAFKA-6793 URL: https://issues.apache.org/jira/browse/KAFKA-6793 Project: Kafka Issue Type: Bug Components:

[jira] [Comment Edited] (KAFKA-6649) ReplicaFetcher stopped after non fatal exception is thrown

[ https://issues.apache.org/jira/browse/KAFKA-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439951#comment-16439951 ] Srinivas Dhruvakumar edited comment on KAFKA-6649 at 4/16/18 7:51 PM: --

[jira] [Commented] (KAFKA-6727) org.apache.kafka.clients.admin.Config has broken equals and hashCode method.

[ https://issues.apache.org/jira/browse/KAFKA-6727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439922#comment-16439922 ] ASF GitHub Bot commented on KAFKA-6727: --- hachikuji closed pull request #4796: KAFKA-6727 fix broken

[jira] [Commented] (KAFKA-6649) ReplicaFetcher stopped after non fatal exception is thrown

[ https://issues.apache.org/jira/browse/KAFKA-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439951#comment-16439951 ] Srinivas Dhruvakumar commented on KAFKA-6649: - [~hachikuji] - Sorry for the miscommunication.

[jira] [Commented] (KAFKA-6795) Add unit test for ReplicaAlterLogDirsThread

[ https://issues.apache.org/jira/browse/KAFKA-6795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439991#comment-16439991 ] Dong Lin commented on KAFKA-6795: - Thanks for adding more tests [~apovzner]. Currently 

[jira] [Created] (KAFKA-6795) Add unit test for ReplicaAlterLogDirsThread

Anna Povzner created KAFKA-6795: --- Summary: Add unit test for ReplicaAlterLogDirsThread Key: KAFKA-6795 URL: https://issues.apache.org/jira/browse/KAFKA-6795 Project: Kafka Issue Type:

[jira] [Resolved] (KAFKA-6514) Add API version as a tag for the RequestsPerSec metric

[ https://issues.apache.org/jira/browse/KAFKA-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6514. Resolution: Fixed Fix Version/s: 1.2.0 > Add API version as a tag for the

[jira] [Commented] (KAFKA-4327) Move Reset Tool from core to streams

[ https://issues.apache.org/jira/browse/KAFKA-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439943#comment-16439943 ] Guozhang Wang commented on KAFKA-4327: -- As we discussed before, it may not worth the effort since 1)

[jira] [Resolved] (KAFKA-4327) Move Reset Tool from core to streams

[ https://issues.apache.org/jira/browse/KAFKA-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4327. -- Resolution: Won't Fix I'm resolving this ticket as won't fix for now. > Move Reset Tool from

[jira] [Commented] (KAFKA-6361) Fast leader fail over can lead to log divergence between leader and follower

[ https://issues.apache.org/jira/browse/KAFKA-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439970#comment-16439970 ] ASF GitHub Bot commented on KAFKA-6361: --- apovzner opened a new pull request #4882: KAFKA-6361: Fix

[jira] [Issue Comment Deleted] (KAFKA-6649) ReplicaFetcher stopped after non fatal exception is thrown

[ https://issues.apache.org/jira/browse/KAFKA-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinivas Dhruvakumar updated KAFKA-6649: Comment: was deleted (was: [~hachikuji] - Sorry for the miscommunication. We had an

[jira] [Commented] (KAFKA-6796) Surprising UNKNOWN_TOPIC error for produce/fetch requests to non-replicas

[ https://issues.apache.org/jira/browse/KAFKA-6796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16440133#comment-16440133 ] ASF GitHub Bot commented on KAFKA-6796: --- hachikuji opened a new pull request #4883: KAFKA-6796; Fix

[jira] [Comment Edited] (KAFKA-6649) ReplicaFetcher stopped after non fatal exception is thrown

[ https://issues.apache.org/jira/browse/KAFKA-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16440047#comment-16440047 ] Srinivas Dhruvakumar edited comment on KAFKA-6649 at 4/16/18 9:27 PM: --

[jira] [Created] (KAFKA-6796) Surprising UNKNOWN_TOPIC error for produce/fetch requests to non-replicas

Jason Gustafson created KAFKA-6796: -- Summary: Surprising UNKNOWN_TOPIC error for produce/fetch requests to non-replicas Key: KAFKA-6796 URL: https://issues.apache.org/jira/browse/KAFKA-6796 Project:

[jira] [Commented] (KAFKA-6649) ReplicaFetcher stopped after non fatal exception is thrown

[ https://issues.apache.org/jira/browse/KAFKA-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16440047#comment-16440047 ] Srinivas Dhruvakumar commented on KAFKA-6649: - The Offset Out Of Range Exception has been

[jira] [Commented] (KAFKA-6788) Grouping consumer requests per consumer coordinator in admin client

[ https://issues.apache.org/jira/browse/KAFKA-6788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439027#comment-16439027 ] ASF GitHub Bot commented on KAFKA-6788: --- cyrusv closed pull request #4875: KAFKA-6788: Grouping

[jira] [Comment Edited] (KAFKA-6792) Wrong pointer in the link for stream dsl

[ https://issues.apache.org/jira/browse/KAFKA-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16438990#comment-16438990 ] robin m edited comment on KAFKA-6792 at 4/16/18 6:36 AM: -

[jira] [Commented] (KAFKA-6696) Trogdor should support destroying tasks

[ https://issues.apache.org/jira/browse/KAFKA-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439086#comment-16439086 ] ASF GitHub Bot commented on KAFKA-6696: --- rajinisivaram closed pull request #4759: KAFKA-6696 Trogdor

[jira] [Commented] (KAFKA-6788) Grouping consumer requests per consumer coordinator in admin client

[ https://issues.apache.org/jira/browse/KAFKA-6788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439050#comment-16439050 ] ASF GitHub Bot commented on KAFKA-6788: --- cyrusv opened a new pull request #4878: KAFKA-6788: Combine

[jira] [Commented] (KAFKA-6771) Make specifying partitions in RoundTripWorkload, ProduceBench more flexible

[ https://issues.apache.org/jira/browse/KAFKA-6771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439088#comment-16439088 ] ASF GitHub Bot commented on KAFKA-6771: --- rajinisivaram closed pull request #4850: KAFKA-6771. Make

[jira] [Updated] (KAFKA-6266) Kafka 1.0.0 : Repeated occurrence of WARN Resetting first dirty offset of __consumer_offsets-xx to log start offset 203569 since the checkpointed offset 120955 is invalid

[ https://issues.apache.org/jira/browse/KAFKA-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-6266: --- Affects Version/s: 1.0.1 > Kafka 1.0.0 : Repeated occurrence of WARN Resetting first dirty offset of

[jira] [Updated] (KAFKA-6266) Kafka 1.0.0 : Repeated occurrence of WARN Resetting first dirty offset of __consumer_offsets-xx to log start offset 203569 since the checkpointed offset 120955 is invalid

[ https://issues.apache.org/jira/browse/KAFKA-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-6266: --- Description: I upgraded Kafka from 0.10.2.1 to 1.0.0 version. From then, I see the below warnings in

[jira] [Commented] (KAFKA-6266) Kafka 1.0.0 : Repeated occurrence of WARN Resetting first dirty offset of __consumer_offsets-xx to log start offset 203569 since the checkpointed offset 120955 is inval

[ https://issues.apache.org/jira/browse/KAFKA-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16440212#comment-16440212 ] Jeff Widman commented on KAFKA-6266: I am hitting this after upgrading a 0.10.0.1 broker to 1.0.1.

[jira] [Comment Edited] (KAFKA-6266) Kafka 1.0.0 : Repeated occurrence of WARN Resetting first dirty offset of __consumer_offsets-xx to log start offset 203569 since the checkpointed offset 120955 is

[ https://issues.apache.org/jira/browse/KAFKA-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16440212#comment-16440212 ] Jeff Widman edited comment on KAFKA-6266 at 4/17/18 1:07 AM: - I am hitting

[jira] [Resolved] (KAFKA-6650) The controller should be able to handle a partially deleted topic

[ https://issues.apache.org/jira/browse/KAFKA-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-6650. Resolution: Fixed Fix Version/s: 2.0.0 merged the PR to trunk. > The controller should be able to

[jira] [Commented] (KAFKA-6054) ERROR "SubscriptionInfo - unable to decode subscription data: version=2" when upgrading from 0.10.0.0 to 0.10.2.1

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