[jira] [Created] (KAFKA-9354) SSL handshake failed without ssl.endpoint.identification.algorithm= and with a valid certificate

Agostino Sarubbo created KAFKA-9354: --- Summary: SSL handshake failed without ssl.endpoint.identification.algorithm= and with a valid certificate Key: KAFKA-9354 URL: https://issues.apache.org/jira/browse/KAFKA-93

[jira] [Created] (KAFKA-9355) RocksDB state metrics are removed from MBeans when EOS enabled and

Stanislav Savulchik created KAFKA-9355: -- Summary: RocksDB state metrics are removed from MBeans when EOS enabled and Key: KAFKA-9355 URL: https://issues.apache.org/jira/browse/KAFKA-9355 Project

[jira] [Created] (KAFKA-9356) Potential data loss in InMemoryWindowStore and InMemorySessionStore

Roman Leventov created KAFKA-9356: - Summary: Potential data loss in InMemoryWindowStore and InMemorySessionStore Key: KAFKA-9356 URL: https://issues.apache.org/jira/browse/KAFKA-9356 Project: Kafka

[jira] [Created] (KAFKA-9357) Error sending fetch request

Byoung joo, Lee created KAFKA-9357: -- Summary: Error sending fetch request Key: KAFKA-9357 URL: https://issues.apache.org/jira/browse/KAFKA-9357 Project: Kafka Issue Type: Bug Compo

Build failed in Jenkins: kafka-trunk-jdk11 #1047

See Changes: [github] MINOR: Add missing space in isolation-level doc (#7473) -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variab

Build failed in Jenkins: kafka-trunk-jdk8 #4128

See Changes: [github] MINOR: Add missing space in isolation-level doc (#7473) -- [...truncated 5.62 MB...] org.apache.kafka.streams.test.ConsumerRecordFactoryTest > shou

[jira] [Created] (KAFKA-9358) Explicitly resign controller leadership and broker znode

Lucas Bradstreet created KAFKA-9358: --- Summary: Explicitly resign controller leadership and broker znode Key: KAFKA-9358 URL: https://issues.apache.org/jira/browse/KAFKA-9358 Project: Kafka

[jira] [Created] (KAFKA-9359) Controller does not handle requests while broker is being shutdown

Lucas Bradstreet created KAFKA-9359: --- Summary: Controller does not handle requests while broker is being shutdown Key: KAFKA-9359 URL: https://issues.apache.org/jira/browse/KAFKA-9359 Project: Kafka

Re: [VOTE] KIP-526: Reduce Producer Metadata Lookups for Large Number of Topics

Hello all, After further discussion and improvements, I'd like to reinstate the voting process. The updated KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-526 %3A+Reduce+Producer+Metadata+Lookups+for+Large+Number+of+Topics The continued discussion: https://lists.apache.org/thread.htm

Re: [DISCUSS] KIP-526: Reduce Producer Metadata Lookups for Large Number of Topics

Hello Brain, For the newly added `metadata.evict.ms` config, since its default value is set as the same as `metadata.max.age.ms` and most users would not override default config values, would it be possible for scenarios that producer send to a specific topic once and never send again, we may end

Re: [DISCUSS] KIP-526: Reduce Producer Metadata Lookups for Large Number of Topics

Hi Guozhang, You're correct in that, with the current defined default values, it's likely we'll be more proactive in refreshing metadata for once/rarely-touched topics, which isn't ideal. It'd be at most 2x the rate, but we can certainly do better. I made the default eviction rate to mirror the cu

Re: [DISCUSS] KIP-526: Reduce Producer Metadata Lookups for Large Number of Topics

On Thu, Jan 2, 2020 at 12:42 PM Brian Byrne wrote: > Hi Guozhang, > > You're correct in that, with the current defined default values, it's > likely we'll be more proactive in refreshing metadata for > once/rarely-touched topics, which isn't ideal. It'd be at most 2x the rate, > but we can certai

Re: [DISCUSS] KIP-526: Reduce Producer Metadata Lookups for Large Number of Topics

Hi Guozhang, Only evicting due to memory pressure (or if the metadata is stale, to prevent infinitely refreshing no longer used topics when memory's not an issue) makes sense, and would be the most intuitive way of going about it. >From an implementation perspective, it's a little more difficult

Re: [DISCUSS] KIP-526: Reduce Producer Metadata Lookups for Large Number of Topics

Cool. Sounds good to me! On Thu, Jan 2, 2020 at 2:21 PM Brian Byrne wrote: > Hi Guozhang, > > Only evicting due to memory pressure (or if the metadata is stale, to > prevent infinitely refreshing no longer used topics when memory's not an > issue) makes sense, and would be the most intuitive way

[jira] [Created] (KAFKA-9360) emitting checkpoint and heartbeat set to false will not disable the activity in their SourceTask

Ning Zhang created KAFKA-9360: - Summary: emitting checkpoint and heartbeat set to false will not disable the activity in their SourceTask Key: KAFKA-9360 URL: https://issues.apache.org/jira/browse/KAFKA-9360

[jira] [Reopened] (KAFKA-9350) IllegalStateException when materializing transactional offset commits

[ https://issues.apache.org/jira/browse/KAFKA-9350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reopened KAFKA-9350: > IllegalStateException when materializing transactional offset commits > -

[jira] [Resolved] (KAFKA-9350) IllegalStateException when materializing transactional offset commits

[ https://issues.apache.org/jira/browse/KAFKA-9350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9350. Fix Version/s: 2.4.1 Resolution: Fixed > IllegalStateException when materializing tr

[jira] [Resolved] (KAFKA-8933) An unhandled SSL handshake exception in polling event - needed a retry logic

[ https://issues.apache.org/jira/browse/KAFKA-8933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-8933. Fix Version/s: 2.4.1 Resolution: Fixed > An unhandled SSL handshake exception in pol

Build failed in Jenkins: kafka-trunk-jdk11 #1048

See Changes: [github] MINOR: Remove spammy, unhelpful log message in the controller (#7879) -- [...truncated 2.79 MB...] org.apache.kafka.streams.TestTopicsTest > testR

[jira] [Created] (KAFKA-9361) Consider being restrictive on overloaded commit function with specific partition->offsets

Guozhang Wang created KAFKA-9361: Summary: Consider being restrictive on overloaded commit function with specific partition->offsets Key: KAFKA-9361 URL: https://issues.apache.org/jira/browse/KAFKA-9361

Jenkins build is back to normal : kafka-trunk-jdk8 #4129

See

[jira] [Resolved] (KAFKA-8553) Kafka Connect Schema Compatibility Checks for Name Changes

[ https://issues.apache.org/jira/browse/KAFKA-8553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjin Lee resolved KAFKA-8553. Resolution: Not A Problem In Kafka Connect, there are two kinds of 'schema's: 1. Avro schema, whic

[jira] [Resolved] (KAFKA-9357) Error sending fetch request

[ https://issues.apache.org/jira/browse/KAFKA-9357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjin Lee resolved KAFKA-9357. Resolution: Not A Problem Could you check the resource status in node 2? (For example, open sockets