[jira] [Created] (KAFKA-6482) when produce send a invalidity timestamps, broker will be not delete retention files

HongLiang created KAFKA-6482: Summary: when produce send a invalidity timestamps, broker will be not delete retention files Key: KAFKA-6482 URL: https://issues.apache.org/jira/browse/KAFKA-6482 Project: K

Re: [VOTE] KIP-227: Introduce Fetch Requests that are Incremental to Increase Partition Scalability

I'm late to the party but +1 and thanks for the KIP On Thu, Jan 25, 2018 at 12:36 AM, Ismael Juma wrote: > Agreed, Jun. > > Ismael > > On Wed, Jan 24, 2018 at 4:08 PM, Jun Rao wrote: > >> Since this is a server side metric, it's probably better to use Yammer Rate >> (which has count) for consist

Build failed in Jenkins: kafka-trunk-jdk9 #331

See Changes: [jason] KAFKA-6180; Add a Validator for NonNull configurations and remove -- [...truncated 1.84 MB...] org.apache.kafka.streams.integration.RestoreIntegration

Re: [DISCUSS] KIP 226 - Dynamic Broker Configuration

Yea, if other commands seem to follow this pattern, I'll update KIP-248 as well :). Also introducing those arguments in the current ConfigCommand also makes sense from the migration point of view too as it will be introduced in 1.1 which makes it somewhat easier for KIP-248. On Wed, Jan 24, 2018 a

[jira] [Created] (KAFKA-6483) Support ExtendedSerializer in Kafka Streams

Tamas Cserveny created KAFKA-6483: - Summary: Support ExtendedSerializer in Kafka Streams Key: KAFKA-6483 URL: https://issues.apache.org/jira/browse/KAFKA-6483 Project: Kafka Issue Type: Impro

Best practices Partition Key

Hi everyone, I´m trying to understand the best practice to define the partition key. I have defined some topics that they are related with entities in cassandra data model, the relationship is one-to-one, one entity - one topic, because I need to ensure the properly ordering in the events. I have

[jira] [Created] (KAFKA-6484) 'ConsumerGroupCommand' performance optimization for old consumer describe group

HongLiang created KAFKA-6484: Summary: 'ConsumerGroupCommand' performance optimization for old consumer describe group Key: KAFKA-6484 URL: https://issues.apache.org/jira/browse/KAFKA-6484 Project: Kafka

[jira] [Created] (KAFKA-6485) 'ConsumerGroupCommand' performance optimization for old consumer describe group

HongLiang created KAFKA-6485: Summary: 'ConsumerGroupCommand' performance optimization for old consumer describe group Key: KAFKA-6485 URL: https://issues.apache.org/jira/browse/KAFKA-6485 Project: Kafka

[jira] [Resolved] (KAFKA-4256) Use IP for ZK broker register

[ https://issues.apache.org/jira/browse/KAFKA-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4256. -- Resolution: Won't Fix Closing as per above comment. Pls reopen If the issue still exists. > Use IP for

[jira] [Resolved] (KAFKA-1475) Kafka consumer stops LeaderFinder/FetcherThreads, but application does not know

[ https://issues.apache.org/jira/browse/KAFKA-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1475. -- Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported. > Kafka consum

[jira] [Resolved] (KAFKA-1458) kafka hanging on shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1458. -- Resolution: Auto Closed {color:#00}Closing inactive issue. Please reopen if you think the issue sti

Re: [DISCUSS] Improving ACLs by allowing ip ranges and subnet expressions?

Regardless of our personal opinions about security, fact is that Kafka right now has "limit access by IP" functionality (as does MySQL for instance). And the usability of the feature is limited by the fact that you can only manage one IP at a time, while in the real-world applications normally have

[jira] [Created] (KAFKA-6486) TimeWindows causes unordered calls to windowed aggregation functions

Valentino Proietti created KAFKA-6486: - Summary: TimeWindows causes unordered calls to windowed aggregation functions Key: KAFKA-6486 URL: https://issues.apache.org/jira/browse/KAFKA-6486 Project:

[jira] [Resolved] (KAFKA-5500) it is impossible to have custom Login Modules for PLAIN SASL mechanism

[ https://issues.apache.org/jira/browse/KAFKA-5500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5500. -- Resolution: Duplicate Closing in favor of KIP-88/KAFKA-4292.  Please reopen if you think otherwise. > i

[jira] [Resolved] (KAFKA-5617) Update to the list of third-party clients

[ https://issues.apache.org/jira/browse/KAFKA-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5617. -- Resolution: Fixed > Update to the list of third-party clients >

[jira] [Resolved] (KAFKA-3408) consumer rebalance fail

[ https://issues.apache.org/jira/browse/KAFKA-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3408. -- Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported, please upgrade

[jira] [Resolved] (KAFKA-4185) Abstract out password verifier in SaslServer as an injectable dependency

[ https://issues.apache.org/jira/browse/KAFKA-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4185. -- Resolution: Duplicate Closing this in favor of KIP-86/KAFKA-4292. Please reopen if you think otherwise

[jira] [Resolved] (KAFKA-6091) Authorization API is called hundred's of times when there are no privileges

[ https://issues.apache.org/jira/browse/KAFKA-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6091. -- Resolution: Fixed Fixed via KAFKA-5547. Please reopen if you think the issue still exists > Authorizati

RE: Build failed in Jenkins: kafka-trunk-jdk9 #331

Hi, For around two weeks Jenkins is sending me Kafka Build notifications. To: dev@kafka.apache.org , ja...@confluent.io, m...@farewellutopia.com Why? And how do I stop this? Please reply directly or with CC to me, I don't want to subscribe to the list to get less mails. Cheers, Reto > -

[jira] [Resolved] (KAFKA-6429) dirtyNonActiveSegments in `cleanableOffsets` should only be created when log.cleaner.min.compaction.lag.ms > 0

[ https://issues.apache.org/jira/browse/KAFKA-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6429. Resolution: Fixed > dirtyNonActiveSegments in `cleanableOffsets` should only be created when

Expiring record(s) for topic: 30011 ms has passed since last append

Hi, I'm running an app on Kafka Streams 1.0.0, and in the past day a lot of nodes are failing and I see this in the log. These appear to be failures when attempting to update the changelog. Any ideas on what I should do to work around this? Should I configure separate retry and timeouts for the

Build failed in Jenkins: kafka-trunk-jdk7 #3116

See Changes: [jason] MINOR: Fix typo in consumer group command error (#4463) [jason] MINOR: Update consumer group command documentation with additionally -- [...truncated

Re: 1.1 KIPs

Thanks Vahid, i've updated the release plan On Wed, 24 Jan 2018 at 13:31 Vahid S Hashemian wrote: > Hi Damian, > > Could you please add KIP-229 to the list? It was approved earlier this > week > https://www.mail-archive.com/dev@kafka.apache.org/msg84851.html > > Thanks for running the release. >

[jira] [Created] (KAFKA-6487) ChangeLoggingKeyValueBytesStore.all() returns null

Bill Bejeck created KAFKA-6487: -- Summary: ChangeLoggingKeyValueBytesStore.all() returns null Key: KAFKA-6487 URL: https://issues.apache.org/jira/browse/KAFKA-6487 Project: Kafka Issue Type: Bug

Build failed in Jenkins: kafka-trunk-jdk7 #3117

See Changes: [jason] KAFKA-6429; LogCleanerManager.cleanableOffsets should create objects … -- [...truncated 404.19 KB...] kafka.api.PlaintextConsumerTest > testCommitMet

[jira] [Resolved] (KAFKA-4897) LogCleaner#cleanSegments should not ignore failures to delete files

[ https://issues.apache.org/jira/browse/KAFKA-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-4897. Resolution: Fixed > LogCleaner#cleanSegments should not ignore failures to delete files > --

[jira] [Created] (KAFKA-6488) Prevent log corruption in case of OOM

Dong Lin created KAFKA-6488: --- Summary: Prevent log corruption in case of OOM Key: KAFKA-6488 URL: https://issues.apache.org/jira/browse/KAFKA-6488 Project: Kafka Issue Type: Bug Reporte

Build failed in Jenkins: kafka-trunk-jdk9 #332

See Changes: [jason] MINOR: Fix typo in consumer group command error (#4463) [jason] MINOR: Update consumer group command documentation with additionally -- [...truncated

Re: [VOTE] KIP-227: Introduce Fetch Requests that are Incremental to Increase Partition Scalability

On Thu, Jan 25, 2018, at 02:23, Mickael Maison wrote: > I'm late to the party but +1 and thanks for the KIP Thanks > > On Thu, Jan 25, 2018 at 12:36 AM, Ismael Juma wrote: > > Agreed, Jun. > > > > Ismael > > > > On Wed, Jan 24, 2018 at 4:08 PM, Jun Rao wrote: > > > >> Since this is a server si

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

See Changes: [jason] MINOR: Fix typo in consumer group command error (#4463) [jason] MINOR: Update consumer group command documentation with additionally [jason] KAFKA-6429; LogCleanerManager.cleanableOffsets s

Re: [VOTE] KIP-232: Detect outdated metadata using leaderEpoch and partitionEpoch

On Wed, Jan 24, 2018, at 21:07, Dong Lin wrote: > Hey Colin, > > Thanks for reviewing the KIP. > > If I understand you right, you maybe suggesting that we can use a global > metadataEpoch that is incremented every time controller updates metadata. > The problem with this solution is that, if a to

Re: [VOTE] KIP-232: Detect outdated metadata using leaderEpoch and partitionEpoch

Hey Colin, Thanks for the comment. On Thu, Jan 25, 2018 at 4:15 PM, Colin McCabe wrote: > On Wed, Jan 24, 2018, at 21:07, Dong Lin wrote: > > Hey Colin, > > > > Thanks for reviewing the KIP. > > > > If I understand you right, you maybe suggesting that we can use a global > > metadataEpoch that

Jenkins build is back to normal : kafka-trunk-jdk9 #333

See

Build failed in Jenkins: kafka-trunk-jdk7 #3118

See Changes: [jason] KAFKA-4897; Add pause method to ShutdownableThread (#4393) -- [...truncated 1.87 MB...] org.apache.kafka.streams.integration.QueryableStateIntegratio

Re: [DISCUSS] KIP-250 Add Support for Quorum-based Producer Acknowledgment

Hey Litao, Not sure there will be an easy way to select the broker with highest LEO without losing acknowledged message. In case it is useful, here is another idea. Maybe we can have a mechanism to turn switch between the min.isr and isr set for determining when to acknowledge a message. Controlle

[jira] [Created] (KAFKA-6489) Fetcher.retrieveOffsetsByTimes() should add all the topics to the metadata refresh topics set.

Jiangjie Qin created KAFKA-6489: --- Summary: Fetcher.retrieveOffsetsByTimes() should add all the topics to the metadata refresh topics set. Key: KAFKA-6489 URL: https://issues.apache.org/jira/browse/KAFKA-6489

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

See Changes: [jason] KAFKA-4897; Add pause method to ShutdownableThread (#4393) -- [...truncated 1.62 MB...] org.apache.kafka.streams.integration.KTableSourceTopicRestart

Build failed in Jenkins: kafka-trunk-jdk7 #3119

See Changes: [becket.qin] KAFKA-6321; Consolidate calls to KafkaConsumer's `beginningOffsets()` -- [...truncated 405.44 KB...] kafka.zookeeper.ZooKeeperClientTest > testZ

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

See Changes: [becket.qin] KAFKA-6321; Consolidate calls to KafkaConsumer's `beginningOffsets()` -- [...truncated 1.43 MB...] org.apache.kafka.common.config.ConfigDefTest