[jira] [Created] (KAFKA-6581) ConsumerGroupCommand hangs if even one of the partition is unavailable

Sahil Aggarwal created KAFKA-6581: - Summary: ConsumerGroupCommand hangs if even one of the partition is unavailable Key: KAFKA-6581 URL: https://issues.apache.org/jira/browse/KAFKA-6581 Project: Kafka

[jira] [Commented] (KAFKA-5157) Options for handling corrupt data during deserialization

[ https://issues.apache.org/jira/browse/KAFKA-5157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372564#comment-16372564 ] Marcel "childNo͡.de" Trautwein commented on KAFKA-5157: --- Just a ques

[jira] [Comment Edited] (KAFKA-5157) Options for handling corrupt data during deserialization

[ https://issues.apache.org/jira/browse/KAFKA-5157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372564#comment-16372564 ] Marcel "childNo͡.de" Trautwein edited comment on KAFKA-5157 at 2/22/18 9:08 AM:

[jira] [Resolved] (KAFKA-6577) Connect standalone SASL file source and sink test fails without explanation

[ https://issues.apache.org/jira/browse/KAFKA-6577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-6577. --- Resolution: Fixed Fix Version/s: 1.2.0 Issue resolved by pull request 4610 [https://github.com/

[jira] [Commented] (KAFKA-6577) Connect standalone SASL file source and sink test fails without explanation

[ https://issues.apache.org/jira/browse/KAFKA-6577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372606#comment-16372606 ] ASF GitHub Bot commented on KAFKA-6577: --- dguy closed pull request #4610: KAFKA-6577:

[jira] [Commented] (KAFKA-6572) kafka-consumer-groups does not reset offsets to specified datetime correctly

[ https://issues.apache.org/jira/browse/KAFKA-6572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372618#comment-16372618 ] huxihx commented on KAFKA-6572: --- [~slucas] Currently, the partition's offset will be set to

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

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372629#comment-16372629 ] AMOUSSOU DJANGBAN Baruch commented on KAFKA-4477: - Hi All, I have same is

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

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372644#comment-16372644 ] Håkon Åmdal commented on KAFKA-4477: We ended up running our own build of Kafka 0.11.0

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

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372665#comment-16372665 ] AMOUSSOU DJANGBAN Baruch commented on KAFKA-4477: - Thanks [~hawk_aa] Are

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

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372683#comment-16372683 ] Håkon Åmdal commented on KAFKA-4477: Not sure, but if they use Kafka 1.0.0, all those

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

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372689#comment-16372689 ] AMOUSSOU DJANGBAN Baruch commented on KAFKA-4477: - Ok Thanks    > Node r

[jira] [Commented] (KAFKA-6581) ConsumerGroupCommand hangs if even one of the partition is unavailable

[ https://issues.apache.org/jira/browse/KAFKA-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372688#comment-16372688 ] ASF GitHub Bot commented on KAFKA-6581: --- SahilAggarwal opened a new pull request #46

[jira] [Updated] (KAFKA-6581) ConsumerGroupCommand hangs if even one of the partition is unavailable

[ https://issues.apache.org/jira/browse/KAFKA-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Aggarwal updated KAFKA-6581: -- Priority: Minor (was: Major) > ConsumerGroupCommand hangs if even one of the partition is unava

[jira] [Created] (KAFKA-6582) Partitions get underreplicated, with a single ISR, and doesn't recover. Other brokers do not take over and we need to manually restart the broker.

Jurriaan Pruis created KAFKA-6582: - Summary: Partitions get underreplicated, with a single ISR, and doesn't recover. Other brokers do not take over and we need to manually restart the broker. Key: KAFKA-6582 URL:

[jira] [Commented] (KAFKA-3450) Producer blocks on send to topic that doesn't exist if auto create is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372875#comment-16372875 ] Josef Ludvíček commented on KAFKA-3450: --- Same problem with 0.11.0.1 Is there any pl

[jira] [Commented] (KAFKA-6572) kafka-consumer-groups does not reset offsets to specified datetime correctly

[ https://issues.apache.org/jira/browse/KAFKA-6572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372986#comment-16372986 ] Sharon Lucas commented on KAFKA-6572: - No.  There were tons of messages whose timestam

[jira] [Comment Edited] (KAFKA-6572) kafka-consumer-groups does not reset offsets to specified datetime correctly

[ https://issues.apache.org/jira/browse/KAFKA-6572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372986#comment-16372986 ] Sharon Lucas edited comment on KAFKA-6572 at 2/22/18 4:03 PM: --

[jira] [Updated] (KAFKA-6583) Metadata should include number of state stores for task

[ https://issues.apache.org/jira/browse/KAFKA-6583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-6583: -- Component/s: streams > Metadata should include number of state stores for task > ---

[jira] [Created] (KAFKA-6583) Metadata should include number of state stores for task

Richard Yu created KAFKA-6583: - Summary: Metadata should include number of state stores for task Key: KAFKA-6583 URL: https://issues.apache.org/jira/browse/KAFKA-6583 Project: Kafka Issue Type: I

[jira] [Updated] (KAFKA-6583) Metadata should include number of state stores for task

[ https://issues.apache.org/jira/browse/KAFKA-6583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-6583: -- Affects Version/s: 0.10.2.0 0.11.0.0 > Metadata should include number of state st

[jira] [Created] (KAFKA-6584) Session expiration concurrent with ZooKeeper leadership failover may lead to broker registration failure

Chris Thunes created KAFKA-6584: --- Summary: Session expiration concurrent with ZooKeeper leadership failover may lead to broker registration failure Key: KAFKA-6584 URL: https://issues.apache.org/jira/browse/KAFKA-65

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

[ https://issues.apache.org/jira/browse/KAFKA-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-4696: -- External issue URL: https://issues.apache.org/jira/browse/KAFKA-6583 > Streams standby task assignment s

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

[ https://issues.apache.org/jira/browse/KAFKA-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-4696: -- External issue URL: (was: https://issues.apache.org/jira/browse/KAFKA-6583) > Streams standby task as

[jira] [Commented] (KAFKA-6583) Metadata should include number of state stores for task

[ https://issues.apache.org/jira/browse/KAFKA-6583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373124#comment-16373124 ] Richard Yu commented on KAFKA-6583: --- This issue will block https://issues.apache.org/jir

[jira] [Updated] (KAFKA-5157) Options for handling corrupt data during deserialization

[ https://issues.apache.org/jira/browse/KAFKA-5157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5157: --- Description: When there is a bad formatted data in the source topics, deserialization will th

[jira] [Updated] (KAFKA-5157) Options for handling corrupt data during deserialization

[ https://issues.apache.org/jira/browse/KAFKA-5157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5157: --- Labels: kip user-experience (was: user-experience) > Options for handling corrupt data during

[jira] [Created] (KAFKA-6585) Sonsolidate duplicated logic on reset tools

Guozhang Wang created KAFKA-6585: Summary: Sonsolidate duplicated logic on reset tools Key: KAFKA-6585 URL: https://issues.apache.org/jira/browse/KAFKA-6585 Project: Kafka Issue Type: Improve

[jira] [Updated] (KAFKA-6585) Consolidate duplicated logic on reset tools

[ https://issues.apache.org/jira/browse/KAFKA-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-6585: --- Summary: Consolidate duplicated logic on reset tools (was: Sonsolidate duplicated logic on re

[jira] [Created] (KAFKA-6586) Refactor Connect executables

Randall Hauch created KAFKA-6586: Summary: Refactor Connect executables Key: KAFKA-6586 URL: https://issues.apache.org/jira/browse/KAFKA-6586 Project: Kafka Issue Type: Improvement

[jira] [Updated] (KAFKA-6586) Refactor Connect executables

[ https://issues.apache.org/jira/browse/KAFKA-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-6586: - Description: The main methods in {{ConnectDistributed}} and {{ConnectStandalone}} have a lot of du

[jira] [Commented] (KAFKA-6585) Consolidate duplicated logic on reset tools

[ https://issues.apache.org/jira/browse/KAFKA-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373401#comment-16373401 ] Aditya Vivek commented on KAFKA-6585: - [~guozhang] Can I pick this up? > Consolidate

[jira] [Commented] (KAFKA-5157) Options for handling corrupt data during deserialization

[ https://issues.apache.org/jira/browse/KAFKA-5157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373432#comment-16373432 ] Matthias J. Sax commented on KAFKA-5157: It is by design. It's of course something

[jira] [Assigned] (KAFKA-6585) Consolidate duplicated logic on reset tools

[ https://issues.apache.org/jira/browse/KAFKA-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-6585: -- Assignee: Aditya Vivek > Consolidate duplicated logic on reset tools >

[jira] [Commented] (KAFKA-6585) Consolidate duplicated logic on reset tools

[ https://issues.apache.org/jira/browse/KAFKA-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373546#comment-16373546 ] Jason Gustafson commented on KAFKA-6585: [~adityavivek94] I went ahead and assigne

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

[ https://issues.apache.org/jira/browse/KAFKA-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373589#comment-16373589 ] ASF GitHub Bot commented on KAFKA-4696: --- ConcurrencyPractitioner opened a new pull r

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

[ https://issues.apache.org/jira/browse/KAFKA-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu reassigned KAFKA-4696: - Assignee: Richard Yu > Streams standby task assignment should be state-store aware >

[jira] [Updated] (KAFKA-6583) Metadata should include number of state stores for task

[ https://issues.apache.org/jira/browse/KAFKA-6583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-6583: -- Labels: needs-kip (was: ) > Metadata should include number of state stores for task > -

[jira] [Comment Edited] (KAFKA-6583) Metadata should include number of state stores for task

[ https://issues.apache.org/jira/browse/KAFKA-6583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373124#comment-16373124 ] Richard Yu edited comment on KAFKA-6583 at 2/23/18 12:52 AM: -

[jira] [Updated] (KAFKA-6583) Metadata should include number of state stores for task

[ https://issues.apache.org/jira/browse/KAFKA-6583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-6583: -- Issue Type: New Feature (was: Improvement) > Metadata should include number of state stores for task >

[jira] [Commented] (KAFKA-6002) Kafka Connect Transform transforming JSON string into actual object

[ https://issues.apache.org/jira/browse/KAFKA-6002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373755#comment-16373755 ] Ewen Cheslack-Postava commented on KAFKA-6002: -- [~edvard.poliakov] Not sure i

[jira] [Commented] (KAFKA-6583) Metadata should include number of state stores for task

[ https://issues.apache.org/jira/browse/KAFKA-6583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373759#comment-16373759 ] Matthias J. Sax commented on KAFKA-6583: Thanks for putting the comment. It's bett

[jira] [Commented] (KAFKA-5828) Allow explicitly setting polling interval for Kafka connectors

[ https://issues.apache.org/jira/browse/KAFKA-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373773#comment-16373773 ] Ewen Cheslack-Postava commented on KAFKA-5828: -- I don't think this is best so

[jira] [Commented] (KAFKA-6551) Unbounded queues in WorkerSourceTask cause OutOfMemoryError

[ https://issues.apache.org/jira/browse/KAFKA-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373906#comment-16373906 ] Ewen Cheslack-Postava commented on KAFKA-6551: -- Seems reasonable – this shoul

[jira] [Issue Comment Deleted] (KAFKA-6583) Metadata should include number of state stores for task

[ https://issues.apache.org/jira/browse/KAFKA-6583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Yu updated KAFKA-6583: -- Comment: was deleted (was: This issue will block KAFKA-4696 until resolved.) > Metadata should include

[jira] [Commented] (KAFKA-5575) SchemaBuilder should have a method to clone an existing Schema.

[ https://issues.apache.org/jira/browse/KAFKA-5575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373925#comment-16373925 ] Ewen Cheslack-Postava commented on KAFKA-5575: -- [~rhauch] I think I didn't tr

[jira] [Commented] (KAFKA-5740) Use separate file for HTTP logs

[ https://issues.apache.org/jira/browse/KAFKA-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373949#comment-16373949 ] Ewen Cheslack-Postava commented on KAFKA-5740: -- Isn't this something that can

[jira] [Commented] (KAFKA-6585) Consolidate duplicated logic on reset tools

[ https://issues.apache.org/jira/browse/KAFKA-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373951#comment-16373951 ] Aditya Vivek commented on KAFKA-6585: - Thanks Jason :) > Consolidate duplicated logic

[jira] [Commented] (KAFKA-6433) Connect distributed workers should fail if their config is "incompatible" with leader's

[ https://issues.apache.org/jira/browse/KAFKA-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373961#comment-16373961 ] Ewen Cheslack-Postava commented on KAFKA-6433: -- This needs a lot of thought a

[jira] [Commented] (KAFKA-6578) Connect distributed and standalone worker 'main()' methods should catch and log all exceptions

[ https://issues.apache.org/jira/browse/KAFKA-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373981#comment-16373981 ] ASF GitHub Bot commented on KAFKA-6578: --- hachikuji closed pull request #4609: KAFKA-

[jira] [Resolved] (KAFKA-6578) Connect distributed and standalone worker 'main()' methods should catch and log all exceptions

[ https://issues.apache.org/jira/browse/KAFKA-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6578. Resolution: Fixed Fix Version/s: 1.1.0 > Connect distributed and standalone worker 'm

[jira] [Commented] (KAFKA-6572) kafka-consumer-groups does not reset offsets to specified datetime correctly

[ https://issues.apache.org/jira/browse/KAFKA-6572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374023#comment-16374023 ] huxihx commented on KAFKA-6572: --- [~slucas] Could it be possible that some records in those s