Jenkins build is back to normal : kafka-trunk-jdk7 #2049

See

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

See Changes: [jason] MINOR: Support streaming decompression of fetched records for new format -- [...truncated 900.39 KB...] org.apache.kafka.streams.kstream.WindowsTest

[jira] [Commented] (KAFKA-4966) Producer throw a NullPointerException under a network environment where packet loss and error packets exist.

[ https://issues.apache.org/jira/browse/KAFKA-4966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946410#comment-15946410 ] Ismael Juma commented on KAFKA-4966: [~wangbo23], can you please post the stacktrace for the trunk

[jira] [Comment Edited] (KAFKA-4966) Producer throw a NullPointerException under a network environment where packet loss and error packets exist.

[ https://issues.apache.org/jira/browse/KAFKA-4966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946408#comment-15946408 ] Bo Wang edited comment on KAFKA-4966 at 3/29/17 2:06 AM: - Hi, Ismael Juma. I used

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

With regard to KIP-130: Form KIP-130 thread: > About subtopologies and tasks. We do have the concept of subtopologies > already in KIP-120. It's only missing and ID that allow to link a subtopology > to a task. > > IMHO, adding a simple variable to `Subtopoloy` that provide the id should be

Re: [DISCUSS] KIP 130: Expose states of active tasks to KafkaStreams public API

Thanks for updating the KIP! I think it's good as is -- I would not add anything more to TaskMetadata. About subtopologies and tasks. We do have the concept of subtopologies already in KIP-120. It's only missing and ID that allow to link a subtopology to a task. IMHO, adding a simple variable

[jira] [Commented] (KAFKA-3436) Speed up controlled shutdown.

[ https://issues.apache.org/jira/browse/KAFKA-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946392#comment-15946392 ] Stephane Maarek commented on KAFKA-3436: [~onurkaraman] I can't find the JIRA / PR regarding your

[jira] [Comment Edited] (KAFKA-3083) a soft failure in controller may leave a topic partition in an inconsistent state

[ https://issues.apache.org/jira/browse/KAFKA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946384#comment-15946384 ] Stephane Maarek edited comment on KAFKA-3083 at 3/29/17 1:42 AM: - Just hit

[jira] [Commented] (KAFKA-3083) a soft failure in controller may leave a topic partition in an inconsistent state

[ https://issues.apache.org/jira/browse/KAFKA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946384#comment-15946384 ] Stephane Maarek commented on KAFKA-3083: Just hit this issue in prod, and the only solution was to

Re: [DISCUSS] KIP-135 : Send of null key to a compacted topic should throw non-retriable error back to user

Hi, I think error messages and error codes serve different purposes. Error messages provide additional information about the error, but users should never have to match on a message to handle an error/exception. For this case, it seems like this is a fatal error so we could get away with just

[jira] [Commented] (KAFKA-4818) Implement transactional producer

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

[GitHub] kafka pull request #2756: KAFKA-4818: Implement transactional producer

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2756 KAFKA-4818: Implement transactional producer add public API for transactions - add new Producer methods to interface - add new Producer and Consumer config parameters We want to add

[jira] [Commented] (KAFKA-4574) Transient failure in ZooKeeperSecurityUpgradeTest.test_zk_security_upgrade with security_protocol = SASL_PLAINTEXT, SSL

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

[GitHub] kafka pull request #2742: KAFKA-4574: Ignore test_zk_security_upgrade until ...

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

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

See Changes: [becket.qin] Minor: Remove the accidentally checked in file which broke checkStyle. -- [...truncated 1.68 MB...]

[GitHub] kafka pull request #2738: MINOR: Support streaming decompression of fetched ...

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

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

See Changes: [ismael] KAFKA-4959; Remove controller concurrent access to non-threadsafe -- [...truncated 900.22 KB...] org.apache.kafka.streams.KafkaStreamsTest >

[jira] [Commented] (KAFKA-4970) Add a 'ProducerIdResource' to enable authorization for generating producer ids

[ https://issues.apache.org/jira/browse/KAFKA-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946333#comment-15946333 ] Apurva Mehta commented on KAFKA-4970: - cc [~junrao] [~hachikuji] -- this is based on our discussion.

[jira] [Created] (KAFKA-4970) Add a 'ProducerIdResource' to enable authorization for generating producer ids

Apurva Mehta created KAFKA-4970: --- Summary: Add a 'ProducerIdResource' to enable authorization for generating producer ids Key: KAFKA-4970 URL: https://issues.apache.org/jira/browse/KAFKA-4970 Project:

Jenkins build is back to normal : kafka-0.10.2-jdk7 #114

See

[jira] [Commented] (KAFKA-4814) ZookeeperLeaderElector not respecting zookeeper.set.acl

[ https://issues.apache.org/jira/browse/KAFKA-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946169#comment-15946169 ] Ismael Juma commented on KAFKA-4814: [~baluchicken], are you working on this JIRA? It would be good to

[jira] [Updated] (KAFKA-3866) KerberosLogin refresh time bug and other improvements

[ https://issues.apache.org/jira/browse/KAFKA-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3866: --- Fix Version/s: (was: 0.10.2.1) > KerberosLogin refresh time bug and other improvements >

[jira] [Updated] (KAFKA-4959) remove controller concurrent access to non-threadsafe NetworkClient, Selector, and SSLEngine

[ https://issues.apache.org/jira/browse/KAFKA-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4959: --- Fix Version/s: 0.10.2.1 0.11.0.0 > remove controller concurrent access to

[jira] [Updated] (KAFKA-4959) remove controller concurrent access to non-threadsafe NetworkClient, Selector, and SSLEngine

[ https://issues.apache.org/jira/browse/KAFKA-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4959: --- Resolution: Fixed Status: Resolved (was: Patch Available) > remove controller concurrent

[jira] [Commented] (KAFKA-4959) remove controller concurrent access to non-threadsafe NetworkClient, Selector, and SSLEngine

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

[GitHub] kafka pull request #2746: KAFKA-4959: remove controller concurrent access to...

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

[DISCUSS] Time for 0.10.2.1 bugfix release

Hi Team Kafka, Since the 0.10.2.0 release we've fixed 13 JIRAs, few rather critical, that are targeted for 0.10.2.1:

[jira] [Commented] (KAFKA-3992) InstanceAlreadyExistsException Error for Consumers Starting in Parallel

[ https://issues.apache.org/jira/browse/KAFKA-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946118#comment-15946118 ] Charly Molter commented on KAFKA-3992: -- This is not a contribution. While I understand this limit it

Re: [DISCUSS] KIP 130: Expose states of active tasks to KafkaStreams public API

Hi all, I've updated the KIP and the PR to reflect your suggestions. https://cwiki.apache.org/confluence/display/KAFKA/KIP+130%3A+Expose+states+of+active+tasks+to+KafkaStreams+public+API https://github.com/apache/kafka/pull/2612 Also, I've exposed property StreamThread#state as a string through

[jira] [Commented] (KAFKA-4938) Creating a connector with missing name parameter throws a NullPointerException

[ https://issues.apache.org/jira/browse/KAFKA-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946075#comment-15946075 ] Sönke Liebau commented on KAFKA-4938: - The fix for KAFKA-4930 as it is currently proposed would also

Re: [DISCUSS] KIP-134: Delay initial consumer group rebalance

I think separating leave/join makes sense. The scenario I can think of for delaying a rebalance on LeaveGroupRequest is rolling bounce of a service. But that scenario could be tricky because there may be mixture of joining and leaving. What happens if a consumer left the group right after another

[jira] [Commented] (KAFKA-4960) Invalid state store exception

[ https://issues.apache.org/jira/browse/KAFKA-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946030#comment-15946030 ] Matthias J. Sax commented on KAFKA-4960: Is it failing all the time? Or only occasionally? Do you

[jira] [Commented] (KAFKA-4963) Global Store: startup recovery process skipping processor

[ https://issues.apache.org/jira/browse/KAFKA-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945998#comment-15945998 ] Matthias J. Sax commented on KAFKA-4963: Your observation is correct and the behavior is by

[jira] [Comment Edited] (KAFKA-4930) Connect Rest API allows creating connectors with an empty name

[ https://issues.apache.org/jira/browse/KAFKA-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945987#comment-15945987 ] Sönke Liebau edited comment on KAFKA-4930 at 3/28/17 9:22 PM: -- I've created a

[jira] [Commented] (KAFKA-4930) Connect Rest API allows creating connectors with an empty name

[ https://issues.apache.org/jira/browse/KAFKA-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945987#comment-15945987 ] Sönke Liebau commented on KAFKA-4930: - I've created a PR with my approach as it currently stands. I

[jira] [Created] (KAFKA-4969) State-store workload-aware StreamsPartitionAssignor

Matthias J. Sax created KAFKA-4969: -- Summary: State-store workload-aware StreamsPartitionAssignor Key: KAFKA-4969 URL: https://issues.apache.org/jira/browse/KAFKA-4969 Project: Kafka Issue

[GitHub] kafka pull request #2755: KAFKA-4930: Added connector name validator …

GitHub user soenkeliebau opened a pull request: https://github.com/apache/kafka/pull/2755 KAFKA-4930: Added connector name validator … …to check for empty connector name and illegal characters in connector name. This also fixes KAFKA-4938 by removing the check for slashes in

[jira] [Commented] (KAFKA-4930) Connect Rest API allows creating connectors with an empty name

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

Re: [DISCUSS] KIP-134: Delay initial consumer group rebalance

Hey Damian, Thanks for the KIP. I think the proposal makes sense as a workaround maybe for some advanced users. However, I'm not sure we can depend on average users knowing that the config exists, much less setting it to something that makes sense. It's kind of a trend in streams that I'm not too

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

See Changes: [becket.qin] KAFKA-4586; Add purgeDataBefore() API (KIP-107) -- [...truncated 330.82 KB...] kafka.admin.AdminRackAwareTest >

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

See Changes: [becket.qin] KAFKA-4586; Add purgeDataBefore() API (KIP-107) -- [...truncated 162.30 KB...] kafka.admin.AdminRackAwareTest >

Re: [DISCUSS] KIP-134: Delay initial consumer group rebalance

I think it makes sense to reset the timer when group changes. This allows broker to possibly wait longer if more consumers are restarted in parallel. For example, user may start a large number of consumers in sequence using script. The time for all consumers to send JoinGroupRequest will likely be

Re: [VOTE] KIP-81: Bound Fetch memory usage in the consumer

1) Makes sense. 2) Makes sense. Thanks! On Tue, Mar 28, 2017 at 10:11 AM, Mickael Maison wrote: > Hi Guozhang, > > Thanks for the feedback. > > 1) By MemoryPool, I mean the implementation added in KIP-72. That will > most likely be SimpleMemoryPool, but the PR for

[jira] [Commented] (KAFKA-4755) SimpleBenchmark consume test fails for streams

[ https://issues.apache.org/jira/browse/KAFKA-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945604#comment-15945604 ] Eno Thereska commented on KAFKA-4755: - So the second test is actually a different failure. The first

[jira] [Commented] (KAFKA-4968) The NetworkClient should rate-limit its log messages about protocol downgrades

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

[GitHub] kafka pull request #2754: KAFKA-4968. The NetworkClient should rate-limit it...

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/2754 KAFKA-4968. The NetworkClient should rate-limit its log messages abou… …t protocol downgrades You can merge this pull request into a Git repository by running: $ git pull

[jira] [Updated] (KAFKA-4755) SimpleBenchmark consume test fails for streams

[ https://issues.apache.org/jira/browse/KAFKA-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Hoover updated KAFKA-4755: Priority: Blocker (was: Major) > SimpleBenchmark consume test fails for streams >

[jira] [Created] (KAFKA-4968) The NetworkClient should rate-limit its log messages about protocol downgrades

Colin P. McCabe created KAFKA-4968: -- Summary: The NetworkClient should rate-limit its log messages about protocol downgrades Key: KAFKA-4968 URL: https://issues.apache.org/jira/browse/KAFKA-4968

Re: [VOTE] KIP-81: Bound Fetch memory usage in the consumer

Hi Guozhang, Thanks for the feedback. 1) By MemoryPool, I mean the implementation added in KIP-72. That will most likely be SimpleMemoryPool, but the PR for KIP-72 has not been merged yet. I've updated the KIP to make it more obvious. 2) I was thinking to pass in the priority when creating the

[jira] [Commented] (KAFKA-4586) Add purgeDataBefore() API in AdminClient

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

[GitHub] kafka pull request #2476: KAFKA-4586; Add purgeDataBefore() API (KIP-107)

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2476 --- 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] [Reopened] (KAFKA-4755) SimpleBenchmark consume test fails for streams

[ https://issues.apache.org/jira/browse/KAFKA-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Hoover reopened KAFKA-4755: - Happened again. Logs here:

[jira] [Commented] (KAFKA-4689) OffsetValidationTest fails validation with "Current position greater than the total number of consumed records"

[ https://issues.apache.org/jira/browse/KAFKA-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945543#comment-15945543 ] Roger Hoover commented on KAFKA-4689: - Happened again. Logs here

Re: [DISCUSS] KIP-134: Delay initial consumer group rebalance

@Ismael - yeah sure we can reduce the default, though i'm not sure what the "right" default would be. On Tue, 28 Mar 2017 at 15:40 Ismael Juma wrote: > Is 3 seconds the right default if the timer gets reset after each consumer > joins? Maybe we can lower the default value

LDAP with Kafka?

Hello everyone. I'm a bit confused on LDAP auth status. Documentation says "AFAICT there is no SASL mechanism covering LDAP (and the Java SASL library doesn't support it, at any rate". The Java library linked documentation though, seems to indicate the opposite. Can anyone clarify this

Re: [DISCUSS] KIP-134: Delay initial consumer group rebalance

Is 3 seconds the right default if the timer gets reset after each consumer joins? Maybe we can lower the default value given the new approach. Ismael On Tue, Mar 28, 2017 at 9:53 AM, Damian Guy wrote: > All, > I'd like to get this back to the original discussion about

Re: [DISCUSS] KIP-134: Delay initial consumer group rebalance

I don't understand, why you want to split join/leave into two parts... But it up to you I guess. +1 for broker config plus "retriggering" delay -Matthias On 3/28/17 1:53 AM, Damian Guy wrote: > All, > I'd like to get this back to the original discussion about Delaying initial > consumer group

[jira] [Commented] (KAFKA-4955) Add network handler thread utilization to request quota calculation

[ https://issues.apache.org/jira/browse/KAFKA-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945223#comment-15945223 ] Rajini Sivaram commented on KAFKA-4955: --- Have included this is in the KAFKA-4954 PR

[jira] [Created] (KAFKA-4967) java.io.EOFException Error while committing offsets

Upendra Yadav created KAFKA-4967: Summary: java.io.EOFException Error while committing offsets Key: KAFKA-4967 URL: https://issues.apache.org/jira/browse/KAFKA-4967 Project: Kafka Issue

[jira] [Commented] (KAFKA-3039) Temporary loss of leader resulted in log being completely truncated

[ https://issues.apache.org/jira/browse/KAFKA-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945156#comment-15945156 ] Ralph Weires commented on KAFKA-3039: - Experienced the same problem on v0.10.2.0, during update of

[jira] [Updated] (KAFKA-4882) Remove internal converter configuration from example property files

[ https://issues.apache.org/jira/browse/KAFKA-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mitch Seymour updated KAFKA-4882: - Fix Version/s: 0.10.2.1 > Remove internal converter configuration from example property files >

[jira] [Commented] (KAFKA-3123) Follower Broker cannot start if offsets are already out of range

[ https://issues.apache.org/jira/browse/KAFKA-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945105#comment-15945105 ] Mickael Maison commented on KAFKA-3123: --- We're running 0.10.0.1. I've added a comment in the PR with

[jira] [Commented] (KAFKA-3123) Follower Broker cannot start if offsets are already out of range

[ https://issues.apache.org/jira/browse/KAFKA-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945094#comment-15945094 ] Ismael Juma commented on KAFKA-3123: [~mimaison], thanks for the comment. Can you share the broker

[jira] [Commented] (KAFKA-4460) Consumer stops getting messages when partition leader dies

[ https://issues.apache.org/jira/browse/KAFKA-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945085#comment-15945085 ] Ismael Juma commented on KAFKA-4460: Hi, would it be possible for you to test a newer version (0.10.2

[jira] [Updated] (KAFKA-4873) Investigate issues uncovered by CORDS

[ https://issues.apache.org/jira/browse/KAFKA-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4873: --- Description: "CORDS is a fault-injection system consisting of errfs, a FUSE file system, and

[jira] [Updated] (KAFKA-4960) Invalid state store exception

[ https://issues.apache.org/jira/browse/KAFKA-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] j yeargers updated KAFKA-4960: -- Attachment: text.html This is essentially all the app does: ObjectMapper objectMapper = new

[jira] [Commented] (KAFKA-4966) Producer throw a NullPointerException under a network environment where packet loss and error packets exist.

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

[GitHub] kafka pull request #2753: KAFKA-4966：Producer throw a NullPointerException...

GitHub user Aegeaner opened a pull request: https://github.com/apache/kafka/pull/2753 KAFKA-4966：Producer throw a NullPointerException under a network environment where packet loss and error packets exist. fix KAFKA-4966 NPE in sender complete batch You can merge this pull

[GitHub] kafka pull request #2752: Using English characters to prevent garbled charac...

GitHub user tyronecai opened a pull request: https://github.com/apache/kafka/pull/2752 Using English characters to prevent garbled characters to fix garbled characters Stream as Table: A stream can be considered a changelog of a table, where each data record in the

[jira] [Assigned] (KAFKA-3758) KStream job fails to recover after Kafka broker stopped

[ https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reassigned KAFKA-3758: --- Assignee: Eno Thereska (was: Guozhang Wang) > KStream job fails to recover after Kafka

[jira] [Commented] (KAFKA-4966) Producer throw a NullPointerException under a network environment where packet loss and error packets exist.

[ https://issues.apache.org/jira/browse/KAFKA-4966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15944879#comment-15944879 ] Ismael Juma commented on KAFKA-4966: Thanks for the report. Can you specify the Kafka Producer version

[GitHub] kafka pull request #2751: Document ordering contract of iterator for window ...

GitHub user miguno opened a pull request: https://github.com/apache/kafka/pull/2751 Document ordering contract of iterator for window stores and session stores You can merge this pull request into a Git repository by running: $ git pull https://github.com/miguno/kafka

[jira] [Updated] (KAFKA-4966) Producer throw a NullPointerException under a network environment where packet loss and error packets exist.

[ https://issues.apache.org/jira/browse/KAFKA-4966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Wang updated KAFKA-4966: --- Summary: Producer throw a NullPointerException under a network environment where packet loss and error

[jira] [Created] (KAFKA-4966) Producer maybe throw a NullPointerException under a network environment where packet loss and error packets exist.

Bo Wang created KAFKA-4966: -- Summary: Producer maybe throw a NullPointerException under a network environment where packet loss and error packets exist. Key: KAFKA-4966 URL:

Re: [DISCUSS] KIP-134: Delay initial consumer group rebalance

All, I'd like to get this back to the original discussion about Delaying initial consumer group rebalance. I think i'm leaning towards sticking with the broker config and changing the delay so that the timer starts again when a new consumer joins the group. What are peoples thoughts on that?

Re: [DISCUSS] KIP-134: Delay initial consumer group rebalance

Matthias, Yes i know. Thanks, Damian On Mon, 27 Mar 2017 at 18:17 Matthias J. Sax wrote: > Damian, > > about "rebalance immediately" on timeout -- I guess, that's a different > case as no LeaveGroupRequest will be sent. Thus, the broker should be > able to distinguish

[jira] [Commented] (KAFKA-4965) set internal.leave.group.on.close to false in KafkaStreams

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

[GitHub] kafka pull request #2750: KAFKA-4965: set internal.leave.group.on.close to f...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2750 KAFKA-4965: set internal.leave.group.on.close to false in StreamsConfig Set the internal consumer config internal.leave.group.on.close in `StreamsConfig`. This is to reduce the number of rebalances we

[jira] [Updated] (KAFKA-4965) set internal.leave.group.on.close to false in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-4965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4965: -- Summary: set internal.leave.group.on.close to false in KafkaStreams (was: set leave.group.on.close to

[jira] [Work started] (KAFKA-4965) set leave.group.on.close to false in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-4965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4965 started by Damian Guy. - > set leave.group.on.close to false in KafkaStreams >

[jira] [Created] (KAFKA-4965) set leave.group.on.close to false in KafkaStreams

Damian Guy created KAFKA-4965: - Summary: set leave.group.on.close to false in KafkaStreams Key: KAFKA-4965 URL: https://issues.apache.org/jira/browse/KAFKA-4965 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-4964) Delete the kafka to prefix the name of the keystore and truststore file will be more suitable

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

[GitHub] kafka pull request #2749: [KAFKA-4964]Delete the kafka to prefix the name of...

GitHub user zhengsg opened a pull request: https://github.com/apache/kafka/pull/2749 [KAFKA-4964]Delete the kafka to prefix the name of the keystore and truststore file will be more suitable [https://issues.apache.org/jira/browse/KAFKA-4964](url) Kafka to prefix the name of the

[GitHub] kafka pull request #2748: MINOR: remove misleading scala setter in Controlle...

GitHub user onurkaraman opened a pull request: https://github.com/apache/kafka/pull/2748 MINOR: remove misleading scala setter in ControllerContext You can merge this pull request into a Git repository by running: $ git pull https://github.com/onurkaraman/kafka

[jira] [Created] (KAFKA-4964) Delete the kafka to prefix the name of the keystore and truststore file will be more suitable

shuguo zheng created KAFKA-4964: --- Summary: Delete the kafka to prefix the name of the keystore and truststore file will be more suitable Key: KAFKA-4964 URL: https://issues.apache.org/jira/browse/KAFKA-4964

[jira] [Created] (KAFKA-4963) Global Store: startup recovery process skipping processor

Yennick Trevels created KAFKA-4963: -- Summary: Global Store: startup recovery process skipping processor Key: KAFKA-4963 URL: https://issues.apache.org/jira/browse/KAFKA-4963 Project: Kafka

Re: [DISCUSS] KIP-135 : Send of null key to a compacted topic should throw non-retriable error back to user

I think, it's OK to do this right now. The other KIP will have a wider base to cover as it will include other exceptions as well and will take time. Thanks, Mayuresh On Mon, Mar 27, 2017 at 11:20 PM Dong Lin wrote: > Sorry, I forget that you have mentioned this idea in

Re: [DISCUSS] KIP-135 : Send of null key to a compacted topic should throw non-retriable error back to user

Sorry, I forget that you have mentioned this idea in your previous reply. I guess the question is, do we still need this KIP if we can have custom error message specified in the exception via the other KIP? On Mon, Mar 27, 2017 at 11:00 PM, Mayuresh Gharat < gharatmayures...@gmail.com> wrote: >

Re: [DISCUSS] KIP-135 : Send of null key to a compacted topic should throw non-retriable error back to user

Hi Dong, I do agree with that as I said before the thought did cross my mind and I am working on getting another KIP ready to have error responses returned back to the client. In my opinion, it's OK to add a new error code if it justifies the need. As Ismael, mentioned on the jira, we need a