Re: [DISCUSS] KIP 141 - ProducerRecordBuilder Interface

I understand the convenience of pointing at a JIRA/PR, but can we put the concrete changes proposed in the JIRA (under "Proposed Changes"). I don't think voting on the KIP would be reasonable otherwise since the changes under vote could change arbitrarily... I'm increasingly skeptical of adding mo

Re: [VOTE] KIP-137: Enhance TopicCommand --describe to show topics marked for deletion

+1 (binding) Thanks for helping improve the CLI tools! -Ewen On Tue, May 2, 2017 at 8:25 AM, Vahid S Hashemian wrote: > +1 (non-binding) > > Thanks Mickael. > > --Vahid > > > > > From: Ismael Juma > To: dev@kafka.apache.org > Date: 05/02/2017 03:46 AM > Subject:Re: [VOTE] KIP-

Re: [DISCUSS] KIP-137: Enhance TopicCommand --describe to show topics marked for deletion

Since everything is whitespace delimited anyway, I don't think we should worry about the compatibility issue. We don't guarantee this unstructured output format. I think it is fine to say that any parser that doesn't do something straightforward and reliable like splitting the line by whitespace th

Re: [DISCUSS] KIP-146: Classloading Isolation in Connect

On Tue, May 2, 2017 at 10:01 PM, Stephane Maarek < steph...@simplemachines.com.au> wrote: Excellent feedback, Stephane! Thanks for the work, it’s definitely needed! > I’d like to suggest to take it one step further. > > To me, I’d like to see Kafka Connect the same way we have Docker and > Docker

[jira] [Commented] (KAFKA-3754) Kafka default -Xloggc settings should include GC log rotation flags

[ https://issues.apache.org/jira/browse/KAFKA-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994280#comment-15994280 ] James Cheng commented on KAFKA-3754: FYI, I tried out this change in my cluster today.

Re: [DISCUSS] KIP-146: Classloading Isolation in Connect

Thanks for the work, it’s definitely needed! I’d like to suggest to take it one step further. To me, I’d like to see Kafka Connect the same way we have Docker and Docker repositories. Here’s how I would envision the flow: - Kafka Connect workers are just workers. They come with no jars whatsoeve

Re: [DISCUSS] KIP 145 - Expose Record Headers in Kafka Connect

Michael, Aren't JMS headers an example where the variety is a problem? Unless I'm misunderstanding, there's not even a fixed serialization format expected for them since JMS defines the runtime types, not the wire format. For example, we have JMSCorrelationID (String), JMSExpires (Long), and JMSRe

[jira] [Commented] (KAFKA-4667) Connect should create internal topics

[ https://issues.apache.org/jira/browse/KAFKA-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994268#comment-15994268 ] Ewen Cheslack-Postava commented on KAFKA-4667: -- [~rhauch] Discussed some of t

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

See Changes: [ismael] MINOR: Handle 0 futures in all() -- [...truncated 842.54 KB...] kafka.integration.SaslPlaintextTopicMetadataTest > testAutoCreateTopicWithCollision

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

See

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

See Changes: [ismael] KAFKA-5131; WriteTxnMarkers and complete commit/abort on partition [ismael] MINOR: Serialize the real isolationLevel in FetchRequest -- [...truncate

[jira] [Commented] (KAFKA-5153) KAFKA Cluster : 0.10.2.0 : Servers Getting disconnected : Service Impacting

[ https://issues.apache.org/jira/browse/KAFKA-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994197#comment-15994197 ] huxi commented on KAFKA-5153: - Could you set `replica.lag.time.max.ms`, `replica.fetch.wait.ma

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

See Changes: [ismael] KAFKA-5131; WriteTxnMarkers and complete commit/abort on partition [ismael] MINOR: Serialize the real isolationLevel in FetchRequest -- [...truncate

[GitHub] kafka pull request #2964: KAFKA-5130: Refactor TC In-memory Cache

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/2964 KAFKA-5130: Refactor TC In-memory Cache 1. Collapsed the `ownedPartitions`, `pendingTxnMap` and the `transactionMetadataCache` into a single in-memory structure, which is a two-layered map: fi

[jira] [Commented] (KAFKA-5130) Change InterBrokerSendThread to use a Queue per broker

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

[jira] [Comment Edited] (KAFKA-5155) Messages can be deleted prematurely when some producers use timestamps and some not

[ https://issues.apache.org/jira/browse/KAFKA-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994177#comment-15994177 ] huxi edited comment on KAFKA-5155 at 5/3/17 2:27 AM: - This is very sim

[jira] [Commented] (KAFKA-5155) Messages can be deleted prematurely when some producers use timestamps and some not

[ https://issues.apache.org/jira/browse/KAFKA-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994177#comment-15994177 ] huxi commented on KAFKA-5155: - This is very similar with a jira issue([kafka-4398|https://iss

[GitHub] kafka pull request #2963: Minor: Removed use of keySerde in CachingSessionSt...

GitHub user KyleWinkelman opened a pull request: https://github.com/apache/kafka/pull/2963 Minor: Removed use of keySerde in CachingSessionStore. CachingSessionStore wasn't properly using the default keySerde if no Serde was supplied. I saw the below error in the logs for one of my

[GitHub] kafka pull request #2962: Kafka5161 reassign-partitions to check if broker o...

GitHub user amethystic opened a pull request: https://github.com/apache/kafka/pull/2962 Kafka5161 reassign-partitions to check if broker of ID exists in cluster Added code to check existence of the brokers in the proposed plan. You can merge this pull request into a Git repository b

[jira] [Assigned] (KAFKA-5161) reassign-partitions to check if broker of ID exists in cluster

[ https://issues.apache.org/jira/browse/KAFKA-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxi reassigned KAFKA-5161: --- Assignee: huxi > reassign-partitions to check if broker of ID exists in cluster > ---

[GitHub] kafka pull request #2953: handle 0 futures in all()

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

See Changes: [ismael] KAFKA-5131; WriteTxnMarkers and complete commit/abort on partition -- [...truncated 846.70 KB...] kafka.integration.SaslPlaintextTopicMetadataTest >

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

See Changes: [ismael] KAFKA-5131; WriteTxnMarkers and complete commit/abort on partition -- [...truncated 849.20 KB...] kafka.server.DynamicConfigChangeTest > testDefaultC

[jira] [Updated] (KAFKA-4422) Drop support for Scala 2.10 (KIP-119)

[ https://issues.apache.org/jira/browse/KAFKA-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4422: --- Summary: Drop support for Scala 2.10 (KIP-119) (was: Drop support for Scala 2.10) > Drop support for

[jira] [Updated] (KAFKA-5131) WriteTxnMarkers and complete commit/abort on partition immigration

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

[GitHub] kafka pull request #2961: MINOR: Serialize the real isolationLevel in FetchR...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2961 --- 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-5131) WriteTxnMarkers and complete commit/abort on partition immigration

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

[GitHub] kafka pull request #2926: KAFKA-5131: WriteTxnMarkers and complete commit/ab...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2926 --- 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] [Comment Edited] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993902#comment-15993902 ] Lukas Gemela edited comment on KAFKA-5154 at 5/2/17 11:10 PM: --

[jira] [Comment Edited] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993902#comment-15993902 ] Lukas Gemela edited comment on KAFKA-5154 at 5/2/17 10:56 PM: --

[jira] [Commented] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993933#comment-15993933 ] Matthias J. Sax commented on KAFKA-5154: Thanks for the details. We will investiga

[jira] [Comment Edited] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993902#comment-15993902 ] Lukas Gemela edited comment on KAFKA-5154 at 5/2/17 10:35 PM: --

[jira] [Comment Edited] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993902#comment-15993902 ] Lukas Gemela edited comment on KAFKA-5154 at 5/2/17 10:34 PM: --

[jira] [Comment Edited] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993902#comment-15993902 ] Lukas Gemela edited comment on KAFKA-5154 at 5/2/17 10:33 PM: --

[jira] [Comment Edited] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993902#comment-15993902 ] Lukas Gemela edited comment on KAFKA-5154 at 5/2/17 10:33 PM: --

[jira] [Comment Edited] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993902#comment-15993902 ] Lukas Gemela edited comment on KAFKA-5154 at 5/2/17 10:27 PM: --

[jira] [Commented] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993902#comment-15993902 ] Lukas Gemela commented on KAFKA-5154: - Hi, we have a kafka streams app consuming from

[GitHub] kafka pull request #2961: MINOR: Serialize the real isolationLevel in FetchR...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/2961 MINOR: Serialize the real isolationLevel in FetchRequest You can merge this pull request into a Git repository by running: $ git pull https://github.com/apurvam/kafka MINOR-serialize-isolatio

Re: [VOTE] KIP-118: Drop Support for Java 7 in Kafka 0.11

Hi all, As I looked deeper into the details of the impact of this change, it became apparent to me that it may better to postpone it to a future release. Reasons follow: 1. Once we move to Java 8, there will be a ripple effect in all projects that depend on the Kafka clients jar. Given where we a

Re: [DISCUSS] KIP 151 - Expose Connector type in REST API

Both the proposal and PR look good to me. -Ewen On Tue, May 2, 2017 at 1:48 PM, dan wrote: > hello. > > in an attempt to make the connect rest endpoints more useful i'd like to > add the Connector type (Sink/Source) in our rest endpoints to make them > more self descriptive. > > KIP here: > htt

[jira] [Created] (KAFKA-5164) SetSchemaMetadata does not replace the schemas in structs correctly

Ewen Cheslack-Postava created KAFKA-5164: Summary: SetSchemaMetadata does not replace the schemas in structs correctly Key: KAFKA-5164 URL: https://issues.apache.org/jira/browse/KAFKA-5164 Pro

[DISCUSS] KIP 151 - Expose Connector type in REST API

hello. in an attempt to make the connect rest endpoints more useful i'd like to add the Connector type (Sink/Source) in our rest endpoints to make them more self descriptive. KIP here: https://cwiki.apache.org/confluence/display/KAFKA/KIP-151+Expose+Connector+type+in+REST+API initial pr: https://

[jira] [Commented] (KAFKA-4343) Connect REST API should expose whether each connector is a source or sink

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

[GitHub] kafka pull request #2960: KAFKA-4343: Expose Connector type in REST API

GitHub user norwood opened a pull request: https://github.com/apache/kafka/pull/2960 KAFKA-4343: Expose Connector type in REST API https://cwiki.apache.org/confluence/display/KAFKA/KIP-151+Expose+Connector+type+in+REST+API You can merge this pull request into a Git repository by ru

[GitHub] kafka pull request #2959: Created convenience method to create ZkUtils

GitHub user bbaugher opened a pull request: https://github.com/apache/kafka/pull/2959 Created convenience method to create ZkUtils You can merge this pull request into a Git repository by running: $ git pull https://github.com/bbaugher/kafka zkutils Alternatively you can revi

[jira] [Created] (KAFKA-5163) Support replicas movement between log directories (KIP-113)

Dong Lin created KAFKA-5163: --- Summary: Support replicas movement between log directories (KIP-113) Key: KAFKA-5163 URL: https://issues.apache.org/jira/browse/KAFKA-5163 Project: Kafka Issue Type:

[jira] [Assigned] (KAFKA-4343) Connect REST API should expose whether each connector is a source or sink

[ https://issues.apache.org/jira/browse/KAFKA-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dan norwood reassigned KAFKA-4343: -- Assignee: dan norwood > Connect REST API should expose whether each connector is a source or si

Re: [DISCUSS] KIP-136: Add Listener name and Security Protocol name to SelectorMetrics tags

Hi, Edo, Thanks for the proposal. It looks good to me. Jun On Thu, Mar 30, 2017 at 8:51 AM, Edoardo Comar wrote: > Hi all, > > We created KIP-136: Add Listener name and Security Protocol name to > SelectorMetrics tags > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 136%3A+Add+List

Re: Kafka Connect and Partitions

Hi, David. Excellent. I'm glad that you've solved the puzzle. Best regards, Randall On Tue, May 2, 2017 at 9:18 AM, wrote: > Hi Gwen/Randall, > > I think I've finally understood, more or less, how partitioning relates to > SourceRecords. > > Because I was using the SourceRecord constructor tha

Re: [DISCUSS] KIP 145 - Expose Record Headers in Kafka Connect

Hi Ewan, So on the point of JMS the predefined/standardised JMS and JMSX headers have predefined types. So these can be serialised/deserialised accordingly. Custom jms headers agreed could be a bit more difficult but on the 80/20 rule I would agree mostly they're string values and as anyhow you

[jira] [Commented] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993594#comment-15993594 ] Guozhang Wang commented on KAFKA-5154: -- I think I saw a similar issue a days ago and

[jira] [Commented] (KAFKA-5162) Add a reference to AdminClient to docs/api.html

[ https://issues.apache.org/jira/browse/KAFKA-5162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993566#comment-15993566 ] Colin P. McCabe commented on KAFKA-5162: https://github.com/apache/kafka/pull/2958

[jira] [Work started] (KAFKA-5162) Add a reference to AdminClient to docs/api.html

[ https://issues.apache.org/jira/browse/KAFKA-5162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5162 started by Colin P. McCabe. -- > Add a reference to AdminClient to docs/api.html > -

[GitHub] kafka pull request #2958: KAFKA-5162: Add a reference to AdminClient to docs...

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/2958 KAFKA-5162: Add a reference to AdminClient to docs/api.html You can merge this pull request into a Git repository by running: $ git pull https://github.com/cmccabe/kafka KAFKA-5162 Alternativ

[jira] [Commented] (KAFKA-5162) Add a reference to AdminClient to docs/api.html

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

[jira] [Created] (KAFKA-5162) Add a reference to AdminClient to docs/api.html

Colin P. McCabe created KAFKA-5162: -- Summary: Add a reference to AdminClient to docs/api.html Key: KAFKA-5162 URL: https://issues.apache.org/jira/browse/KAFKA-5162 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-136: Add Listener name and Security Protocol name to SelectorMetrics tags

Edoardo, Are you planning to do this only in the broker? Listener names only exist at the broker level. Also, clients only have a single security protocol, so maybe we should do this for brokers only. In that case, the compatibility impact is also lower because more users rely on the Yammer metric

[jira] [Created] (KAFKA-5161) reassign-partitions to check if broker of ID exists in cluster

Lawrence Weikum created KAFKA-5161: -- Summary: reassign-partitions to check if broker of ID exists in cluster Key: KAFKA-5161 URL: https://issues.apache.org/jira/browse/KAFKA-5161 Project: Kafka

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

See

[jira] [Commented] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

[ https://issues.apache.org/jira/browse/KAFKA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993467#comment-15993467 ] Michael Noll commented on KAFKA-1194: - [~guozhang]: Do you happen to know the latest s

[jira] [Updated] (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:all-tabpanel ] Rajini Sivaram updated KAFKA-4955: -- Resolution: Fixed Status: Resolved (was: Patch Available) [~junrao] Yes, thank you. T

Re: [DISCUSS] KIP-146: Classloading Isolation in Connect

Thanks for the KIP. A few responses inline, followed by additional comments. On Mon, May 1, 2017 at 9:50 PM, Konstantine Karantasis < konstant...@confluent.io> wrote: > Gwen, Randall thank you for your very insightful observations. I'm glad you > find this first draft to be an adequate platform

[jira] [Created] (KAFKA-5160) KIP-98 : broker side handling for the TxnOffsetCommitRequest

Apurva Mehta created KAFKA-5160: --- Summary: KIP-98 : broker side handling for the TxnOffsetCommitRequest Key: KAFKA-5160 URL: https://issues.apache.org/jira/browse/KAFKA-5160 Project: Kafka Iss

[jira] [Commented] (KAFKA-1313) Support adding replicas to existing topic partitions via kafka-topics tool without manually setting broker assignments

[ https://issues.apache.org/jira/browse/KAFKA-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993414#comment-15993414 ] Steven Schlansker commented on KAFKA-1313: -- I started using Kafka Streams recentl

[jira] [Commented] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993408#comment-15993408 ] Matthias J. Sax commented on KAFKA-5154: Thanks for reporting this [~Lukas Gemela]

[jira] [Updated] (KAFKA-3266) Implement KIP-140 RPCs and APIs for creating, altering, and listing ACLs

[ https://issues.apache.org/jira/browse/KAFKA-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-3266: --- Summary: Implement KIP-140 RPCs and APIs for creating, altering, and listing ACLs (was: Imple

Re: [DISCUSS] KIP 145 - Expose Record Headers in Kafka Connect

A couple of thoughts: First, agreed that we definitely want to expose header functionality. Thank you Mike for starting the conversation! Even if Connect doesn't do anything special with it, there's value in being able to access/set headers. On motivation -- I think there are much broader use cas

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

See Changes: [junrao] KAFKA-5107; remove preferred replica election state from -- [...truncated 842.45 KB...] kafka.integration.SaslPlaintextTopicMetadataTest > testAutoC

Re: [DISCUSS] KIP-145: Classloading Isolation in Connect

Thank you for your vote Colin! Unfortunately the discussion thread had to move because of a KIP-number collision. Here's a link to the active discussion thread: https://www.mail-archive.com/dev@kafka.apache.org/msg71453.html Apologies for the inconvenience. Konstantine On Mon, May 1, 2017 at 1

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

See Changes: [ismael] KAFKA-4623; Default unclean.leader.election.enabled to false (KIP-106) -- [...truncated 1.52 MB...] kafka.admin.ConfigCommandTest > shouldDeleteBrok

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

See Changes: [ismael] KAFKA-4623; Default unclean.leader.election.enabled to false (KIP-106) -- [...truncated 844.92 KB...] kafka.integration.SaslPlaintextTopicMetadataTes

RE: Kafka Connect and Partitions

Hi Gwen/Randall, I think I've finally understood, more or less, how partitioning relates to SourceRecords. Because I was using the SourceRecord constructor that doesn't provide values for key and key schema, the key is null. The DefaultPartioner appears to map null to a constant value rather

[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&focusedCommentId=15993165#comment-15993165 ] Jun Rao commented on KAFKA-4955: [~rsivaram], now that KAFKA-4954 is committed, should we

[jira] [Commented] (KAFKA-4857) Improve Client handling

[ https://issues.apache.org/jira/browse/KAFKA-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993127#comment-15993127 ] Ismael Juma commented on KAFKA-4857: There are 2 changes here. One is to use AdminClie

[jira] [Commented] (KAFKA-5107) remove preferred replica election state from ControllerContext

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

[jira] [Created] (KAFKA-5159) Update Kafka documentation to mention AdminClient

Ismael Juma created KAFKA-5159: -- Summary: Update Kafka documentation to mention AdminClient Key: KAFKA-5159 URL: https://issues.apache.org/jira/browse/KAFKA-5159 Project: Kafka Issue Type: Impro

[GitHub] kafka pull request #2927: KAFKA-5107: remove preferred replica election stat...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2927 --- 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-5107) remove preferred replica election state from ControllerContext

[ https://issues.apache.org/jira/browse/KAFKA-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-5107: --- Resolution: Fixed Fix Version/s: 0.11.0.0 Status: Resolved (was: Patch Available) Issue res

[jira] [Updated] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford updated KAFKA-4623: Issue Type: New Feature (was: Task) > Change Default unclean.leader.election.enabled from True to F

[jira] [Commented] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993120#comment-15993120 ] Ismael Juma commented on KAFKA-4623: Not sure why, but it seems like this issue cannot

[jira] [Updated] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford updated KAFKA-4623: Issue Type: Improvement (was: New Feature) > Change Default unclean.leader.election.enabled from Tr

[jira] [Updated] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford updated KAFKA-4623: Issue Type: Task (was: Improvement) > Change Default unclean.leader.election.enabled from True to F

[jira] [Assigned] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford reassigned KAFKA-4623: --- Assignee: Ben Stopford (was: Sharad) > Change Default unclean.leader.election.enabled from T

[jira] [Assigned] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-4623: -- Assignee: Sharad (was: Ben Stopford) > Change Default unclean.leader.election.enabled from Tru

[jira] [Commented] (KAFKA-5153) KAFKA Cluster : 0.10.2.0 : Servers Getting disconnected : Service Impacting

[ https://issues.apache.org/jira/browse/KAFKA-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993116#comment-15993116 ] Arpan commented on KAFKA-5153: -- Yes KAFKA-4477 was fixed by KAFKFA-3994 in 0.10.1.1 but stil

[jira] [Assigned] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford reassigned KAFKA-4623: --- Assignee: Ben Stopford (was: Sharad) > Change Default unclean.leader.election.enabled from T

[jira] [Updated] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4623: --- Issue Type: Improvement (was: Bug) > Change Default unclean.leader.election.enabled from True to Fals

[jira] [Assigned] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-4623: -- Assignee: Sharad (was: Ismael Juma) > Change Default unclean.leader.election.enabled from True

[jira] [Assigned] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-4623: -- Assignee: Ismael Juma (was: Sharad) > Change Default unclean.leader.election.enabled from True

[jira] [Commented] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

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

[GitHub] kafka pull request #2625: KAFKA-4623: Change default unclean.leader.election...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2625 --- 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-5131) WriteTxnMarkers and complete commit/abort on partition immigration

[ https://issues.apache.org/jira/browse/KAFKA-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5131: -- Status: Patch Available (was: Open) > WriteTxnMarkers and complete commit/abort on partition immigratio

Re: [VOTE] KIP-137: Enhance TopicCommand --describe to show topics marked for deletion

+1 (non-binding) Thanks Mickael. --Vahid From: Ismael Juma To: dev@kafka.apache.org Date: 05/02/2017 03:46 AM Subject:Re: [VOTE] KIP-137: Enhance TopicCommand --describe to show topics marked for deletion Sent by:isma...@gmail.com Thanks for the KIP, +1 (binding).

[jira] [Updated] (KAFKA-5132) Abort long running transactions

[ https://issues.apache.org/jira/browse/KAFKA-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5132: -- Status: Patch Available (was: Open) > Abort long running transactions > ---

[DISCUSS] KIP-148: Add a connect timeout for client

Hi all, Currently in our test environment, we found that after one of the broker node crash (reboot or os crash), the client may still be connecting to the crash node to send metadata request or other request, and it needs several minutes to be aware that the connection is timeout then try anot

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

See

[jira] [Updated] (KAFKA-4743) Add a tool to Reset Consumer Group Offsets

[ https://issues.apache.org/jira/browse/KAFKA-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4743: --- Fix Version/s: 0.11.0.0 > Add a tool to Reset Consumer Group Offsets > ---

[jira] [Commented] (KAFKA-5132) Abort long running transactions

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

[GitHub] kafka pull request #2957: KAFKA-5132: abort long running transactions

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2957 KAFKA-5132: abort long running transactions Abort any ongoing transactions that haven't been touched for longer than the transaction timeout You can merge this pull request into a Git repository by ru

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

Hi Jeyhun, This approach would change ValueMapper (...etc) to be classes, rather than interfaces, which is also a backwards incompatible change. An alternative approach that would be backwards compatible would be to define new interfaces, and provide overrides where those interfaces are used. Un

  1   2   >