[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=15270149#comment-15270149 ] Taiyuan Zhang commented on KAFKA-3649: -- When you're talking about configuration settings, are you

[jira] [Commented] (KAFKA-3585) Shutdown slow when there is only one broker which is controller

[ https://issues.apache.org/jira/browse/KAFKA-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15270140#comment-15270140 ] Taiyuan Zhang commented on KAFKA-3585: -- How to check? I saw outputs like "New leader is 2", does that

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

See Changes: [ismael] MINOR: Handle null values in validators -- [...truncated 6363 lines...] org.apache.kafka.connect.runtime.rest.resources.ConnectorsResourceTest >

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

See

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

Alexey Raga created KAFKA-3656: -- Summary: Avoid stressing system more when already under stress Key: KAFKA-3656 URL: https://issues.apache.org/jira/browse/KAFKA-3656 Project: Kafka Issue Type:

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

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1317 MINOR: Modify checkstyle to allow import classes only used in javadoc You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka

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

See Changes: [me] KAFKA-3654: Config validation should validate both common and connector -- [...truncated 6110 lines...] org.apache.kafka.connect.storage.KafkaOffsetBackingStoreTest >

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

See Changes: [me] KAFKA-3654: Config validation should validate both common and connector -- [...truncated 3977 lines...] org.apache.kafka.common.protocol.types.ProtocolSerializationTest >

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

See

[jira] [Commented] (KAFKA-3173) Error while moving some partitions to OnlinePartition state

[ https://issues.apache.org/jira/browse/KAFKA-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269978#comment-15269978 ] Jun Rao commented on KAFKA-3173: [~fpj], thanks the analysis. It seems that the whole

[GitHub] kafka pull request: MINOR: Handle null values in validators.

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

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

See Changes: [ismael] MINOR: Clean up of ConsumerCoordinator and PartitionAssignor [ismael] KAFKA-3648; maxTimeToBlock in BufferPool.allocate should be enforced -- [...truncated 1676 lines...]

[jira] [Commented] (KAFKA-3654) Config validation should validate both common and connector specific configurations

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

[jira] [Resolved] (KAFKA-3654) Config validation should validate both common and connector specific configurations

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

[GitHub] kafka pull request: KAFKA-3654: Config validation should validate ...

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

[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: (was: Bill Bejeck) > Optimize Aggregation Outputs >

[jira] [Work stopped] (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 stopped by Bill Bejeck. -- > Optimize Aggregation Outputs > > >

[jira] [Commented] (KAFKA-3651) Whenever the BufferPool throws a "Failed to allocate memory within the configured max blocking time" exception, it should also remove the condition object from the wait

[ https://issues.apache.org/jira/browse/KAFKA-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269937#comment-15269937 ] Mayuresh Gharat commented on KAFKA-3651: [~amandazhu19620...@gmail.com] did you intend to open a

[GitHub] kafka pull request: MINOR: Handle null values in validators.

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/1316 MINOR: Handle null values in validators. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ewencp/kafka minor-handle-null-values-validators

[jira] [Commented] (KAFKA-3651) Whenever the BufferPool throws a "Failed to allocate memory within the configured max blocking time" exception, it should also remove the condition object from the wait

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

[GitHub] kafka pull request: KAFKA-3651; awaitFlushCompletion() in RecordAc...

GitHub user zhuchen1018 opened a pull request: https://github.com/apache/kafka/pull/1315 KAFKA-3651; awaitFlushCompletion() in RecordAccumulator should always decrement flushesInProgress count You can merge this pull request into a Git repository by running: $ git pull

[jira] [Updated] (KAFKA-3655) awaitFlushCompletion() in RecordAccumulator should always decrement flushesInProgress count.

[ https://issues.apache.org/jira/browse/KAFKA-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-3655: Assignee: chen zhu (was: Dong Lin) > awaitFlushCompletion() in RecordAccumulator should always decrement

[jira] [Created] (KAFKA-3655) awaitFlushCompletion() in RecordAccumulator should always decrement flushesInProgress count.

Dong Lin created KAFKA-3655: --- Summary: awaitFlushCompletion() in RecordAccumulator should always decrement flushesInProgress count. Key: KAFKA-3655 URL: https://issues.apache.org/jira/browse/KAFKA-3655

[jira] [Commented] (KAFKA-3651) Whenever the BufferPool throws a "Failed to allocate memory within the configured max blocking time" exception, it should also remove the condition object from the wait

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

[GitHub] kafka pull request: KAFKA-3651 : Remove the condition variable wai...

GitHub user MayureshGharat opened a pull request: https://github.com/apache/kafka/pull/1314 KAFKA-3651 : Remove the condition variable waiting on memory availabilty in Bufferpool when a TimeoutException is thrown Whenever the BufferPool throws a "Failed to allocate memory within

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

See -- [...truncated 2949 lines...] kafka.integration.PlaintextTopicMetadataTest > testIsrAfterBrokerShutDownAndJoinsBack PASSED kafka.integration.PlaintextTopicMetadataTest >

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

See -- [...truncated 2966 lines...] kafka.integration.PlaintextTopicMetadataTest > testBasicTopicMetadata PASSED kafka.integration.PlaintextTopicMetadataTest >

[jira] [Commented] (KAFKA-3654) Config validation should validate both common and connector specific configurations

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

[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=15269854#comment-15269854 ] Jiangjie Qin commented on KAFKA-3565: - Woops...Touched the the yubi key accidentally... > Producer's

[jira] [Updated] (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:all-tabpanel ] Jiangjie Qin updated KAFKA-3565: Summary: Producer's throughput lower with compressed data after KIP-31/32 (was:

[GitHub] kafka pull request: KAFKA-3654: Config validation should validate ...

GitHub user Ishiihara opened a pull request: https://github.com/apache/kafka/pull/1313 KAFKA-3654: Config validation should validate both common and connector specific configurations You can merge this pull request into a Git repository by running: $ git pull

[jira] [Updated] (KAFKA-3654) Config validation should validate both common and connector specific configurations

[ https://issues.apache.org/jira/browse/KAFKA-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei updated KAFKA-3654: -- Summary: Config validation should validate both common and connector specific configurations (was:

[jira] [Updated] (KAFKA-3654) ConnectorConfig short circuit implementation config validation

[ https://issues.apache.org/jira/browse/KAFKA-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei updated KAFKA-3654: -- Description: Right now if you call the validate endpoint with a config that has an invalid value for

[jira] [Updated] (KAFKA-3654) ConnectorConfig short circuit implementation config validation

[ https://issues.apache.org/jira/browse/KAFKA-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei updated KAFKA-3654: -- Summary: ConnectorConfig short circuit implementation config validation (was: ConnectorConfig defs

[jira] [Created] (KAFKA-3654) ConnectorConfig defs short circuit implementation config checks

Liquan Pei created KAFKA-3654: - Summary: ConnectorConfig defs short circuit implementation config checks Key: KAFKA-3654 URL: https://issues.apache.org/jira/browse/KAFKA-3654 Project: Kafka

[jira] [Commented] (KAFKA-3651) Whenever the BufferPool throws a "Failed to allocate memory within the configured max blocking time" exception, it should also remove the condition object from the wait

[ https://issues.apache.org/jira/browse/KAFKA-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269841#comment-15269841 ] Ismael Juma commented on KAFKA-3651: Great, make sure to pull from trunk as the other JIRA that

[jira] [Updated] (KAFKA-3651) Whenever the BufferPool throws a "Failed to allocate memory within the configured max blocking time" exception, it should also remove the condition object from the waiter

[ https://issues.apache.org/jira/browse/KAFKA-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3651: --- Fix Version/s: 0.10.0.0 > Whenever the BufferPool throws a "Failed to allocate memory within the >

[jira] [Commented] (KAFKA-3651) Whenever the BufferPool throws a "Failed to allocate memory within the configured max blocking time" exception, it should also remove the condition object from the wait

[ https://issues.apache.org/jira/browse/KAFKA-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269837#comment-15269837 ] Mayuresh Gharat commented on KAFKA-3651: [~ijuma] Yes just working on the unit test. > Whenever

[jira] [Commented] (KAFKA-3565) bceunbfjcvtdvidckvjrrcklvtdnjgvlj

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269836#comment-15269836 ] Guozhang Wang commented on KAFKA-3565: -- [~becket_qin] JIRA title? :) >

[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: --- Reviewer: Ismael Juma Status: Patch Available (was: Open) > ConsumerLag metrics persist after

[jira] [Commented] (KAFKA-3173) Error while moving some partitions to OnlinePartition state

[ https://issues.apache.org/jira/browse/KAFKA-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269832#comment-15269832 ] Ismael Juma commented on KAFKA-3173: [~gwenshap], the PR has been ready for a while, we need [~junrao]

[jira] [Commented] (KAFKA-3651) Whenever the BufferPool throws a "Failed to allocate memory within the configured max blocking time" exception, it should also remove the condition object from the wait

[ https://issues.apache.org/jira/browse/KAFKA-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269821#comment-15269821 ] Ismael Juma commented on KAFKA-3651: [~mgharat], are you planning to submit a PR for this soon? >

[jira] [Resolved] (KAFKA-3648) maxTimeToBlock should be enforced

[ https://issues.apache.org/jira/browse/KAFKA-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3648. Resolution: Fixed Fix Version/s: 0.10.0.0 > maxTimeToBlock should be enforced >

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

See

[jira] [Updated] (KAFKA-3648) maxTimeToBlock in BufferPool.allocate should be enforced

[ https://issues.apache.org/jira/browse/KAFKA-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3648: --- Summary: maxTimeToBlock in BufferPool.allocate should be enforced (was: maxTimeToBlock should be

[jira] [Commented] (KAFKA-3648) maxTimeToBlock should be enforced

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

[GitHub] kafka pull request: KAFKA-3648; maxTimeToBlock in BufferPool.alloc...

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

[jira] [Commented] (KAFKA-3565) bceunbfjcvtdvidckvjrrcklvtdnjgvlj

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269805#comment-15269805 ] Jun Rao commented on KAFKA-3565: [~becket_qin], thanks for the new results. Could you also test consumer

[jira] [Updated] (KAFKA-3651) Whenever the BufferPool throws a "Failed to allocate memory within the configured max blocking time" exception, it should also remove the condition object from the waiter

[ https://issues.apache.org/jira/browse/KAFKA-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3651: --- Summary: Whenever the BufferPool throws a "Failed to allocate memory within the configured max

[GitHub] kafka pull request: MINOR: Clean up of ConsumerCoordinator and Par...

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

[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=15269739#comment-15269739 ] ASF GitHub Bot commented on KAFKA-3632: --- GitHub user hachikuji opened a pull request:

[jira] [Assigned] (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 ] Jason Gustafson reassigned KAFKA-3632: -- Assignee: Jason Gustafson > ConsumerLag metrics persist after partition migration >

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

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1312 KAFKA-3632: remove fetcher metrics on shutdown and leader migration You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka

[jira] [Assigned] (KAFKA-3653) expose the queue size in ControllerChannelManager

[ https://issues.apache.org/jira/browse/KAFKA-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira reassigned KAFKA-3653: --- Assignee: Gwen Shapira > expose the queue size in ControllerChannelManager >

[jira] [Updated] (KAFKA-3565) bceunbfjcvtdvidckvjrrcklvtdnjgvlj

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3565: Summary: bceunbfjcvtdvidckvjrrcklvtdnjgvlj (was: Producer's throughput lower with compressed data

[jira] [Created] (KAFKA-3653) expose the queue size in ControllerChannelManager

Jun Rao created KAFKA-3653: -- Summary: expose the queue size in ControllerChannelManager Key: KAFKA-3653 URL: https://issues.apache.org/jira/browse/KAFKA-3653 Project: Kafka Issue Type: Improvement

[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=15269706#comment-15269706 ] ASF GitHub Bot commented on KAFKA-3639: --- GitHub user guozhangwang opened a pull request:

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

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1311 KAFKA-3639: Configure default serdes upon construction You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka K3639

[jira] [Assigned] (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 ] Guozhang Wang reassigned KAFKA-3639: Assignee: Guozhang Wang > Configure default serdes passed via StreamsConfig >

[jira] [Updated] (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 ] Guozhang Wang updated KAFKA-3639: - Fix Version/s: (was: 0.10.1.0) 0.10.0.0 > Configure default serdes passed

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

See Changes: [wangguoz] MINOR: Added more integration tests -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on jenkins-test-a4 (jenkins-cloud-4GB

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

Gwen, On your second point. Can you describe a usecase where mutliple clients ended up sharing a producer and even if they do why can't they not use single token that producer captures. Why would we need multiple clients with different tokens

[jira] [Commented] (KAFKA-3383) Producer should not remove an in flight request before successfully parsing the response.

[ https://issues.apache.org/jira/browse/KAFKA-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269599#comment-15269599 ] ASF GitHub Bot commented on KAFKA-3383: --- Github user zhuchen1018 closed the pull request at:

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

See Changes: [wangguoz] MINOR: Added more integration tests -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on jenkins-test-a4 (jenkins-cloud-4GB

[GitHub] kafka pull request: KAFKA-3383: remove in flight request only afte...

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

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

See

[jira] [Commented] (KAFKA-3651) Whenever the BufferPool throws a "Failed to allocate memory within the configured max blocking time" excepion, it should also remove the condition object from the waite

[ https://issues.apache.org/jira/browse/KAFKA-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269596#comment-15269596 ] Ismael Juma commented on KAFKA-3651: Maybe we can fix that as part of

[jira] [Created] (KAFKA-3651) Whenever the BufferPool throws a "Failed to allocate memory within the configured max blocking time" excepion, it should also remove the condition object from the waiters

Mayuresh Gharat created KAFKA-3651: -- Summary: Whenever the BufferPool throws a "Failed to allocate memory within the configured max blocking time" excepion, it should also remove the condition object from the waiters deque Key:

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269586#comment-15269586 ] James Cheng commented on KAFKA-3587: The fix for KAFKA-3587 may resolve both KAFKA-2235 and KAFAK-2303

[GitHub] kafka pull request: MINOR: Added more integration tests

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

[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=15269491#comment-15269491 ] Jiangjie Qin commented on KAFKA-3565: - [~junrao] Thanks for help looking into this. I updated run 11

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

See Changes: [me] KAFKA-3650: Fix vagrant download URL [me] MINOR: add logfilename to error message when file missing [wangguoz] KAFKA-3642: Fix NPE from ProcessorStateManager when the changelog topic [junrao] KAFKA-3128; Add

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

See Changes: [junrao] KAFKA-3517; Add documentation for SASL/PLAIN [me] KAFKA-3650: Fix vagrant download URL [me] MINOR: add logfilename to error message when file missing -- [...truncated

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

See Changes: [junrao] KAFKA-3517; Add documentation for SASL/PLAIN -- [...truncated 4065 lines...] kafka.admin.AdminRackAwareTest > testAssignmentWithRackAwareWithUnevenReplicas PASSED

[jira] [Assigned] (KAFKA-3480) Autogenerate metrics documentation

[ https://issues.apache.org/jira/browse/KAFKA-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Cheng reassigned KAFKA-3480: -- Assignee: James Cheng > Autogenerate metrics documentation >

[jira] [Updated] (KAFKA-3637) Add method that checks if streams are initialised

[ https://issues.apache.org/jira/browse/KAFKA-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3637: Description: Currently when streams are initialised and started with streams.start(), there is no

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

Sorry for the delay: Two questions that we didn't see in the wiki: 1. Is there an expiration for delegation tokens? Renewal? How do we revoke them? 2. If we want to use delegation tokens for "do-as" (say, submit Storm job as my user), we will need a producer for every job (we can't share them

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

GitHub user theduderog opened a pull request: https://github.com/apache/kafka/pull/1309 Minor fixes to AWS init script for testing A path was wrong in the script and in the documentation. You can merge this pull request into a Git repository by running: $ git pull

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

Good work on this Dana. I'll test it with librdkafka (which uses the official liblz4) and report back. 2016-05-03 20:02 GMT+02:00 Dana Powers : > Yes, great point. The intent of adding "naive" support for the > remaining LZ4 header flags (contentsize and contentchecksum)

[jira] [Updated] (KAFKA-3479) Add new consumer metrics documentation

[ https://issues.apache.org/jira/browse/KAFKA-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3479: Assignee: Kaufman Ng > Add new consumer metrics documentation >

[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: --- Resolution: Fixed Fix Version/s: (was: 0.10.1.0) 0.10.0.0

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

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

[GitHub] kafka pull request: KAFKA-3448: Support zone index in IPv6 regex

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

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

Yes, great point. The intent of adding "naive" support for the remaining LZ4 header flags (contentsize and contentchecksum) is to avoid rejecting any lz4 messages framed according to the interoperable spec (v1.5.1). If we can accept all such messages (which this KIP does), we should never have to

[jira] [Updated] (KAFKA-3128) Add metrics for ZooKeeper events

[ https://issues.apache.org/jira/browse/KAFKA-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3128: --- Resolution: Fixed Fix Version/s: (was: 0.10.1.0) 0.10.0.0 Status:

[jira] [Commented] (KAFKA-3128) Add metrics for ZooKeeper events

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

[GitHub] kafka pull request: KAFKA-3128; Add metrics for ZooKeeper events z...

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

[GitHub] kafka pull request: KAFKA-3642: Fix NPE from ProcessorStateManager...

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

[jira] [Updated] (KAFKA-3642) Fix NPE from ProcessorStateManager when the changelog topic not exists

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

[jira] [Commented] (KAFKA-3642) Fix NPE from ProcessorStateManager when the changelog topic not exists

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

[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 ] Soumyajit Sahu updated KAFKA-3448: -- Summary: Support zone index in IPv6 regex (was: IPV6 Regex is missing % character) > Support

[jira] [Updated] (KAFKA-3448) IPV6 Regex is missing % character

[ https://issues.apache.org/jira/browse/KAFKA-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Soumyajit Sahu updated KAFKA-3448: -- Description: When an address is written textually, the zone index is appended to the address,

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

+1 One caveat on the vote though -- I don't know the details of LZ4 (format, libraries, etc) well enough to have a handle on whether the changes under "KafkaLZ4* code" are going to be sufficient to get broad support from other LZ4 libraries. Are we going to have multiple implementations we can

[jira] [Commented] (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:comment-tabpanel=15269155#comment-15269155 ] Ismael Juma commented on KAFKA-3646: Updating this issue with conversation that happened elsewhere.

[jira] [Commented] (KAFKA-3144) report members with no assigned partitions in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269149#comment-15269149 ] Vahid Hashemian commented on KAFKA-3144: Sorry for broken formatting. I hope what I suggested is

[jira] [Commented] (KAFKA-3209) Support single message transforms in Kafka Connect

[ https://issues.apache.org/jira/browse/KAFKA-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269148#comment-15269148 ] Ewen Cheslack-Postava commented on KAFKA-3209: -- To help clarify [~Skandragon]'s comment a

[jira] [Commented] (KAFKA-3144) report members with no assigned partitions in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269145#comment-15269145 ] Vahid Hashemian commented on KAFKA-3144: [~junrao] I haven't heard from [~Konrad Kalita] and have

[GitHub] kafka pull request: MINOR: add logfilename to error message when f...

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

[GitHub] kafka pull request: KAFKA-3650: Fix vagrant download URL

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

[jira] [Resolved] (KAFKA-3650) AWS test script fails to install vagrant

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

  1   2   >