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

See Changes: [jason] KAFKA-4483; Fix NPE in `Log` constructor if log level is INFO or finer -- [...truncated 14392 lines...] org.apache.kafka.streams.StreamsConfigTest > shouldSupportPrefixedPr

[GitHub] kafka pull request #2207: KAFKA-4483; Fix NPE in `Log` constructor if log le...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2207 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Updated] (KAFKA-4483) NPE in `Log` constructor if log level is INFO or finer

[ https://issues.apache.org/jira/browse/KAFKA-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-4483: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull requ

[jira] [Commented] (KAFKA-4483) NPE in `Log` constructor if log level is INFO or finer

[ https://issues.apache.org/jira/browse/KAFKA-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15717341#comment-15717341 ] ASF GitHub Bot commented on KAFKA-4483: --- Github user asfgit closed the pull request

[jira] [Commented] (KAFKA-4485) Follower should be in the isr if its FetchRequest has fetched up to the logEndOffset of leader

[ https://issues.apache.org/jira/browse/KAFKA-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15717277#comment-15717277 ] ASF GitHub Bot commented on KAFKA-4485: --- GitHub user lindong28 opened a pull request

[GitHub] kafka pull request #2208: KAFKA-4485; Follower should be in the isr if its F...

GitHub user lindong28 opened a pull request: https://github.com/apache/kafka/pull/2208 KAFKA-4485; Follower should be in the isr if its FetchRequest has fetched up to the logEndOffset of leader You can merge this pull request into a Git repository by running: $ git pull https

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

See Changes: [wangguoz] MINOR: Improvements in group metadata cleanup and test coverage -- [...truncated 14234 lines...] org.apache.kafka.streams.processor.TopologyBuilderTest > shouldNotAllow

[jira] [Updated] (KAFKA-4485) Follower should be in the isr if its FetchRequest has fetched up to the logEndOffset of leader

[ https://issues.apache.org/jira/browse/KAFKA-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4485: Description: As of current implementation, we will exclude follower from ISR if the begin offset of FetchRe

[jira] [Created] (KAFKA-4487) Tests should be run in Jenkins with INFO or DEBUG level

Ismael Juma created KAFKA-4487: -- Summary: Tests should be run in Jenkins with INFO or DEBUG level Key: KAFKA-4487 URL: https://issues.apache.org/jira/browse/KAFKA-4487 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-4483) NPE in `Log` constructor if log level is INFO or finer

[ https://issues.apache.org/jira/browse/KAFKA-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15717163#comment-15717163 ] Ismael Juma commented on KAFKA-4483: I updated the title to describe the problem bette

[jira] [Commented] (KAFKA-4483) NPE in `Log` constructor if log level is INFO or finer

[ https://issues.apache.org/jira/browse/KAFKA-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15717161#comment-15717161 ] Ismael Juma commented on KAFKA-4483: I updated the title to describe the problem bette

[jira] [Updated] (KAFKA-4483) NPE in `Log` constructor if log level is INFO or finer

[ https://issues.apache.org/jira/browse/KAFKA-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4483: --- Fix Version/s: 0.10.2.0 > NPE in `Log` constructor if log level is INFO or finer > ---

[jira] [Updated] (KAFKA-4483) NPE in `Log` constructor if log level is INFO or finer

[ https://issues.apache.org/jira/browse/KAFKA-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4483: --- Status: Patch Available (was: Open) > NPE in `Log` constructor if log level is INFO or finer > --

[jira] [Updated] (KAFKA-4483) NPE in `Log` constructor if log level is INFO or finer

[ https://issues.apache.org/jira/browse/KAFKA-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4483: --- Summary: NPE in `Log` constructor if log level is INFO or finer (was: Exception when creating topics)

[jira] [Commented] (KAFKA-4483) Exception when creating topics

[ https://issues.apache.org/jira/browse/KAFKA-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15717119#comment-15717119 ] ASF GitHub Bot commented on KAFKA-4483: --- GitHub user ijuma opened a pull request:

[GitHub] kafka pull request #2207: KAFKA-4483; Fix NPE in Log constructor

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2207 KAFKA-4483; Fix NPE in Log constructor You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka kafka-4483-npe-in-log-constructor Alternativel

Re: [VOTE] KIP-87 - Add Compaction Tombstone Flag

Hi Jun, Have updated. Thanks again for the feedback. Agree yes we should align up when it gets to that, I assume you’ve flagged the same in the other KIP? I think for now let’s get this KIP approved, then we can start the work to get an initial PR, then we can discuss how to align the two if n

[jira] [Assigned] (KAFKA-4483) Exception when creating topics

[ https://issues.apache.org/jira/browse/KAFKA-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-4483: -- Assignee: Ismael Juma > Exception when creating topics > -- > >

[jira] [Commented] (KAFKA-4483) Exception when creating topics

[ https://issues.apache.org/jira/browse/KAFKA-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15717079#comment-15717079 ] Ismael Juma commented on KAFKA-4483: Thanks for the report [~vahid], investigating. >

Re: [DISCUSS] KIP-82 - Add Record Headers

Hi Jun. Per Transaction Tracing / Data Lineage. As Stated in the KIP this has the first use case of how many APM tools now work. I would find it impossible for any one to argue this is not important or a niche market as it has its own gartner report for this space. Such companies as Appdynamics

[jira] [Created] (KAFKA-4486) Kafka Streams - exception in process still commits offsets

Joel Lundell created KAFKA-4486: --- Summary: Kafka Streams - exception in process still commits offsets Key: KAFKA-4486 URL: https://issues.apache.org/jira/browse/KAFKA-4486 Project: Kafka Issue

[jira] [Commented] (KAFKA-4322) StateRestoreCallback begin and end indication

[ https://issues.apache.org/jira/browse/KAFKA-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716971#comment-15716971 ] Guozhang Wang commented on KAFKA-4322: -- I think I agree that some app-specific logic

[jira] [Created] (KAFKA-4485) Follower should be in the isr if its FetchRequest has fetched up to the logEndOffset of leader

Dong Lin created KAFKA-4485: --- Summary: Follower should be in the isr if its FetchRequest has fetched up to the logEndOffset of leader Key: KAFKA-4485 URL: https://issues.apache.org/jira/browse/KAFKA-4485 Pr

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

See Changes: [wangguoz] MINOR: Improvements in group metadata cleanup and test coverage -- [...truncated 14315 lines...] org.apache.kafka.streams.kstream.KStreamBuilderTest > shouldThrowExcept

[jira] [Resolved] (KAFKA-4478) Deadlock between heartbeat executor, group metadata manager and request handler

[ https://issues.apache.org/jira/browse/KAFKA-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-4478. Resolution: Duplicate Resolving this as a duplicate. Please reopen if you think this is a mi

Re: [DISCUSS] KIP-94: Session Windows

Thanks for the KIP Damian, it looks great to me overall. A couple of minor comments: 1. findSessionsToMerge(): does this need to be a public interface? Does users ever need to call it from the processor API or even DSL? 2. SessionMerger: I am wondering if we could make it more general by renaming

[jira] [Commented] (KAFKA-4483) Exception when creating topics

[ https://issues.apache.org/jira/browse/KAFKA-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716919#comment-15716919 ] Vahid Hashemian commented on KAFKA-4483: It would be great if others can confirm t

[jira] [Updated] (KAFKA-4483) Exception when creating topics

[ https://issues.apache.org/jira/browse/KAFKA-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-4483: --- Description: The latest trunk codebase seems to expose a critical bug. Steps to reproduce on

[jira] [Commented] (KAFKA-4454) Authorizer should also include the Principal generated by the PrincipalBuilder.

[ https://issues.apache.org/jira/browse/KAFKA-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716846#comment-15716846 ] ASF GitHub Bot commented on KAFKA-4454: --- GitHub user MayureshGharat opened a pull re

[GitHub] kafka pull request #2206: KAFKA-4454 : Authorizer should also include the Pr...

GitHub user MayureshGharat opened a pull request: https://github.com/apache/kafka/pull/2206 KAFKA-4454 : Authorizer should also include the Principal generated by the PrincipalBuilder. Added support to include the Principal generated by the PrincipalBuilder in KafkaChannel You can

[jira] [Updated] (KAFKA-4484) Set more conservative default values on RocksDB for memory usage

[ https://issues.apache.org/jira/browse/KAFKA-4484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4484: - Assignee: (was: Henry Cai) > Set more conservative default values on RocksDB for memory usage

[jira] [Commented] (KAFKA-4484) Set more conservative default values on RocksDB for memory usage

[ https://issues.apache.org/jira/browse/KAFKA-4484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716836#comment-15716836 ] Guozhang Wang commented on KAFKA-4484: -- [~h...@pinterest.com] [~flyaruu] do you want

[jira] [Created] (KAFKA-4484) Set more conservative default values on RocksDB for memory usage

Guozhang Wang created KAFKA-4484: Summary: Set more conservative default values on RocksDB for memory usage Key: KAFKA-4484 URL: https://issues.apache.org/jira/browse/KAFKA-4484 Project: Kafka

[jira] [Created] (KAFKA-4483) Exception when creating topics

Vahid Hashemian created KAFKA-4483: -- Summary: Exception when creating topics Key: KAFKA-4483 URL: https://issues.apache.org/jira/browse/KAFKA-4483 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-4473) RecordCollector should handle retriable exceptions more strictly

[ https://issues.apache.org/jira/browse/KAFKA-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4473: - Labels: architecture (was: ) > RecordCollector should handle retriable exceptions more strictly >

[jira] [Updated] (KAFKA-4473) RecordCollector should handle retriable exceptions more strictly

[ https://issues.apache.org/jira/browse/KAFKA-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4473: - Summary: RecordCollector should handle retriable exceptions more strictly (was: KafkaStreams does

[jira] [Commented] (KAFKA-4473) KafkaStreams does *not* guarantee at-least-once delivery

[ https://issues.apache.org/jira/browse/KAFKA-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716796#comment-15716796 ] Guozhang Wang commented on KAFKA-4473: -- Thanks for the update [~Thomas Schulz]. I thi

[jira] [Updated] (KAFKA-4458) Add per partition metrics for in-sync and assigned replica count

[ https://issues.apache.org/jira/browse/KAFKA-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-4458: - Status: Patch Available (was: In Progress) > Add per partition metrics for in-sync and assigned r

[jira] [Updated] (KAFKA-4481) Relax Kafka Streams API type constraints

[ https://issues.apache.org/jira/browse/KAFKA-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-4481: - Status: Patch Available (was: In Progress) > Relax Kafka Streams API type constraints > -

[jira] [Work started] (KAFKA-4458) Add per partition metrics for in-sync and assigned replica count

[ https://issues.apache.org/jira/browse/KAFKA-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4458 started by Xavier Léauté. > Add per partition metrics for in-sync and assigned replica count >

[jira] [Work started] (KAFKA-4481) Relax Kafka Streams API type constraints

[ https://issues.apache.org/jira/browse/KAFKA-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4481 started by Xavier Léauté. > Relax Kafka Streams API type constraints >

[jira] [Updated] (KAFKA-4481) Relax Kafka Streams API type constraints

[ https://issues.apache.org/jira/browse/KAFKA-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-4481: - Issue Type: Bug (was: Improvement) > Relax Kafka Streams API type constraints > -

Re: [VOTE] KIP-93: Improve invalid timestamp handling in Kafka Streams

I am closing this vote now. KIP-93 is accepted with +3 (binding) +2 (non-binding) Thanks for feedback on DISCUSS thread and voting. -Matthias On 11/30/16 9:29 AM, Sriram Subramanian wrote: > +1 (binding) > > I second Ewen's point about compatibility. > > On Wed, Nov 30, 2016 at 2:53 AM, Dami

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

See Changes: [wangguoz] 2198 -- [...truncated 14238 lines...] org.apache.kafka.streams.processor.TopologyBuilderTest > shouldThroughOnUnassignedStateStoreAccess PASSED org.apache.kafka.streams

[jira] [Updated] (KAFKA-4481) Relax Kafka Streams API type constraints

[ https://issues.apache.org/jira/browse/KAFKA-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-4481: - Description: Streams API methods that apply transformations to streams are currently invariant in

Re: [DISCUSS] KIP-82 - Add Record Headers

Since this KIP affects message format, wire protocol, apis, I think it's worth spending a bit more time to nail down the concrete use cases. It would be bad if we add this feature, but when start implementing it for say mirroring, we then realize that header is not the best approach. Initially, I t

[jira] [Resolved] (KAFKA-4482) Kafka streams test failure and hang causing PR builds to fail

[ https://issues.apache.org/jira/browse/KAFKA-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-4482. Resolution: Duplicate > Kafka streams test failure and hang causing PR builds to fail >

[jira] [Commented] (KAFKA-4482) Kafka streams test failure and hang causing PR builds to fail

[ https://issues.apache.org/jira/browse/KAFKA-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716675#comment-15716675 ] Matthias J. Sax commented on KAFKA-4482: Thanks for reporting. There is already a

[jira] [Commented] (KAFKA-4482) Kafka streams test failure and hang causing PR builds to fail

[ https://issues.apache.org/jira/browse/KAFKA-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716623#comment-15716623 ] Ismael Juma commented on KAFKA-4482: There is a PR to disable these tests, but [~guozh

Re: [DISCUSS] KIP-82 - Add Record Headers

this KIP is about enabling headers, nothing more nothing less - so no, broker-side use of headers is not in the KIP scope. obviously though, once you have headers potential use cases could include broker-side header-aware interceptors (which would be the topic of other future KIPs). a trivially c

Re: [DISCUSS] KIP-97: Improved Kafka Client RPC Compatibility Policy

Colin, I just rebased KAFKA-3600's PR on trunk. KAFKA-4457 is a good idea, however it is probably doing some redundant work. AdminClient has a network client that will already have api versions info (after KAFKA-3600 goes in), so I do not think we need to send out another ApiVersions request over

[jira] [Created] (KAFKA-4482) Kafka streams test failure and hang causing PR builds to fail

Ashish K Singh created KAFKA-4482: - Summary: Kafka streams test failure and hang causing PR builds to fail Key: KAFKA-4482 URL: https://issues.apache.org/jira/browse/KAFKA-4482 Project: Kafka

Build failed in Jenkins: kafka-0.10.1-jdk7 #98

See Changes: [wangguoz] MINOR: Improvements in group metadata cleanup and test coverage -- [...truncated 5550 lines...] kafka.api.AuthorizerIntegrationTest > testPatternSubscriptionWithTopicAnd

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

See Changes: [wangguoz] 2198 -- [...truncated 14383 lines...] org.apache.kafka.streams.StreamsConfigTest > shouldSupportPrefixedPropertiesThatAreNotPartOfRestoreConsumerConfig STARTED org.apa

Re: [DISCUSS] 0.10.1.1 Plan

@Sean, There have been some discussions about KAFKA-4250, from Ismael. The main concern is on backward compatibility between 0.10.1.0 and the coming 0.10.1.1. Status Update: We are having three tasks left for 0.10.1.1, all of which have a PR under review and close to be merged. After those thre

Re: [DISCUSS] KIP-82 - Add Record Headers

Woah, I wasn't aware this is something we'll do. It wasn't in the KIP, right? I guess we could do it the same way ACLs currently work. I had in mind something that will allow admins to apply rules to the new create/delete/config topic APIs. So Todd can decide to reject "create topic" requests that

Re: [DISCUSS] KIP-82 - Add Record Headers

Daniel, Can you share specifics of how you'd use headers (the same way Todd did)? I think it may help the discussion. Thanks! On Fri, Dec 2, 2016 at 12:30 AM, Daniel Schierbeck wrote: > I don't have a lot of feedback on this, but at Zendesk we could definitely > use a standardized header system

Re: [DISCUSS] KIP-96 - Add per partition metrics for in-sync and assigned replica count

All replicas are assigned replicas. Calling it AssignedReplicasCount makes it sound like we have non-assigned replicas that we are also counting somewhere. (Guess who requested the change...) On Fri, Dec 2, 2016 at 5:25 AM, Ismael Juma wrote: > Hi Xavier, > > Can you please share the reasoning f

[jira] [Commented] (KAFKA-4481) Relax Kafka Streams API type constraints

[ https://issues.apache.org/jira/browse/KAFKA-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716152#comment-15716152 ] ASF GitHub Bot commented on KAFKA-4481: --- GitHub user xvrl opened a pull request:

[jira] [Comment Edited] (KAFKA-4454) Authorizer should also include the Principal generated by the PrincipalBuilder.

[ https://issues.apache.org/jira/browse/KAFKA-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716114#comment-15716114 ] Mayuresh Gharat edited comment on KAFKA-4454 at 12/2/16 8:13 PM: ---

[GitHub] kafka pull request #2205: KAFKA-4481: relax streams api type contraints

GitHub user xvrl opened a pull request: https://github.com/apache/kafka/pull/2205 KAFKA-4481: relax streams api type contraints Make appropriate methods contravariant in key and value types. You can merge this pull request into a Git repository by running: $ git pull https://gi

Re: [DISCUSS] KIP-98: Exactly Once Delivery and Transactional Messaging

@Henry Seems like you cannot wait for the Streams EOS KIP any more :P We do not make assumptions on the underlying state store's transaction semantics, since it may not be necessarily RocksDB as users could customize their own store engines. As I mentioned, in the worst case we will invalidate t

[jira] [Commented] (KAFKA-4481) Relax Kafka Streams API type constraints

[ https://issues.apache.org/jira/browse/KAFKA-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716140#comment-15716140 ] Xavier Léauté commented on KAFKA-4481: -- This change should be backwards-compatible an

[jira] [Created] (KAFKA-4481) Relax Kafka Streams API type constraints

Xavier Léauté created KAFKA-4481: Summary: Relax Kafka Streams API type constraints Key: KAFKA-4481 URL: https://issues.apache.org/jira/browse/KAFKA-4481 Project: Kafka Issue Type: Improvemen

Re: [DISCUSS] KIP-98: Exactly Once Delivery and Transactional Messaging

@Jay 1. Stream's applicationId is shared among all instances for the app, and is used as part of the consumer group id, while "app.id" is per producer instance. So a Streams app that has a single "applicationID" config will likely contain multiple producers each with a different appID based on the

[jira] [Comment Edited] (KAFKA-4454) Authorizer should also include the Principal generated by the PrincipalBuilder.

[ https://issues.apache.org/jira/browse/KAFKA-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716114#comment-15716114 ] Mayuresh Gharat edited comment on KAFKA-4454 at 12/2/16 8:00 PM: ---

[jira] [Commented] (KAFKA-4454) Authorizer should also include the Principal generated by the PrincipalBuilder.

[ https://issues.apache.org/jira/browse/KAFKA-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716114#comment-15716114 ] Mayuresh Gharat commented on KAFKA-4454: [~ijuma] I might not be understanding "ac

[jira] [Commented] (KAFKA-4322) StateRestoreCallback begin and end indication

[ https://issues.apache.org/jira/browse/KAFKA-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716086#comment-15716086 ] Mark Shelton commented on KAFKA-4322: - I do not at all like the idea of using the metr

[GitHub] kafka pull request #2202: MINOR: Improvements in group metadata cleanup and ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2202 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

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

See Changes: [ismael] KAFKA-2247; Merge kafka.utils.Time and kafka.common.utils.Time -- [...truncated 14223 lines...] org.apache.kafka.streams.processor.TopologyBuilderTest > shouldNotAllowNul

[jira] [Work started] (KAFKA-4456) Offsets of deleted topics are not removed from consumer groups

[ https://issues.apache.org/jira/browse/KAFKA-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4456 started by Vahid Hashemian. -- > Offsets of deleted topics are not removed from consumer groups > --

Re: [VOTE] KIP-87 - Add Compaction Tombstone Flag

Hi, Michael, For 2), this is fine. Could you update the KIP wiki to make this and other points clearer? Other than that, the KIP looks good to me. An orthogonal thing is that there are other KIPs such as KIP-98 that also intend to change the message format. If they all get approved, we should thi

[GitHub] kafka pull request #2198: HOTFIX: Forgot one transition

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2198 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

Re: [VOTE] KIP-87 - Add Compaction Tombstone Flag

Hi Michael, 5) I believe this was in the discussion thread, @Mayuresh is this something we’ve overlooked? I thought we would down convert and remove the value so the old consumer had existing behavior, or is there something we haven’t thought about? ---> Yea, we would have to down convert and remo

[jira] [Commented] (KAFKA-4473) KafkaStreams does *not* guarantee at-least-once delivery

[ https://issues.apache.org/jira/browse/KAFKA-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15715586#comment-15715586 ] Thomas Schulz commented on KAFKA-4473: -- UPDATE: I added the following config: stream

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

See Changes: [ismael] KAFKA-2247; Merge kafka.utils.Time and kafka.common.utils.Time -- [...truncated 14450 lines...] org.apache.kafka.streams.KafkaStreamsTest > shouldReturnFalseOnCloseWhenThr

[jira] [Commented] (KAFKA-4473) KafkaStreams does *not* guarantee at-least-once delivery

[ https://issues.apache.org/jira/browse/KAFKA-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15715388#comment-15715388 ] Thomas Schulz commented on KAFKA-4473: -- 1. I did not configure the retries explicitly

[jira] [Commented] (KAFKA-4473) KafkaStreams does *not* guarantee at-least-once delivery

[ https://issues.apache.org/jira/browse/KAFKA-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15715394#comment-15715394 ] Thomas Schulz commented on KAFKA-4473: -- To 1.) Even if the retries are in fact "0", t

Re: [DISCUSS] KIP-82 - Add Record Headers

"wouldn't you be in the business of making sure everyone uses them properly?" thats where a broker-side plugin would come handy - any incoming message that does not conform to org policy (read - does not have the proper headers) gets thrown out (with an error returned to user) On Thu, Dec 1, 2016

[jira] [Updated] (KAFKA-4205) NullPointerException in fetchOffsetsBefore

[ https://issues.apache.org/jira/browse/KAFKA-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-4205: - Status: Patch Available (was: Open) > NullPointerException in fetchOffsetsBefore > --

[jira] [Updated] (KAFKA-4205) NullPointerException in fetchOffsetsBefore

[ https://issues.apache.org/jira/browse/KAFKA-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-4205: - Assignee: Anton Karamanov > NullPointerException in fetchOffsetsBefore > -

[GitHub] kafka pull request #2204: KAFKA-4205; KafkaApis: fix NPE caused by conversio...

GitHub user ataraxer opened a pull request: https://github.com/apache/kafka/pull/2204 KAFKA-4205; KafkaApis: fix NPE caused by conversion to array NPE was caused by `log.logSegments.toArray` resulting in array containing `null` values. The exact reason still remains somewhat a myste

[jira] [Commented] (KAFKA-4205) NullPointerException in fetchOffsetsBefore

[ https://issues.apache.org/jira/browse/KAFKA-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15715331#comment-15715331 ] ASF GitHub Bot commented on KAFKA-4205: --- GitHub user ataraxer opened a pull request:

[jira] [Commented] (KAFKA-4322) StateRestoreCallback begin and end indication

[ https://issues.apache.org/jira/browse/KAFKA-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15715322#comment-15715322 ] Damian Guy commented on KAFKA-4322: --- My only concern with adding the extra methods is th

Re: [VOTE] KIP-84: Support SASL SCRAM mechanisms

Ismael, 1. Jun had suggested added the full list of SHA-nnn in the [DISCUSS] thread. I am ok with limiting to a smaller number if required. 3. Added a section on security considerations to the KIP. Thank you, Rajini On Thu, Dec 1, 2016 at 4:22 PM, Ismael Juma wrote: > Hi Rajini, > > Sorry fo

Re: [VOTE] KIP-84: Support SASL SCRAM mechanisms

Thanks Rajini. Let's see what Jun says about limiting the number of SHA variants. Either way, +1 from me. Ismael On Fri, Dec 2, 2016 at 2:40 PM, Rajini Sivaram wrote: > Ismael, > > 1. Jun had suggested added the full list of SHA-nnn in the [DISCUSS] > thread. I am ok with limiting to a smaller

[jira] [Created] (KAFKA-4480) kafka-configs will execute the removal of an invalid property and not report an error

Justin created KAFKA-4480: - Summary: kafka-configs will execute the removal of an invalid property and not report an error Key: KAFKA-4480 URL: https://issues.apache.org/jira/browse/KAFKA-4480 Project: Kafka

[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=15715279#comment-15715279 ] Ismael Juma commented on KAFKA-4477: Stacktraces would be useful indeed. > Node reduc

[jira] [Updated] (KAFKA-4205) NullPointerException in fetchOffsetsBefore

[ https://issues.apache.org/jira/browse/KAFKA-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4205: --- Labels: reliability (was: ) > NullPointerException in fetchOffsetsBefore > --

[jira] [Updated] (KAFKA-4205) NullPointerException in fetchOffsetsBefore

[ https://issues.apache.org/jira/browse/KAFKA-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4205: --- Fix Version/s: 0.10.1.1 > NullPointerException in fetchOffsetsBefore > ---

[jira] [Commented] (KAFKA-4205) NullPointerException in fetchOffsetsBefore

[ https://issues.apache.org/jira/browse/KAFKA-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15715235#comment-15715235 ] Ismael Juma commented on KAFKA-4205: cc [~becket_qin] [~hachikuji] > NullPointerExcep

[jira] [Comment Edited] (KAFKA-4205) NullPointerException in fetchOffsetsBefore

[ https://issues.apache.org/jira/browse/KAFKA-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15715235#comment-15715235 ] Ismael Juma edited comment on KAFKA-4205 at 12/2/16 2:16 PM: -

[jira] [Created] (KAFKA-4479) Streams tests should pass without hardcoded Time.SYSTEM in GroupCoordinator

Ismael Juma created KAFKA-4479: -- Summary: Streams tests should pass without hardcoded Time.SYSTEM in GroupCoordinator Key: KAFKA-4479 URL: https://issues.apache.org/jira/browse/KAFKA-4479 Project: Kafka

[jira] [Commented] (KAFKA-4322) StateRestoreCallback begin and end indication

[ https://issues.apache.org/jira/browse/KAFKA-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15715221#comment-15715221 ] Mark Shelton commented on KAFKA-4322: - >> "We tend not to have such callbacks" The St

[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=15715205#comment-15715205 ] Michael Andre Pearce (IG) commented on KAFKA-4477: -- What we see as per th

[jira] [Commented] (KAFKA-2247) Merge kafka.utils.Time and kafka.common.utils.Time

[ https://issues.apache.org/jira/browse/KAFKA-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15715202#comment-15715202 ] ASF GitHub Bot commented on KAFKA-2247: --- Github user asfgit closed the pull request

[jira] [Updated] (KAFKA-2247) Merge kafka.utils.Time and kafka.common.utils.Time

[ https://issues.apache.org/jira/browse/KAFKA-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2247: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 2095

[GitHub] kafka pull request #2095: KAFKA-2247: Merge kafka.utils.Time and kafka.commo...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2095 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-4205) NullPointerException in fetchOffsetsBefore

[ https://issues.apache.org/jira/browse/KAFKA-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15715179#comment-15715179 ] Alexey Ozeritskiy commented on KAFKA-4205: -- We see this on 0.10.1. ~20-30 errors

Re: [VOTE] KIP-87 - Add Compaction Tombstone Flag

*Hi Jun, Soo sorry for the typo/mistake. On 02/12/2016, 11:19, "Michael Pearce" wrote: Hi Jao Thanks for the response. Sorry for slow reply, both with personal sickness and also battling some critical issues encountered since upgrading to 0.10.1.0 1) Thans for spotting,

  1   2   >