[GitHub] kafka pull request #3628: KAFKA-5681; jarAll should build all scala versions...
Github user becketqin closed the pull request at: https://github.com/apache/kafka/pull/3628 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #3628: KAFKA-5681; jarAll should build all scala versions...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/3628 KAFKA-5681; jarAll should build all scala versions. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-5681 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/3628.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3628 commit 5a6d614b98cd2694c93c029331690490675e39c2 Author: Jiangjie Qin Date: 2017-08-04T19:46:32Z KAFKA-5681; jarAll should build all scala versions. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #3573: KAFKA-5630; The consumer should block on courrupt ...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/3573 KAFKA-5630; The consumer should block on courrupt records and keeping throw exception This patch handles the case that a CorruptRecordException is thrown from the iterator directly. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-5630 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/3573.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3573 commit e51ddce3ddacefee7101b95021a3af5da32bcff4 Author: Jiangjie Qin Date: 2017-07-25T18:20:09Z KAFKA-5630; The consumer should block on courrupt records and keeping throw exception. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #2828: KAFKA-5011: down convert the message on replicatio...
Github user becketqin closed the pull request at: https://github.com/apache/kafka/pull/2828 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #3163: KAFKA-5344: set message.timestamp.difference.max.m...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/3163 KAFKA-5344: set message.timestamp.difference.max.ms back to Long.MaxValue You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-5344 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/3163.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3163 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #3114: KAFKA-5211: Do not skip a corrupted record in cons...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/3114 KAFKA-5211: Do not skip a corrupted record in consumer You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-5211 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/3114.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3114 commit e15530c262b4fc4727e61656f22881642d5e5049 Author: Jiangjie Qin Date: 2017-05-22T06:24:22Z KAFKA-5211: Do not skip a corrupted record in consumer --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #2828: KAFKA-5011: down convert the message on replicatio...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/2828 KAFKA-5011: down convert the message on replication if necessary You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-5011 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/2828.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2828 commit b7762a60439c617bab2f541a44edcf92c0537b81 Author: Jiangjie Qin Date: 2017-04-07T23:25:52Z KAFKA-5011: down convert the message on replication if necessary --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #2705: KAFKA-4907: message.timestamp.difference.max.ms sh...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/2705 KAFKA-4907: message.timestamp.difference.max.ms should not be applied to log compacted topic if user did not set the property. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-4907 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/2705.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2705 commit 96e1301338619b7d45d5b90adf0cecbf40491a2c Author: Jiangjie Qin Date: 2017-03-19T06:11:19Z KAFKA-4907: message.timestamp.difference.max.ms should not be applied to log compacted topic if user did not set the property. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #2638: KAFKA-3995: fix compression ratio estimation.
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/2638 KAFKA-3995: fix compression ratio estimation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3995 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/2638.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2638 commit cee4d58cb0afaa526bddd372246894bab82c82c2 Author: Jiangjie Qin Date: 2017-03-04T01:40:12Z KAFKA-3995: fix compression ratio estimation. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #2544: KFKA-4340: update the upgrade.html
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/2544 KFKA-4340: update the upgrade.html You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-4340_follow_up Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/2544.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2544 commit 03a3beedfa3063574586fa337463ee792ce6d17e Author: Jiangjie Qin Date: 2017-02-13T10:10:34Z Follow up patch for KAFKA-4340 to update the upgrade.html --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #2501: KAFKA-4734; Trim the time index on old segments
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/2501 KAFKA-4734; Trim the time index on old segments You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-4734 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/2501.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2501 commit c77900a66ab9464f54fdb828299d57589e7939bd Author: Jiangjie Qin Date: 2017-02-04T06:39:00Z KAFKA-4734; Trim the time index on old segments --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #2329: KAFKA-4381: Add per partition lag metrics to the c...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/2329 KAFKA-4381: Add per partition lag metrics to the consumer You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-4381 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/2329.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2329 commit 8770bcaf6ba2a2bb1ce4971a1d45e6a934a118f1 Author: Jiangjie Qin Date: 2017-01-06T22:30:52Z KAFKA-4381: Add per partition lag metrics to the consumer --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #2251: KAFKA-4529; Fix the issue that tombstone can be de...
Github user becketqin closed the pull request at: https://github.com/apache/kafka/pull/2251 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #660: KAFKA-2980 Fix deadlock when ZookeeperConsumerConne...
Github user becketqin closed the pull request at: https://github.com/apache/kafka/pull/660 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #2260: KAFKA-4529; LogCleaner should not delete the tombs...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/2260 KAFKA-4529; LogCleaner should not delete the tombstone too early. cc @junrao You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-4529-trunk Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/2260.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2260 commit 681613bb7acd2df2a3abd1519dab1272a5b3c207 Author: Jiangjie Qin Date: 2016-12-15T05:53:35Z KAFKA-4529; LogCleaner should not delete the tombstone too early. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #2242: KAFKA-4497: Fix the ByteBufferMessageSet.filterInt...
Github user becketqin closed the pull request at: https://github.com/apache/kafka/pull/2242 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #2251: KAFKA-4529; Fix the issue that tombstone can be de...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/2251 KAFKA-4529; Fix the issue that tombstone can be deleted too early. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-4529 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/2251.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2251 commit 42f284bf0c1897899b4d620d18de9f66f65617f3 Author: Jiangjie Qin Date: 2016-12-13T19:02:08Z KAFKA-4529; Fix the issue that tombstone can be deleted too early. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #2243: KAFKA-4497: LogCleaner appended the wrong offset t...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/2243 KAFKA-4497: LogCleaner appended the wrong offset to time index. Backport the fix to 0.10.1. The code in trunk has been changed, so we need to provide a different fix for this problem in 0.10.1. Some explanations. I was able to reproduce the initial issue with a unit test. I did not include the unit test here because the tests requires a lot of hard coded constants to precisely control the message size after compression, read buffer and which message is filtered out. In trunk I have added a unit test to `ByteBufferMessageSet.fliterInto()` which holds the current buggy logic. Given no one will be developing on 0.10.1 branch anymore except bug fixes, I think it is fine to leave the ugly unit test out of this patch. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-4497-0.10.1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/2243.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2243 commit 5b869e7ee4c6b554787330c386988b5447b127ca Author: Jiangjie Qin Date: 2016-12-12T01:32:05Z KAFKA-4497: LogCleaner appended the wrong offset to time index. Backport the fix to 0.10.1. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #2242: KAFKA-4497: Fix the ByteBufferMessageSet.filterInt...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/2242 KAFKA-4497: Fix the ByteBufferMessageSet.filterInto There seems a few bugs in `ByteBufferMessageSet.filterInto`, including incorrect offsets, messages read and retained. This patch fixes them and added unit test. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-4497 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/2242.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2242 commit b01f88466461f04c683eb35207b6ec5d4fa04698 Author: Jiangjie Qin Date: 2016-12-12T00:38:54Z KAFKA-4497: Fix the ByteBufferMessageSet.filterInto --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[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 have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[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 Does the updated page look good to you? --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[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 That's fair. I updated the page. The thing I found confusing is that we have documentation in three places: 1) Kafka code repo 2) kafka-site repo 3) some documentation are just a wiki page. I'll update https://cwiki.apache.org/confluence/display/KAFKA/Contributing+Website+Documentation+Changes to clarify this a little. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[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 The github site has stated that it is mirrored from the Apache repo. I added the link anyways. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka-site pull request #29: Update the website repo link in code.html to po...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka-site/pull/29 Update the website repo link in code.html to point to github. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka-site asf-site Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka-site/pull/29.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka-site issue #28: Add Becket to the committers page
Github user becketqin commented on the issue: https://github.com/apache/kafka-site/pull/28 I'll try to merge this myself :) --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka-site pull request #28: Add Becket to the committers page
GitHub user becketqin opened a pull request: https://github.com/apache/kafka-site/pull/28 Add Becket to the committers page You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka-site asf-site Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka-site/pull/28.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #28 commit 8b967a7c8da8184e3d186c4fe607b2fb3e7e109a Author: Jiangjie Qin Date: 2016-11-02T16:59:15Z Add Becket to the committers page --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #2071: KAFKA-4340: Change default message.timestamp.diffe...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/2071 KAFKA-4340: Change default message.timestamp.difference.max.ms to the same as log.retention.ms You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-4340 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/2071.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2071 commit 5693cf603afdffe4d49659de2a1d9b0faa9f Author: Jiangjie Qin Date: 2016-10-27T03:05:52Z KAFKA-4340: Change default message.timestamp.difference.max.ms to the same as log.retention.ms --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #1993: KAFKA-4274: offsetsForTimes() hang on empty map.
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1993 KAFKA-4274: offsetsForTimes() hang on empty map. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-4274 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1993.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1993 commit 8c6a1b7b0c219843f4785078f2d2ca0d0b2e9c24 Author: Jiangjie Qin Date: 2016-10-07T23:00:05Z KAFKA-4274: offsetsForTimes() hang on empty map. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #1939: KAFKA-4235: Fix the race condition in Sender.initi...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1939 KAFKA-4235: Fix the race condition in Sender.initiateClose() that may result in missing some callbacks. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-4235 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1939.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1939 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #1935: KAFKA-4232: make MemoryRecords.writable volatile.
Github user becketqin closed the pull request at: https://github.com/apache/kafka/pull/1935 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #1935: KAFKA-4232: make MemoryRecords.writable volatile.
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1935 KAFKA-4232: make MemoryRecords.writable volatile. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-4232 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1935.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1935 commit 5b19237a34ab35c5d0dbaf473e6648249bb2fd6a Author: Jiangjie Qin Date: 2016-09-29T17:55:24Z KAFKA-4232 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #1915: KAFKA-3965 mirror maker should not commit offset w...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1915 KAFKA-3965 mirror maker should not commit offset when exception is thrown from producer.send() You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3965 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1915.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1915 commit 0893c16af702cb896d94c3ec63034508f2679ab4 Author: Jiangjie Qin Date: 2016-09-27T05:05:18Z KAFKA-3965 mirror maker should not commit offset when exception is thrown from producer.send() --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #1897: KAFKA-4194 follow up patch for KIP-79
Github user becketqin closed the pull request at: https://github.com/apache/kafka/pull/1897 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #1897: KAFKA-4194 follow up patch for KIP-79
GitHub user becketqin reopened a pull request: https://github.com/apache/kafka/pull/1897 KAFKA-4194 follow up patch for KIP-79 You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-4194 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1897.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1897 commit 5556276d339486c055ee101397d745e7f86d09e0 Author: Jiangjie Qin Date: 2016-09-21T17:40:37Z KAFKA-4148 follow up patch for KIP-79 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #1897: KAFKA-4148 follow up patch for KIP-79
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1897 KAFKA-4148 follow up patch for KIP-79 You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-4194 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1897.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1897 commit 5556276d339486c055ee101397d745e7f86d09e0 Author: Jiangjie Qin Date: 2016-09-21T17:40:37Z KAFKA-4148 follow up patch for KIP-79 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #1852: KAFKA-4148: KIP-79 ListOffsetRequest v1 and add se...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1852 KAFKA-4148: KIP-79 ListOffsetRequest v1 and add search offsets by timestamp in consumer You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-4148 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1852.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1852 commit 38df21b214904fb65cea43a358ab8b22983f6de3 Author: Jiangjie Qin Date: 2016-09-13T16:52:43Z KAFKA-4148: KIP-79 ListOffsetRequest v1 and add search offsets by timestamp in consumer commit 52d8d409a314bc0c764db19ffb040ca93794a2dc Author: Jiangjie Qin Date: 2016-09-13T23:42:53Z Added the handling of duplicate partitions in ListOffsetRequest v1 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #1809: KAFKA-4099: Fix the potential frequent log rolling
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1809 KAFKA-4099: Fix the potential frequent log rolling You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-4099 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1809.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1809 commit 06b9548feaa68c5f224d56df5e1d35bb0287fc8c Author: Jiangjie Qin Date: 2016-09-01T03:24:52Z KAFKA-4099: Fix the potential frequent log rolling. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request #1769: Minor follow up for KAFKA-3163 (KIP-33)
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1769 Minor follow up for KAFKA-3163 (KIP-33) @junrao Could you take a look when get a chance? Thanks. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3163-follow-up Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1769.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1769 commit 2895d0b9af99a29b64de4c3ef42bf9312f313ff9 Author: Jiangjie Qin Date: 2016-08-22T16:39:25Z Minor follow up for KAFKA-3163 (KIP-33) --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-3721: Put UpdateMetadataRequest V2 in 0....
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1400 KAFKA-3721: Put UpdateMetadataRequest V2 in 0.10.0-IV1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3721 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1400.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1400 commit 123bd518c8ad3dbfba8a1c9a26d3bf659c61a514 Author: Jiangjie Qin Date: 2016-05-18T01:25:11Z Put UpdateMetadataRequest V2 in 0.10.0-IV1 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-3554 Improve ProducerPerformance test
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1399 KAFKA-3554 Improve ProducerPerformance test 1. Added multiple thread support. 2. Added value-bound to make compressed data more realistic. 3. Print out the producer metrics. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3554 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1399.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1399 commit c6a96a95673e89a60a19959100982ab151ffb73c Author: Jiangjie Qin Date: 2016-05-17T23:10:57Z KAFKA-3554 ProducerPerformance test improvements. commit 71fd4c8e92d3d9e695c8c0fcfab838de61f4ffc4 Author: Jiangjie Qin Date: 2016-05-17T23:12:40Z remove change in the server property file --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-3698: Update the message format section.
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1375 KAFKA-3698: Update the message format section. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3698 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1375.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1375 commit 0ca431b2e745a15fa3c8d6008a05945bd40c07e7 Author: Jiangjie Qin Date: 2016-05-11T23:31:25Z KAFKA-3698: Update the message format section. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-3565: Add documentation to warn user abo...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1372 KAFKA-3565: Add documentation to warn user about the potential messag⦠â¦e throughput drop due to the addition of timestamp field. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3565 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1372.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1372 commit b0fd341cbb41992424dd20434ffa25d7611bdd19 Author: Jiangjie Qin Date: 2016-05-11T22:32:28Z KAFKA-3565: Add documentation to warn user about the potential message throughput drop due to the addition of timestamp field. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-3163: Add time based index to Kafka.
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1215 KAFKA-3163: Add time based index to Kafka. This is patch for KIP-33. https://cwiki.apache.org/confluence/display/KAFKA/KIP-33+-+Add+a+time+based+log+index You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3163 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1215.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1215 commit 712357a3fbf1423e05f9eed7d2fed5b6fe6c37b7 Author: Jiangjie Qin Date: 2016-04-07T00:38:48Z KIP-33: Add time based log index. commit 739d138f9d2dc36165fa751db06bed779eb3235b Author: Jiangjie Qin Date: 2016-04-08T03:28:02Z Add more unit tests commit 09d3505e3f0acf8d11b2b4bf6a1819d8aa56f6fd Author: Jiangjie Qin Date: 2016-04-11T22:21:48Z Refactored the code a bit. Added some unit test. Added documentation. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-3436: Speed up controlled shutdown.
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1149 KAFKA-3436: Speed up controlled shutdown. This patch does the followings: 1. Batched LeaderAndIsrRequest and UpdateMetadataRequest during controlled shutdown. 2. Added async read and write method to an extending ZkClient. Used the async zk operation for LeaderAndIsr read and update. The async method can be used in other places as well (e.g. preferred leader election, replica reassignment, controller bootstrap, etc), but those are out of the scope of this ticket. Conducted some rolling boucne test, a controlled shutdown involving 2500 partitions takes around 3 seconds now. Previously it can takes more than 30 seconds. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3436 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1149.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1149 commit c2d22821c6c3ad7aa45090def6b984719209f5af Author: Jiangjie Qin Date: 2016-03-27T21:29:30Z KAFKA-3436: Speed up controlled shutdown commit 7e7cf3fb1fc4a44d7af4ea935b38bf2e90e6cadd Author: Jiangjie Qin Date: 2016-03-28T00:47:22Z Remove pre-sent StopReplicaRequests and split state transition into multiple groups. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-3442: Fix FileMessageSet iterator.
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1112 KAFKA-3442: Fix FileMessageSet iterator. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3442 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1112.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1112 commit 3ca0e390aabd31dd178991da77373c44e05a4044 Author: Jiangjie Qin Date: 2016-03-22T04:44:45Z KAFKA-3442: Fix FileMessageSet iterator. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-3388: Fix expiration of batches sitting ...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1056 KAFKA-3388: Fix expiration of batches sitting in the accumulator You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3388 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1056.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1056 commit 7561b81254d4361122c3467b741f98f37a769b29 Author: Jiangjie Qin Date: 2016-03-13T23:57:52Z KAFKA-3388: Fix expiration of batches sitting in the accumulator --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-3373 add 'log' prefix to configurations ...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1049 KAFKA-3373 add 'log' prefix to configurations in KIP-31/32 You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3373 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1049.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1049 commit ff4a509902a888563a1dc39fd129eba7f0c53bb9 Author: Jiangjie Qin Date: 2016-03-10T21:57:46Z KAFKA-3373 add 'log' prefix to configurations in KIP-31/32 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-3343: Use NoTimestamp in GroupMetadataMa...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1023 KAFKA-3343: Use NoTimestamp in GroupMetadataManager when message v0 i⦠â¦s used. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3343 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1023.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1023 commit 2b0cc6dd5583716eda9cef6c03a837af701a91a5 Author: Jiangjie Qin Date: 2016-03-07T21:07:39Z KAFKA-3343: Use NoTimestamp in GroupMetadataManager when message v0 is used. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2960: Clear purgatory for partitions bef...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1018 KAFKA-2960: Clear purgatory for partitions before becoming follower You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2960 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1018.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1018 commit 6ee590bc8f65217227c8bda98644dce35ed0d701 Author: Jiangjie Qin Date: 2016-03-07T04:04:45Z KAFKA-2960: Clear purgatory for partition before becoming follower --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-3300: Avoid over allocating disk space a...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/983 KAFKA-3300: Avoid over allocating disk space and memory for index files. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3300 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/983.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #983 commit b49a9af4c19513e458ced92ef49504f7a1c237df Author: Jiangjie Qin Date: 2016-02-29T01:39:18Z KAFKA-3300: Avoid over allocating disk space and memory for index files. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-3256: Add print.timestamp option to cons...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/949 KAFKA-3256: Add print.timestamp option to console consumer. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3256 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/949.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #949 commit f4a2ebd5feb75cde8b44b3cb1512152805259383 Author: Jiangjie Qin Date: 2016-02-21T06:03:27Z KAFKA-3256: Add print.timestamp option to console consumer. It is disabled by default --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-3190 Producer should not fire callback i...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/880 KAFKA-3190 Producer should not fire callback in Send() method @guozhangwang Would you mind take a look? This was originally introduced in KAFKA-1260. I did not find specific reason in the original rb that we have to handle ApiException separately in callback. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3190 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/880.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #880 commit e41464bffae59e3d79beb34d8999b560017a19dc Author: Jiangjie Qin Date: 2016-02-05T23:46:25Z KAFKA-3190 Producer should not fire callback in Send() method --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-3197 Fix producer sending records out of...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/857 KAFKA-3197 Fix producer sending records out of order This patch adds a new configuration to the producer to enforce the maximum in flight batch for each partition. The patch itself is small, but this is an interface change. Given this is a pretty important fix, may be we can run a quick KIP on it. This patch did not remove max.in.flight.request.per.connection configuration because it might still have some value to throttle the number of requests sent to a broker. This is primarily for broker's interest. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3197 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/857.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #857 commit c12c1e2044fe92954e0c8a27f63263f2020ddd3c Author: Jiangjie Qin Date: 2016-02-03T06:51:41Z KAFKA-3197 Fix producer sending records out of order --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-3179 Fix seek on compressed messages
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/842 KAFKA-3179 Fix seek on compressed messages The fix itself is simple. Some explanation on unit tests. Currently we the vast majority of unit test is running with uncompressed messages. I was initially thinking about run all the tests using compressed messages. But it seems uncompressed messages are necessary in a many test cases because we need the bytes sent and appended to the log to be predictable. In most of other cases, it does not matter whether the message is compressed or not, and compression will slow down the unit test. So I just added one method in the BaseConsumerTest to send compressed messages whenever we need it. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3179 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/842.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #842 commit 0f5cd3184f63ba9ec93c4450f81e0222ae96b422 Author: Jiangjie Qin Date: 2016-02-01T01:38:37Z KAFKA-3179 Fix seek on compressed messages --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-3174: Change Crc32 to use java.util.zip....
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/841 KAFKA-3174: Change Crc32 to use java.util.zip.CRC32 You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3174 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/841.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #841 commit 4419cb58d84466e36c8b1119704eac93566c9974 Author: Jiangjie Qin Date: 2016-01-30T06:44:20Z Change Crc32 to use java.util.zip.CRC32 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-3025 Added timetamp to Message and use r...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/764 KAFKA-3025 Added timetamp to Message and use relative offset. See KIP-31 and KIP-32 for details. A few notes on the patch: 1. This patch only implements the server side message format change. It also implements the message format conversion. 2. All unit tests passed when set . Some of the tests require specific message format versions. I will fix them once the change on o.a.k.clients are done. 3. The unit tests were run with new and old message format. 4. When message format conversion occurs during consumption, the consumer will not be able to detect the message size too large situation. I did not try to fix this because the situation seems rare and only happen during migration phase. The remaining work for KIP-31 and KIP-32 is 1. Add timestamp and relative offset to o.a.k.clients. 2. Add more unit test and integration test You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3025 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/764.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #764 commit 5604b4a57fff61188c562cc634daca4dee72aa4f Author: Jiangjie Qin Date: 2016-01-07T14:30:39Z Added timetamp to Message and use relative offset. See KIP-31 and KIP-32 for details. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-3003 Update the replica.highWatermark co...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/688 KAFKA-3003 Update the replica.highWatermark correctly You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3003 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/688.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #688 commit d3f9edf89ac32f44413edc3d58e227fa2d859ca2 Author: Jiangjie Qin Date: 2015-12-17T06:52:11Z KAFKA-3003 Update the replica.highWatermark correctly --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2980 Fix deadlock when ZookeeperConsumer...
GitHub user becketqin reopened a pull request: https://github.com/apache/kafka/pull/660 KAFKA-2980 Fix deadlock when ZookeeperConsumerConnector create messag⦠You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2980 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/660.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #660 commit 6ad40206f354512b1f2db1e3784754ea29415ce7 Author: Jiangjie Qin Date: 2015-12-10T19:08:15Z KAKFA-2980 Fix deadlock when ZookeeperConsumerConnector create message streams. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2980 Fix deadlock when ZookeeperConsumer...
Github user becketqin closed the pull request at: https://github.com/apache/kafka/pull/660 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAKFA-2980 Fix deadlock when ZookeeperConsumer...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/660 KAKFA-2980 Fix deadlock when ZookeeperConsumerConnector create messag⦠You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2980 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/660.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #660 commit 6ad40206f354512b1f2db1e3784754ea29415ce7 Author: Jiangjie Qin Date: 2015-12-10T19:08:15Z KAKFA-2980 Fix deadlock when ZookeeperConsumerConnector create message streams. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2784: swallow exceptions when mirror mak...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/478 KAFKA-2784: swallow exceptions when mirror maker exits. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2784 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/478.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #478 commit 7272a4488780529cb0dc6a9e1abc14a6f8117cbe Author: Jiangjie Qin Date: 2015-11-10T00:01:13Z KAFKA-2784: swallow exceptions when mirror maker exits. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2722: Improve ISR change propagation.
GitHub user becketqin reopened a pull request: https://github.com/apache/kafka/pull/402 KAFKA-2722: Improve ISR change propagation. The patch has two changes: 1. fixed a bug in controller that it sends UpdateMetadataRequest of all the partitions in the cluster. 2. Uses the following rules to propagate ISR change: 1) if there are ISR changes pending propagation and the last ISR change is more than five seconds ago, propagate the changes. 2) if there is ISR change at T in the recent five seconds, delay the propagation until T + 5s. 3) if the last propagation is more than 1 min ago, ignore rule No.2 and propagate ISR change if there are changes pending propagation. This algorithm avoids a fixed configuration of ISR propagation interval as we discussed about in KIP-29. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2722 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/402.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #402 commit 13892856d806183536657f0c3ea2aa63b1f1c4f2 Author: Jiangjie Qin Date: 2015-11-02T01:26:27Z Improve ISR change propagation. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2722: Improve ISR change propagation.
Github user becketqin closed the pull request at: https://github.com/apache/kafka/pull/402 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: Improve ISR change propagation.
GitHub user becketqin reopened a pull request: https://github.com/apache/kafka/pull/402 Improve ISR change propagation. The patch has two changes: 1. fixed a bug in controller that it sends UpdateMetadataRequest of all the partitions in the cluster. 2. Uses the following rules to propagate ISR change: 1) if there are ISR changes pending propagation and the last ISR change is more than five seconds ago, propagate the changes. 2) if there is ISR change at T in the recent five seconds, delay the propagation until T + 5s. 3) if the last propagation is more than 1 min ago, ignore rule No.2 and propagate ISR change if there are changes pending propagation. This algorithm avoids a fixed configuration of ISR propagation interval as we discussed about in KIP-29. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2722 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/402.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #402 commit 13892856d806183536657f0c3ea2aa63b1f1c4f2 Author: Jiangjie Qin Date: 2015-11-02T01:26:27Z Improve ISR change propagation. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: Improve ISR change propagation.
Github user becketqin closed the pull request at: https://github.com/apache/kafka/pull/402 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: Improve ISR change propagation.
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/402 Improve ISR change propagation. The patch has two changes: 1. fixed a bug in controller that it sends UpdateMetadataRequest of all the partitions in the cluster. 2. Uses the following rules to propagate ISR change: 1) if there are ISR changes pending propagation and the last ISR change is more than five seconds ago, propagate the changes. 2) if there is ISR change at T in the recent five seconds, delay the propagation until T + 5s. 3) if the last propagation is more than 1 min ago, ignore rule No.2 and propagate ISR change if there are changes pending propagation. This algorithm avoids a fixed configuration of ISR propagation interval as we discussed about in KIP-29. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2722 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/402.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #402 commit 13892856d806183536657f0c3ea2aa63b1f1c4f2 Author: Jiangjie Qin Date: 2015-11-02T01:26:27Z Improve ISR change propagation. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2452: Add new consumer option to mirror ...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/266 KAFKA-2452: Add new consumer option to mirror maker. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2452 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/266.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #266 commit 2feafd6d2e67555c80545f2983f5a6d4674aab76 Author: Jiangjie Qin Date: 2015-09-02T23:51:28Z KAFKA-2452: Add new consumer option to mirror maker commit 5f52ac3af0a2817240e59c9c979baea8bc735a48 Author: Jiangjie Qin Date: 2015-09-30T17:45:46Z Expand the import --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2555: Infinite recursive function call w...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/221 KAFKA-2555: Infinite recursive function call when call commitSync in ⦠@hachikuji @ewencp I found this problem when adding new consumer to mirror maker which commits offset in the rebalance callback. It is not clear to me why we are triggering rebalance for commitSync() and fetchCommittedOffset(). Can you help review to see if I miss something? Regarding commitSync, After each poll() the partitions will be either assigned to a consumer or it will be already revoked. As long as user is using internal offset map, the offset map will always be valid. i.e. the offset map will always only contain the assigned partitions when commitSync is called. Hence there is no need to trigger a rebalance in commitSync(). The same guarantee also apply to fetchCommittedOffset(), isn't the only requirement is to ensure we know the coordinator? Another related issue is that today the IllegalGenerationIdException is a bit confusing. When we receive an IllegalGenerationIdException from heartbeat, we need to use that same generation Id to commit offset and the coordinator will take it. So the generation ID was not really illegal. I will file a ticket for this issue. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2555 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/221.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #221 commit 77b6a59eb926bf99773e7b53bf0e4b1610dc8277 Author: Jiangjie Qin Date: 2015-09-18T17:21:27Z KAFKA-2555: Infinite recursive function call when call commitSync in RebalanceListener.onPartitionRevoked() --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2477: Fix a race condition between log a...
Github user becketqin closed the pull request at: https://github.com/apache/kafka/pull/204 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2477: Fix a race condition between log a...
GitHub user becketqin reopened a pull request: https://github.com/apache/kafka/pull/204 KAFKA-2477: Fix a race condition between log append and fetch that causes OffsetOutOfRangeException. Tried two fixes. I prefer the second approach because it saves an additional offset search. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2477 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/204.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #204 commit e7610fb69a4007ae661a768635e930355c8caa76 Author: Jiangjie Qin Date: 2015-09-11T02:17:12Z KAFKA-2477: Fix a race condition between log append and fetch that causes OffsetOutOfRangeException commit 45364d76e756fc6075924b3a07651b7fbbcc391a Author: Jiangjie Qin Date: 2015-09-11T03:06:35Z A second fix that avoids an addition offset search --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: Kafka 2477
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/204 Kafka 2477 Tried two fixes. I prefer the second approach because it saves an additional offset search. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2477 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/204.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #204 commit e7610fb69a4007ae661a768635e930355c8caa76 Author: Jiangjie Qin Date: 2015-09-11T02:17:12Z KAFKA-2477: Fix a race condition between log append and fetch that causes OffsetOutOfRangeException commit 45364d76e756fc6075924b3a07651b7fbbcc391a Author: Jiangjie Qin Date: 2015-09-11T03:06:35Z A second fix that avoids an addition offset search --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2512: Add version check to broker and cl...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/200 KAFKA-2512: Add version check to broker and clients. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2512 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/200.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #200 commit 486476bd7e270b5f32e35df98d9d3921a665879b Author: Jiangjie Qin Date: 2015-09-08T14:47:56Z KAFKA-2512: Add version check to broker and clients. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2437: Fix ZookeeperLeaderElector to hand...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/189 KAFKA-2437: Fix ZookeeperLeaderElector to handle node deletion correctly. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2437 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/189.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #189 commit 11d9fd6595932553e138a3c3094322ebd9170d6c Author: Jiangjie Qin Date: 2015-09-03T00:41:26Z KAFKA-2437: Fix ZookeeperLeaderElector to handle node deletion correctly. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2454: Deadlock between log segment delet...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/153 KAFKA-2454: Deadlock between log segment deletion and server shutdown. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2454 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/153.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #153 commit 27c6a6e70f969ee13d857213d5a0aa3e40b1c19f Author: Jiangjie Qin Date: 2015-08-20T18:21:32Z KAFKA-2454: Deadlock between log segment deletion and server shutdown. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2402: Create IsrChangeNotificationPath w...
Github user becketqin closed the pull request at: https://github.com/apache/kafka/pull/108 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2389: remove commit type from new consum...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/134 KAFKA-2389: remove commit type from new consumer. A shot to remove commit type from new consumer. The coordinator constructor takes a default offset commit callback mainly for testing purpose. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2389 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/134.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #134 commit 5f332efa6c690fad730278283d8c419c6a223a8e Author: Jiangjie Qin Date: 2015-08-11T19:41:15Z KAFKA-2389: Remove commit type from commit() --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2134: fix replica offset truncate to beg...
Github user becketqin closed the pull request at: https://github.com/apache/kafka/pull/104 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2143: fix replica offset truncate to beg...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/129 KAFKA-2143: fix replica offset truncate to beginning during leader migration. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2143 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/129.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #129 commit 71f8a4716e1f0b4fc2bd88aa30fe38aef8a9f92e Author: Jiangjie Qin Date: 2015-08-03T02:22:02Z Fix for KAFKA-2134, fix replica offset truncate to beginning during leader migration. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2415: Fix transient failure in LogRecove...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/121 KAFKA-2415: Fix transient failure in LogRecoveryTest You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2415 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/121.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #121 commit 346103c410f0afd875f95770b47a9235e0bf8ed2 Author: Jiangjie Qin Date: 2015-08-07T03:25:57Z KAFKA-2415: Fix transient failure in LogRecoveryTest --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-1997: Follow-up patch, hardcode key/valu...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/120 KAFKA-1997: Follow-up patch, hardcode key/value serializer in mirror maker to byte serializer. Hardcode the key/value serializer to ByteArraySerializer according to Junâs comments. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-1997 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/120.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #120 commit 7f2e5a6ad9d43a4da8fdbcd5b2aaefa1de4c8963 Author: Jiangjie Qin Date: 2015-08-07T03:03:18Z KAFKA-1997: Follow-up patch, hardcode key/value serializer in mirror maker to byte serializer. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2406[WIP]: Throttle ISR propagation
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/114 KAFKA-2406[WIP]: Throttle ISR propagation This is a follow up patch for KAFKA-2406. Further test to verify if this change alone is enough to solve the problem or not. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2406 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/114.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #114 commit 27224779c21781e87353a28d060322bfc2c70be2 Author: Jiangjie Qin Date: 2015-08-05T07:09:06Z KAFKA-2406: Throttle ISR propagation --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2401: fix transient failure in ProducerS...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/113 KAFKA-2401: fix transient failure in ProducerSendTest.testCloseWithZeroTimeoutFromSenderThread You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2401 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/113.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #113 commit 7d4223df1325e42560a0d55a1b31f369157133e4 Author: Jiangjie Qin Date: 2015-08-05T01:36:54Z KAFKA-2401: fix transient failure in ProducerSendTest.testCloseWithZeroTimeoutFromSenderThread --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: KAFKA-2402: Create IsrChangeNotificationPath w...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/108 KAFKA-2402: Create IsrChangeNotificationPath when server statrs. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2402 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/108.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #108 commit 37e423066c5ff8a695a8fcde4f0c2e51832aa6b5 Author: Jiangjie Qin Date: 2015-08-04T05:36:20Z KAFKA-2402: Create IsrChangeNotificationPath when start the server. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] kafka pull request: Fix for KAFKA-2134, fix replica offset truncat...
GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/104 Fix for KAFKA-2134, fix replica offset truncate to beginning during leader migration. Fix replica truncate log to beginning during leader migration. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-2134 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/104.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #104 commit 71f8a4716e1f0b4fc2bd88aa30fe38aef8a9f92e Author: Jiangjie Qin Date: 2015-08-03T02:22:02Z Fix for KAFKA-2134, fix replica offset truncate to beginning during leader migration. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
