[jira] [Updated] (KAFKA-5355) Broker returns messages beyond "latest stable offset" to transactional consumer in read_committed mode

[ https://issues.apache.org/jira/browse/KAFKA-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5355: Summary: Broker returns messages beyond "latest stable offset" to transactional consumer in read_com

[jira] [Created] (KAFKA-5356) Producer with transactionalId should be able to send outside of a transaction

Jason Gustafson created KAFKA-5356: -- Summary: Producer with transactionalId should be able to send outside of a transaction Key: KAFKA-5356 URL: https://issues.apache.org/jira/browse/KAFKA-5356 Proje

[jira] [Assigned] (KAFKA-5355) Broker returns messages beyond "latest stable offset" to transactional consumer in read_committed mode

[ https://issues.apache.org/jira/browse/KAFKA-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-5355: -- Assignee: Jason Gustafson > Broker returns messages beyond "latest stable offset" to tr

[jira] [Commented] (KAFKA-4566) Can't Symlink to Kafka bins

[ https://issues.apache.org/jira/browse/KAFKA-4566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032048#comment-16032048 ] Jim Jagielski commented on KAFKA-4566: -- Since this is a shell, we can check which OS

[GitHub] kafka pull request #2855: Minor improve streams config parameters

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2855 --- 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 #3184: KAFKA-5351: Reset pending state when returning an ...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/3184 KAFKA-5351: Reset pending state when returning an error in appendTransactionToLog Without this patch, future client retries would get the `CONCURRENT_TRANSACTIONS` error code indefinitely, since th

[jira] [Updated] (KAFKA-5355) Broker returns messages beyond "latest stable offset" to transactional consumer in read_committed mode

[ https://issues.apache.org/jira/browse/KAFKA-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5355: --- Issue Type: Sub-task (was: Bug) Parent: KAFKA-4815 > Broker returns messages beyond "

[jira] [Commented] (KAFKA-5351) Broker clean bounce test puts the broker into a 'CONCURRENT_TRANSACTIONS' state permanently

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

[GitHub] kafka pull request #3017: KAFKA-5218: New Short serializer, deserializer, se...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3017 --- 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-5218) New Short serializer, deserializer, serde

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

[jira] [Commented] (KAFKA-5218) New Short serializer, deserializer, serde

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

[jira] [Updated] (KAFKA-5351) Broker clean bounce test puts the broker into a 'CONCURRENT_TRANSACTIONS' state permanently

[ https://issues.apache.org/jira/browse/KAFKA-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5351: Status: Patch Available (was: Open) > Broker clean bounce test puts the broker into a 'CONCURRENT_T

[GitHub] kafka pull request #3182: MINOR: Use `waitUntil` to fix transient failures o...

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

See Changes: [jason] KAFKA-5093; Avoid loading full batch data when possible when iterating -- [...truncated 4.06 MB...] kafka.utils.UtilsTest > testCsvMap PASSED kafka.

[jira] [Resolved] (KAFKA-5353) Set baseTimestamp correctly if log append time and no broker recompression

[ https://issues.apache.org/jira/browse/KAFKA-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5353. Resolution: Fixed Issue resolved by pull request 3177 [https://github.com/apache/kafka/pull/3177] >

[GitHub] kafka pull request #3177: KAFKA-5353: baseTimestamp should always have a cre...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3177 --- 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-5353) baseTimestamp should always have a create timestamp

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

[jira] [Updated] (KAFKA-5353) baseTimestamp should always have a create timestamp

[ https://issues.apache.org/jira/browse/KAFKA-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5353: --- Summary: baseTimestamp should always have a create timestamp (was: Set baseTimestamp correctly if log

[jira] [Updated] (KAFKA-5353) baseTimestamp should always have a create timestamp

[ https://issues.apache.org/jira/browse/KAFKA-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5353: --- Description: This makes the case where we build the records from scratch consistent with the case wher

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

See Changes: [wangguoz] MINOR: Improve streams config parameters [wangguoz] KAFKA-5218; New Short serializer, deserializer, serde -- [...truncated 905.87 KB...] kafka.serv

[jira] [Updated] (KAFKA-5293) Do not apply exponential backoff if users have overridden reconnect.backoff.ms

[ https://issues.apache.org/jira/browse/KAFKA-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5293: --- Status: Patch Available (was: Open) > Do not apply exponential backoff if users have overridden recon

[jira] [Updated] (KAFKA-5356) Producer with transactionalId should be able to send outside of a transaction

[ https://issues.apache.org/jira/browse/KAFKA-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5356: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Producer with transactionalId should

[jira] [Updated] (KAFKA-4628) Support KTable/GlobalKTable Joins

[ https://issues.apache.org/jira/browse/KAFKA-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4628: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Support KTable/GlobalKTable Joins > -

[jira] [Updated] (KAFKA-4487) Tests should be run in Jenkins with INFO or DEBUG level

[ https://issues.apache.org/jira/browse/KAFKA-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4487: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Tests should be run in Jenkins with I

[jira] [Updated] (KAFKA-5270) TransactionManager should send and `AddOffsetsToTxn` request only once per group per transaction

[ https://issues.apache.org/jira/browse/KAFKA-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5270: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > TransactionManager should sen

[GitHub] kafka pull request #3098: KAFKA-5291: AdminClient should not trigger auto cr...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3098 --- 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-5291) AdminClient should not trigger auto creation of topics

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

[jira] [Commented] (KAFKA-5291) AdminClient should not trigger auto creation of topics

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

[jira] [Commented] (KAFKA-4592) Kafka Producer Metrics Invalid Value

[ https://issues.apache.org/jira/browse/KAFKA-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032261#comment-16032261 ] Jun Rao commented on KAFKA-4592: [~huxi], sorry for the late response. If a metric is neve

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

See

[jira] [Commented] (KAFKA-1595) Remove deprecated and slower scala JSON parser from kafka.consumer.TopicCount

[ https://issues.apache.org/jira/browse/KAFKA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032276#comment-16032276 ] Onur Karaman commented on KAFKA-1595: - I think [~ijuma]'s PR (https://github.com/apach

[jira] [Comment Edited] (KAFKA-1595) Remove deprecated and slower scala JSON parser from kafka.consumer.TopicCount

[ https://issues.apache.org/jira/browse/KAFKA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032276#comment-16032276 ] Onur Karaman edited comment on KAFKA-1595 at 6/1/17 12:50 AM: --

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

See

[GitHub] kafka pull request #3172: KAFKA-5350: Modify unstable annotations in Streams...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3172 --- 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] [Resolved] (KAFKA-5350) Modify Unstable annotations in Streams API

[ https://issues.apache.org/jira/browse/KAFKA-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-5350. -- Resolution: Fixed Issue resolved by pull request 3172 [https://github.com/apache/kafka/pull/3172

[jira] [Commented] (KAFKA-5350) Modify Unstable annotations in Streams API

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

[GitHub] kafka pull request #3185: MINOR: Logging/debugging improvements for transact...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3185 MINOR: Logging/debugging improvements for transactions You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka minor-transaction-logg

[GitHub] kafka pull request #3157: KAFKA-5226: Fixes issue where adding topics matchi...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3157 --- 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-5226) NullPointerException (NPE) in SourceNodeRecordDeserializer.deserialize

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

[jira] [Commented] (KAFKA-5226) NullPointerException (NPE) in SourceNodeRecordDeserializer.deserialize

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

[jira] [Commented] (KAFKA-5226) NullPointerException (NPE) in SourceNodeRecordDeserializer.deserialize

[ https://issues.apache.org/jira/browse/KAFKA-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032345#comment-16032345 ] Guozhang Wang commented on KAFKA-5226: -- [~ian.springer] The fix has just been merged

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

See Changes: [ismael] KAFKA-5291; AdminClient should not trigger auto creation of topics -- [...truncated 909.59 KB...] kafka.admin.ConfigCommandTest > shouldNotUpdateBro

[DISCUSS] KIP-166 Add a tool to make amounts of replicas and leaders on brokers balanced

Hi, We created KIP-166 to propose adding a tool to balance amounts of replicas and leaders on brokers. The KIP wiki can be found at https://cwiki.apache.org/confluence/display/KAFKA/KIP-166+-+Add+a+tool+to+make+amounts+of+replicas+and+leaders+on+brokers+balanced And the JIRA is KAFKA-5319 http

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

See Changes: [wangguoz] KAFKA-5350: Modify unstable annotations in Streams API [wangguoz] KAFKA-5226; Fixes issue where adding topics matching a regex -- [...truncated 2.

[jira] [Updated] (KAFKA-5340) Add additional test cases for batch splitting to ensure idempotent/transactional metadata is preserved

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

[GitHub] kafka pull request #3162: KAFKA-5340: Batch splitting should preserve magic ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3162 --- 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-5340) Add additional test cases for batch splitting to ensure idempotent/transactional metadata is preserved

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

[jira] [Created] (KAFKA-5357) StackOverFlow error in transaction coordinator

Apurva Mehta created KAFKA-5357: --- Summary: StackOverFlow error in transaction coordinator Key: KAFKA-5357 URL: https://issues.apache.org/jira/browse/KAFKA-5357 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-5358) Consumer perf tool should count rebalance time separately

Jason Gustafson created KAFKA-5358: -- Summary: Consumer perf tool should count rebalance time separately Key: KAFKA-5358 URL: https://issues.apache.org/jira/browse/KAFKA-5358 Project: Kafka I

[jira] [Commented] (KAFKA-5357) StackOverFlow error in transaction coordinator

[ https://issues.apache.org/jira/browse/KAFKA-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032470#comment-16032470 ] Apurva Mehta commented on KAFKA-5357: - The upshot of this ticket is that the commit of

[jira] [Updated] (KAFKA-5357) StackOverFlow error in transaction coordinator

[ https://issues.apache.org/jira/browse/KAFKA-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5357: Attachment: KAFKA-5357.tar.gz > StackOverFlow error in transaction coordinator > ---

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

[ https://issues.apache.org/jira/browse/KAFKA-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5019 started by Jason Gustafson. -- > Exactly-once upgrade notes > -- > >

[jira] [Updated] (KAFKA-5322) Resolve AddPartitions response error code inconsistency

[ https://issues.apache.org/jira/browse/KAFKA-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriram Subramanian updated KAFKA-5322: -- Labels: exactly-once (was: ) > Resolve AddPartitions response error code inconsistency

[jira] [Commented] (KAFKA-1595) Remove deprecated and slower scala JSON parser from kafka.consumer.TopicCount

[ https://issues.apache.org/jira/browse/KAFKA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032478#comment-16032478 ] Guozhang Wang commented on KAFKA-1595: -- Sounds great. If [~ijuma] is fine with it fee

[jira] [Resolved] (KAFKA-5321) MemoryRecords.filterTo can return corrupt data if output buffer is not large enough

[ https://issues.apache.org/jira/browse/KAFKA-5321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5321. Resolution: Fixed We decided to fix this in KAFKA-5316. > MemoryRecords.filterTo can return

[jira] [Commented] (KAFKA-5322) Resolve AddPartitions response error code inconsistency

[ https://issues.apache.org/jira/browse/KAFKA-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032485#comment-16032485 ] Jason Gustafson commented on KAFKA-5322: [~guozhang] That sounds good to me. I'll

[jira] [Updated] (KAFKA-5351) Broker clean bounce test puts the broker into a 'CONCURRENT_TRANSACTIONS' state permanently

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

[jira] [Commented] (KAFKA-5351) Broker clean bounce test puts the broker into a 'CONCURRENT_TRANSACTIONS' state permanently

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

[GitHub] kafka pull request #3184: KAFKA-5351: Reset pending state when returning an ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3184 --- 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-5322) Resolve AddPartitions response error code inconsistency

[ https://issues.apache.org/jira/browse/KAFKA-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032502#comment-16032502 ] Ismael Juma commented on KAFKA-5322: I prefer option 2 as well. > Resolve AddPartitio

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

See Changes: [jason] KAFKA-5340; Batch splitting should preserve magic and transactional flag -- [...truncated 905.92 KB...] kafka.controller.ControllerIntegrationTest >

[jira] [Commented] (KAFKA-5357) StackOverFlow error in transaction coordinator

[ https://issues.apache.org/jira/browse/KAFKA-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032525#comment-16032525 ] Apurva Mehta commented on KAFKA-5357: - The bigger problem is that once the InterBroker

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

See

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

See Changes: [wangguoz] KAFKA-5351: Reset pending state when returning an error in -- [...truncated 903.05 KB...] kafka.integration.PrimitiveApiTest > testMultiProduce PAS

[jira] [Commented] (KAFKA-5357) StackOverFlow error in transaction coordinator

[ https://issues.apache.org/jira/browse/KAFKA-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032547#comment-16032547 ] Apurva Mehta commented on KAFKA-5357: - The stack over flow error is essentially due to

[jira] [Commented] (KAFKA-5357) StackOverFlow error in transaction coordinator

[ https://issues.apache.org/jira/browse/KAFKA-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032552#comment-16032552 ] Ismael Juma commented on KAFKA-5357: Even if we do that, it's still possible to overfl

[jira] [Comment Edited] (KAFKA-5357) StackOverFlow error in transaction coordinator

[ https://issues.apache.org/jira/browse/KAFKA-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032547#comment-16032547 ] Apurva Mehta edited comment on KAFKA-5357 at 6/1/17 6:56 AM: -

[jira] [Commented] (KAFKA-5357) StackOverFlow error in transaction coordinator

[ https://issues.apache.org/jira/browse/KAFKA-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032555#comment-16032555 ] Ismael Juma commented on KAFKA-5357: The other option, which is better if possible, is

<    1   2