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

See Changes: [jason] KAFKA-5211; Do not skip a corrupted record in consumer -- [...truncated 904.24 KB...] kafka.security.auth.SimpleAclAuthorizerTest > testDenyTakesPrec

[jira] [Commented] (KAFKA-4785) Records from internal repartitioning topics should always use RecordMetadataTimestampExtractor

[ https://issues.apache.org/jira/browse/KAFKA-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030732#comment-16030732 ] Ismael Juma commented on KAFKA-4785: Is this still planned for 0.11.0.0? > Records fr

[jira] [Updated] (KAFKA-4686) Null Message payload is shutting down broker

[ https://issues.apache.org/jira/browse/KAFKA-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4686: --- Priority: Critical (was: Major) > Null Message payload is shutting down broker >

[jira] [Updated] (KAFKA-4686) Null Message payload is shutting down broker

[ https://issues.apache.org/jira/browse/KAFKA-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4686: --- Fix Version/s: (was: 0.11.0.0) 0.11.0.1 > Null Message payload is shutting down

[jira] [Updated] (KAFKA-4808) send of null key to a compacted topic should throw error back to user

[ https://issues.apache.org/jira/browse/KAFKA-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4808: --- Status: Patch Available (was: Open) > send of null key to a compacted topic should throw error back t

Re: Jira-Spam on Dev-Mailinglist

+1 agree with Jeff, Michał On 31/05/17 06:25, Jeff Widman wrote: I'm hugely in favor of this change as well... Although I actually find the Github pull request emails less useful than the jirabot ones since Jira typically has more info when I'm trying to figure out if the issue is relevant to

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

[ https://issues.apache.org/jira/browse/KAFKA-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030729#comment-16030729 ] Apurva Mehta commented on KAFKA-5351: - I saw the following in the logs for two of the

[jira] [Updated] (KAFKA-4808) send of null key to a compacted topic should throw error back to user

[ https://issues.apache.org/jira/browse/KAFKA-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4808: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > send of null key to a compacted topic

[jira] [Updated] (KAFKA-5031) Additional validation in validateMessagesAndAssignOffsets

[ https://issues.apache.org/jira/browse/KAFKA-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5031: --- Status: Patch Available (was: Open) > Additional validation in validateMessagesAndAssignOffsets > ---

[jira] [Updated] (KAFKA-5051) Avoid DNS reverse lookup in security-critical TLS code path

[ https://issues.apache.org/jira/browse/KAFKA-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5051: --- Status: Patch Available (was: Open) > Avoid DNS reverse lookup in security-critical TLS code path > -

[jira] [Resolved] (KAFKA-5059) Implement Transactional Coordinator

[ https://issues.apache.org/jira/browse/KAFKA-5059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5059. Resolution: Fixed Marking this as resolved since all, but one task have been completed and the unco

[jira] [Updated] (KAFKA-5212) Consumer ListOffsets request can starve group heartbeats

[ https://issues.apache.org/jira/browse/KAFKA-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5212: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Consumer ListOffsets request can star

[jira] [Commented] (KAFKA-5308) TC should handle UNSUPPORTED_FOR_MESSAGE_FORMAT in WriteTxnMarker response

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

[GitHub] kafka pull request #3152: KAFKA-5308: TC should handle UNSUPPORTED_FOR_MESSA...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3152 --- 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-1482) Transient test failures for kafka.admin.DeleteTopicTest.testPartitionReassignmentDuringDeleteTopic

[ https://issues.apache.org/jira/browse/KAFKA-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1482: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Transient test failures for > kafka

[jira] [Updated] (KAFKA-5308) TC should handle UNSUPPORTED_FOR_MESSAGE_FORMAT in WriteTxnMarker response

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

[jira] [Updated] (KAFKA-4972) Kafka 0.10.0 Found a corrupted index file during Kafka broker startup

[ https://issues.apache.org/jira/browse/KAFKA-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4972: --- Fix Version/s: (was: 0.12.0.0) (was: 0.11.0.0) 0.11.0.1

[jira] [Updated] (KAFKA-4669) KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives throws exception

[ https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4669: --- Fix Version/s: (was: 0.11.0.0) 0.11.0.1 > KafkaProducer.flush hangs when Networ

[jira] [Commented] (KAFKA-4595) Controller send thread can't stop when broker change listener event trigger for dead brokers

[ https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030705#comment-16030705 ] Ismael Juma commented on KAFKA-4595: [~junrao], is this fixed given that deletion no l

[jira] [Updated] (KAFKA-3955) Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot

[ https://issues.apache.org/jira/browse/KAFKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3955: --- Fix Version/s: (was: 0.11.0.0) 0.11.0.1 > Kafka log recovery doesn't truncate l

[jira] [Updated] (KAFKA-1694) KIP-4: Command line and centralized operations

[ https://issues.apache.org/jira/browse/KAFKA-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1694: --- Fix Version/s: (was: 0.11.0.0) > KIP-4: Command line and centralized operations >

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

[ https://issues.apache.org/jira/browse/KAFKA-5321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030703#comment-16030703 ] Ismael Juma commented on KAFKA-5321: [~hachikuji], this was fixed as part of KAFKA-531

[jira] [Updated] (KAFKA-4693) Consumer subscription change during rebalance causes exception

[ https://issues.apache.org/jira/browse/KAFKA-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4693: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Consumer subscription change during r

[jira] [Updated] (KAFKA-4950) ConcurrentModificationException when iterating over Kafka Metrics

[ https://issues.apache.org/jira/browse/KAFKA-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4950: --- Fix Version/s: (was: 0.11.0.0) 0.11.0.1 > ConcurrentModificationException when

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

[ https://issues.apache.org/jira/browse/KAFKA-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030701#comment-16030701 ] Ismael Juma commented on KAFKA-5218: Is this still planned for 0.11.0.0? > New Short

[jira] [Updated] (KAFKA-2875) Class path contains multiple SLF4J bindings warnings when using scripts under bin

[ https://issues.apache.org/jira/browse/KAFKA-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2875: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Class path contains multiple SLF4J bi

[jira] [Updated] (KAFKA-3733) Avoid long command lines by setting CLASSPATH in environment

[ https://issues.apache.org/jira/browse/KAFKA-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3733: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Avoid long command lines by setting C

[jira] [Commented] (KAFKA-4064) Add support for infinite endpoints for range queries in Kafka Streams KV stores

[ https://issues.apache.org/jira/browse/KAFKA-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030700#comment-16030700 ] Ismael Juma commented on KAFKA-4064: Is this still planned for 0.11.0.0? > Add suppor

[jira] [Updated] (KAFKA-1548) Refactor the "replica_id" in requests

[ https://issues.apache.org/jira/browse/KAFKA-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1548: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Refactor the "replica_id" in requests

[jira] [Updated] (KAFKA-1899) Update code coverage report generation once gradle-scoverage starts publishing scoverage report

[ https://issues.apache.org/jira/browse/KAFKA-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1899: --- Fix Version/s: (was: 0.11.0.0) > Update code coverage report generation once gradle-scoverage star

[jira] [Updated] (KAFKA-1900) Add documentation on usage of code coverage in the project and how it works

[ https://issues.apache.org/jira/browse/KAFKA-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1900: --- Fix Version/s: (was: 0.11.0.0) > Add documentation on usage of code coverage in the project and ho

[jira] [Updated] (KAFKA-2394) Use RollingFileAppender by default in log4j.properties

[ https://issues.apache.org/jira/browse/KAFKA-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2394: --- Fix Version/s: (was: 0.11.0.0) 0.12.0.0 > Use RollingFileAppender by default in

[GitHub] kafka pull request #3155: KAKFA-5334: Allow rocksdb.config.setter to be spec...

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

[jira] [Resolved] (KAFKA-5334) rocksdb.config.setter must be a class instance, not a class name

[ https://issues.apache.org/jira/browse/KAFKA-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-5334. -- Resolution: Fixed Fix Version/s: 0.11.0.0 Issue resolved by pull request 3155 [https://gi

[GitHub] kafka pull request #3114: KAFKA-5211: Do not skip a corrupted record in cons...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3114 --- 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-5211) KafkaConsumer should not skip a corrupted record after throwing an exception.

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

[jira] [Commented] (KAFKA-5211) KafkaConsumer should not skip a corrupted record after throwing an exception.

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

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

See Changes: [jason] KAFKA-5251; Producer should cancel unsent AddPartitions and Produce -- [...truncated 904.12 KB...] kafka.security.auth.SimpleAclAuthorizerTest > test

Re: Jira-Spam on Dev-Mailinglist

I'm hugely in favor of this change as well... Although I actually find the Github pull request emails less useful than the jirabot ones since Jira typically has more info when I'm trying to figure out if the issue is relevant to me or not... On Tue, May 30, 2017 at 2:28 PM, Guozhang Wang wrote:

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

[ https://issues.apache.org/jira/browse/KAFKA-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reassigned KAFKA-5351: --- Assignee: Apurva Mehta > Broker clean bounce test puts the broker into a 'CONCURRENT_TRANSACT

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

Apurva Mehta created KAFKA-5351: --- Summary: Broker clean bounce test puts the broker into a 'CONCURRENT_TRANSACTIONS' state permanently Key: KAFKA-5351 URL: https://issues.apache.org/jira/browse/KAFKA-5351

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

See Changes: [jason] KAFKA-5251; Producer should cancel unsent AddPartitions and Produce -- [...truncated 902.76 KB...] kafka.producer.ProducerTest > testUpdateBrokerParti

Request a permission to KIP

Hi, I want to get a permission to add a KIP.My wiki username is marktcma. Tahnks.

[jira] [Commented] (KAFKA-5251) Producer should drop queued sends when transaction is aborted

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

[GitHub] kafka pull request #3161: KAFKA-5251: Producer should cancel unsent AddParti...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3161 --- 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-5251) Producer should drop queued sends when transaction is aborted

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

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

See

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

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

[GitHub] kafka pull request #3174: KAFKA-5293. Do not apply exponential backoff if us...

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/3174 KAFKA-5293. Do not apply exponential backoff if users have overridden… … reconnect.backoff.ms You can merge this pull request into a Git repository by running: $ git pull https://github.com

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

See

[jira] [Resolved] (KAFKA-5324) AdminClient: add close with timeout, fix some timeout bugs

[ https://issues.apache.org/jira/browse/KAFKA-5324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5324. Resolution: Fixed Fix Version/s: 0.11.0.0 > AdminClient: add close with timeout, fix some tim

[jira] [Commented] (KAFKA-5324) AdminClient: add close with timeout, fix some timeout bugs

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

[GitHub] kafka pull request #3173: MINOR: Traverse plugin path recursively in connect

GitHub user kkonstantine opened a pull request: https://github.com/apache/kafka/pull/3173 MINOR: Traverse plugin path recursively in connect You can merge this pull request into a Git repository by running: $ git pull https://github.com/kkonstantine/kafka MINOR-Traverse-plugi

[GitHub] kafka pull request #3141: KAFKA-5324: AdminClient: add close with timeout, f...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3141 --- 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-5293) Do not apply exponential backoff if users have overridden reconnect.backoff.ms

[ https://issues.apache.org/jira/browse/KAFKA-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-5293: -- Assignee: Colin P. McCabe (was: Ismael Juma) > Do not apply exponential backoff if users have

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

See Changes: [junrao] MINOR: onControllerResignation should be invoked if -- [...truncated 904.48 KB...] kafka.server.ReplicaManagerTest > testClearPurgatoryOnBecomingFol

[jira] [Commented] (KAFKA-5150) LZ4 decompression is 4-5x slower than Snappy on small batches / messages

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

[GitHub] kafka pull request #2967: KAFKA-5150 reduce lz4 decompression overhead

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

[GitHub] kafka pull request #2054: kafka-4295: ConsoleConsumer does not delete the te...

Github user amethystic closed the pull request at: https://github.com/apache/kafka/pull/2054 --- 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 #2317: kafka-4592: Kafka Producer Metrics Invalid Value

Github user amethystic closed the pull request at: https://github.com/apache/kafka/pull/2317 --- 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 #2576: kafka-4767: KafkaProducer is not joining its IO th...

Github user amethystic closed the pull request at: https://github.com/apache/kafka/pull/2576 --- 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-trunk-jdk7 #2289

See Changes: [junrao] MINOR: Fix doc for producer throttle time metrics -- [...truncated 905.43 KB...] kafka.server.DelayedOperationTest > testRequestPurge PASSED kafka.

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

See Changes: [junrao] MINOR: Fix doc for producer throttle time metrics -- [...truncated 906.15 KB...] kafka.controller.ControllerEventManagerTest > testSuccessfulEvent PA

[GitHub] kafka-site pull request #59: Add auto syntax highlighter

GitHub user derrickdoo opened a pull request: https://github.com/apache/kafka-site/pull/59 Add auto syntax highlighter Added plugin to do auto syntax highlighting for code snippets in our docs. Here's an example of how to syntax highlight some java code: `` Here

Re: [DISCUSS] KIP-108: Create Topic Policy

Yes, and the only way to enforce it is by restricting ZK access to brokers only. If ZK access is available to users, they can get around the broker config proposal as well. And then the question is about benefit versus cost. We can have that discussion when the KIP is proposed. Ismael On Wed, May

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

See

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

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/3172 KAFKA-5350: Modify unstable annotations in Streams API You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka K5350-compatibil

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

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

[GitHub] kafka pull request #2935: MINOR: onControllerResignation should be invoked i...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2935 --- 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-3761) Controller has RunningAsBroker instead of RunningAsController state

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

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

Guozhang Wang created KAFKA-5350: Summary: Modify Unstable annotations in Streams API Key: KAFKA-5350 URL: https://issues.apache.org/jira/browse/KAFKA-5350 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP-108: Create Topic Policy

Certainly. I think it is reasonable to create a separate KIP to enforce the topic creation policy. After all the administrator needs a guarantee that the policy that they have specified in the broker will be enforce -- otherwise the feature doesn't seem complete. On Tue, May 30, 2017 at 4:45 PM, I

Re: [DISCUSS] KIP-108: Create Topic Policy

I am not sure if the additional complexity in the Controller is worth it for this use case. It seems like it would be better to swap the tools to use AdminClient and then restrict access to ZK (via ACLs and/or network segmentation). Either way, that proposal should be done via a separate KIP as KIP

[GitHub] kafka pull request #3171: MINOR: A few cleanups in KafkaApis and Transaction...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3171 MINOR: A few cleanups in KafkaApis and TransactionMarkerChannelManager You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka minor-t

Re: [DISCUSS] KIP-108: Create Topic Policy

On Tue, May 30, 2017 at 4:26 PM, Colin McCabe wrote: > On Tue, May 30, 2017, at 15:55, Dong Lin wrote: > > Hey Colin, > > > > I think one big advantage of the broker side config is that it can not be > > ignored by the malicious client, right? > > Hi Dong, > > The scenario I was thinking of is wh

[GitHub] kafka pull request #3169: MINOR: Fix doc for producer throttle time metrics

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

Re: [DISCUSS] KIP-108: Create Topic Policy

On Tue, May 30, 2017, at 15:55, Dong Lin wrote: > Hey Colin, > > I think one big advantage of the broker side config is that it can not be > ignored by the malicious client, right? Hi Dong, The scenario I was thinking of is where a malicious client communicates directly with ZooKeeper, bypassing

[GitHub] kafka-site pull request #58: [PLEASE DO NOT MERGE] Further break apart Strea...

GitHub user derrickdoo opened a pull request: https://github.com/apache/kafka-site/pull/58 [PLEASE DO NOT MERGE] Further break apart Streams docs This is just to illustrate necessary changes for changing the structure of Streams documentation. Please don't merge yet.

Re: [DISCUSS] KIP-108: Create Topic Policy

@Colin checkout kafka.admin.ZkSecurityMigrator. This is what I meant in my earlier comment on "acl off zookeeper" On Tue, May 30, 2017 at 3:39 PM Colin McCabe wrote: > It seems like, to make it really secure, we need the enforcement to be > done at the ZooKepeer level. Any broker or client-side

Re: [DISCUSS] KIP-108: Create Topic Policy

Hey Colin, I think one big advantage of the broker side config is that it can not be ignored by the malicious client, right? Thanks, Dong On Tue, May 30, 2017 at 3:53 PM, Dong Lin wrote: > Do we have an old version of bin/kafka-topics.sh which creates topic via > ZK and still allows user to ac

Re: [DISCUSS] KIP-108: Create Topic Policy

Do we have an old version of bin/kafka-topics.sh which creates topic via ZK and still allows user to access ZK with ACL? Another concern is that some user may not have ACL service deployed in their cluster. If neither of these is issue, then I would prefer the zookeeper approach instead of adding

Re: [DISCUSS] KIP-140: Add administrative RPCs for adding, deleting, and listing ACLs

Hi all, In the course of reviewing the AdminClient#apiVersions API, we found out that it was using an internal class, org.apache.kafka.clients.NodeApiVersions. This internal class references more internal stuff, including things in org.apache.kafka.common.protocol. So we filed KAFKA-5214 to crea

[GitHub] kafka pull request #3164: KAFKA-5150: Reduce lz4 decompression overhead (wit...

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

[jira] [Commented] (KAFKA-5150) LZ4 decompression is 4-5x slower than Snappy on small batches / messages

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

Re: [DISCUSS] KIP-108: Create Topic Policy

It seems like, to make it really secure, we need the enforcement to be done at the ZooKepeer level. Any broker or client-side configuration can just be ignored by a malicious client. Do we have documentation or code that configures ZK to prevent unprivileged users from modifying the topic configu

Re: [DISCUSS] KIP-108: Create Topic Policy

Just for completeness, I think one option is to: 1. Upgrade broker-side auto topic creation to send CreateTopicsRequest. This is just to unify the topic creation flow and policy enforcement. 2. Migrate all clients away from topic creation from zookeeper and instead send CreateTopicsRequest 3. ACL o

[jira] [Commented] (KAFKA-5349) KafkaConsumer occasionally hits IllegalStateException

[ https://issues.apache.org/jira/browse/KAFKA-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030276#comment-16030276 ] Apurva Mehta commented on KAFKA-5349: - cc [~hachikuji] > KafkaConsumer occasionally h

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

See

[jira] [Created] (KAFKA-5349) KafkaConsumer occasionally hits IllegalStateException

Apurva Mehta created KAFKA-5349: --- Summary: KafkaConsumer occasionally hits IllegalStateException Key: KAFKA-5349 URL: https://issues.apache.org/jira/browse/KAFKA-5349 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-108: Create Topic Policy

Hey Ismael, I agree that it makes sense not to cover ZK-based topic creation with the topic creation policy and limit ZK access to brokers only going forward. My point is that we need a way to disable ZK-based topic creation so that all topic creation goes through the topic creation policy as spec

[jira] [Commented] (KAFKA-5202) Handle topic deletion for ongoing transactions

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

[GitHub] kafka pull request #3130: KAFKA-5202: Handle topic deletion while trying to ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3130 --- 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-5202) Handle topic deletion for ongoing transactions

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

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

See Changes: [jason] KAFKA-5316; Follow-up with ByteBufferOutputStream and other misc -- [...truncated 2.96 MB...] kafka.utils.UtilsTest > testReadBytes PASSED kafka.uti

Re: Jira-Spam on Dev-Mailinglist

I actually do not know.. Maybe Jun knows better than me? Guozhang On Mon, May 29, 2017 at 12:58 PM, Gwen Shapira wrote: > I agree. > > Guozhang, do you know how to implement the suggestion? JIRA to Apache > Infra? Or is this something we can do ourselves somehow? > > On Mon, May 29, 2017 at 9:

[jira] [Issue Comment Deleted] (KAFKA-5339) Transactions system test with hard broker bounces fails sporadically

[ https://issues.apache.org/jira/browse/KAFKA-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5339: Comment: was deleted (was: Another puzzling one: {noformat} 21:02:37,450] ERROR Uncaught error in

Re: [DISCUSS] KIP-108: Create Topic Policy

Hi Dong, No, ZK-based topic creation doesn't go through the policy since it doesn't go through the broker. Given that, I am not sure how the broker config would work. Can you please elaborate? It seems like the way forward is to limit ZK access to brokers only. Ismael On Tue, May 30, 2017 at 10:

Re: [DISCUSS] KIP-108: Create Topic Policy

Hey Ismael, Thanks for the KIP. This is definitely useful. Does the KIP apply the topic creation policy to ZK-based topic creation? If not, which seems to be the case from my understanding, should we have a new broker config to disable ZK-based topic creation? This seems necessary to prevent user

[jira] [Commented] (KAFKA-5339) Transactions system test with hard broker bounces fails sporadically

[ https://issues.apache.org/jira/browse/KAFKA-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030147#comment-16030147 ] Apurva Mehta commented on KAFKA-5339: - Another puzzling one: {noformat} 21:02:37,45

[jira] [Commented] (KAFKA-5332) When resize the index file, maybe caused the content disappear

[ https://issues.apache.org/jira/browse/KAFKA-5332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030120#comment-16030120 ] Guozhang Wang commented on KAFKA-5332: -- Does look like a bug, [~junrao] could you tak

  1   2   >