[jira] [Updated] (KAFKA-989) Race condition shutting down high-level consumer results in spinning background thread

[ https://issues.apache.org/jira/browse/KAFKA-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Hargett updated KAFKA-989: --- Status: Patch Available (was: Open) When in doubt about how to fix a locking issue...add another

[jira] [Updated] (KAFKA-989) Race condition shutting down high-level consumer results in spinning background thread

[ https://issues.apache.org/jira/browse/KAFKA-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Hargett updated KAFKA-989: --- Attachment: KAFKA-989-failed-to-find-leader-patch2.patch Race condition shutting down high-level

[jira] [Commented] (KAFKA-996) Capitalize first letter for log entries

[ https://issues.apache.org/jira/browse/KAFKA-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13729561#comment-13729561 ] Guozhang Wang commented on KAFKA-996: - Yes this patch is for trunk. As I said when 0.8

[jira] [Commented] (KAFKA-615) Avoid fsync on log segment roll

[ https://issues.apache.org/jira/browse/KAFKA-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13729559#comment-13729559 ] Jun Rao commented on KAFKA-615: --- 50.3 Yes, I think your reasoning is correct. I didn't look

[jira] [Updated] (KAFKA-967) Use key range in ProducerPerformance

[ https://issues.apache.org/jira/browse/KAFKA-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-967: Attachment: KAFKA-967.v3.patch Now if messageKeyRangeOpt is not specified, null will be passed as

[jira] [Commented] (KAFKA-989) Race condition shutting down high-level consumer results in spinning background thread

[ https://issues.apache.org/jira/browse/KAFKA-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13729635#comment-13729635 ] Phil Hargett commented on KAFKA-989: Thanks for the feedback! Working on a patch that

[jira] [Updated] (KAFKA-992) Double Check on Broker Registration to Avoid False NodeExist Exception

[ https://issues.apache.org/jira/browse/KAFKA-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-992: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to 0.8

[jira] [Commented] (KAFKA-989) Race condition shutting down high-level consumer results in spinning background thread

[ https://issues.apache.org/jira/browse/KAFKA-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13729666#comment-13729666 ] Jun Rao commented on KAFKA-989: --- Hmm, in the shutdown logic of consumer connector, we set

[jira] [Updated] (KAFKA-718) kafka-run-class.sh should use reasonable gc settings

[ https://issues.apache.org/jira/browse/KAFKA-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-718: Resolution: Fixed Fix Version/s: 0.8 Assignee: Jay Kreps (was: Neha Narkhede)

[jira] [Commented] (KAFKA-998) Producer should not retry on non-recoverable error codes

[ https://issues.apache.org/jira/browse/KAFKA-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13729681#comment-13729681 ] Guozhang Wang commented on KAFKA-998: - Approach proposal: 1. Passing the errorCode

[jira] [Commented] (KAFKA-615) Avoid fsync on log segment roll

[ https://issues.apache.org/jira/browse/KAFKA-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13729684#comment-13729684 ] Jay Kreps commented on KAFKA-615: - 1.1 Good catch 2.1 My desire is to ensure that

[jira] [Commented] (KAFKA-989) Race condition shutting down high-level consumer results in spinning background thread

[ https://issues.apache.org/jira/browse/KAFKA-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13729682#comment-13729682 ] Phil Hargett commented on KAFKA-989: Yes, but my working hypothesis is that because

[jira] [Commented] (KAFKA-615) Avoid fsync on log segment roll

[ https://issues.apache.org/jira/browse/KAFKA-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13729700#comment-13729700 ] Jay Kreps commented on KAFKA-615: - Jun. 52.2 In most filesystems there is no guarantee

[jira] Subscription: outstanding kafka patches

Issue Subscription Filter: outstanding kafka patches (66 issues) The list of outstanding kafka patches Subscriber: kafka-mailing-list Key Summary KAFKA-997 Provide a strict verification mode when reading configuration properties

[jira] [Commented] (KAFKA-989) Race condition shutting down high-level consumer results in spinning background thread

[ https://issues.apache.org/jira/browse/KAFKA-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13729842#comment-13729842 ] Phil Hargett commented on KAFKA-989: I also think I've convinced myself that while the

[jira] [Commented] (KAFKA-999) Controlled shutdown never succeeds until the broker is killed

[ https://issues.apache.org/jira/browse/KAFKA-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13729864#comment-13729864 ] Neha Narkhede commented on KAFKA-999: - I think the fix is to remove the smart in the

[jira] [Commented] (KAFKA-999) Controlled shutdown never succeeds until the broker is killed

[ https://issues.apache.org/jira/browse/KAFKA-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13729869#comment-13729869 ] Sriram Subramanian commented on KAFKA-999: -- +1 on the proposed fix. Also this

[jira] [Updated] (KAFKA-615) Avoid fsync on log segment roll

[ https://issues.apache.org/jira/browse/KAFKA-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-615: Attachment: KAFKA-615-v7.patch Patch which uses the correct but slow approach of synchronously committing

[jira] [Commented] (KAFKA-615) Avoid fsync on log segment roll

[ https://issues.apache.org/jira/browse/KAFKA-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13729935#comment-13729935 ] Sriram Subramanian commented on KAFKA-615: -- Do you not want to reset the

[jira] [Updated] (KAFKA-615) Avoid fsync on log segment roll

[ https://issues.apache.org/jira/browse/KAFKA-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-615: Attachment: KAFKA-615-v8.patch Ack, yes, I did mean to fix the recoveryPoint/logEndOffset issue, I just

[jira] [Commented] (KAFKA-615) Avoid fsync on log segment roll

[ https://issues.apache.org/jira/browse/KAFKA-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13729989#comment-13729989 ] Sriram Subramanian commented on KAFKA-615: -- +1 Avoid fsync on

[jira] [Updated] (KAFKA-998) Producer should not retry on non-recoverable error codes

[ https://issues.apache.org/jira/browse/KAFKA-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-998: Status: Patch Available (was: Open) Needs rebase once 0.8 is merged in trunk.

[jira] [Updated] (KAFKA-998) Producer should not retry on non-recoverable error codes

[ https://issues.apache.org/jira/browse/KAFKA-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-998: Attachment: KAFKA-998.v1.patch 1. Add a function in ErrorMapping, which takes an error code and

[jira] [Created] (KAFKA-1001) Handle follower transition in batch

Jay Kreps created KAFKA-1001: Summary: Handle follower transition in batch Key: KAFKA-1001 URL: https://issues.apache.org/jira/browse/KAFKA-1001 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-615) Avoid fsync on log segment roll

[ https://issues.apache.org/jira/browse/KAFKA-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13730155#comment-13730155 ] Jay Kreps commented on KAFKA-615: - Also, Jun, basic system tests all pass with v8.

[jira] [Commented] (KAFKA-615) Avoid fsync on log segment roll

[ https://issues.apache.org/jira/browse/KAFKA-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13730154#comment-13730154 ] Jay Kreps commented on KAFKA-615: - Filed KAFKA-1001 to handle the follow-up work to

[jira] [Commented] (KAFKA-999) Controlled shutdown never succeeds until the broker is killed

[ https://issues.apache.org/jira/browse/KAFKA-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13730243#comment-13730243 ] Swapnil Ghike commented on KAFKA-999: - I think the right fix would be to undo any

[jira] [Updated] (KAFKA-989) Race condition shutting down high-level consumer results in spinning background thread

[ https://issues.apache.org/jira/browse/KAFKA-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-989: -- Resolution: Fixed Fix Version/s: 0.8 Assignee: Phil Hargett Status: Resolved (was:

[jira] [Comment Edited] (KAFKA-999) Controlled shutdown never succeeds until the broker is killed

[ https://issues.apache.org/jira/browse/KAFKA-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13730294#comment-13730294 ] Neha Narkhede edited comment on KAFKA-999 at 8/6/13 3:03 AM: -

[jira] [Commented] (KAFKA-999) Controlled shutdown never succeeds until the broker is killed

[ https://issues.apache.org/jira/browse/KAFKA-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13730294#comment-13730294 ] Neha Narkhede commented on KAFKA-999: - Sriram, Ack you are right. Forgot to mention

[jira] [Commented] (KAFKA-717) scala 2.10 build support

[ https://issues.apache.org/jira/browse/KAFKA-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13730320#comment-13730320 ] Rob Withers commented on KAFKA-717: --- patch tarball no longer applies cleanly to 0.8

[jira] [Commented] (KAFKA-615) Avoid fsync on log segment roll

[ https://issues.apache.org/jira/browse/KAFKA-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13730325#comment-13730325 ] Jun Rao commented on KAFKA-615: --- Thanks for patch v8. Just the following comment. Otherwise,

[jira] [Commented] (KAFKA-999) Controlled shutdown never succeeds until the broker is killed

[ https://issues.apache.org/jira/browse/KAFKA-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13730331#comment-13730331 ] Swapnil Ghike commented on KAFKA-999: - I see your points. After thinking a bit about

[jira] [Resolved] (KAFKA-615) Avoid fsync on log segment roll

[ https://issues.apache.org/jira/browse/KAFKA-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-615. - Resolution: Fixed Fix Version/s: 0.8.1 Assignee: Jay Kreps (was: Neha Narkhede) Ah, nice

[jira] [Commented] (KAFKA-999) Controlled shutdown never succeeds until the broker is killed

[ https://issues.apache.org/jira/browse/KAFKA-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13730340#comment-13730340 ] Neha Narkhede commented on KAFKA-999: - However controller passing live brokers minus

[jira] [Created] (KAFKA-1002) Delete aliveLeaders field from LeaderAndIsrRequest

Swapnil Ghike created KAFKA-1002: Summary: Delete aliveLeaders field from LeaderAndIsrRequest Key: KAFKA-1002 URL: https://issues.apache.org/jira/browse/KAFKA-1002 Project: Kafka Issue Type: