Re: [DISCUSS] KIP-35 - Retrieve protocol version

I agree with Jason we should aim to have clients to properly detect and handle unknown-protocol error. The hack of empty response should be shorten solution. After reading the earlier discussion and wiki, I have two questions: - In the future, do we expect all clients to send ProtocolVersionReque

Kafka License Detail

Hi All, We are using Apache Kafka for our messaging functionalities. We have developed the messaging system using Kafka. Now we are planning to setup in production environment. *Please any one confirm me the Apache Kafka is free of cost?* *Can we use it in Production environment?* Thanks, Sug

Re: [DISCUSS] KIP-35 - Retrieve protocol version

2015-10-07 9:49 GMT+02:00 Dong Lin : > I agree with Jason we should aim to have clients to properly detect and > handle unknown-protocol error. The hack of empty response should be shorten > solution. > Yes, in the long run we want to modify the common protocol response header to include a reques

Re: Kafka License Detail

Sugumar, The short answer is yes to both your questions, but if you have any specific concern, I suggest you have a look at the Apache License under which Kafka is distributed: http://www.apache.org/licenses/LICENSE-2.0 -Flavio > On 07 Oct 2015,

[jira] [Work started] (KAFKA-2614) No more clients can connect after `TooManyConnectionsException` threshold (max.connections.per.ip) is reached

[ https://issues.apache.org/jira/browse/KAFKA-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-2614 started by Ismael Juma. -- > No more clients can connect after `TooManyConnectionsException` threshold > (max.c

[jira] [Commented] (KAFKA-2614) No more clients can connect after `TooManyConnectionsException` threshold (max.connections.per.ip) is reached

[ https://issues.apache.org/jira/browse/KAFKA-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946786#comment-14946786 ] Ismael Juma commented on KAFKA-2614: Thanks for filing this, there is indeed an issue

[jira] [Updated] (KAFKA-2609) SSL renegotiation code paths need more tests

[ https://issues.apache.org/jira/browse/KAFKA-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-2609: -- Fix Version/s: (was: 0.9.0.0) 0.10.0.0 Changing the target version as per

[jira] [Updated] (KAFKA-2572) zk connection instability

[ https://issues.apache.org/jira/browse/KAFKA-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Firth updated KAFKA-2572: -- Description: On several occasions, we've seen our process enter a cycle of: zk session expiry; new sess

[jira] [Updated] (KAFKA-2572) zk connection instability

[ https://issues.apache.org/jira/browse/KAFKA-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Firth updated KAFKA-2572: -- Description: On two occasions, we've seen our process enter a cycle of: zk session expiry; new session

Re: [jira] [Updated] (KAFKA-2572) zk connection instability

This sounds an awful lot like GC activity. Have you checked to see if you are having full GCs that would pause your application and cause a timeout? -Clark Sent from my iPhone > On Oct 7, 2015, at 8:39 AM, John Firth (JIRA) wrote: > > > [ > https://issues.apache.org/jira/browse/KAFKA-25

[jira] [Commented] (KAFKA-2103) kafka.producer.AsyncProducerTest failure.

[ https://issues.apache.org/jira/browse/KAFKA-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947034#comment-14947034 ] Eno Thereska commented on KAFKA-2103: - Part of this test is still failing for me regul

[jira] [Reopened] (KAFKA-2103) kafka.producer.AsyncProducerTest failure.

[ https://issues.apache.org/jira/browse/KAFKA-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reopened KAFKA-2103: - This test fails for me repeatedly on latest MacOS (but not on Ubuntu): kafka.common.FailedToSendMessag

[jira] [Commented] (KAFKA-2058) ProducerTest.testSendWithDeadBroker transient failure

[ https://issues.apache.org/jira/browse/KAFKA-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947048#comment-14947048 ] Eno Thereska commented on KAFKA-2058: - I get this too intermittently under Ubuntu: Dis

[jira] [Commented] (KAFKA-2587) Transient test failure: `SimpleAclAuthorizerTest`

[ https://issues.apache.org/jira/browse/KAFKA-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947054#comment-14947054 ] Eno Thereska commented on KAFKA-2587: - I get this too on trunk, under Ubuntu but not M

Kafka dotnet SDK suggestion

Hi All, We are developing Messaging system with Kafka using DotNet (C#). We found there are 2 different SDK available for Dotnet 1. https://github.com/Jroland/kafka-net/ 2. https://github.com/ExactTargetDev/kafka-net First one is officially referred by Apache Kafka. But It is an initial stage,

[GitHub] kafka pull request: KAFKA-2534: Fixes and unit tests for SSLTransp...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/205 --- 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-2534) SSLTransportLayer does not handle buffer overflow correctly

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

[jira] [Updated] (KAFKA-2534) SSLTransportLayer does not handle buffer overflow correctly

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

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

See Changes: [junrao] KAFKA-2534: Fixes and unit tests for SSLTransportLayer buffer overflow -- [...truncated 1450 lines...] kafka.integration.PlaintextTopicMetadataTest > testAliveBrokersListWi

[jira] [Created] (KAFKA-2618) Disable SSL renegotiation for 0.9.0.0

Ismael Juma created KAFKA-2618: -- Summary: Disable SSL renegotiation for 0.9.0.0 Key: KAFKA-2618 URL: https://issues.apache.org/jira/browse/KAFKA-2618 Project: Kafka Issue Type: Bug Com

[jira] [Updated] (KAFKA-2618) Disable SSL renegotiation for 0.9.0.0

[ https://issues.apache.org/jira/browse/KAFKA-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2618: --- Description: As discussed in KAFKA-2609, we don't have enough tests for SSL renegotiation to be confi

[jira] [Commented] (KAFKA-2618) Disable SSL renegotiation for 0.9.0.0

[ https://issues.apache.org/jira/browse/KAFKA-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947220#comment-14947220 ] Ismael Juma commented on KAFKA-2618: cc [~junrao] [~rsivaram] [~harsha_ch] > Disable

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

See Changes: [junrao] KAFKA-2534: Fixes and unit tests for SSLTransportLayer buffer overflow -- [...truncated 3282 lines...] kafka.integration.SslTopicMetadataTest > testAutoCreateTopicWithCollisi

[jira] [Commented] (KAFKA-1894) Avoid long or infinite blocking in the consumer

[ https://issues.apache.org/jira/browse/KAFKA-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947277#comment-14947277 ] Onur Karaman commented on KAFKA-1894: - Just for reference, this is similar to the foll

[jira] [Commented] (KAFKA-2391) Blocking call such as position(), partitionsFor(), committed() and listTopics() should have a timeout

[ https://issues.apache.org/jira/browse/KAFKA-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947279#comment-14947279 ] Onur Karaman commented on KAFKA-2391: - As brought up earlier, blocking for request.tim

[jira] [Updated] (KAFKA-2428) Add sanity test in kafkaConsumer for the timeouts. This is a followup ticket for Kafka-2120

[ https://issues.apache.org/jira/browse/KAFKA-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2428: --- Reviewer: Joel Koshy Status: Patch Available (was: Open) There is a PR, so setting the status t

[jira] [Commented] (KAFKA-1894) Avoid long or infinite blocking in the consumer

[ https://issues.apache.org/jira/browse/KAFKA-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947298#comment-14947298 ] Jason Gustafson commented on KAFKA-1894: [~onurkaraman] Maybe we clarify the scope

[GitHub] kafka pull request: KAFKA-2391 [WIP]: add timeout to KafkaConsumer...

GitHub user onurkaraman opened a pull request: https://github.com/apache/kafka/pull/283 KAFKA-2391 [WIP]: add timeout to KafkaConsumer blocking calls You can merge this pull request into a Git repository by running: $ git pull https://github.com/onurkaraman/kafka KAFKA-2391 A

[jira] [Commented] (KAFKA-2391) Blocking call such as position(), partitionsFor(), committed() and listTopics() should have a timeout

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

[jira] [Created] (KAFKA-2619) Kafka tools dont allow override of some properties using config files

Rajini Sivaram created KAFKA-2619: - Summary: Kafka tools dont allow override of some properties using config files Key: KAFKA-2619 URL: https://issues.apache.org/jira/browse/KAFKA-2619 Project: Kafka

[jira] [Updated] (KAFKA-2619) Kafka tools dont allow override of some properties using config files

[ https://issues.apache.org/jira/browse/KAFKA-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-2619: -- Description: [~ewencp] pointed out in the PR review of KAFKA-2581 that the parsing of config fil

[GitHub] kafka-site pull request: updated contributing.html

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

[jira] [Commented] (KAFKA-2598) Add Test with authorizer for producer and consumer

[ https://issues.apache.org/jira/browse/KAFKA-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947369#comment-14947369 ] Jun Rao commented on KAFKA-2598: [~parth.brahmbhatt], are you still working on this? Thank

[jira] [Created] (KAFKA-2620) Introduce Scalariform

Grant Henke created KAFKA-2620: -- Summary: Introduce Scalariform Key: KAFKA-2620 URL: https://issues.apache.org/jira/browse/KAFKA-2620 Project: Kafka Issue Type: Bug Components: build

[GitHub] kafka pull request: KAFKA-2620: Introduce Scalariform

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/284 KAFKA-2620: Introduce Scalariform This is a WIP. There will likely need to be discussion around a rule set we want to use and if we actually want to include this in the build. This could also be

[jira] [Commented] (KAFKA-2620) Introduce Scalariform

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

[jira] [Created] (KAFKA-2621) nextOffsetMetadata should be changed after rolling a new log segment

Jun Rao created KAFKA-2621: -- Summary: nextOffsetMetadata should be changed after rolling a new log segment Key: KAFKA-2621 URL: https://issues.apache.org/jira/browse/KAFKA-2621 Project: Kafka Issue

[jira] [Commented] (KAFKA-2598) Add Test with authorizer for producer and consumer

[ https://issues.apache.org/jira/browse/KAFKA-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947417#comment-14947417 ] Parth Brahmbhatt commented on KAFKA-2598: - I just started yesterday, should have a

[jira] [Commented] (KAFKA-2620) Introduce Scalariform

[ https://issues.apache.org/jira/browse/KAFKA-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947425#comment-14947425 ] Ismael Juma commented on KAFKA-2620: I was thinking we'd use Scalastyle (KAFKA-2423).

[jira] [Assigned] (KAFKA-2621) nextOffsetMetadata should be changed after rolling a new log segment

[ https://issues.apache.org/jira/browse/KAFKA-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin reassigned KAFKA-2621: --- Assignee: Dong Lin > nextOffsetMetadata should be changed after rolling a new log segment > -

[jira] [Commented] (KAFKA-2620) Introduce Scalariform

[ https://issues.apache.org/jira/browse/KAFKA-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947464#comment-14947464 ] Grant Henke commented on KAFKA-2620: [~ijuma] I agree we should use Scalastyle as well

[GitHub] kafka pull request: KAFKA-2419; Garbage collect unused sensors

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/233 --- 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] [Resolved] (KAFKA-2419) Allow certain Sensors to be garbage collected after inactivity

[ https://issues.apache.org/jira/browse/KAFKA-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy resolved KAFKA-2419. --- Resolution: Fixed > Allow certain Sensors to be garbage collected after inactivity > -

[jira] [Commented] (KAFKA-2419) Allow certain Sensors to be garbage collected after inactivity

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

[jira] [Updated] (KAFKA-2527) System Test for Quotas in Ducktape

[ https://issues.apache.org/jira/browse/KAFKA-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-2527: Fix Version/s: 0.9.0.0 > System Test for Quotas in Ducktape > -- > >

[jira] [Updated] (KAFKA-2171) System Test for Quotas

[ https://issues.apache.org/jira/browse/KAFKA-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-2171: Resolution: Duplicate Status: Resolved (was: Patch Available) Discard this patch in favor of quota

[jira] [Updated] (KAFKA-2527) System Test for Quotas in Ducktape

[ https://issues.apache.org/jira/browse/KAFKA-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-2527: Labels: quota (was: ) > System Test for Quotas in Ducktape > -- > >

[jira] [Commented] (KAFKA-2593) KeyValueStores should not require use of the context's default serializers and deserializers

[ https://issues.apache.org/jira/browse/KAFKA-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947520#comment-14947520 ] Randall Hauch commented on KAFKA-2593: -- ~guozhang, I've replaced the static factory m

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

See Changes: [jjkoshy] KAFKA-2419; Garbage collect unused sensors -- [...truncated 2742 lines...] kafka.coordinator.ConsumerCoordinatorResponseTest > testValidHeartbeat PASSED kafka.zk.ZKEpheme

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

See Changes: [jjkoshy] KAFKA-2419; Garbage collect unused sensors -- [...truncated 2084 lines...] kafka.coordinator.PartitionAssignorTest > testRangeAssignorOneConsumerMultipleTopics PASSED kafka

[jira] [Created] (KAFKA-2622) Add Time logical type for Copycat

Ewen Cheslack-Postava created KAFKA-2622: Summary: Add Time logical type for Copycat Key: KAFKA-2622 URL: https://issues.apache.org/jira/browse/KAFKA-2622 Project: Kafka Issue Type: S

[GitHub] kafka pull request: KAFKA-2622: Add Time logical type for Copycat.

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/285 KAFKA-2622: Add Time logical type for Copycat. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ewencp/kafka kafka-2622-time-logical-type Alternat

[jira] [Commented] (KAFKA-2622) Add Time logical type for Copycat

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

[jira] [Created] (KAFKA-2623) Kakfa broker not deleting logs after configured retention time properly

Hao Zhang created KAFKA-2623: Summary: Kakfa broker not deleting logs after configured retention time properly Key: KAFKA-2623 URL: https://issues.apache.org/jira/browse/KAFKA-2623 Project: Kafka

[jira] [Updated] (KAFKA-2623) Kakfa broker not deleting logs after configured retention time properly

[ https://issues.apache.org/jira/browse/KAFKA-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Zhang updated KAFKA-2623: - Environment: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.04 DISTRIB_CODENAME=precise DISTRIB_DESCRIPTION="Ubuntu

[GitHub] kafka pull request: Kafka-2587: Only notification handler will upd...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/277 --- 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] [Resolved] (KAFKA-2587) Transient test failure: `SimpleAclAuthorizerTest`

[ https://issues.apache.org/jira/browse/KAFKA-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-2587. Resolution: Fixed Issue resolved by pull request 277 [https://github.com/apache/kafka/pull/277] > Transient

[GitHub] kafka pull request: KAFKA-2428

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/282 --- 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] [Updated] (KAFKA-2428) Add sanity test in kafkaConsumer for the timeouts. This is a followup ticket for Kafka-2120

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

[jira] [Commented] (KAFKA-2428) Add sanity test in kafkaConsumer for the timeouts. This is a followup ticket for Kafka-2120

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

[jira] [Commented] (KAFKA-2598) Add Test with authorizer for producer and consumer

[ https://issues.apache.org/jira/browse/KAFKA-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947921#comment-14947921 ] Jun Rao commented on KAFKA-2598: You could get identities through SSL if you set up 2-way

[jira] [Updated] (KAFKA-2622) Add Time logical type for Copycat

[ https://issues.apache.org/jira/browse/KAFKA-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-2622: - Status: Patch Available (was: Open) > Add Time logical type for Copycat > ---

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

See Changes: [junrao] Kafka-2587: Only notification handler will update the cache and all [wangguoz] KAFKA-2428: Add sanity check in KafkaConsumer for the timeouts -- [...truncated 322 lines...

Re: Kafka dotnet SDK suggestion

The project doesn't make official recommendations about third party clients. The only client directly supported is the Java/Scala library included in the project's source repository. However, the community does maintain a list of third-party clients here: https://cwiki.apache.org/confluence/displa

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

See Changes: [junrao] Kafka-2587: Only notification handler will update the cache and all [wangguoz] KAFKA-2428: Add sanity check in KafkaConsumer for the timeouts -- [...truncated 2047 lines...]

[GitHub] kafka pull request: KAFKA-2477: Fix a race condition between log a...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/204 --- 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-2477) Replicas spuriously deleting all segments in partition

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

[jira] [Updated] (KAFKA-2477) Replicas spuriously deleting all segments in partition

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

[jira] [Commented] (KAFKA-2477) Replicas spuriously deleting all segments in partition

[ https://issues.apache.org/jira/browse/KAFKA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948076#comment-14948076 ] Jun Rao commented on KAFKA-2477: [~Håkon Hitland], the fix is committed in trunk. Do you t

[jira] [Resolved] (KAFKA-2621) nextOffsetMetadata should be changed after rolling a new log segment

[ https://issues.apache.org/jira/browse/KAFKA-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-2621. Resolution: Fixed Assignee: Jiangjie Qin (was: Dong Lin) This is fixed as part of KAFKA-2477. > next

[GitHub] kafka pull request: KAFKA-2621; nextOffsetMetadata should be chang...

GitHub user lindong28 opened a pull request: https://github.com/apache/kafka/pull/286 KAFKA-2621; nextOffsetMetadata should be changed after rolling a new log segment You can merge this pull request into a Git repository by running: $ git pull https://github.com/lindong28/kaf

[jira] [Commented] (KAFKA-2621) nextOffsetMetadata should be changed after rolling a new log segment

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

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

See Changes: [junrao] KAFKA-2477: Fix a race condition between log append and fetch that -- [...truncated 2036 lines...] kafka.integration.PrimitiveApiTest > testPipelinedProduceRequests PASSED

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

See