[GitHub] kafka pull request #1801: MINOR: Include TopicPartition in warning when log ...
GitHub user dpkp opened a pull request: https://github.com/apache/kafka/pull/1801 MINOR: Include TopicPartition in warning when log cleaner resets dirty offset Typically this error condition is caused by topic-level configuration issues, so it is useful to say include which topic partition was reset for operator use when debugging the root cause. You can merge this pull request into a Git repository by running: $ git pull https://github.com/dpkp/kafka log_topic_partition_reset_dirty_offset Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1801.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 #1801 commit aa5de24f3d302fda5e8bd1196d16a3723c81f4f3 Author: Dana Powers <dana.pow...@gmail.com> Date: 2016-08-30T16:09:31Z MINOR: Include TopicPartition in warning message when log cleaner resets dirty offset --- 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 #1523: Support exponential backoff policy via reconnect.b...
GitHub user dpkp opened a pull request: https://github.com/apache/kafka/pull/1523 Support exponential backoff policy via reconnect.backoff.max This PR is an alternate / simplified approach to alternate backoff policies than KIP-53 and KAFKA-3496. Summary: * add `reconnect.backoff.max` common client configuration parameter * if `reconnect.backoff.max` > `reconnect.backoff.ms`, apply an exponential backoff policy * select actual backoff per node via uniform random distribution to smooth cluster reconnects You can merge this pull request into a Git repository by running: $ git pull https://github.com/dpkp/kafka exp_backoff Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1523.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 #1523 commit 04bf44a44dbd74c60577bb653089b7c455491926 Author: Dana Powers <dana.pow...@gmail.com> Date: 2016-06-19T17:03:37Z Support exponential backoff policy via reconnect.backoff.max --- 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: Fixup KAFKA-3160: catch decompression errors i...
GitHub user dpkp opened a pull request: https://github.com/apache/kafka/pull/1344 Fixup KAFKA-3160: catch decompression errors in constructor After testing KAFKA-3160 a bit more, I found that the error code was not being set properly in ProduceResponse. This happened because the validation error is raised in the CompressionFactory constructor, which was not wrapped in a try / catch. @ijuma @junrao (This contribution is my original work and I license the work under Apache 2.0.) You can merge this pull request into a Git repository by running: $ git pull https://github.com/dpkp/kafka decompress_error_code Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1344.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 #1344 commit bac92e133cb80aa13ee155a1200bf085947376b7 Author: Dana Powers <dana.pow...@gmail.com> Date: 2016-05-09T01:54:22Z Fixup to KAFKA-3160: catch decompression errors in constructor; return CorruptMessageError --- 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 main classpath libs glob for release (fixu...
GitHub user dpkp opened a pull request: https://github.com/apache/kafka/pull/1302 Fix main classpath libs glob for release (fixup KAFKA-3615 regression) bin/kafka-run-class.sh does not correctly setup the CLASSPATH in release rc2. You can merge this pull request into a Git repository by running: $ git pull https://github.com/dpkp/kafka KAFKA-3615-fix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1302.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 #1302 commit fb67470da3e8487f30cca4f186df6f80ba7272a6 Author: Dana Powers <dana.pow...@gmail.com> Date: 2016-05-01T01:05:56Z Fix main classpath libs glob for release (fixup KAFKA-3615 regression) --- 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-3160: Fix LZ4 Framing
GitHub user dpkp opened a pull request: https://github.com/apache/kafka/pull/1212 KAFKA-3160: Fix LZ4 Framing This contribution is my original work and I license the work under Apache 2.0. You can merge this pull request into a Git repository by running: $ git pull https://github.com/dpkp/kafka KAFKA-3160 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1212.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 #1212 commit b64e5f9f054131ae7bf6b9a10be861f5fb0caeab Author: Dana Powers <dana.pow...@gmail.com> Date: 2016-04-11T04:35:43Z Update KafkaLZ4Block* implementation to 1.5.1 framing spec - update spec to 1.5.1; remove dictID - fix frame descriptor HC check (dont include magic bytes) - dont require HC validation on input by default - add useBrokenHC boolean for output compatibility - nominal support for contentChecksum / contentSize flags commit f1380d0e5f6e1e9d7b48a9cff3fbcd13b7a5fe3f Author: Dana Powers <dana.pow...@gmail.com> Date: 2016-04-11T05:35:31Z KAFKA-3160: use LZ4 v1.5.1 framing for all v1 messages; keep old framing for v0 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: Add expected Error Codes to ProduceResponse do...
GitHub user dpkp opened a pull request: https://github.com/apache/kafka/pull/918 Add expected Error Codes to ProduceResponse documentation This is a documentation-only patch discussed on the mailing list. The intent is to have these changes propagated to the protocol wiki (https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol) . You can merge this pull request into a Git repository by running: $ git pull https://github.com/dpkp/kafka produce_response_errors Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/918.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 #918 commit 03db2c60b4cb394ba96112f5ec106816f316de87 Author: Dana Powers <dana.pow...@gmail.com> Date: 2016-02-15T19:51:13Z Add expected Error Codes to ProduceResponse 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. ---
