[GitHub] kafka pull request #3123: KAFKA-4935 [WIP]: Deprecate client checksum API an...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3123 KAFKA-4935 [WIP]: Deprecate client checksum API and compute lazy partial checksum for magic v2 You can merge this pull request into a Git repository by running: $ git pull https://github.co

[jira] [Commented] (KAFKA-4935) Consider disabling record level CRC checks for message format V2

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

[jira] [Updated] (KAFKA-4935) Consider disabling record level CRC checks for message format V2

[ https://issues.apache.org/jira/browse/KAFKA-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-4935: --- Status: Patch Available (was: In Progress) > Consider disabling record level CRC checks for m

[jira] [Updated] (KAFKA-5233) Changes to punctuate semantics (KIP-138)

[ https://issues.apache.org/jira/browse/KAFKA-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Borowiecki updated KAFKA-5233: - Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Changes to punctuate sema

[jira] [Commented] (KAFKA-5243) Request to add row limit in ReadOnlyKeyValueStore range function

[ https://issues.apache.org/jira/browse/KAFKA-5243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020911#comment-16020911 ] Michal Borowiecki commented on KAFKA-5243: -- Just a note, replacing the second arg

[jira] [Commented] (KAFKA-5253) KStreamTestDriver must handle streams created with patterns

[ https://issues.apache.org/jira/browse/KAFKA-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020920#comment-16020920 ] Wim Van Leuven commented on KAFKA-5253: --- Can anybody give direction in how to improv

[jira] [Updated] (KAFKA-5310) reset ControllerContext during resignation

[ https://issues.apache.org/jira/browse/KAFKA-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5310: --- Fix Version/s: 0.11.0.0 > reset ControllerContext during resignation > ---

[jira] [Created] (KAFKA-5311) Support ExtendedDeserializer in Kafka Streams

Dale Peakall created KAFKA-5311: --- Summary: Support ExtendedDeserializer in Kafka Streams Key: KAFKA-5311 URL: https://issues.apache.org/jira/browse/KAFKA-5311 Project: Kafka Issue Type: Improve

[jira] [Commented] (KAFKA-5263) kakfa-clients consume 100% CPU with manual partition assignment when network connection is lost

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

[GitHub] kafka pull request #3124: KAFKA-5263: Avoid tight polling loop in consumer w...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/3124 KAFKA-5263: Avoid tight polling loop in consumer with no ready nodes If all brokers are unavailable, consumers using manual assignment poll in a tight loop with no channels to poll from. Produ

[GitHub] kafka pull request #3125: KAFKA-5311: Support ExtendedDeserializer in Kafka ...

GitHub user subnova opened a pull request: https://github.com/apache/kafka/pull/3125 KAFKA-5311: Support ExtendedDeserializer in Kafka Streams. The contribution is my original work and that I license the work to the project under the project's open source license. You can merge thi

[jira] [Commented] (KAFKA-5311) Support ExtendedDeserializer in Kafka Streams

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

[jira] [Updated] (KAFKA-5311) Support ExtendedDeserializer in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Peakall updated KAFKA-5311: Flags: Patch > Support ExtendedDeserializer in Kafka Streams > -

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

Guozhang, At the moment we don't have a connect timeout. And the behaviour suggested in the KIP is useful to address this. We do however have a request.timeout.ms. This is the amount of time it would take to detect a crashed broker if the broker crashed after a connection was established. Unfortu

[GitHub] kafka pull request #3126: KAFKA-5260: Producer should not send AbortTxn unle...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/3126 KAFKA-5260: Producer should not send AbortTxn unless transaction has actually begun Keep track of when a transaction has begun by setting a flag, `transactionStarted` when a successfull `AddPartitions

[jira] [Commented] (KAFKA-5260) Producer should not send AbortTxn unless transaction has actually begun

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

[jira] [Updated] (KAFKA-5260) Producer should not send AbortTxn unless transaction has actually begun

[ https://issues.apache.org/jira/browse/KAFKA-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5260: -- Status: Patch Available (was: Open) > Producer should not send AbortTxn unless transaction has actually

[jira] [Assigned] (KAFKA-5308) TC should handle UNSUPPORTED_FOR_MESSAGE_FORMAT in WriteTxnMarker response

[ https://issues.apache.org/jira/browse/KAFKA-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-5308: - Assignee: Damian Guy > TC should handle UNSUPPORTED_FOR_MESSAGE_FORMAT in WriteTxnMarker response

[jira] [Created] (KAFKA-5312) Improve exception handling for StreamsKafkaClient

Eno Thereska created KAFKA-5312: --- Summary: Improve exception handling for StreamsKafkaClient Key: KAFKA-5312 URL: https://issues.apache.org/jira/browse/KAFKA-5312 Project: Kafka Issue Type: Sub

[jira] [Created] (KAFKA-5313) Improve exception handling on coordinator interactions

Eno Thereska created KAFKA-5313: --- Summary: Improve exception handling on coordinator interactions Key: KAFKA-5313 URL: https://issues.apache.org/jira/browse/KAFKA-5313 Project: Kafka Issue Type

[jira] [Created] (KAFKA-5314) Improve exception handling for state stores

Eno Thereska created KAFKA-5314: --- Summary: Improve exception handling for state stores Key: KAFKA-5314 URL: https://issues.apache.org/jira/browse/KAFKA-5314 Project: Kafka Issue Type: Sub-task

[jira] [Resolved] (KAFKA-5312) Improve exception handling for StreamsKafkaClient

[ https://issues.apache.org/jira/browse/KAFKA-5312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska resolved KAFKA-5312. - Resolution: Duplicate > Improve exception handling for StreamsKafkaClient > --

[jira] [Assigned] (KAFKA-5156) Options for handling exceptions in streams

[ https://issues.apache.org/jira/browse/KAFKA-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reassigned KAFKA-5156: --- Assignee: Eno Thereska > Options for handling exceptions in streams > ---

Pull-Requests not worked on

Hello everyone I am wondering how pull-requests are handled for Kafka? There is currently a huge amount of PRs on Github and most of them are not getting any attention. If the maintainers only have a look at PR which passed the CI (which makes sense due to the amount), then there is a problem,

Re: [DISCUSS]: KIP-159: Introducing Rich functions to Streams

Hi Michal, Thanks for your comments. To me at least it feels strange that something is called a function yet > doesn't follow the functional interface definition of having just one > abstract method. I suppose init and close could be made default methods > with empty bodies once Java 7 support i

[GitHub] kafka pull request #3127: Add sleep between empty polls to avoid burning CPU

GitHub user felixgborrego opened a pull request: https://github.com/apache/kafka/pull/3127 Add sleep between empty polls to avoid burning CPU Workaround for https://issues.apache.org/jira/browse/KAFKA-3159 You can merge this pull request into a Git repository by running: $ git

[jira] [Commented] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

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

Re: [DISCUSS]: KIP-159: Introducing Rich functions to Streams

Hi Jeyhun, I understand your argument about "Rich" in RichFunctions. Perhaps I'm just being too puritan here, but let me ask this anyway: What is it that makes something a function? To me a function is something that takes zero or more arguments and possibly returns a value and while it may

[jira] [Created] (KAFKA-5315) Streams exception w/ partially processed record corrupts state store

Mathieu Fenniak created KAFKA-5315: -- Summary: Streams exception w/ partially processed record corrupts state store Key: KAFKA-5315 URL: https://issues.apache.org/jira/browse/KAFKA-5315 Project: Kafka

Re: KTable aggregate corruption on poorly timed exception

Hi Matthias, I've filed KAFKA-5315 (https://issues.apache.org/jira/browse/KAFKA-5315). Thanks, Mathieu On Fri, May 19, 2017 at 3:07 PM, Matthias J. Sax wrote: > Hi Mathieu, > > Thanks for reporting this! > > This is definitely a bug and it must get fixed for at-last-once > processing, too. Ex

[jira] [Commented] (KAFKA-5308) TC should handle UNSUPPORTED_FOR_MESSAGE_FORMAT in WriteTxnMarker response

[ https://issues.apache.org/jira/browse/KAFKA-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021295#comment-16021295 ] Damian Guy commented on KAFKA-5308: --- [~hachikuji] i think this may not be possible once

Re: [DISCUSS] KIP-158: Kafka Connect should allow source connectors to set topic-specific settings for new topics

Hi Randall, Awesome, very much looking forward to this. It isn't 100% clear from the KIP how multiple config-based rules would be applied; it looks like the first configuration rule whose regex matches the topic name will be used, and no other rules will be applied. Is that correct? (I wasn't s

[GitHub] kafka pull request #3128: MINOR: remove TransactionCoordinatorIntegrationTes...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/3128 MINOR: remove TransactionCoordinatorIntegrationTest `TransactionCoordinatorIntegrationTest` is not covering anything that isn't already covered by the more complete `TransactionsTest` You can merge th

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

Hi Rajini If we only use the request.timeout for the connect and process request, it is not flexible for some cases, for example we need the connecting phase to a short time(5s), and the request for a longer time(40s). Why not add a connect timeout to handler these different cases. Thanks, Da

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

Hi David, The only issue with yet another config is that nearly everyone will just leave it at the default value and it is hard to configure. But that is just my personal opinion. If you need the flexibility, then I don't have any objection to another config option. The specific scenario describe

[jira] [Updated] (KAFKA-5247) Consumer GroupCoordinator should continue to materialize committed offsets in offset order even for transactional offset commits

[ https://issues.apache.org/jira/browse/KAFKA-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5247: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull requ

[GitHub] kafka pull request #3108: KAFKA-5247: Materialize committed offsets in offse...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3108 --- 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-5247) Consumer GroupCoordinator should continue to materialize committed offsets in offset order even for transactional offset commits

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

Re: Pull-Requests not worked on

I agree with this. As a new contributor, it was a bit demoralizing to look at all the open PR's and wonder whether when I sent a patch it would just be left to sit in the ether. In other projects I'm involved with, more typically the maintainers go through periodically and close old PR's that will

[GitHub] kafka pull request #3128: MINOR: remove TransactionCoordinatorIntegrationTes...

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

[GitHub] kafka pull request #3081: MINOR: Log transaction metadata state transitions ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3081 --- 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] [Work started] (KAFKA-5282) Transactions integration test: Use factory methods to keep track of open producers and consumers and close them all on tearDown

[ https://issues.apache.org/jira/browse/KAFKA-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5282 started by Vahid Hashemian. -- > Transactions integration test: Use factory methods to keep track of open >

Re: [DISCUSS] KIP-158: Kafka Connect should allow source connectors to set topic-specific settings for new topics

Thanks for the quick feedback, Mathieu. Yes, the first configuration rule whose regex matches will be applied, and no other rules will be used. I've updated the KIP to try to make this more clear, but let me know if it's still not clear. Best regards, Randall On Tue, May 23, 2017 at 10:07 AM, Ma

[jira] [Commented] (KAFKA-5253) KStreamTestDriver must handle streams created with patterns

[ https://issues.apache.org/jira/browse/KAFKA-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021520#comment-16021520 ] Matthias J. Sax commented on KAFKA-5253: As you can see from the code {{KStreamTes

[jira] [Work started] (KAFKA-5314) Improve exception handling for state stores

[ https://issues.apache.org/jira/browse/KAFKA-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5314 started by Eno Thereska. --- > Improve exception handling for state stores > ---

[GitHub] kafka pull request #3129: KAFKA-5282: Use a factory method to create produce...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/3129 KAFKA-5282: Use a factory method to create producers and consumers an d close them in tearDown You can merge this pull request into a Git repository by running: $ git pull https://gith

[jira] [Commented] (KAFKA-5282) Transactions integration test: Use factory methods to keep track of open producers and consumers and close them all on tearDown

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

[jira] [Assigned] (KAFKA-5315) Streams exception w/ partially processed record corrupts state store

[ https://issues.apache.org/jira/browse/KAFKA-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-5315: -- Assignee: Matthias J. Sax > Streams exception w/ partially processed record corrupts st

[jira] [Commented] (KAFKA-5296) Unable to write to some partitions of newly created topic in 10.2

[ https://issues.apache.org/jira/browse/KAFKA-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021577#comment-16021577 ] Abhisek Saikia commented on KAFKA-5296: --- Any new topic creation is running into issu

[jira] [Updated] (KAFKA-5311) Support ExtendedDeserializer in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5311: --- Status: Patch Available (was: Open) > Support ExtendedDeserializer in Kafka Streams > ---

[jira] [Commented] (KAFKA-5311) Support ExtendedDeserializer in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021584#comment-16021584 ] Matthias J. Sax commented on KAFKA-5311: [~guozhang] Can you add [~dale.peakall] t

[jira] [Comment Edited] (KAFKA-5296) Unable to write to some partitions of newly created topic in 10.2

[ https://issues.apache.org/jira/browse/KAFKA-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021577#comment-16021577 ] Abhisek Saikia edited comment on KAFKA-5296 at 5/23/17 6:45 PM:

Build failed in Jenkins: kafka-0.11.0-jdk7 #18

See Changes: [wangguoz] MINOR: remove TransactionCoordinatorIntegrationTest [jason] MINOR: Log transaction metadata state transitions plus a few cleanups -- [...truncated

[jira] [Comment Edited] (KAFKA-5296) Unable to write to some partitions of newly created topic in 10.2

[ https://issues.apache.org/jira/browse/KAFKA-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021577#comment-16021577 ] Abhisek Saikia edited comment on KAFKA-5296 at 5/23/17 6:46 PM:

[GitHub] kafka pull request #3104: MINOR: improve EmbeddedKafkaCluster test utility f...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3104 --- 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-5311) Support ExtendedDeserializer in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-5311: Assignee: Dale Peakall > Support ExtendedDeserializer in Kafka Streams > --

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

See

[jira] [Updated] (KAFKA-5296) Unable to write to some partitions of newly created topic in 10.2

[ https://issues.apache.org/jira/browse/KAFKA-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhisek Saikia updated KAFKA-5296: -- Affects Version/s: 0.10.2.0 > Unable to write to some partitions of newly created topic in 10.2

[jira] [Commented] (KAFKA-1955) Explore disk-based buffering in new Kafka Producer

[ https://issues.apache.org/jira/browse/KAFKA-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021683#comment-16021683 ] Brandon Bradley commented on KAFKA-1955: I've implemented a barebones malloc/free

Re: [DISCUSS] KIP-158: Kafka Connect should allow source connectors to set topic-specific settings for new topics

Ah, yes, I see you a highlighted part that should've made this clear to me the first read. :-) Much clearer now! By the way, enjoyed your Debezium talk in NYC. Looking forward to this Kafka Connect change; it will allow me to remove a post-deployment tool that I hacked together for the purpose o

Jenkins build is back to normal : kafka-0.11.0-jdk7 #19

See

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

In the AdminClient, we allow setting per-call timeouts. The global timeout is just a default. It seems like that is really what we should do in the producer and consumer as well, rather than having a lot of special cases for timeouts in connecting vs. other call states. Then join requests could

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

See Changes: [wangguoz] MINOR: improve EmbeddedKafkaCluster test utility for deleting topics -- [...truncated 887.44 KB...] kafka.producer.ProducerTest > testUpdateBrokerP

[jira] [Commented] (KAFKA-5167) streams task gets stuck after re-balance due to LockException

[ https://issues.apache.org/jira/browse/KAFKA-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021786#comment-16021786 ] Joao commented on KAFKA-5167: - I just came across this very same exception, logs below, howeve

[jira] [Updated] (KAFKA-5280) Protect concurrent access to the cached transaction status

[ https://issues.apache.org/jira/browse/KAFKA-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5280: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request

[GitHub] kafka pull request #3082: KAFKA-5280: Protect txn metadata map with read-wri...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3082 --- 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-5280) Protect concurrent access to the cached transaction status

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

[jira] [Commented] (KAFKA-5167) streams task gets stuck after re-balance due to LockException

[ https://issues.apache.org/jira/browse/KAFKA-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021868#comment-16021868 ] Matthias J. Sax commented on KAFKA-5167: [~JoaoPeixoto] If I read the log you shar

[jira] [Commented] (KAFKA-5167) streams task gets stuck after re-balance due to LockException

[ https://issues.apache.org/jira/browse/KAFKA-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021879#comment-16021879 ] Joao commented on KAFKA-5167: - [~mjsax] thanks for the clarification regarding the max poll in

[jira] [Comment Edited] (KAFKA-5167) streams task gets stuck after re-balance due to LockException

[ https://issues.apache.org/jira/browse/KAFKA-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021879#comment-16021879 ] Joao edited comment on KAFKA-5167 at 5/23/17 9:20 PM: -- [~mjsax] thank

Can I get a review for a PR for KAFKA-5191?

Hi, Can I get a review of pull request https://github.com/apache/kafka/pull/2993, for JIRA https://issues.apache.org/jira/browse/KAFKA-5191 ? I'm trying to get it into the 0.11.0.0 release. I think tomorrow is the last day to get it merged in? Thanks, -James

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

See

[jira] [Commented] (KAFKA-5167) streams task gets stuck after re-balance due to LockException

[ https://issues.apache.org/jira/browse/KAFKA-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021932#comment-16021932 ] Matthias J. Sax commented on KAFKA-5167: I see your point -- we are working on bet

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

Another note-- it would be really nice if timeouts were end-to-end, rather than being set for particular phases of an RP From a user point of view, a 30 second timeout should mean that the call either succeeds or fails after 30 seconds, regardless of how much time is spent looking for metadata, co

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

See Changes: [wangguoz] KAFKA-5280: Protect txn metadata map with read-write lock -- [...truncated 2.89 MB...] kafka.admin.ReassignPartitionsCommandTest > shouldRemoveThr

[jira] [Created] (KAFKA-5316) Log cleaning can increase message size and cause cleaner to crash with buffer overflow

Jason Gustafson created KAFKA-5316: -- Summary: Log cleaning can increase message size and cause cleaner to crash with buffer overflow Key: KAFKA-5316 URL: https://issues.apache.org/jira/browse/KAFKA-5316

[jira] [Updated] (KAFKA-5316) Log cleaning can increase message size and cause cleaner to crash with buffer overflow

[ https://issues.apache.org/jira/browse/KAFKA-5316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5316: --- Description: We have observed in practice that it is possible for a compressed record set to

[jira] [Resolved] (KAFKA-5010) Log cleaner crashed with BufferOverflowException when writing to the writeBuffer

[ https://issues.apache.org/jira/browse/KAFKA-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5010. Resolution: Duplicate Fix Version/s: (was: 0.11.0.0) Marking this as a duplicate of KAFKA

[jira] [Work started] (KAFKA-5147) KafkaProducer's TransactionManager needs a review on synchronization

[ https://issues.apache.org/jira/browse/KAFKA-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5147 started by Apurva Mehta. --- > KafkaProducer's TransactionManager needs a review on synchronization > --

[jira] [Updated] (KAFKA-5019) Exactly-once upgrade notes

[ https://issues.apache.org/jira/browse/KAFKA-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5019: Labels: exactly-once (was: ) > Exactly-once upgrade notes > -- > >

[jira] [Updated] (KAFKA-5019) Exactly-once upgrade notes

[ https://issues.apache.org/jira/browse/KAFKA-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5019: Labels: documentation exactly-once (was: exactly-once) > Exactly-once upgrade notes > -

[jira] [Updated] (KAFKA-5020) Update protocol documentation to mention message format v2

[ https://issues.apache.org/jira/browse/KAFKA-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5020: Labels: docuentation exactly-once (was: ) > Update protocol documentation to mention message format

[jira] [Updated] (KAFKA-5020) Update protocol documentation to mention message format v2

[ https://issues.apache.org/jira/browse/KAFKA-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5020: Labels: documentation exactly-once (was: docuentation exactly-once) > Update protocol documentation

[jira] [Updated] (KAFKA-5310) reset ControllerContext during resignation

[ https://issues.apache.org/jira/browse/KAFKA-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-5310: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 3122 [https:

[GitHub] kafka pull request #3122: KAFKA-5310: reset ControllerContext during resigna...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3122 --- 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-5021) Update Message Delivery Semantics section to take into account KIP-98

[ https://issues.apache.org/jira/browse/KAFKA-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5021: Labels: documentation exactly-once (was: ) > Update Message Delivery Semantics section to take into

[jira] [Commented] (KAFKA-5310) reset ControllerContext during resignation

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

[jira] [Updated] (KAFKA-5024) Old clients don't support message format V2

[ https://issues.apache.org/jira/browse/KAFKA-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5024: Labels: documentation exactly-once (was: ) > Old clients don't support message format V2 >

[GitHub] kafka pull request #3130: KAFKA-5202: Handle topic deletion while trying to ...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/3130 KAFKA-5202: Handle topic deletion while trying to send txn markers Here is the sketch of this proposal: 1. When handling `addPartition` request, the coordinator will check if all its c

[jira] [Commented] (KAFKA-5202) Handle topic deletion for ongoing transactions

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

[jira] [Commented] (KAFKA-5031) Additional validation in validateMessagesAndAssignOffsets

[ https://issues.apache.org/jira/browse/KAFKA-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022092#comment-16022092 ] Apurva Mehta commented on KAFKA-5031: - [~gosubpl] for the record counts at least, we s

[jira] [Updated] (KAFKA-5135) Controller Health Metrics (KIP-143)

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

[jira] [Updated] (KAFKA-5093) Load only batch header when rebuilding producer ID map

[ https://issues.apache.org/jira/browse/KAFKA-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5093: Priority: Blocker (was: Critical) > Load only batch header when rebuilding producer ID map > --

[GitHub] kafka pull request #2983: KAFKA-5135: Controller Health Metrics (KIP-143)

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2983 --- 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-5093) Load only batch header when rebuilding producer ID map

[ https://issues.apache.org/jira/browse/KAFKA-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5093: Labels: exactly-once (was: ) > Load only batch header when rebuilding producer ID map > ---

[jira] [Commented] (KAFKA-5135) Controller Health Metrics (KIP-143)

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

[jira] [Created] (KAFKA-5317) Update KIP-98 to reflect changes during implementation.

Apurva Mehta created KAFKA-5317: --- Summary: Update KIP-98 to reflect changes during implementation. Key: KAFKA-5317 URL: https://issues.apache.org/jira/browse/KAFKA-5317 Project: Kafka Issue Typ

[jira] [Created] (KAFKA-5318) Streams state may be misleading

Joao created KAFKA-5318: --- Summary: Streams state may be misleading Key: KAFKA-5318 URL: https://issues.apache.org/jira/browse/KAFKA-5318 Project: Kafka Issue Type: Bug Components: streams

[jira] [Updated] (KAFKA-5318) Streams state may be misleading

[ https://issues.apache.org/jira/browse/KAFKA-5318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joao updated KAFKA-5318: Description: I rely on "org.apache.kafka.streams.KafkaStreams#state" to know if my current stream instance is prope

[jira] [Commented] (KAFKA-5032) Think through implications of max.message.size affecting record batches in message format V2

[ https://issues.apache.org/jira/browse/KAFKA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022127#comment-16022127 ] Apurva Mehta commented on KAFKA-5032: - [~ijuma] [~hachikuji] : I am a bit confused abo

  1   2   >