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

[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

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

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 >

[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

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

[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

[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

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

[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

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

[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-jdk8 #1473

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

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

See

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

[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

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

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

[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

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

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

<    1   2