[jira] [Commented] (KAFKA-982) Logo for Kafka

[ https://issues.apache.org/jira/browse/KAFKA-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719316#comment-13719316 ] Esko Suomi commented on KAFKA-982: -- +1 for 301; it looks like queues/buffers in different

[jira] [Commented] (KAFKA-982) Logo for Kafka

[ https://issues.apache.org/jira/browse/KAFKA-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719319#comment-13719319 ] Olson,Andrew commented on KAFKA-982: I will be out of the office without access to

kafka pull request: Unmap before resizing

GitHub user lizziew opened a pull request: https://github.com/apache/kafka/pull/6 Unmap before resizing While I was studying how MappedByteBuffer works, I saw a sharing runtime exception on Windows. I applied what I learned to generate a patch which uses an internal open JDK API

Re: Beta2 release?

I don't think it is. when i was logged in there was only access to staging close and release. I tried to login again but can't so not sure if it is because of recent ldap changes and have to request access again or because I have no uploaded release.. was going to deal with that with the INFRA

[jira] [Commented] (KAFKA-987) Avoid checkpointing offsets in Kafka consumer that have not changed since the last commit

[ https://issues.apache.org/jira/browse/KAFKA-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719723#comment-13719723 ] Jun Rao commented on KAFKA-987: --- 1. The issue on startup is the following. If a consumer

Re: kafka pull request: Unmap before resizing

Hi, can you file a JIRA and attach the patch there? This does the Apache copyright stuff... Instructions here: http://kafka.apache.org/contributing.html This seems like a good thing to have. Is there a more portable way to do this? Obviously this would not work on a non-sun JVM. I think the

[jira] [Updated] (KAFKA-959) DefaultEventHandler can send more produce requests than necesary

[ https://issues.apache.org/jira/browse/KAFKA-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-959: -- Resolution: Fixed Fix Version/s: 0.8 Status: Resolved (was: Patch Available) Thanks for the

kafka pull request: Modified the async producer so it re-queues failed batc...

GitHub user hiloboy0119 opened a pull request: https://github.com/apache/kafka/pull/7 Modified the async producer so it re-queues failed batches. I'm working on an application that needs the throughput offered by an async producer but also needs to handle send failures gracefully

[jira] [Updated] (KAFKA-955) After a leader change, messages sent with ack=0 are lost

[ https://issues.apache.org/jira/browse/KAFKA-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-955: Assignee: Guozhang Wang After a leader change, messages sent with ack=0 are lost

[jira] [Updated] (KAFKA-955) After a leader change, messages sent with ack=0 are lost

[ https://issues.apache.org/jira/browse/KAFKA-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-955: Attachment: KAFKA-955.v1.patch After a leader change, messages sent with ack=0 are lost

[jira] [Updated] (KAFKA-955) After a leader change, messages sent with ack=0 are lost

[ https://issues.apache.org/jira/browse/KAFKA-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-955: Status: Patch Available (was: Open) Following the close-socket approach, I propose the following

[jira] [Updated] (KAFKA-955) After a leader change, messages sent with ack=0 are lost

[ https://issues.apache.org/jira/browse/KAFKA-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-955: Attachment: KAFKA-955.v1.patch Add one case for ack=0 in testSendWithDeadBroker, passed.