[jira] [Created] (KAFKA-17120) Race condition in KafkaStreams.close can result in StreamsException "Failed to shut down while in state"

Andy Coates created KAFKA-17120: --- Summary: Race condition in KafkaStreams.close can result in StreamsException "Failed to shut down while in state" Key: KAFKA-17120 URL:

[jira] [Resolved] (KAFKA-14660) Divide by zero security vulnerability (sonatype-2019-0422)

[ https://issues.apache.org/jira/browse/KAFKA-14660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Coates resolved KAFKA-14660. - Resolution: Fixed > Divide by zero security vulnerability (sonatype-2019-0422) >

[jira] [Reopened] (KAFKA-14660) Divide by zero security vulnerability (sonatype-2019-0422)

[ https://issues.apache.org/jira/browse/KAFKA-14660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Coates reopened KAFKA-14660: - The issue here is more the SonaType security vulnerability report than any impossible to reach

[jira] [Created] (KAFKA-14660) Divide by zero security vulnerability

Andy Coates created KAFKA-14660: --- Summary: Divide by zero security vulnerability Key: KAFKA-14660 URL: https://issues.apache.org/jira/browse/KAFKA-14660 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-10494) Streams: enableSendingOldValues should not call parent if node is itself materialized

Andy Coates created KAFKA-10494: --- Summary: Streams: enableSendingOldValues should not call parent if node is itself materialized Key: KAFKA-10494 URL: https://issues.apache.org/jira/browse/KAFKA-10494

[jira] [Created] (KAFKA-10077) Filter downstream of state-store results in suprious tombstones

Andy Coates created KAFKA-10077: --- Summary: Filter downstream of state-store results in suprious tombstones Key: KAFKA-10077 URL: https://issues.apache.org/jira/browse/KAFKA-10077 Project: Kafka

[jira] [Created] (KAFKA-9865) Expose output topic names from TopologyTestDriver

Andy Coates created KAFKA-9865: -- Summary: Expose output topic names from TopologyTestDriver Key: KAFKA-9865 URL: https://issues.apache.org/jira/browse/KAFKA-9865 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-9668) Iterating over KafkaStreams.getAllMetadata() results in ConcurrentModificationException

Andy Coates created KAFKA-9668: -- Summary: Iterating over KafkaStreams.getAllMetadata() results in ConcurrentModificationException Key: KAFKA-9668 URL: https://issues.apache.org/jira/browse/KAFKA-9668

[jira] [Created] (KAFKA-9667) Connect JSON serde strip trailing zeros

Andy Coates created KAFKA-9667: -- Summary: Connect JSON serde strip trailing zeros Key: KAFKA-9667 URL: https://issues.apache.org/jira/browse/KAFKA-9667 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-9416) Streams get stuck in `PENDING_SHUTDOWN` is underlying topics deleted.

Andy Coates created KAFKA-9416: -- Summary: Streams get stuck in `PENDING_SHUTDOWN` is underlying topics deleted. Key: KAFKA-9416 URL: https://issues.apache.org/jira/browse/KAFKA-9416 Project: Kafka

[jira] [Created] (KAFKA-8454) Add Java AdminClient interface

Andy Coates created KAFKA-8454: -- Summary: Add Java AdminClient interface Key: KAFKA-8454 URL: https://issues.apache.org/jira/browse/KAFKA-8454 Project: Kafka Issue Type: Bug

[jira] [Resolved] (KAFKA-7069) AclCommand does not allow 'create' operation on 'topic'

[ https://issues.apache.org/jira/browse/KAFKA-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Coates resolved KAFKA-7069. Resolution: Invalid > AclCommand does not allow 'create' operation on 'topic' >

[jira] [Created] (KAFKA-7069) AclCommand does not allow 'create' operation on 'topic'

Andy Coates created KAFKA-7069: -- Summary: AclCommand does not allow 'create' operation on 'topic' Key: KAFKA-7069 URL: https://issues.apache.org/jira/browse/KAFKA-7069 Project: Kafka Issue

[jira] [Resolved] (KAFKA-7008) Consider replacing the Resource field in AclBinding with a ResourceFilter or ResourceMatcher

[ https://issues.apache.org/jira/browse/KAFKA-7008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Coates resolved KAFKA-7008. Resolution: Won't Fix > Consider replacing the Resource field in AclBinding with a ResourceFilter

[jira] [Created] (KAFKA-7011) Investigate if its possible to drop the ResourceNameType field from Java Resource class.

Andy Coates created KAFKA-7011: -- Summary: Investigate if its possible to drop the ResourceNameType field from Java Resource class. Key: KAFKA-7011 URL: https://issues.apache.org/jira/browse/KAFKA-7011

[jira] [Created] (KAFKA-7010) Rename ResourceNameType.ANY to MATCH

Andy Coates created KAFKA-7010: -- Summary: Rename ResourceNameType.ANY to MATCH Key: KAFKA-7010 URL: https://issues.apache.org/jira/browse/KAFKA-7010 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-7008) Consider replacing the Resource field in AclBinding with a ResourceFilter or ResourceMatcher.

Andy Coates created KAFKA-7008: -- Summary: Consider replacing the Resource field in AclBinding with a ResourceFilter or ResourceMatcher. Key: KAFKA-7008 URL: https://issues.apache.org/jira/browse/KAFKA-7008

[jira] [Created] (KAFKA-7007) All ACL changes should use single /kafka-acl-changes path

Andy Coates created KAFKA-7007: -- Summary: All ACL changes should use single /kafka-acl-changes path Key: KAFKA-7007 URL: https://issues.apache.org/jira/browse/KAFKA-7007 Project: Kafka Issue

[jira] [Created] (KAFKA-7006) Remove duplicate Scala ResourceNameType class.

Andy Coates created KAFKA-7006: -- Summary: Remove duplicate Scala ResourceNameType class. Key: KAFKA-7006 URL: https://issues.apache.org/jira/browse/KAFKA-7006 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-7005) Remove duplicate Java Resource class.

Andy Coates created KAFKA-7005: -- Summary: Remove duplicate Java Resource class. Key: KAFKA-7005 URL: https://issues.apache.org/jira/browse/KAFKA-7005 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-6849) Add transformValues() method to KTable

Andy Coates created KAFKA-6849: -- Summary: Add transformValues() method to KTable Key: KAFKA-6849 URL: https://issues.apache.org/jira/browse/KAFKA-6849 Project: Kafka Issue Type: Improvement

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

Andy Coates created KAFKA-6727: -- Summary: org.apache.kafka.clients.admin.Config has broken equals and hashCode method. Key: KAFKA-6727 URL: https://issues.apache.org/jira/browse/KAFKA-6727 Project:

[jira] [Updated] (KAFKA-5246) Remove backdoor that allows any client to produce to internal topics

[ https://issues.apache.org/jira/browse/KAFKA-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Coates updated KAFKA-5246: --- Resolution: Won't Fix Status: Resolved (was: Patch Available) Discussions on PR mean we're

[jira] [Updated] (KAFKA-5246) Remove backdoor that allows any client to produce to internal topics

[ https://issues.apache.org/jira/browse/KAFKA-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Coates updated KAFKA-5246: --- Status: Patch Available (was: Open) > Remove backdoor that allows any client to produce to internal

[jira] [Assigned] (KAFKA-5246) Remove backdoor that allows any client to produce to internal topics

[ https://issues.apache.org/jira/browse/KAFKA-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Coates reassigned KAFKA-5246: -- Assignee: Andy Coates > Remove backdoor that allows any client to produce to internal topics

[jira] [Commented] (KAFKA-5246) Remove backdoor that allows any client to produce to internal topics

[ https://issues.apache.org/jira/browse/KAFKA-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010948#comment-16010948 ] Andy Coates commented on KAFKA-5246: I've got a patch waiting for this is someone can assign this Jira

[jira] [Created] (KAFKA-5246) Remove backdoor that allows any client to produce to internal topics

Andy Coates created KAFKA-5246: -- Summary: Remove backdoor that allows any client to produce to internal topics Key: KAFKA-5246 URL: https://issues.apache.org/jira/browse/KAFKA-5246 Project: Kafka

[jira] [Commented] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15522746#comment-15522746 ] Andy Coates commented on KAFKA-3919: Thanks [~ijuma]. Given that the problems I'm experiencing are

[jira] [Commented] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15522583#comment-15522583 ] Andy Coates commented on KAFKA-3919: We experienced a similar incident again recently. This time the

[jira] [Commented] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372565#comment-15372565 ] Andy Coates commented on KAFKA-3919: [~junrao] Good stuff. Look forward to hearing from you and

[jira] [Commented] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367489#comment-15367489 ] Andy Coates commented on KAFKA-3919: [~junrao] Yes, we lost a good number of brokers in a power

[jira] [Commented] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15364141#comment-15364141 ] Andy Coates commented on KAFKA-3919: [~junrao] My understanding was that the offset index looks at the

[jira] [Updated] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Coates updated KAFKA-3919: --- Description: Hi All, I encountered an issue with Kafka following a power outage that saw a

[jira] [Updated] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Coates updated KAFKA-3919: --- Description: Hi All, I encountered an issue with Kafka following a power outage that saw a

[jira] [Commented] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15362604#comment-15362604 ] Andy Coates commented on KAFKA-3919: Hi [~junrao], thanks for taking the time to look at this. First

[jira] [Updated] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Coates updated KAFKA-3919: --- Description: Hi All, I encountered an issue with Kafka following a power outage that saw a

[jira] [Issue Comment Deleted] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Coates updated KAFKA-3919: --- Comment: was deleted (was: Hi [~junrao], thanks for taking the time to look at this. Note: I've

[jira] [Commented] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15358704#comment-15358704 ] Andy Coates commented on KAFKA-3919: Hi [~junrao], thanks for taking the time to look at this. Note:

[jira] [Updated] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Coates updated KAFKA-3919: --- Description: Hi All, I encountered an issue with Kafka following a power outage that saw a

[jira] [Commented] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356679#comment-15356679 ] Andy Coates commented on KAFKA-3919: [~ijuma] - duplicate submission not intentional, (Jira timed out

[jira] [Resolved] (KAFKA-3918) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Coates resolved KAFKA-3918. Resolution: Duplicate > Broker faills to start after ungraceful shutdown due to non-monotonically

[jira] [Updated] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Coates updated KAFKA-3919: --- Description: Hi All, I encountered an issue with Kafka following a power outage that saw a

[jira] [Created] (KAFKA-3918) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

Andy Coates created KAFKA-3918: -- Summary: Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs Key: KAFKA-3918 URL: https://issues.apache.org/jira/browse/KAFKA-3918

[jira] [Created] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

Andy Coates created KAFKA-3919: -- Summary: Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs Key: KAFKA-3919 URL: https://issues.apache.org/jira/browse/KAFKA-3919