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 >

[jira] [Commented] (KAFKA-1641) Log cleaner exits if last cleaned offset is lower than earliest offset

[ https://issues.apache.org/jira/browse/KAFKA-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15714892#comment-15714892 ] yuanjiali commented on KAFKA-1641: -- We are hitting this problem in 0.10.0.0. Log as blow: [2016-12-02

[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=15715235#comment-15715235 ] Ismael Juma commented on KAFKA-4205: cc [~becket_qin] [~hachikuji] > NullPointerException in

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

Sinóros-Szabó Péter created KAFKA-4478: -- Summary: Deadlock between heartbeat executor, group metadata manager and request handler Key: KAFKA-4478 URL: https://issues.apache.org/jira/browse/KAFKA-4478

Re: [DISCUSS] KIP-81: Max in-flight fetches

It's been a few days since the last comments. KIP-72 vote seems to have passed so if I don't get any new comments I'll start the vote on Monday. Thanks On Mon, Nov 14, 2016 at 6:25 PM, radai wrote: > +1 - there's is a need for an effective way to control kafka memory

[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

[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

[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=15715235#comment-15715235 ] Ismael Juma edited comment on KAFKA-4205 at 12/2/16 2:16 PM: - cc [~becket_qin]

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

[jira] [Updated] (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 ] Sinóros-Szabó Péter updated KAFKA-4478: --- Affects Version/s: 0.10.1.0 > Deadlock between heartbeat executor, group metadata

[jira] [Updated] (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 ] Sinóros-Szabó Péter updated KAFKA-4478: --- Labels: reliability (was: ) > Deadlock between heartbeat executor, group metadata

[jira] [Commented] (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:comment-tabpanel=15715094#comment-15715094 ] Sinóros-Szabó Péter commented on KAFKA-4478: Yes, locked threads and stack traces looks very

[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=15715202#comment-15715202 ] ASF GitHub Bot commented on KAFKA-2247: --- Github user asfgit closed the pull request at:

[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

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

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, Document error where we branched this KIP from KIP-82, will get that removed. 2) Intent is to do this just at

[jira] [Updated] (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 ] Sinóros-Szabó Péter updated KAFKA-4478: --- Description: We are running a 0.10.1.0 cluster with 3 brokers with ids 0, 1 and 2. At

[jira] [Updated] (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 ] Sinóros-Szabó Péter updated KAFKA-4478: --- Description: We are running a 0.10.1.0 cluster with 3 brokers with ids 0, 1 and 2. At

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

Hi Xavier, Can you please share the reasoning for the name change? Good to record such things for posterity. :) Ismael On Wed, Nov 30, 2016 at 9:20 PM, Xavier Léauté wrote: > FYI, Based on internal feedback I renamed AssignedReplicasCount to simply > be called

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

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

[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=15715221#comment-15715221 ] Mark Shelton commented on KAFKA-4322: - >> "We tend not to have such callbacks" The

[jira] [Updated] (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:all-tabpanel ] Ismael Juma updated KAFKA-4477: --- Labels: reliability (was: ) > Node reduces its ISR to itself, and doesn't recover. Other nodes do

[jira] [Commented] (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:comment-tabpanel=15715082#comment-15715082 ] Ismael Juma commented on KAFKA-4478: Thanks for the report. Could be related to KAFKA-4399 and/or

[jira] [Updated] (KAFKA-4472) offsetRetentionMs miscalculated in GroupCoordinator

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

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

[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] [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-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-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=15717161#comment-15717161 ] Ismael Juma commented on KAFKA-4483: I updated the title to describe the problem better. It uncovers

[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=15717163#comment-15717163 ] Ismael Juma commented on KAFKA-4483: I updated the title to describe the problem better. It uncovers

[jira] [Commented] (KAFKA-2857) ConsumerGroupCommand throws GroupCoordinatorNotAvailableException when describing a non-existent group before the offset topic is created

[ https://issues.apache.org/jira/browse/KAFKA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15714543#comment-15714543 ] ASF GitHub Bot commented on KAFKA-2857: --- Github user imandhan closed the pull request at:

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

I don't have a lot of feedback on this, but at Zendesk we could definitely use a standardized header system. Using ints as keys sounds tedious, but if that's a necessary tradeoff I'd be okay with it. On Fri, Dec 2, 2016 at 5:44 AM Todd Palino wrote: > Come on, I’ve done at

[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=15714715#comment-15714715 ] Ismael Juma commented on KAFKA-4454: Yes, I understand that we can simply add a field to

[jira] [Comment Edited] (KAFKA-4474) Poor kafka-streams throughput

[ https://issues.apache.org/jira/browse/KAFKA-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15714661#comment-15714661 ] Juan Chorro edited comment on KAFKA-4474 at 12/2/16 9:59 AM: - I have added a

[jira] [Updated] (KAFKA-4474) Poor kafka-streams throughput

[ https://issues.apache.org/jira/browse/KAFKA-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Chorro updated KAFKA-4474: --- Attachment: hctop sreenshot.png Screenshot of htop after 1 minute application running > Poor

[GitHub] kafka pull request #1548: KAFKA-2857 ConsumerGroupCommand throws GroupCoordi...

Github user imandhan closed the pull request at: https://github.com/apache/kafka/pull/1548 --- 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

[jira] [Comment Edited] (KAFKA-4474) Poor kafka-streams throughput

[ https://issues.apache.org/jira/browse/KAFKA-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15714644#comment-15714644 ] Juan Chorro edited comment on KAFKA-4474 at 12/2/16 9:51 AM: - [~enothereska]

[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=15714715#comment-15714715 ] Ismael Juma edited comment on KAFKA-4454 at 12/2/16 10:21 AM: -- Yes, I

[jira] [Created] (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.

Michael Andre Pearce (IG) created KAFKA-4477: Summary: Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted. Key: KAFKA-4477

[jira] [Commented] (KAFKA-4474) Poor kafka-streams throughput

[ https://issues.apache.org/jira/browse/KAFKA-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15714644#comment-15714644 ] Juan Chorro commented on KAFKA-4474: [~enothereska] thanks for you quick response. The application is

[jira] [Comment Edited] (KAFKA-4474) Poor kafka-streams throughput

[ https://issues.apache.org/jira/browse/KAFKA-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15714644#comment-15714644 ] Juan Chorro edited comment on KAFKA-4474 at 12/2/16 9:49 AM: - [~enothereska]

[GitHub] kafka pull request #2203: KAFKA-2857 ConsumerGroupCommand throws GroupCoordi...

GitHub user imandhan opened a pull request: https://github.com/apache/kafka/pull/2203 KAFKA-2857 ConsumerGroupCommand throws GroupCoordinatorNotAvailableEx… …ception when describing a non-existent group before the offset topic is created #1548 You can merge this pull request

[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] [Commented] (KAFKA-4483) Exception when creating topics

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

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

[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

[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] [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=15716846#comment-15716846 ] ASF GitHub Bot commented on KAFKA-4454: --- GitHub user MayureshGharat opened a pull request:

[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

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

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

[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=15717341#comment-15717341 ] ASF GitHub Bot commented on KAFKA-4483: --- Github user asfgit closed the pull request at:

[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

[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

[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=15716796#comment-15716796 ] Guozhang Wang commented on KAFKA-4473: -- Thanks for the update [~Thomas Schulz]. I think what you

[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

[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

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 >

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,

[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

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

[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

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

[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=15717119#comment-15717119 ] ASF GitHub Bot commented on KAFKA-4483: --- GitHub user ijuma opened a pull request:

[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

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

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

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

[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-4483) Exception when creating topics

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

[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=15716836#comment-15716836 ] Guozhang Wang commented on KAFKA-4484: -- [~h...@pinterest.com] [~flyaruu] do you want to consider

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 >

[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=15716971#comment-15716971 ] Guozhang Wang commented on KAFKA-4322: -- I think I agree that some app-specific logic during

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 >

[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=15715586#comment-15715586 ] Thomas Schulz commented on KAFKA-4473: -- UPDATE: I added the following config:

[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-4205) NullPointerException in fetchOffsetsBefore

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

[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

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,

[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=15715394#comment-15715394 ] Thomas Schulz commented on KAFKA-4473: -- To 1.) Even if the retries are in fact "0", then this is

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

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

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

[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=15715322#comment-15715322 ] Damian Guy commented on KAFKA-4322: --- My only concern with adding the extra methods is that it breaks

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

[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=15715388#comment-15715388 ] Thomas Schulz commented on KAFKA-4473: -- 1. I did not configure the retries explicitly, i.e.

[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

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

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

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

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 >

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

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

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

  1   2   >