[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=15274454#comment-15274454 ] Guozhang Wang commented on KAFKA-3587: -- Oops, accidentally deleted my previous comment, re-posting

[jira] [Commented] (KAFKA-3592) System tests - don't hardcode paths to scripts

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

[jira] [Updated] (KAFKA-3667) Improve Section 7.2 Encryption and Authentication using SSL to include proper hostname verification configuration

[ https://issues.apache.org/jira/browse/KAFKA-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P updated KAFKA-3667: -- Description: Kafka's documentation should include additional guidance on how to properly enable SSL with

[jira] [Commented] (KAFKA-3666) Update new Consumer API links in the docs

[ https://issues.apache.org/jira/browse/KAFKA-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274155#comment-15274155 ] Dustin Cote commented on KAFKA-3666: Leaving the github link here since the PR didn't get pushed for

Re: list of challenges encountered using 0.9.0.1

Thanks for the updates, Jason. Let me know if you have questions about use case that brings up any of these scenarios. On Thu, May 5, 2016 at 7:34 PM, Jason Gustafson wrote: > Hey Cliff, > > Thanks for the feedback. A few select comments: > > 1. The new Java KafkaConsumer

[GitHub] kafka pull request: KAFKA-3616: Make kafka producers/consumers inj...

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

See Changes: [ismael] KAFKA-3666; Update links for new consumer API [wangguoz] KAFKA-3616: Make kafka producers/consumers injectable for KafkaStreams -- [...truncated 7829 lines...]

[jira] [Commented] (KAFKA-3664) When subscription set changes on new consumer, the partitions may be removed without offset being committed.

[ https://issues.apache.org/jira/browse/KAFKA-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274390#comment-15274390 ] Jason Gustafson commented on KAFKA-3664: [~becket_qin] Thanks for the report. After the topic

Re: [VOTE] 0.10.0.0 RC3

Thanks, Gwen. I was testing RC2 with Spark Streaming and found an issue that has a minor fix. I think this issue exists with RC3 as well: https://issues.apache.org/jira/browse/KAFKA-3669 On Thu, May 5, 2016 at 1:46 PM, Gwen Shapira wrote: > Hello Kafka users, developers and

[jira] [Resolved] (KAFKA-3592) System tests - don't hardcode paths to scripts

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

[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=15274442#comment-15274442 ] Jun Rao commented on KAFKA-3587: Yes, let's first agree upon the best approach on the jira. It would be

[GitHub] kafka pull request: KAFKA-3592: System test - configurable paths

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1245 --- 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] [Issue Comment Deleted] (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:all-tabpanel ] Manas Alekar updated KAFKA-3587: Comment: was deleted (was: The issue with just building the map till it is full as proposed in pull

[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=15274372#comment-15274372 ] Jun Rao commented on KAFKA-3587: [~ecomar], thanks for the explanation. I am not sure about your first

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

See Changes: [ismael] KAFKA-3666; Update links for new consumer API -- [...truncated 8691 lines...] org.apache.kafka.connect.storage.KafkaStatusBackingStoreTest > readConnectorState PASSED

[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=15274418#comment-15274418 ] Guozhang Wang commented on KAFKA-3587: -- We have multiple PRs for this JIRA now, and I suggest we'd

[jira] [Issue Comment Deleted] (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:all-tabpanel ] Guozhang Wang updated KAFKA-3587: - Comment: was deleted (was: We have multiple PRs for this JIRA now, and I suggest we'd better

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

See

[jira] [Commented] (KAFKA-3664) When subscription set changes on new consumer, the partitions may be removed without offset being committed.

[ https://issues.apache.org/jira/browse/KAFKA-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274470#comment-15274470 ] Jiangjie Qin commented on KAFKA-3664: - [~hachikuji] I am not sure. If we still return the partitions

[jira] [Created] (KAFKA-3669) Add secondary constructor for KafkaConfig with a default value for doLog

Mark Grover created KAFKA-3669: -- Summary: Add secondary constructor for KafkaConfig with a default value for doLog Key: KAFKA-3669 URL: https://issues.apache.org/jira/browse/KAFKA-3669 Project: Kafka

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

See Changes: [ismael] KAFKA-3666; Update links for new consumer API [wangguoz] KAFKA-3616: Make kafka producers/consumers injectable for KafkaStreams -- [...truncated 459 lines...]

[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=15274483#comment-15274483 ] Manas Alekar commented on KAFKA-3587: - The issue with just building the map till it is full as

[jira] [Updated] (KAFKA-3666) Update new Consumer API links in the docs

[ https://issues.apache.org/jira/browse/KAFKA-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dustin Cote updated KAFKA-3666: --- Summary: Update new Consumer API links in the docs (was: Update offset checking example in the docs)

[jira] [Commented] (KAFKA-3666) Update offset checking example in the docs

[ https://issues.apache.org/jira/browse/KAFKA-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274090#comment-15274090 ] Dustin Cote commented on KAFKA-3666: After looking at the docs in trunk, it looks like the

[jira] [Updated] (KAFKA-3666) Update new Consumer API links in the docs

[ https://issues.apache.org/jira/browse/KAFKA-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dustin Cote updated KAFKA-3666: --- Description: New Consumer API links in the docs point to the initial proposed design doc. This

[GitHub] kafka pull request: Update links for new consumer API

GitHub user cotedm opened a pull request: https://github.com/apache/kafka/pull/1331 Update links for new consumer API Pull request to update the consumer API links in the docs. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Assigned] (KAFKA-3664) When subscription set changes on new consumer, the partitions may be removed without offset being committed.

[ https://issues.apache.org/jira/browse/KAFKA-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-3664: -- Assignee: Vahid Hashemian > When subscription set changes on new consumer, the

[jira] [Created] (KAFKA-3667) Improve Section 7.2 Encryption and Authentication using SSL to include proper hostname verification configuration

Ryan P created KAFKA-3667: - Summary: Improve Section 7.2 Encryption and Authentication using SSL to include proper hostname verification configuration Key: KAFKA-3667 URL: https://issues.apache.org/jira/browse/KAFKA-3667

[jira] [Created] (KAFKA-3668) Unable to authenticate Kafka broker to secured Zookeeper

Alex created KAFKA-3668: --- Summary: Unable to authenticate Kafka broker to secured Zookeeper Key: KAFKA-3668 URL: https://issues.apache.org/jira/browse/KAFKA-3668 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-3616) Make kafka producers/consumers injectable for KafkaStreams

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

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274195#comment-15274195 ] Jun Rao commented on KAFKA-3665: Thanks for the patch. A couple of questions. 1. Is the requirement only

[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=15274204#comment-15274204 ] Edoardo Comar commented on KAFKA-3587: -- For clarity, [~mimaison] PR

[jira] [Updated] (KAFKA-3616) Make kafka producers/consumers injectable for KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3616: - Fix Version/s: (was: 0.10.1.0) 0.10.0.0 > Make kafka producers/consumers

Re: KAFKA-3112

Yeah it is a duplicate of KAFKA-2657. The question is how to check / know if it is merged to 0.9.0.1 release. What are the options that I have if I need this fix. How can I get patch for this on 0.8.2.1? Sent from my iPhone > On May 6, 2016, at 12:06 AM, tao xiao wrote:

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

[jira] [Commented] (KAFKA-3666) Update new Consumer API links in the docs

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

[jira] [Resolved] (KAFKA-3666) Update new Consumer API links in the docs

[ https://issues.apache.org/jira/browse/KAFKA-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3666. Resolution: Fixed Fix Version/s: 0.10.0.0 Issue resolved by pull request 1331

[GitHub] kafka pull request: KAFKA-3666: Update links for new consumer API

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1331 --- 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-3616) Make kafka producers/consumers injectable for KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3616: - Resolution: Fixed Status: Resolved (was: Patch Available) > Make kafka

[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=15274513#comment-15274513 ] Manas Alekar commented on KAFKA-3587: - [~guozhang] Like your idea, I'll wait for us to decide on what

Re: KAFKA-3112

KAFKA-2657 is unresolved so you can safely assume it hasn't been fixed yet. On Fri, 6 May 2016 at 07:38 Raj Tanneru wrote: > Yeah it is a duplicate of KAFKA-2657. The question is how to check / know > if it is merged to 0.9.0.1 release. What are the options that I have if

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

See Changes: [me] KAFKA-3592: System test - configurable paths -- [...truncated 1627 lines...] kafka.log.LogTest > testLogRolls PASSED kafka.log.LogTest > testMessageSizeCheck PASSED

[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=15274677#comment-15274677 ] Jun Rao commented on KAFKA-3587: [~ecomar], yes, what you described matches my expectation. Now, I am not

[GitHub] kafka pull request: Minor: added description for lag in consumer g...

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

See Changes: [me] KAFKA-3592: System test - configurable paths -- [...truncated 4441 lines...] kafka.admin.AdminRackAwareTest > testAssignmentWithRackAware PASSED

[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=15274522#comment-15274522 ] Vahid Hashemian commented on KAFKA-3144: [~junrao] It seems the reason for this is groups with no

[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=15274534#comment-15274534 ] Manas Alekar commented on KAFKA-3587: - [~junrao] During cleaning the offset stored in offsetMap is

[jira] [Created] (KAFKA-3670) ControlledShutdownLeaderSelector should pick the preferred replica as the new leader, if possible

Jun Rao created KAFKA-3670: -- Summary: ControlledShutdownLeaderSelector should pick the preferred replica as the new leader, if possible Key: KAFKA-3670 URL: https://issues.apache.org/jira/browse/KAFKA-3670

[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=15274500#comment-15274500 ] Manas Alekar commented on KAFKA-3587: - The issue with just building the map till it is full as

[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=15274526#comment-15274526 ] Jun Rao commented on KAFKA-3587: [~alekar], note that when copying retained messages to new log segments,

[GitHub] kafka pull request: KAFKA-3669: Add secondary constructor for Kafk...

GitHub user markgrover opened a pull request: https://github.com/apache/kafka/pull/1333 KAFKA-3669: Add secondary constructor for KafkaConfig with a default … …value for doLog You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-3669) Add secondary constructor for KafkaConfig with a default value for doLog

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

[GitHub] kafka pull request: KAFKA-3669: Add secondary constructor for Kafk...

GitHub user markgrover opened a pull request: https://github.com/apache/kafka/pull/1334 KAFKA-3669: Add secondary constructor for KafkaConfig with a default … …value for doLog You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-3669) Add secondary constructor for KafkaConfig with a default value for doLog

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

[jira] [Commented] (KAFKA-3669) Add secondary constructor for KafkaConfig with a default value for doLog

[ https://issues.apache.org/jira/browse/KAFKA-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274554#comment-15274554 ] Mark Grover commented on KAFKA-3669: https://github.com/apache/kafka/pull/1333 for 0.10 branch and

[jira] [Commented] (KAFKA-3669) Add secondary constructor for KafkaConfig with a default value for doLog

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

[GitHub] kafka pull request: KAFKA-3669: Add secondary constructor for Kafk...

Github user markgrover closed the pull request at: https://github.com/apache/kafka/pull/1333 --- 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-3671) Topics should not be in common ConnectorConfig definitions

[ https://issues.apache.org/jira/browse/KAFKA-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei updated KAFKA-3671: -- Summary: Topics should not be in common ConnectorConfig definitions (was: topics should not be in

[jira] [Work started] (KAFKA-3671) Topics should not be in common ConnectorConfig definitions

[ https://issues.apache.org/jira/browse/KAFKA-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3671 started by Liquan Pei. - > Topics should not be in common ConnectorConfig definitions >

[jira] [Resolved] (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 ] Ismael Juma resolved KAFKA-3655. Resolution: Fixed Fix Version/s: 0.10.0.0 Issue resolved by pull request 1315

[jira] [Commented] (KAFKA-1981) Make log compaction point configurable

[ https://issues.apache.org/jira/browse/KAFKA-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274757#comment-15274757 ] Ismael Juma commented on KAFKA-1981: [~ewasserman], if you give me your wiki id, I can give you the

[GitHub] kafka pull request: KAFKA-3587: LogCleaner fails due to incorrect ...

GitHub user mimaison opened a pull request: https://github.com/apache/kafka/pull/1332 KAFKA-3587: LogCleaner fails due to incorrect offset map computation … Removed the over pessimistic require and instead attempt to fill the dedup buffer. Use the (only) map until full; this

[GitHub] kafka pull request: KAFKA-3587 Improve logic to build offsetMap in...

Github user alekar closed the pull request at: https://github.com/apache/kafka/pull/1329 --- 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-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=15274683#comment-15274683 ] ASF GitHub Bot commented on KAFKA-3587: --- Github user alekar closed the pull request at:

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

See Changes: [cshapi] Minor: added description for lag in consumer group command -- [...truncated 33 lines...] Building project 'core' with Scala version 2.10.6 Build file

[GitHub] kafka pull request: KAFKA-3669: Add secondary constructor for Kafk...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1334 --- 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-3669) Add secondary constructor for KafkaConfig with a default value for doLog

[ https://issues.apache.org/jira/browse/KAFKA-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274744#comment-15274744 ] Mark Grover commented on KAFKA-3669: Thanks [~ijuma]! > Add secondary constructor for KafkaConfig

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

See Changes: [me] KAFKA-3592: System test - configurable paths -- [...truncated 6393 lines...] org.apache.kafka.connect.storage.KafkaStatusBackingStoreTest > readConnectorState PASSED

[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=15274622#comment-15274622 ] Edoardo Comar commented on KAFKA-3587: -- [~junrao] thanks for your observation

[jira] [Assigned] (KAFKA-3670) ControlledShutdownLeaderSelector should pick the preferred replica as the new leader, if possible

[ https://issues.apache.org/jira/browse/KAFKA-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-3670: -- Assignee: Ismael Juma > ControlledShutdownLeaderSelector should pick the preferred replica as

[jira] [Created] (KAFKA-3671) topics should not be in common ConnectorConfig definitions

Liquan Pei created KAFKA-3671: - Summary: topics should not be in common ConnectorConfig definitions Key: KAFKA-3671 URL: https://issues.apache.org/jira/browse/KAFKA-3671 Project: Kafka Issue

[jira] [Commented] (KAFKA-3669) Add secondary constructor for KafkaConfig with a default value for doLog

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

[jira] [Updated] (KAFKA-3669) Add secondary constructor for KafkaConfig with a default value for doLog

[ https://issues.apache.org/jira/browse/KAFKA-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3669: --- Affects Version/s: (was: 0.11.0.0) > Add secondary constructor for KafkaConfig with a default

[jira] [Updated] (KAFKA-3669) Add secondary constructor for KafkaConfig with a default value for doLog

[ https://issues.apache.org/jira/browse/KAFKA-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3669: --- Assignee: Mark Grover > Add secondary constructor for KafkaConfig with a default value for doLog >

[jira] [Commented] (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:comment-tabpanel=15274720#comment-15274720 ] ASF GitHub Bot commented on KAFKA-3655: --- Github user asfgit closed the pull request at:

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

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1315 --- 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-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:all-tabpanel ] Ismael Juma updated KAFKA-3587: --- Fix Version/s: 0.10.0.0 > LogCleaner fails due to incorrect offset map computation on a replica >

Re: KIP-57: Interoperable LZ4 Framing

On Sun, May 1, 2016 at 3:57 AM, Dana Powers wrote: > > > 2. We're completely disabling checksumming of the compressed payload on > > consumption. Normally you'd want to validate each level of framing for > > correct end-to-end validation. You could still do this (albeit

Re: KIP-57: Interoperable LZ4 Framing

One more suggestion Dana, I would remove the "Public interfaces" section as those classes are not actually public (only the classes with Javadoc are public: https://kafka.apache.org/090/javadoc/index.html) and the information in the KIP is a bit stale when compared to the PR. Ismael On Fri, May

[jira] [Commented] (KAFKA-1981) Make log compaction point configurable

[ https://issues.apache.org/jira/browse/KAFKA-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274751#comment-15274751 ] Eric Wasserman commented on KAFKA-1981: --- I attached a KIP to this Jira ticket as I don't have

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

+1 (assuming the changes I mentioned in the discuss thread are incorporated) Ismael On Thu, May 5, 2016 at 1:13 AM, Jun Rao wrote: > Thanks for the response. +1 on the KIP. > > Jun > > On Thu, Apr 28, 2016 at 9:01 AM, Dana Powers > wrote: > > > Sure

Re: [VOTE] KIP-45: Standardize KafkaConsumer API to use Collection

I understand and empathize with both sides of the story here. I spend some of my time on Spark and Kafka integration and I have cc'ed Cody who's been working on new Kafka consumer API with Spark Streaming. Spark hasn't merged the new Kafka consumer API integration, the PR is up and we, as a

[jira] [Created] (KAFKA-3672) Introduce globally consistent checkpoint in Kafka Streams

Guozhang Wang created KAFKA-3672: Summary: Introduce globally consistent checkpoint in Kafka Streams Key: KAFKA-3672 URL: https://issues.apache.org/jira/browse/KAFKA-3672 Project: Kafka

[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=15274969#comment-15274969 ] Jiangjie Qin commented on KAFKA-3565: - [~junrao] I didn't have time to run the test yet. I will

Re: [VOTE] KIP-45: Standardize KafkaConsumer API to use Collection

Hi Mark, Thanks for the email. First of all, I'd like to mention that the `Unstable` annotation has been removed from the new Java consumer in 0.10, so you can expect compatibility from now on. We definitely understand that compatibility is important for widespread adoption. The current PR for

[jira] [Created] (KAFKA-3666) Update offset checking example in the docs

Dustin Cote created KAFKA-3666: -- Summary: Update offset checking example in the docs Key: KAFKA-3666 URL: https://issues.apache.org/jira/browse/KAFKA-3666 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274035#comment-15274035 ] Ryan P commented on KAFKA-3665: --- [~ijuma], I can absolutely do that. Would you like me to include the

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274052#comment-15274052 ] Ismael Juma commented on KAFKA-3665: [~Ryan P], that sounds great. The reason why I want to do that

[GitHub] kafka pull request: KAFKA-3673: Connect tests don't handle concurr...

GitHub user Ishiihara opened a pull request: https://github.com/apache/kafka/pull/1340 KAFKA-3673: Connect tests don't handle concurrent config changes You can merge this pull request into a Git repository by running: $ git pull https://github.com/Ishiihara/kafka

[jira] [Commented] (KAFKA-3673) Connect tests dont handle concurrent config changes

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

[jira] [Updated] (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:all-tabpanel ] Vahid Hashemian updated KAFKA-3144: --- Status: Patch Available (was: Open) > report members with no assigned partitions in

Re: KIP-57: Interoperable LZ4 Framing

Updated: https://cwiki.apache.org/confluence/display/KAFKA/KIP-57+-+Interoperable+LZ4+Framing Should I restart the vote? -Dana On Fri, May 6, 2016 at 2:12 PM, Ismael Juma wrote: > On Sun, May 1, 2016 at 3:57 AM, Dana Powers wrote: >> >> > 2. We're

Re: KIP-57: Interoperable LZ4 Framing

On Fri, May 6, 2016 at 11:07 PM, Dana Powers wrote: > Updated: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-57+-+Interoperable+LZ4+Framing > > Should I restart the vote? > I think the update is small enough that we don't need to restart the vote. Ismael

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

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

See Changes: [ismael] KAFKA-3669; Add secondary constructor for KafkaConfig with a default [ismael] KAFKA-3655; awaitFlushCompletion() in RecordAccumulator should always -- [...truncated 8747

Re: KIP-57: Interoperable LZ4 Framing

Ok -- removed Public Interfaces discussion. It should be up to date w/ PR review comments now. -Dana On Fri, May 6, 2016 at 2:15 PM, Ismael Juma wrote: > One more suggestion Dana, I would remove the "Public interfaces" section as > those classes are not actually public (only

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

See Changes: [ismael] KAFKA-3669; Add secondary constructor for KafkaConfig with a default [ismael] KAFKA-3655; awaitFlushCompletion() in RecordAccumulator should always -- [...truncated 2154

[jira] [Work started] (KAFKA-3670) ControlledShutdownLeaderSelector should pick the preferred replica as the new leader, if possible

[ https://issues.apache.org/jira/browse/KAFKA-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3670 started by Ismael Juma. -- > ControlledShutdownLeaderSelector should pick the preferred replica as the new >

[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=15274917#comment-15274917 ] Jun Rao commented on KAFKA-3565: [~becket_qin], any new findings on the consumer performance? Thanks. >

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15273917#comment-15273917 ] Rajini Sivaram commented on KAFKA-3665: --- [~ijuma] I agree that secure installations of Kafka would

  1   2   >