[jira] [Commented] (KAFKA-4367) MirrorMaker shuts down gracefully without actually being stopped

[ https://issues.apache.org/jira/browse/KAFKA-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650572#comment-15650572 ] Alex commented on KAFKA-4367: - No, we didn't! That was the issue! Thanks for mentioning. We had to use nohup.

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

thinking about it some more, the best way to transmit the header remapping data to consumers would be to put it in the MD response payload, so maybe it should be discussed now. On Wed, Nov 9, 2016 at 12:09 AM, radai wrote: > im not opposed to the idea of namespace

[jira] [Comment Edited] (KAFKA-4386) Producer Metrics Explanation

[ https://issues.apache.org/jira/browse/KAFKA-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650180#comment-15650180 ] Pratik kumar edited comment on KAFKA-4386 at 11/9/16 9:20 AM: -- Just for

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

@magnus - and very dangerous (youre essentially downloading and executing arbitrary code off the internet on your servers ... bad idea without a sandbox, even with) as for it being a purely administrative task - i disagree. i wish it would, really, because then my earlier point on the complexity

[GitHub] kafka pull request #2105: KAFKA-4322 StateRestoreCallback begin and end indi...

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

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

[GitHub] kafka pull request #2105: KAFKA-4322 StateRestoreCallback begin and end indi...

GitHub user markcshelton reopened a pull request: https://github.com/apache/kafka/pull/2105 KAFKA-4322 StateRestoreCallback begin and end indication This adds a begin and end callback to StateRestoreCallback. The contribution is my original work and I license the work to

Re: Use Android App as a “Producing client” for Kafka?

also, for large-enough kafka clusters (#topics, #partitions) just downloading the metadata (required by the client to know where to publish stuff to) by be a big hit on your bandwidth consumption. I would go with something like a rest-proxy (there are a few open source ones) or roll your own

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

Just following/catching up on what seems to be an active night :) @Radai sorry if it may seem obvious but what does MD stand for? My take on String vs Int: I will state first I am pro Int (16 or 32). I do though playing devils advocate see a big plus with the argument of String keys, this is

[jira] [Issue Comment Deleted] (KAFKA-4189) Consumer poll hangs forever if kafka is disabled

[ https://issues.apache.org/jira/browse/KAFKA-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Catalina-Alina Dobrica updated KAFKA-4189: -- Comment: was deleted (was: This issue also prevents the consumer's thread from

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

I think there is a piece missing in the Strings discussion, where pro-Stringers reason that by providing unique string identifiers for each header everything will just magically work for all parts of the stream pipeline. But the strings dont mean anything by themselves, and while we could

[jira] [Created] (KAFKA-4394) Processor API does not receive timestamp and/or ConsumerRecord

Mark Shelton created KAFKA-4394: --- Summary: Processor API does not receive timestamp and/or ConsumerRecord Key: KAFKA-4394 URL: https://issues.apache.org/jira/browse/KAFKA-4394 Project: Kafka

[jira] [Commented] (KAFKA-1894) Avoid long or infinite blocking in the consumer

[ https://issues.apache.org/jira/browse/KAFKA-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650814#comment-15650814 ] Catalina-Alina Dobrica commented on KAFKA-1894: --- This issue also prevents the consumer's

[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=15651070#comment-15651070 ] ASF GitHub Bot commented on KAFKA-4322: --- GitHub user markcshelton reopened a pull request:

[jira] [Commented] (KAFKA-4189) Consumer poll hangs forever if kafka is disabled

[ https://issues.apache.org/jira/browse/KAFKA-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650781#comment-15650781 ] Catalina-Alina Dobrica commented on KAFKA-4189: --- This issue also prevents the consumer's

[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=15651371#comment-15651371 ] ASF GitHub Bot commented on KAFKA-4322: --- GitHub user markcshelton reopened a pull request:

[jira] [Commented] (KAFKA-4394) Processor API does not receive timestamp and/or ConsumerRecord

[ https://issues.apache.org/jira/browse/KAFKA-4394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15651233#comment-15651233 ] Damian Guy commented on KAFKA-4394: --- The record timestamp is available via

[GitHub] kafka pull request #2105: KAFKA-4322 StateRestoreCallback begin and end indi...

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

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

[GitHub] kafka pull request #2105: KAFKA-4322 StateRestoreCallback begin and end indi...

GitHub user markcshelton reopened a pull request: https://github.com/apache/kafka/pull/2105 KAFKA-4322 StateRestoreCallback begin and end indication This adds a begin and end callback to StateRestoreCallback. The contribution is my original work and I license the work to

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

Since some of the debate has been about overhead + performance, I'm wondering if we have considered a varint encoding ( https://developers.google.com/protocol-buffers/docs/encoding#varints) for the header length field (int32 in the proposal) and for header ids? If you don't use headers, the

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

​What's the main idea behind the namespaceId? What are we segmenting? The KIP does not suggest a global registry. It does suggest segmentation via a "prefix". The proposal in the current KIP has 4 proposed sections, Kafka open source, Local, Open and Testing. Each of these is subdivided. There

[jira] [Commented] (KAFKA-1894) Avoid long or infinite blocking in the consumer

[ https://issues.apache.org/jira/browse/KAFKA-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15651799#comment-15651799 ] Shixiong Zhu commented on KAFKA-1894: - Hit the same issue in Spark Structured Streaming Kafka Source.

[jira] [Commented] (KAFKA-4391) On Windows, Kafka server stops with uncaught exception after coming back from sleep

[ https://issues.apache.org/jira/browse/KAFKA-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15651828#comment-15651828 ] Yiquan Zhou commented on KAFKA-4391: All the "Power options" settings are set to default values. In

[jira] [Comment Edited] (KAFKA-4391) On Windows, Kafka server stops with uncaught exception after coming back from sleep

[ https://issues.apache.org/jira/browse/KAFKA-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15651828#comment-15651828 ] Yiquan Zhou edited comment on KAFKA-4391 at 11/9/16 7:32 PM: - All the "Power

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

See Changes: [wangguoz] KAFKA-4360：Controller may deadLock when autoLeaderRebalance encounter [wangguoz] MINOR: fix typos and incorrect docs [wangguoz] KAFKA-4311: Multi layer cache eviction causes forwarding to incorrect

[jira] [Commented] (KAFKA-3901) KStreamTransformValues$KStreamTransformValuesProcessor#process() forwards null values

[ https://issues.apache.org/jira/browse/KAFKA-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15651775#comment-15651775 ] Guozhang Wang commented on KAFKA-3901: -- [~dminkovsky] The motivation of KAFKA-3519 is that, if user's

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

+1 Mayuresh, I think this is a good solution/strategy. Shall we update the KIP with this? Becket/Jun/Joel any comments to add before we do? On 08/11/2016, 17:29, "Mayuresh Gharat" wrote: I think the migration can be done in 2 stages : 1) In first stage the

[jira] [Updated] (KAFKA-4395) KafkaConfig and LogConfig should not have static initialization order dependencies

[ https://issues.apache.org/jira/browse/KAFKA-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4395: --- Fix Version/s: 0.10.1.1 > KafkaConfig and LogConfig should not have static initialization order >

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

I am not sure if we need the second stage. Wouldn't it be enough to say that a message is a tombstone if one of the following is true? 1. tombstone flag is set. 2. value is null. If we go to stage 2, the only difference is that we can theoretically support a null value non-tombstone message in a

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

I see the reasoning and might be inclined to agree a bit : If we go to stage 2, the only difference is that we can theoretically support a null value non-tombstone message in a log compacted topic, but I am not sure if that has any use case. But as an end goal I see that kafka should clearly

[GitHub] kafka pull request #2109: MINOR: fix incorrect logging in StreamThread

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

See Changes: [wangguoz] MINOR: remove unused fields from KTableImpl [wangguoz] MINOR: fix incorrect logging in StreamThread -- [...truncated 3875 lines...] kafka.utils.CommandLineUtilsTest >

Re: [DISCUSS] KIP 88: OffsetFetch Protocol Update

Jason, For some reason I did not receive your earlier response to the thread. I just saw it when I went to https://www.mail-archive.com/dev@kafka.apache.org/msg59608.html In the updated KIP I exposed the capability via KafkaConsumer (your first suggestion), but would be happy to look into adding

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

varint encoding was considered, but it's not as beneficial as it looks. Varints are useful when you're trying to encode numbers from a very large range. They provide some space savings, but it's not as much as people expect. Varints have a problem of checking for validity. Most varints can

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

- Transposition Within one Kafka ecosystem (a set of clusters, mirror makers, replicators, clients) header keys should be constant. There is no strong benefit for allowing header-key transposition in transit. Yes, it's doable, and maybe the only solution in some edge cases, but not worth the

Re: [DISCUSS] KIP 88: OffsetFetch Protocol Update

Hi Jason (et al.), I modified the KIP towards a change in OffsetFetch protocol, as per your suggestion. https://cwiki.apache.org/confluence/display/KAFKA/KIP-88%3A+OffsetFetch+Protocol+Update I'd appreciate it if you could take another look and share your thoughts. Thanks. --Vahid From:

[GitHub] kafka pull request #2119: MINOR: remove unused fields from KTableImpl

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2119 --- 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: [DISCUSS] KIP-82 - Add Record Headers

I think this discussion is getting a bit into the weeds on technical implementation details. I'd liek to step back a minute and try and establish where we are in the larger picture: (re-wording nacho's last paragraph) 1. are we all in agreement that headers are a worthwhile and useful addition to

Re: [DISCUSS] KIP 88: DescribeGroups Protocol Update

Hey Vahid, What I meant was that the OffsetFetch request includes an array of topic partitions, just like the TopicMetadata request. So similar to that API, we could use a null array in order to fetch all offsets for a given groupId. Then there's the matter of how to expose the capability. Adding

[jira] [Created] (KAFKA-4395) KafkaConfig and LogConfig should not have static initialization order dependencies

Sumant Tambe created KAFKA-4395: --- Summary: KafkaConfig and LogConfig should not have static initialization order dependencies Key: KAFKA-4395 URL: https://issues.apache.org/jira/browse/KAFKA-4395

[jira] [Updated] (KAFKA-4395) KafkaConfig and LogConfig should not have static initialization order dependencies

[ https://issues.apache.org/jira/browse/KAFKA-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumant Tambe updated KAFKA-4395: Affects Version/s: 0.10.0.1 > KafkaConfig and LogConfig should not have static initialization order

[GitHub] kafka pull request #2112: MINOR: fix typos and incorrect docs

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2112 --- 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-72 - Allow putting a bound on memory consumed by Incoming requests

Hi, Radai, Thanks for the KIP. Some comments below. 1. The KIP says "to facilitate faster implementation (as a safety net) the pool will be implemented in such a way that memory that was not release()ed (but still garbage collected) would be detected and "reclaimed". this is to prevent "leaks"

[GitHub] kafka-site issue #29: Update the website repo link in code.html to point to ...

Github user ijuma commented on the issue: https://github.com/apache/kafka-site/pull/29 LGTM, thanks. --- 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

[GitHub] kafka pull request #2120: KAFKA-4395: Break static initialization order depe...

GitHub user sutambe opened a pull request: https://github.com/apache/kafka/pull/2120 KAFKA-4395: Break static initialization order dependency between KafkaConfig and Logconfig Fixes static initialization order dependency between KafkaConfig and LogConfig. You can merge this pull

[jira] [Commented] (KAFKA-4395) KafkaConfig and LogConfig should not have static initialization order dependencies

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

[GitHub] kafka pull request #2051: KAFKA-4311: Multi layer cache eviction causes forw...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2051 --- 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-4311) Multi layer cache eviction causes forwarding to incorrect ProcessorNode

[ https://issues.apache.org/jira/browse/KAFKA-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4311: - Resolution: Fixed Fix Version/s: (was: 0.10.1.1) 0.10.2.0

[jira] [Commented] (KAFKA-4311) Multi layer cache eviction causes forwarding to incorrect ProcessorNode

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

[GitHub] kafka-site issue #29: Update the website repo link in code.html to point to ...

Github user becketqin commented on the issue: https://github.com/apache/kafka-site/pull/29 @ijuma Thanks for the review. Merged to the asf-site. --- 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

[GitHub] kafka-site pull request #29: Update the website repo link in code.html to po...

Github user asfgit closed the pull request at: https://github.com/apache/kafka-site/pull/29 --- 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: replica fetch error and shuabing

Which version of Kafka are you using? On Mon, Nov 7, 2016 at 10:35 AM, Json Tu wrote: > Hi, when I move __consumer_offsets from old broker to new broker, we > encounter error as follow and it always shuabing. > server.log.2016-11-07-19:[2016-11-07 19:17:15,392] ERROR Found

Re: ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted message

Hello Jun, Thanks for reporting this issue. I looked through the code and I agree the logic you found with 0.9.0.1 also exists in 0.10.0+. However, I think the process is designed intentionally like this to skip the message set that is causing such fatal error, since otherwise the thread will

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

I think it will be a good idea. +1 Thanks, Mayuresh On Wed, Nov 9, 2016 at 9:13 AM, Michael Pearce wrote: > +1 Mayuresh, I think this is a good solution/strategy. > > Shall we update the KIP with this? Becket/Jun/Joel any comments to add > before we do? > > On

[GitHub] kafka pull request #2094: KAFKA-4360：Controller may deadLock when autoLead...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2094 --- 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] [Resolved] (KAFKA-4360) Controller may deadLock when autoLeaderRebalance encounter zk expired

[ https://issues.apache.org/jira/browse/KAFKA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4360. -- Resolution: Fixed Fix Version/s: 0.10.2.0 Issue resolved by pull request 2094

[VOTE] KIP-89: Allow sink connectors to decouple flush and offset commit

Hi, I would like to initiate a vote on KIP-89 https://cwiki.apache.org/confluence/display/KAFKA/KIP-89%3A+Allow+sink+connectors+to+decouple+flush+and+offset+commit Best, Shikhar

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

Sorry for going a little in the weeds but thanks for the replies regarding varint. Agreed that a prefix and {int, int} can be the same. It doesn't look like that's what the KIP is saying the "Open" section. The example shows 211 for New Relic and 210002 for App Dynamics implying that the

[jira] [Resolved] (KAFKA-4364) Sink tasks expose secrets in DEBUG logging

[ https://issues.apache.org/jira/browse/KAFKA-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-4364. -- Resolution: Fixed Fix Version/s: 0.10.2.0 Issue resolved by pull request

[jira] [Commented] (KAFKA-4364) Sink tasks expose secrets in DEBUG logging

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

[GitHub] kafka pull request #2115: KAFKA-4364: Remove secrets from DEBUG logging

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2115 --- 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-4396) Seeing offsets not resetting even when reset policy is configured explicitly

[ https://issues.apache.org/jira/browse/KAFKA-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Miller updated KAFKA-4396: - Description: I've been seeing a curious error with kafka 0.10 (spark 2.11), these may be two

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

See Changes: [me] KAFKA-4364: Remove secrets from DEBUG logging [wangguoz] MINOR: add upgrade guide for Kafka Streams API -- [...truncated 12251 lines...]

[jira] [Commented] (KAFKA-4396) Seeing offsets not resetting even when reset policy is configured explicitly

[ https://issues.apache.org/jira/browse/KAFKA-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15652596#comment-15652596 ] huxi commented on KAFKA-4396: - I notice that you set "enable.auto.commit" to false meaning you might want to

Upgrading from kafka-0.8.1.1 to kafka-0.9.0.1

Hi, For the past 6 months,I am the dev for our solution written on top of kafka-0.8.1.1. It is in stable for us. We thought we would upgrade to kafka-0.9.0.1. With the server upgrade, we did not face any issues. We have our own solution built to extract the messages and write to different

[GitHub] kafka-site pull request #30: New meetup links and kafka summit to events pag...

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

[jira] [Updated] (KAFKA-4396) Seeing offsets not resetting even when reset policy is configured explicitly

[ https://issues.apache.org/jira/browse/KAFKA-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Miller updated KAFKA-4396: - Description: I've been seeing a curious error with kafka 0.10 (spark 2.11), these may be two

[jira] [Created] (KAFKA-4396) Seeing offsets not resetting even when reset policy is configured explicitly

Justin Miller created KAFKA-4396: Summary: Seeing offsets not resetting even when reset policy is configured explicitly Key: KAFKA-4396 URL: https://issues.apache.org/jira/browse/KAFKA-4396 Project:

[jira] [Updated] (KAFKA-4396) Seeing offsets not resetting even when reset policy is configured explicitly

[ https://issues.apache.org/jira/browse/KAFKA-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Miller updated KAFKA-4396: - Description: I've been seeing a curious error with kafka 0.10 (spark 2.11), these may be two

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

See Changes: [wangguoz] MINOR: add upgrade guide for Kafka Streams API -- [...truncated 12159 lines...] org.apache.kafka.common.security.ssl.SslFactoryTest > testClientMode STARTED

[GitHub] kafka pull request #2114: MINOR: add upgrade guide for Kafka Streams API

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

[GitHub] kafka-site pull request #30: New meetup links and kafka summit to events pag...

GitHub user derrickdoo opened a pull request: https://github.com/apache/kafka-site/pull/30 New meetup links and kafka summit to events page Added new meetup locations and a link to the Kafka Summit conference page You can merge this pull request into a Git repository by running:

[jira] [Work started] (KAFKA-4161) Decouple flush and offset commits

[ https://issues.apache.org/jira/browse/KAFKA-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4161 started by Shikhar Bhushan. -- > Decouple flush and offset commits > - > >

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

See Changes: [me] KAFKA-4364: Remove secrets from DEBUG logging -- [...truncated 14356 lines...] org.apache.kafka.streams.KafkaStreamsTest >

[jira] [Resolved] (KAFKA-4367) MirrorMaker shuts down gracefully without actually being stopped

[ https://issues.apache.org/jira/browse/KAFKA-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex resolved KAFKA-4367. - Resolution: Not A Problem Not a bug. We had to run kafka-mirror-maker.sh with nohup to completely detach the

[jira] [Issue Comment Deleted] (KAFKA-4384) ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted message

[ https://issues.apache.org/jira/browse/KAFKA-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun He updated KAFKA-4384: -- Comment: was deleted (was: Patch for KAFKA-4384 (ReplicaFetcherThread stopped after ReplicaFetcherThread

[jira] [Updated] (KAFKA-4384) ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted message

[ https://issues.apache.org/jira/browse/KAFKA-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun He updated KAFKA-4384: -- Attachment: KAFKA-4384.patch Patch for KAFKA-4384 (ReplicaFetcherThread stopped after ReplicaFetcherThread

[jira] [Updated] (KAFKA-4384) ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted message

[ https://issues.apache.org/jira/browse/KAFKA-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun He updated KAFKA-4384: -- Reviewer: Jiangjie Qin Affects Version/s: 0.10.1.0 Status: Patch Available (was:

[jira] [Commented] (KAFKA-4384) ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted message

[ https://issues.apache.org/jira/browse/KAFKA-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15653249#comment-15653249 ] Jun He commented on KAFKA-4384: --- Hi [~becket_qin], I have attached my patch including an unit test, please

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

See Changes: [wangguoz] MINOR: add upgrade guide for Kafka Streams API -- [...truncated 12292 lines...] org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest >

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

selectively reading from sockets achieves memory control (up to and not including talk of (de)compression) this is exactly what i (also, even mostly) did for kip-72 - which i hope in itself should be a reason to think about both KIPs at the same time because the changes will be similar (at least

Re: [VOTE] KIP-72 - Allow putting a bound on memory consumed by Incoming requests

Hi Jun, Thank you for taking the time to review this. 1. short version - yes, the concern is bugs, but the cost is tiny and worth it, and its a common pattern. long version: 1.1 detecting these types of bugs (leaks) cannot be easily done with simple testing, but requires stress/stability

[jira] [Resolved] (KAFKA-4328) The parameters for creating the ZkUtils object is reverse

[ https://issues.apache.org/jira/browse/KAFKA-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Wang resolved KAFKA-4328. -- Resolution: Fixed > The parameters for creating the ZkUtils object is reverse >

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

my personal opinion - a log compacted topic is basically a kv-store, so a map API. map.put(key, null) is not the same as map.remove(key), which to me means a null value should not represent a delete. a delete should be explicit (meaning flag). On Wed, Nov 9, 2016 at 11:01 AM, Mayuresh Gharat

[jira] [Commented] (KAFKA-4396) Seeing offsets not resetting even when reset policy is configured explicitly

[ https://issues.apache.org/jira/browse/KAFKA-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15653148#comment-15653148 ] Justin Miller commented on KAFKA-4396: -- Hi huxi, thanks for responding. I do have that set to false

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

im not opposed to the idea of namespace mapping. all im saying is that its not part of the "mvp" and, since it requires no wire format change, can always be added later. also, its not as simple as just configuring MM to do the transform: lets say i've implemented large message support as {666,1}

[jira] [Commented] (KAFKA-4386) Producer Metrics Explanation

[ https://issues.apache.org/jira/browse/KAFKA-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650180#comment-15650180 ] Pratik kumar commented on KAFKA-4386: - Just for clarification: Async producers use sync producers