[GitHub] kafka pull request #1629: KAFKA-3960 - Committed offset not set after first ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1629 --- 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-3960) Committed offset not set after first assign

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

[jira] [Resolved] (KAFKA-3960) Committed offset not set after first assign

[ https://issues.apache.org/jira/browse/KAFKA-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3960. Resolution: Fixed Reviewer: Jason Gustafson Fix Version/s: 0.10.0.1 > Committed offs

[jira] [Updated] (KAFKA-3960) Committed offset not set after first assign

[ https://issues.apache.org/jira/browse/KAFKA-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3960: --- Assignee: Alexey Romanchuk > Committed offset not set after first assign > ---

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

See Changes: [ismael] KAFKA-3960; Committed offset not set after first assign -- [...truncated 1929 lines...] jdk1.7.0_51/THIRDPARTYLICENSEREADME-JAVAFX.txt Building remotely on H10 (docker Ubun

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

See Changes: [ismael] KAFKA-3960; Committed offset not set after first assign -- [...truncated 13022 lines...] org.apache.kafka.clients.consumer.KafkaConsumerTest > verifyHeartbeatSentWhenFetc

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

See

[jira] [Created] (KAFKA-3986) completedReceives can contain closed channels

Ryan P created KAFKA-3986: - Summary: completedReceives can contain closed channels Key: KAFKA-3986 URL: https://issues.apache.org/jira/browse/KAFKA-3986 Project: Kafka Issue Type: Bug Comp

[jira] [Updated] (KAFKA-3986) completedReceives can contain closed channels

[ https://issues.apache.org/jira/browse/KAFKA-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3986: --- Fix Version/s: 0.10.0.1 > completedReceives can contain closed channels > ---

[GitHub] kafka pull request #1657: Kafka 3986

GitHub user rnpridgeon opened a pull request: https://github.com/apache/kafka/pull/1657 Kafka 3986 Add null check to guard against the unlikely event where a channel has been closed but not yet removed from completedReceives You can merge this pull request into a Git repository by

[jira] [Commented] (KAFKA-3980) JmxReporter uses excessive memory causing OutOfMemoryException

[ https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390792#comment-15390792 ] Manikumar Reddy commented on KAFKA-3980: [~ajorgensen] Can you enable debug log an

[jira] [Comment Edited] (KAFKA-3980) JmxReporter uses excessive memory causing OutOfMemoryException

[ https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390792#comment-15390792 ] Manikumar Reddy edited comment on KAFKA-3980 at 7/23/16 6:27 PM: ---

[jira] [Updated] (KAFKA-3575) Use console consumer access topic that does not exist, can not use "Control + C" to exit process

[ https://issues.apache.org/jira/browse/KAFKA-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taiyuan Zhang updated KAFKA-3575: - Assignee: (was: Taiyuan Zhang) > Use console consumer access topic that does not exist, can no

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

[ https://issues.apache.org/jira/browse/KAFKA-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taiyuan Zhang updated KAFKA-3585: - Assignee: (was: Taiyuan Zhang) > Shutdown slow when there is only one broker which is controll

Re: [DISCUSS] KIP-66 Kafka Connect Transformers for messages

On Fri, Jul 22, 2016 at 12:58 AM, Shikhar Bhushan wrote: > flatMap() / supporting 1->n feels nice and general since filtering is just > the case of going from 1->0 > > I'm not sure why we'd need to do any more granular offset tracking (like > sub-offsets) for source connectors: after transformati

Re: [DISCUSS] KIP-4 ACL Admin Schema

Re: 4 and Create/Delete vs Alter, I'm a fan of being able to bundle a bunch of changes in one request. Seems like an ACL change could easily include additions + deletions and is nice to bundle in one request that can be processed as quickly as possible. I don't think its a requirement, but the usag

Re: Changing hash algorithm to LogCleaner offset map

Nothing wrong about using MD5 for that from FIPS point of view, but we want to deploy with FIPS 140-2 mode enabled using only RSA security providers. With this settings it is not possible to use MD5. On Fri, Jul 22, 2016 at 8:49 PM, Shikhar Bhushan wrote: > Not sure I understand the motivation t

[GitHub] kafka pull request #1558: org.apache.kafka.streams.errors.StreamsException: ...

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

[jira] [Commented] (KAFKA-1429) Yet another deadlock in controller shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390887#comment-15390887 ] Pengwei commented on KAFKA-1429: hi Jun, I have open a PR for this issue. Can you review i