[jira] [Commented] (KAFKA-3494) mbeans overwritten with identical clients on a single jvm

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

[GitHub] kafka pull request: KAFKA-3494: add metric id to client mbeans

GitHub user onurkaraman opened a pull request: https://github.com/apache/kafka/pull/1323 KAFKA-3494: add metric id to client mbeans KafkaConsumer and KafkaProducer mbeans currently only have a client-id granularity. Client-id represents a logical name for an application. Gi

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

See

[jira] [Commented] (KAFKA-3659) Consumer does not handle coordinator connection blackout period gracefully

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

[GitHub] kafka pull request: KAFKA-3659: Handle coordinator disconnects mor...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1322 KAFKA-3659: Handle coordinator disconnects more gracefully in client You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-365

[jira] [Commented] (KAFKA-3656) Avoid stressing system more when already under stress

[ https://issues.apache.org/jira/browse/KAFKA-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15271880#comment-15271880 ] Alexey Raga commented on KAFKA-3656: Also, can it be backported to 0.9.0.1 ? It causes

[jira] [Commented] (KAFKA-3656) Avoid stressing system more when already under stress

[ https://issues.apache.org/jira/browse/KAFKA-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15271876#comment-15271876 ] Alexey Raga commented on KAFKA-3656: Thanks, are the binaries published somewhere? >

[jira] [Reopened] (KAFKA-725) Broker Exception: Attempt to read with a maximum offset less than start offset

[ https://issues.apache.org/jira/browse/KAFKA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao reopened KAFKA-725: --- Reopen this jira since the fix exposes a new issue. When the leader switches (say due to leader balancing), the ne

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

See Changes: [me] KAFKA-3527: Consumer commitAsync should not expose internal exceptions [me] MINOR: Fixes to AWS init script for testing -- [...truncated 2194 lines...] kafka.admin.AdminRackA

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

See Changes: [junrao] KAFKA-3652; Return error response for unsupported version of -- [...truncated 3305 lines...] kafka.integration.AutoOffsetResetTest > testResetToEarliestWhenOffsetTooHigh P

[GitHub] kafka pull request: MINOR: Add Kafka Streams API / upgrade notes

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1321 MINOR: Add Kafka Streams API / upgrade notes You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka KStreamsJavaDoc Alternativ

Build failed in Jenkins: kafka-0.10.0-jdk7 #52

See Changes: [me] KAFKA-3527: Consumer commitAsync should not expose internal exceptions -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H10 (do

[GitHub] kafka pull request: Minor fixes to AWS init script for testing

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1309 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-3527) Consumer commitAsync should not expose internal exceptions

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

[jira] [Resolved] (KAFKA-3527) Consumer commitAsync should not expose internal exceptions

[ https://issues.apache.org/jira/browse/KAFKA-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-3527. -- Resolution: Fixed Fix Version/s: 0.10.0.0 0.10.1.0 Iss

[GitHub] kafka pull request: KAFKA-3527: Consumer commitAsync should not ex...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1300 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15271795#comment-15271795 ] Jiangjie Qin commented on KAFKA-3565: - [~junrao] I noticed that the consumer tests fin

Build failed in Jenkins: kafka-0.10.0-jdk7 #51

See Changes: [junrao] KAFKA-3652; Return error response for unsupported version of -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H10 (docker U

Build failed in Jenkins: kafka-0.10.0-jdk7 #50

See Changes: [ismael] KAFKA-3639; Configure default serdes upon construction -- [...truncated 8717 lines...] org.apache.kafka.connect.storage.KafkaStatusBackingStoreTest > readConnectorState PA

[jira] [Resolved] (KAFKA-3652) Return error response for unsupported version of ApiVersionsRequest

[ https://issues.apache.org/jira/browse/KAFKA-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-3652. Resolution: Fixed Committed the PR to 0.10.0. > Return error response for unsupported version of ApiVersion

[jira] [Commented] (KAFKA-3652) Return error response for unsupported version of ApiVersionsRequest

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

[GitHub] kafka pull request: KAFKA-3652: Return error response for unsuppor...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1310 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Assigned] (KAFKA-3101) Optimize Aggregation Outputs

[ https://issues.apache.org/jira/browse/KAFKA-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck reassigned KAFKA-3101: -- Assignee: Bill Bejeck > Optimize Aggregation Outputs > > >

[jira] [Work started] (KAFKA-3101) Optimize Aggregation Outputs

[ https://issues.apache.org/jira/browse/KAFKA-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3101 started by Bill Bejeck. -- > Optimize Aggregation Outputs > > > Key

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

See

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

See Changes: [ismael] KAFKA-3639; Configure default serdes upon construction -- [...truncated 4363 lines...] kafka.admin.AdminRackAwareTest > testAssignmentWith2ReplicasRackAwareWith6Partitions

[jira] [Updated] (KAFKA-3160) Kafka LZ4 framing code miscalculates header checksum

[ https://issues.apache.org/jira/browse/KAFKA-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3160: --- Assignee: Dana Powers (was: Magnus Edenhill) > Kafka LZ4 framing code miscalculates header checksum >

Build failed in Jenkins: kafka-0.10.0-jdk7 #49

See Changes: [me] KAFKA 3656: Remove logging outstanding messages when producer flush -- [...truncated 8289 lines...] org.apache.kafka.connect.storage.KafkaStatusBackingStoreTest > readConnecto

Re: [VOTE] KIP-57: Interoperable LZ4 Framing

Thanks for the response. +1 on the KIP. Jun On Thu, Apr 28, 2016 at 9:01 AM, Dana Powers wrote: > Sure thing. Yes, the substantive change is fixing the HC checksum. > > But to further improve interoperability, the kafka LZ4 class would no > longer reject messages that have these optional header

[jira] [Updated] (KAFKA-3659) Consumer does not handle coordinator connection blackout period gracefully

[ https://issues.apache.org/jira/browse/KAFKA-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3659: --- Summary: Consumer does not handle coordinator connection blackout period gracefully (was: Con

[jira] [Created] (KAFKA-3659) Consumer handle coordinator connection blackout period

Jason Gustafson created KAFKA-3659: -- Summary: Consumer handle coordinator connection blackout period Key: KAFKA-3659 URL: https://issues.apache.org/jira/browse/KAFKA-3659 Project: Kafka Issu

[jira] [Resolved] (KAFKA-3639) Configure default serdes passed via StreamsConfig

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

[jira] [Commented] (KAFKA-3639) Configure default serdes passed via StreamsConfig

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

[GitHub] kafka pull request: KAFKA-3639: Configure default serdes upon cons...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1311 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

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

See Changes: [me] KAFKA 3656: Remove logging outstanding messages when producer flush -- [...truncated 114 lines...] 1 warning :kafka-trunk-jdk8:clients:processTestResources :kafka-trunk-jdk8:cl

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

See Changes: [wangguoz] KAFKA-2236; Offset request reply racing with segment rolling -- [...truncated 8588 lines...] org.apache.kafka.connect.storage.KafkaStatusBackingStoreTest > readConnector

[jira] [Updated] (KAFKA-3656) Avoid stressing system more when already under stress

[ https://issues.apache.org/jira/browse/KAFKA-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3656: - Resolution: Fixed Reviewer: Ewen Cheslack-Postava Fix Version/s: 0.

[GitHub] kafka pull request: added description for lag in consumer group co...

GitHub user coughman opened a pull request: https://github.com/apache/kafka/pull/1320 added description for lag in consumer group command You can merge this pull request into a Git repository by running: $ git pull https://github.com/coughman/kafka trunk Alternatively you can

[GitHub] kafka pull request: KAFKA 3656: Remove logging outstanding message...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1319 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Updated] (KAFKA-3658) RocksDBWindowStore should guarantee a single window locates completely in one segment

[ https://issues.apache.org/jira/browse/KAFKA-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3658: - Fix Version/s: (was: 0.10.0.0) 0.10.0.1 > RocksDBWindowStore should guarant

[jira] [Created] (KAFKA-3658) RocksDBWindowStore should guarantee a single window locates completely in one segment

Guozhang Wang created KAFKA-3658: Summary: RocksDBWindowStore should guarantee a single window locates completely in one segment Key: KAFKA-3658 URL: https://issues.apache.org/jira/browse/KAFKA-3658 P

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

See Changes: [wangguoz] KAFKA-2236; Offset request reply racing with segment rolling -- [...truncated 8610 lines...] org.apache.kafka.connect.storage.KafkaStatusBackingStoreTest > readConnecto

Build failed in Jenkins: kafka-0.10.0-jdk7 #48

See Changes: [wangguoz] KAFKA-2236; Offset request reply racing with segment rolling -- [...truncated 39 lines...] :core:clean :examples:clean :log4j-appender:clean :streams:clean :tools:clean :c

[jira] [Updated] (KAFKA-3627) New consumer doesn't run delayed tasks while under load

[ https://issues.apache.org/jira/browse/KAFKA-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3627: --- Priority: Blocker (was: Critical) > New consumer doesn't run delayed tasks while under load >

Build failed in Jenkins: kafka-0.10.0-jdk7 #47

See Changes: [wangguoz] MINOR: Modify checkstyle to allow import classes only used in javadoc [wangguoz] MINOR: Added more integration tests [wangguoz] KAFKA-3642: Fix NPE from ProcessorStateManager when the changelog topic

[jira] [Commented] (KAFKA-3525) max.reserved.broker.id off-by-one error

[ https://issues.apache.org/jira/browse/KAFKA-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15271527#comment-15271527 ] Gwen Shapira commented on KAFKA-3525: - This will wait for the next release. The max re

[jira] [Updated] (KAFKA-3525) max.reserved.broker.id off-by-one error

[ https://issues.apache.org/jira/browse/KAFKA-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3525: Fix Version/s: (was: 0.10.0.0) 0.10.1.0 > max.reserved.broker.id off-by-one e

[jira] [Updated] (KAFKA-2236) offset request reply racing with segment rolling

[ https://issues.apache.org/jira/browse/KAFKA-2236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2236: - Resolution: Fixed Fix Version/s: 0.10.0.0 Status: Resolved (was: Patch Available

[jira] [Updated] (KAFKA-2236) offset request reply racing with segment rolling

[ https://issues.apache.org/jira/browse/KAFKA-2236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2236: - Assignee: William Thurston (was: Jason Gustafson) > offset request reply racing with segment roll

[jira] [Commented] (KAFKA-2236) offset request reply racing with segment rolling

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

[GitHub] kafka pull request: KAFKA-2236; Offset request reply racing with s...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1318 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

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

See Changes: [ismael] KAFKA-3632; remove fetcher metrics on shutdown and leader migration -- [...truncated 8287 lines...] org.apache.kafka.connect.storage.KafkaStatusBackingStoreTest > readCon

list of challenges encountered using 0.9.0.1

While at the Kafka Summit I was asked to write up a list of challenges and confusions my team encountered using Kafka. We are using 0.9.0.1 and use the new Java KakfaConsumer. 1. The new Java KafkaConsumer doesn’t have a method to return the high watermark (last offset in the topic/partiti

Build failed in Jenkins: kafka-0.10.0-jdk7 #46

See Changes: [ismael] KAFKA-3632; remove fetcher metrics on shutdown and leader migration -- [...truncated 8606 lines...] org.apache.kafka.connect.storage.KafkaStatusBackingStoreTest > readConn

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

See Changes: [wangguoz] MINOR: Modify checkstyle to allow import classes only used in javadoc [ismael] KAFKA-3632; remove fetcher metrics on shutdown and leader migration -- [...truncated 4398 l

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

See

[jira] [Updated] (KAFKA-3632) ConsumerLag metrics persist after partition migration

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

[jira] [Commented] (KAFKA-3632) ConsumerLag metrics persist after partition migration

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

[GitHub] kafka pull request: KAFKA-3632: remove fetcher metrics on shutdown...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1312 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15271185#comment-15271185 ] Jun Rao commented on KAFKA-3565: [~becket_qin], thanks for the results. As I was looking a

[jira] [Updated] (KAFKA-2236) offset request reply racing with segment rolling

[ https://issues.apache.org/jira/browse/KAFKA-2236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2236: --- Reviewer: Guozhang Wang Status: Patch Available (was: Open) > offset request reply racing with

[GitHub] kafka pull request: MINOR: Modify checkstyle to allow import class...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1317 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-725) Broker Exception: Attempt to read with a maximum offset less than start offset

[ https://issues.apache.org/jira/browse/KAFKA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15271051#comment-15271051 ] Jiangjie Qin commented on KAFKA-725: [~junrao] I asked this question in the RB. It seem

[jira] [Resolved] (KAFKA-3646) Console producer using new producer should set timestamp

[ https://issues.apache.org/jira/browse/KAFKA-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3646. -- Resolution: Not A Bug This is not an issue as {{KafkaProducer}} already set timestamp as current

[jira] [Updated] (KAFKA-3656) Avoid stressing system more when already under stress

[ https://issues.apache.org/jira/browse/KAFKA-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei updated KAFKA-3656: -- Status: Patch Available (was: In Progress) > Avoid stressing system more when already under stress > --

[jira] [Work started] (KAFKA-3656) Avoid stressing system more when already under stress

[ https://issues.apache.org/jira/browse/KAFKA-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3656 started by Liquan Pei. - > Avoid stressing system more when already under stress > -

[GitHub] kafka pull request: KAFKA 3656: Remove logging outstanding message...

GitHub user Ishiihara opened a pull request: https://github.com/apache/kafka/pull/1319 KAFKA 3656: Remove logging outstanding messages when producer flush fails You can merge this pull request into a Git repository by running: $ git pull https://github.com/Ishiihara/kafka kaf

[jira] [Commented] (KAFKA-3657) NewProducer NullPointerException on ProduceRequest

[ https://issues.apache.org/jira/browse/KAFKA-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15271007#comment-15271007 ] Vamsi Subhash Achanta commented on KAFKA-3657: -- I haven't tested it against 0

[jira] [Commented] (KAFKA-3649) Add capability to query broker process for configuration properties

[ https://issues.apache.org/jira/browse/KAFKA-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15270996#comment-15270996 ] Grant Henke commented on KAFKA-3649: [~liquanpei] I see you assigned yourself to this.

[jira] [Assigned] (KAFKA-3649) Add capability to query broker process for configuration properties

[ https://issues.apache.org/jira/browse/KAFKA-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei reassigned KAFKA-3649: - Assignee: Liquan Pei > Add capability to query broker process for configuration properties >

[jira] [Assigned] (KAFKA-3656) Avoid stressing system more when already under stress

[ https://issues.apache.org/jira/browse/KAFKA-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei reassigned KAFKA-3656: - Assignee: Liquan Pei > Avoid stressing system more when already under stress > --

Re: [jira] [Updated] (KAFKA-3160) Kafka LZ4 framing code miscalculates header checksum

You can assign to me also

Re: [DISCUSS] KIP-48 Support for delegation tokens as an authentication mechanism

Thanks for reviewing Gwen. The wiki already has details on token expiration under token acquisition process . Current proposal is that tokens will expir

[jira] [Updated] (KAFKA-3525) max.reserved.broker.id off-by-one error

[ https://issues.apache.org/jira/browse/KAFKA-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3525: --- Priority: Major (was: Blocker) > max.reserved.broker.id off-by-one error > --

[jira] [Updated] (KAFKA-3160) Kafka LZ4 framing code miscalculates header checksum

[ https://issues.apache.org/jira/browse/KAFKA-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3160: --- Fix Version/s: 0.10.0.0 > Kafka LZ4 framing code miscalculates header checksum > -

[jira] [Updated] (KAFKA-3160) Kafka LZ4 framing code miscalculates header checksum

[ https://issues.apache.org/jira/browse/KAFKA-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3160: --- Priority: Critical (was: Major) > Kafka LZ4 framing code miscalculates header checksum >

[jira] [Updated] (KAFKA-3652) Return error response for unsupported version of ApiVersionsRequest

[ https://issues.apache.org/jira/browse/KAFKA-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3652: --- Priority: Blocker (was: Major) > Return error response for unsupported version of ApiVersionsRequest

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

See Changes: [ismael] KAFKA-2684; Add force option to topic / config command so they can be -- [...truncated 2475 lines...] kafka.api.SslEndToEndAuthorizationTest > testNoConsumeAcl PASSED kaf

[jira] [Commented] (KAFKA-3657) NewProducer NullPointerException on ProduceRequest

[ https://issues.apache.org/jira/browse/KAFKA-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15270823#comment-15270823 ] Ismael Juma commented on KAFKA-3657: Thanks for the bug report. Do you know if this ha

[jira] [Commented] (KAFKA-725) Broker Exception: Attempt to read with a maximum offset less than start offset

[ https://issues.apache.org/jira/browse/KAFKA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15270789#comment-15270789 ] Jun Rao commented on KAFKA-725: --- [~Srdo], thanks for the patch. It's still not very clear to

[jira] [Created] (KAFKA-3657) NewProducer NullPointerException on ProduceRequest

Vamsi Subhash Achanta created KAFKA-3657: Summary: NewProducer NullPointerException on ProduceRequest Key: KAFKA-3657 URL: https://issues.apache.org/jira/browse/KAFKA-3657 Project: Kafka

[jira] [Updated] (KAFKA-3657) NewProducer NullPointerException on ProduceRequest

[ https://issues.apache.org/jira/browse/KAFKA-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsi Subhash Achanta updated KAFKA-3657: - Description: The producer upon send.get() on the future appends to the accumulator

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

See Changes: [ismael] KAFKA-2684; Add force option to topic / config command so they can be -- [...truncated 1643 lines...] kafka.controller.ControllerFailoverTest > testMetadataUpdate PASSED k

How to write Connect logs to file?

How to write Kafka Connect logs to a rolling file? It runs in a distributed environment. Adding a log4j.properties file doesn't seem to work. What are other ways I could do the same? -- Anish Samir Mashankar

Fwd: How to build kafka jar with all dependencies?

Hello All, I used .*/gradlew jarAll* but still scala ​dependent ​ libs are missing from the jar? ​It should be something ​very simple which I might be missing. Please let me know if anyone knows. -- *Regards,* *Ravi*

[jira] [Updated] (KAFKA-2684) Add force option to TopicCommand & ConfigCommand to suppress console prompts

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

[jira] [Commented] (KAFKA-2684) Add force option to TopicCommand & ConfigCommand to suppress console prompts

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

[GitHub] kafka pull request: KAFKA-2684: Add force option to topic / config...

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

Re: [DISCUSS] KIP-48 Support for delegation tokens as an authentication mechanism

Harsha, I was thinking of the Rest Proxy. I didn't see your design yet, but in our proxy, we have a set of producers, which will serve multiple users going through the proxy. Since these users will have different privileges, they'll need to authenticate separately, and can't share a token. Am I m

[jira] [Commented] (KAFKA-3647) Unable to set a ssl provider

[ https://issues.apache.org/jira/browse/KAFKA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15270550#comment-15270550 ] Rajini Sivaram commented on KAFKA-3647: --- {{ssl.provider}} is the name of the provide

[jira] [Commented] (KAFKA-3647) Unable to set a ssl provider / only DSS ciphers available

[ https://issues.apache.org/jira/browse/KAFKA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15270520#comment-15270520 ] Elvar commented on KAFKA-3647: -- Found the problem with the ciphers, when you create the keyst

[jira] [Updated] (KAFKA-3647) Unable to set a ssl provider / only DSS ciphers available

[ https://issues.apache.org/jira/browse/KAFKA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elvar updated KAFKA-3647: - Priority: Minor (was: Major) > Unable to set a ssl provider / only DSS ciphers available > --

[jira] [Updated] (KAFKA-3647) Unable to set a ssl provider

[ https://issues.apache.org/jira/browse/KAFKA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elvar updated KAFKA-3647: - Summary: Unable to set a ssl provider (was: Unable to set a ssl provider / only DSS ciphers available) > Unable

[jira] [Updated] (KAFKA-3652) Return error response for unsupported version of ApiVersionsRequest

[ https://issues.apache.org/jira/browse/KAFKA-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3652: -- Description: Discussion is in the PR https://github.com/apache/kafka/pull/1286. Dont fail authe

[jira] [Updated] (KAFKA-3647) Unable to set a ssl provider / only DSS ciphers available

[ https://issues.apache.org/jira/browse/KAFKA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elvar updated KAFKA-3647: - Summary: Unable to set a ssl provider / only DSS ciphers available (was: Unable to set a ssl provider) > Unable

[jira] [Commented] (KAFKA-3647) Unable to set a ssl provider

[ https://issues.apache.org/jira/browse/KAFKA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15270468#comment-15270468 ] Elvar commented on KAFKA-3647: -- Regarding the ssl provider in the Kafka config, has anyone go

[jira] [Commented] (KAFKA-3647) Unable to set a ssl provider

[ https://issues.apache.org/jira/browse/KAFKA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15270467#comment-15270467 ] Elvar commented on KAFKA-3647: -- Tried recreating the JKS's and this is how I did it {code} G

[jira] [Updated] (KAFKA-3448) Support zone index in IPv6 regex

[ https://issues.apache.org/jira/browse/KAFKA-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3448: --- Assignee: Soumyajit Sahu > Support zone index in IPv6 regex > > >

[jira] [Commented] (KAFKA-3647) Unable to set a ssl provider

[ https://issues.apache.org/jira/browse/KAFKA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15270401#comment-15270401 ] Elvar commented on KAFKA-3647: -- Yes, tried with OpenJDK 1.7 and 1.8 and the Oracle JRE with a

[jira] [Resolved] (KAFKA-3147) Memory records is not writable in MirrorMaker

[ https://issues.apache.org/jira/browse/KAFKA-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3147. Resolution: Fixed Thanks [~omkreddy], closing again. > Memory records is not writable in MirrorMake

  1   2   >