[GitHub] kafka pull request: MINOR: Revert 0.10.0 branch to SNAPSHOT per ch...

Github user gwenshap closed the pull request at: https://github.com/apache/kafka/pull/1126 --- 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-3434) Add old ConsumerRecord constructor for compatibility

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

Re: Messages corrupted in kafka

I am using java client and kafka 0.8.2, since events are corrupted in kafka broker i cant read and replay them again. On Thu, Mar 24, 2016 at 9:42 AM, Becket Qin wrote: > Hi Sunil, > > The messages in Kafka has a CRC stored with each of them. When consumer > receives a

Re: Messages corrupted in kafka

Hi Sunil, The messages in Kafka has a CRC stored with each of them. When consumer receives a message, it will compute the CRC from the message bytes and compare it to the stored CRC. If the computed CRC and stored CRC does not match, that indicates the message has corrupted. I am not sure in your

Re: Messages corrupted in kafka

can some one help me out here. On Wed, Mar 23, 2016 at 7:36 PM, sunil kalva wrote: > Hi > I am seeing few messages getting corrupted in kafka, It is not happening > frequently and percentage is also very very less (less than 0.1%). > > Basically i am publishing thrift

[jira] [Updated] (KAFKA-3418) Add section on detecting consumer failures in new consumer javadoc

[ https://issues.apache.org/jira/browse/KAFKA-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3418: --- Status: Patch Available (was: In Progress) > Add section on detecting consumer failures in

[jira] [Commented] (KAFKA-3418) Add section on detecting consumer failures in new consumer javadoc

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

[GitHub] kafka pull request: KAFKA-3418: add javadoc section describing con...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1129 KAFKA-3418: add javadoc section describing consumer failure detection You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka

Re: [VOTE] KIP-35: Retrieving protocol version

We (Jay + me) had some extra information we wanted to see in the KIP before we are comfortable voting: * Where does the Java client fits in. Hopefully we can use this KIP to standardize behavior and guarantees between Java and non-Java clients, so when we reason about the Java clients, which most

[jira] [Commented] (KAFKA-2309) ISR shrink rate not updated on LeaderAndIsr request with shrunk ISR

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

[GitHub] kafka pull request: KAFKA-2309; ISR shrink rate not updated on Lea...

GitHub user auradkar reopened a pull request: https://github.com/apache/kafka/pull/185 KAFKA-2309; ISR shrink rate not updated on LeaderAndIsr request with shrunk ISR Currently, a LeaderAndIsrRequest does not mark the isrShrinkRate if the received ISR is smaller than the existing

Re: [VOTE] KIP-35: Retrieving protocol version

speaking of pending KIPs, what's the status on this one? On Fri, Mar 18, 2016 at 9:47 PM, Ashish Singh wrote: > Hey Jay, > > Answers inline. > > On Fri, Mar 18, 2016 at 10:45 AM, Jay Kreps wrote: > > Hey Ashish, > > > > Couple quick things: > > > > 1.

[jira] [Updated] (KAFKA-3434) Add old ConsumerRecord constructor for compatibility

[ https://issues.apache.org/jira/browse/KAFKA-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3434: --- Reviewer: Ewen Cheslack-Postava (was: Jun Rao) > Add old ConsumerRecord constructor for

[jira] [Updated] (KAFKA-2370) Add pause/unpause connector support

[ https://issues.apache.org/jira/browse/KAFKA-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2370: --- Priority: Critical (was: Blocker) > Add pause/unpause connector support >

[jira] [Updated] (KAFKA-2370) Add pause/unpause connector support

[ https://issues.apache.org/jira/browse/KAFKA-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2370: --- Fix Version/s: (was: 0.10.0.0) 0.10.1.0 > Add pause/unpause connector support

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

See Changes: [wangguoz] MINOR: remove streams-smoke-test.sh -- [...truncated 3797 lines...] org.apache.kafka.common.config.ConfigDefTest > testInvalidDefaultString PASSED

[jira] [Commented] (KAFKA-2309) ISR shrink rate not updated on LeaderAndIsr request with shrunk ISR

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

[GitHub] kafka pull request: KAFKA-2309; ISR shrink rate not updated on Lea...

Github user auradkar closed the pull request at: https://github.com/apache/kafka/pull/185 --- 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-3427) broker can return incorrect version of fetch response when the broker hits an unknown exception

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

[GitHub] kafka pull request: KAFKA-3427 - Broker should return correct vers...

GitHub user auradkar opened a pull request: https://github.com/apache/kafka/pull/1128 KAFKA-3427 - Broker should return correct version of FetchResponse on exception Merging the fix from: https://issues.apache.org/jira/browse/KAFKA-3427 The original version of the code,

Jenkins build is back to normal : kafka-0.10.0-jdk7 #12

See

[jira] [Updated] (KAFKA-3453) Transient test failures due to MiniKDC port allocation strategy

[ https://issues.apache.org/jira/browse/KAFKA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3453: --- Fix Version/s: 0.10.0.1 > Transient test failures due to MiniKDC port allocation strategy >

[jira] [Commented] (KAFKA-3453) Transient test failures due to MiniKDC port allocation strategy

[ https://issues.apache.org/jira/browse/KAFKA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209443#comment-15209443 ] Ismael Juma commented on KAFKA-3453: Plan is to update to MiniKDC 2.8.0 when it is released. Assigned

[jira] [Assigned] (KAFKA-3453) Transient test failures due to MiniKDC port allocation strategy

[ https://issues.apache.org/jira/browse/KAFKA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-3453: -- Assignee: Ismael Juma > Transient test failures due to MiniKDC port allocation strategy >

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

See Changes: [wangguoz] MINOR: remove streams-smoke-test.sh -- [...truncated 3089 lines...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[3] PASSED

[jira] [Commented] (KAFKA-3453) Transient test failures due to MiniKDC port allocation strategy

[ https://issues.apache.org/jira/browse/KAFKA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209404#comment-15209404 ] Ismael Juma commented on KAFKA-3453: MiniKDC has recently received a fix for something similar to what

[jira] [Commented] (KAFKA-3454) Add Kafka Streams section in documentation

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

[GitHub] kafka pull request: [WIP] KAFKA-3454: add Kafka Streams web docs

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1127 [WIP] KAFKA-3454: add Kafka Streams web docs You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka KStreamsDocs

Re: [VOTE] KIP-43: Kafka SASL enhancements

Sorry! Got distracted by the impending release! +1 on the current revision of the KIP. On Wed, Mar 23, 2016 at 3:33 PM, Harsha wrote: > Any update on this. Gwen since the KIP is adjusted to address the > pluggable classes we should make a move on this. > > Rajini, >

Re: Fallout from upgrading to kafka 0.9.0.0 from 0.8.2.1

More information about the issue: When the issue happens, the controller is always on the 0.9 version Kafka broker. In server.log of other brokers, we can see this kind of error: [2016-03-23 22:36:02,814] ERROR [ReplicaFetcherThread-0-5], Error for partition [topic,208] to broker

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

See Changes: [wangguoz] HOTFIX: fix NPE in changelogger -- [...truncated 5242 lines...] org.apache.kafka.streams.kstream.internals.KTableKTableOuterJoinTest > testNotSendingOldValue PASSED

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

See Changes: [wangguoz] KAFKA-3432; Cluster.update() thread-safety [wangguoz] HOTFIX: fix NPE in changelogger -- [...truncated 4389 lines...] kafka.admin.AdminRackAwareTest >

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

See Changes: [wangguoz] HOTFIX: fix NPE in changelogger [wangguoz] MINOR: remove streams-smoke-test.sh -- [...truncated 1557 lines...] kafka.log.BrokerCompressionTest >

Re: [VOTE] KIP-43: Kafka SASL enhancements

Any update on this. Gwen since the KIP is adjusted to address the pluggable classes we should make a move on this. Rajini, Can you restart the voting thread. Thanks, Harsha On Wed, Mar 16, 2016, at 06:42 AM, Rajini Sivaram wrote: > As discussed in the KIP meeting yesterday, the scope

[GitHub] kafka pull request: MINOR: Revert 0.10.0 branch to SNAPSHOT per ch...

GitHub user gwenshap opened a pull request: https://github.com/apache/kafka/pull/1126 MINOR: Revert 0.10.0 branch to SNAPSHOT per change in release process You can merge this pull request into a Git repository by running: $ git pull https://github.com/gwenshap/kafka

Jenkins build is back to normal : kafka-0.10.0-jdk7 #10

See

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

See Changes: [cshapi] KAFKA-3441: 0.10.0 documentation still says "0.9.0" -- [...truncated 5274 lines...] org.apache.kafka.streams.processor.TopologyBuilderTest > testAddSinkWithSelfParent

[GitHub] kafka pull request: MINOR: remove streams-smoke-test.sh

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/1125 MINOR: remove streams-smoke-test.sh @guozhangwang You can merge this pull request into a Git repository by running: $ git pull https://github.com/ymatsuda/kafka remove_smoketest_shell_script

[GitHub] kafka pull request: HOTFIX: fix NPE in changelogger

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1124 --- 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: HOTFIX: fix NPE in changelogger

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/1124 HOTFIX: fix NPE in changelogger Fix NPE in StoreChangeLogger caused by a record out of window retention period. @guozhangwang You can merge this pull request into a Git repository by

[jira] [Work started] (KAFKA-3434) Add old ConsumerRecord constructor for compatibility

[ https://issues.apache.org/jira/browse/KAFKA-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3434 started by Jason Gustafson. -- > Add old ConsumerRecord constructor for compatibility >

[jira] [Updated] (KAFKA-3434) Add old ConsumerRecord constructor for compatibility

[ https://issues.apache.org/jira/browse/KAFKA-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3434: --- Status: Patch Available (was: In Progress) > Add old ConsumerRecord constructor for

[jira] [Work started] (KAFKA-3418) Add section on detecting consumer failures in new consumer javadoc

[ https://issues.apache.org/jira/browse/KAFKA-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3418 started by Jason Gustafson. -- > Add section on detecting consumer failures in new consumer javadoc >

[jira] [Updated] (KAFKA-3418) Add section on detecting consumer failures in new consumer javadoc

[ https://issues.apache.org/jira/browse/KAFKA-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3418: --- Description: There still seems to be a lot of confusion about the design of the poll() loop

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

See Changes: [cshapi] KAFKA-3441: 0.10.0 documentation still says "0.9.0" [wangguoz] KAFKA-3432; Cluster.update() thread-safety -- [...truncated 1769 lines...]

[jira] [Updated] (KAFKA-3432) Cluster.update() thread-safety

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

[jira] [Commented] (KAFKA-3432) Cluster.update() thread-safety

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

[GitHub] kafka pull request: KAFKA-3432; Cluster.update() thread-safety

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1118 --- 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] [Created] (KAFKA-3455) Connect custom processors with the streams DSL

Jonathan Bender created KAFKA-3455: -- Summary: Connect custom processors with the streams DSL Key: KAFKA-3455 URL: https://issues.apache.org/jira/browse/KAFKA-3455 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-3454) Add Kafka Streams section in documentation

Guozhang Wang created KAFKA-3454: Summary: Add Kafka Streams section in documentation Key: KAFKA-3454 URL: https://issues.apache.org/jira/browse/KAFKA-3454 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-3441) 0.10.0 documentation still says "0.9.0"

[ https://issues.apache.org/jira/browse/KAFKA-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3441: Fix Version/s: 0.10.1.0 > 0.10.0 documentation still says "0.9.0" >

Re: [ANN] Small change to release process

Works for me. Thanks for the quick response! On Wed, Mar 23, 2016 at 3:09 PM, Gwen Shapira wrote: > It was decided (rather unilaterally by your humble release manager), but > that doesn't mean decisions can't change :) > > 1. We can definitely have multiple tags for each

Re: [ANN] Small change to release process

It was decided (rather unilaterally by your humble release manager), but that doesn't mean decisions can't change :) 1. We can definitely have multiple tags for each separate RC. Actually I think this is better than moving the tag. 2. We can't change release artifacts after the vote, which mean

[jira] [Resolved] (KAFKA-3441) 0.10.0 documentation still says "0.9.0"

[ https://issues.apache.org/jira/browse/KAFKA-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KAFKA-3441. Resolution: Fixed > 0.10.0 documentation still says "0.9.0" >

[jira] [Created] (KAFKA-3453) Transient test failures due to MiniKDC port allocation strategy

Ewen Cheslack-Postava created KAFKA-3453: Summary: Transient test failures due to MiniKDC port allocation strategy Key: KAFKA-3453 URL: https://issues.apache.org/jira/browse/KAFKA-3453

Re: [ANN] Small change to release process

Hi Gwen, Is the new release process already decided? If so you can ignore my question below. Since we are making a change to the process. What do you think about publishing release candidates using "RC" in the version? So instead of re-using the 0.10.0.0 tag and using 0.10.0.0-SNAPSHOT as the

[jira] [Commented] (KAFKA-3441) 0.10.0 documentation still says "0.9.0"

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

[GitHub] kafka pull request: KAFKA-3441: 0.10.0 documentation still says "0...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1122 --- 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-3434) Add old ConsumerRecord constructor for compatibility

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

[GitHub] kafka pull request: KAFKA-3434: add old constructor to ConsumerRec...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1123 KAFKA-3434: add old constructor to ConsumerRecord You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-3434 Alternatively

[ANN] Small change to release process

Hey Team Kafka, As you know, our current release process is: * Branch * Change version from 0.10.0.0-SNAPSHOT to 0.10.0.0 * Roll out a release candidate with version 0.10.0.0 * Fix bugs and keep rolling out release candidates * After vote passed and release was published, bump the branch to

RE: [VOTE] KIP-51 - List Connectors REST API

+1 (non-binding) +1 for re-evaluating the KIP process. This one went through very quickly, but they can drag on sometimes. > Date: Wed, 23 Mar 2016 11:31:37 -0700 > Subject: Re: [VOTE] KIP-51 - List Connectors REST API > From: wangg...@gmail.com > To:

Re: [VOTE] KIP-51 - List Connectors REST API

+1. On Wed, Mar 23, 2016 at 10:24 AM, Ashish Singh wrote: > +1 (non-binding) > > On Wed, Mar 23, 2016 at 10:00 AM, Gwen Shapira wrote: > > > Very large +1 on re-evaluating the KIP process. > > > > I was hoping we can do a meta-kip meeting after the

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

See Changes: [wangguoz] KAFKA-3409: handle CommitFailedException in MirrorMaker -- [...truncated 1555 lines...] kafka.integration.AutoOffsetResetTest > testResetToLatestWhenOffsetTooLow PASSED

[jira] [Created] (KAFKA-3452) Support session windows besides time interval windows

Guozhang Wang created KAFKA-3452: Summary: Support session windows besides time interval windows Key: KAFKA-3452 URL: https://issues.apache.org/jira/browse/KAFKA-3452 Project: Kafka Issue

[jira] [Commented] (KAFKA-3441) 0.10.0 documentation still says "0.9.0"

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

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

See Changes: [wangguoz] KAFKA-3409: handle CommitFailedException in MirrorMaker -- [...truncated 3153 lines...] at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:947)

[GitHub] kafka pull request: KAFKA-3441: 0.10.0 documentation still says "0...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/1122 KAFKA-3441: 0.10.0 documentation still says "0.9.0" You can merge this pull request into a Git repository by running: $ git pull https://github.com/granthenke/kafka docs-10 Alternatively

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

See Changes: [wangguoz] KAFKA-3409: handle CommitFailedException in MirrorMaker -- [...truncated 1573 lines...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[17] PASSED

Re: [VOTE] KIP-51 - List Connectors REST API

+1 (non-binding) On Wed, Mar 23, 2016 at 10:00 AM, Gwen Shapira wrote: > Very large +1 on re-evaluating the KIP process. > > I was hoping we can do a meta-kip meeting after the release (Maybe even > in-person at Kafka Summit?) to discuss. > > On Tue, Mar 22, 2016 at 7:59 PM,

[jira] [Updated] (KAFKA-3451) Add basic HTML coverage report generation to gradle

[ https://issues.apache.org/jira/browse/KAFKA-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3451: --- Attachment: Jacoco-html.zip scoverage.zip > Add basic HTML coverage report generation

[jira] [Updated] (KAFKA-3451) Add basic HTML coverage report generation to gradle

[ https://issues.apache.org/jira/browse/KAFKA-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3451: --- Status: Patch Available (was: Open) > Add basic HTML coverage report generation to gradle >

[jira] [Commented] (KAFKA-3451) Add basic HTML coverage report generation to gradle

[ https://issues.apache.org/jira/browse/KAFKA-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208786#comment-15208786 ] Grant Henke commented on KAFKA-3451: Attached sample report output. > Add basic HTML coverage report

[jira] [Commented] (KAFKA-3451) Add basic HTML coverage report generation to gradle

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

[GitHub] kafka pull request: KAFKA-3451: Add basic HTML coverage report gen...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/1121 KAFKA-3451: Add basic HTML coverage report generation to gradle You can merge this pull request into a Git repository by running: $ git pull https://github.com/granthenke/kafka coverage

[jira] [Created] (KAFKA-3451) Add basic HTML coverage report generation to gradle

Grant Henke created KAFKA-3451: -- Summary: Add basic HTML coverage report generation to gradle Key: KAFKA-3451 URL: https://issues.apache.org/jira/browse/KAFKA-3451 Project: Kafka Issue Type:

Re: [VOTE] KIP-51 - List Connectors REST API

Very large +1 on re-evaluating the KIP process. I was hoping we can do a meta-kip meeting after the release (Maybe even in-person at Kafka Summit?) to discuss. On Tue, Mar 22, 2016 at 7:59 PM, Grant Henke wrote: > +1 (non-binding) > > I am also a +1 to evaluating the KIP

[jira] [Commented] (KAFKA-3003) The fetch.wait.max.ms is not honored when new log segment rolled for low volume topics.

[ https://issues.apache.org/jira/browse/KAFKA-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208764#comment-15208764 ] Jiangjie Qin commented on KAFKA-3003: - In this particular case, the problem was due to high watermark

[jira] [Resolved] (KAFKA-3409) Mirror maker hangs indefinitely due to commit

[ https://issues.apache.org/jira/browse/KAFKA-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3409. -- Resolution: Fixed Issue resolved by pull request 1115

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208751#comment-15208751 ] Gwen Shapira commented on KAFKA-3442: - Perfect! Thank you [~dana.powers] for testing our release

[jira] [Commented] (KAFKA-3409) Mirror maker hangs indefinitely due to commit

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

[GitHub] kafka pull request: KAFKA-3409: handle CommitFailedException in Mi...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1115 --- 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-3135) Unexpected delay before fetch response transmission

[ https://issues.apache.org/jira/browse/KAFKA-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208740#comment-15208740 ] Jason Gustafson commented on KAFKA-3135: [~rangadi] [~kciesielski] Thanks for letting me know. I

[jira] [Updated] (KAFKA-3135) Unexpected delay before fetch response transmission

[ https://issues.apache.org/jira/browse/KAFKA-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3135: --- Priority: Critical (was: Major) > Unexpected delay before fetch response transmission >

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

See Changes: [junrao] KAFKA-3442; Fix FileMessageSet iterator. -- [...truncated 3133 lines...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[17] PASSED

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208721#comment-15208721 ] Dana Powers commented on KAFKA-3442: +1. verified test passes on trunk commit `7af67ce` >

[jira] [Commented] (KAFKA-960) Upgrade Metrics to 3.x

[ https://issues.apache.org/jira/browse/KAFKA-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208671#comment-15208671 ] Xavier Stevens commented on KAFKA-960: -- We would be interested in having this still. Latest dropwizard

[jira] [Commented] (KAFKA-3400) Topic stop working / can't describe topic

[ https://issues.apache.org/jira/browse/KAFKA-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208642#comment-15208642 ] Tobias commented on KAFKA-3400: --- I tried building from trunk (0.10.1.0) and recreated the cluster but still

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

See Changes: [junrao] KAFKA-3442; Fix FileMessageSet iterator. -- [...truncated 1591 lines...] kafka.log.LogTest > testTruncateTo PASSED kafka.log.LogTest > testCleanShutdownFile PASSED

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

See Changes: [junrao] KAFKA-3442; Fix FileMessageSet iterator. -- [...truncated 1605 lines...] kafka.consumer.ZookeeperConsumerConnectorTest > testConsumerDecoder PASSED

[jira] [Comment Edited] (KAFKA-3400) Topic stop working / can't describe topic

[ https://issues.apache.org/jira/browse/KAFKA-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208542#comment-15208542 ] Tobias edited comment on KAFKA-3400 at 3/23/16 3:11 PM: I also checked the data

[jira] [Commented] (KAFKA-3400) Topic stop working / can't describe topic

[ https://issues.apache.org/jira/browse/KAFKA-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208542#comment-15208542 ] Tobias commented on KAFKA-3400: --- I also checked the data directories and the only topic to have any files

[jira] [Commented] (KAFKA-3400) Topic stop working / can't describe topic

[ https://issues.apache.org/jira/browse/KAFKA-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208531#comment-15208531 ] Tobias commented on KAFKA-3400: --- More research. I've now setup a completely new cluster using auto.create

[jira] [Commented] (KAFKA-3135) Unexpected delay before fetch response transmission

[ https://issues.apache.org/jira/browse/KAFKA-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208512#comment-15208512 ] Raghu Angadi commented on KAFKA-3135: - [~hachikuji], mine is also on Linux with Java8 (docker

[jira] [Updated] (KAFKA-3135) Unexpected delay before fetch response transmission

[ https://issues.apache.org/jira/browse/KAFKA-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3135: --- Fix Version/s: 0.10.0.1 > Unexpected delay before fetch response transmission >

[jira] [Commented] (KAFKA-3296) All consumer reads hang indefinately

[ https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208491#comment-15208491 ] Jun Rao commented on KAFKA-3296: [~thecoop1984], thanks for the results. We will need to figure out why

[GitHub] kafka pull request: KAFKA-3442: Fix FileMessageSet iterator.

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1112 --- 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-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208459#comment-15208459 ] Jun Rao commented on KAFKA-3442: [~dana.powers], this issue is fixed now. Could you verify that with your

[jira] [Updated] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

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

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

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

  1   2   >