[jira] [Commented] (KAFKA-2311) Consumer's ensureNotClosed method not thread safe

[ https://issues.apache.org/jira/browse/KAFKA-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384483#comment-15384483 ] Tim Brooks commented on KAFKA-2311: --- Yes. Sorry, I had not been checking in with develop

[jira] [Commented] (KAFKA-2311) Consumer's ensureNotClosed method not thread safe

[ https://issues.apache.org/jira/browse/KAFKA-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619684#comment-14619684 ] Tim Brooks commented on KAFKA-2311: --- I removed the unnecessary close check as suggested

[jira] [Commented] (KAFKA-2311) Consumer's ensureNotClosed method not thread safe

[ https://issues.apache.org/jira/browse/KAFKA-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619682#comment-14619682 ] Tim Brooks commented on KAFKA-2311: --- Created reviewboard https://reviews.apache.org/r/36

[jira] [Updated] (KAFKA-2311) Consumer's ensureNotClosed method not thread safe

[ https://issues.apache.org/jira/browse/KAFKA-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Brooks updated KAFKA-2311: -- Attachment: KAFKA-2311.patch > Consumer's ensureNotClosed method not thread safe > -

[jira] [Commented] (KAFKA-2312) Use AtomicLong opposed to AtomicReference to store currentThread in consumer

[ https://issues.apache.org/jira/browse/KAFKA-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616179#comment-14616179 ] Tim Brooks commented on KAFKA-2312: --- Created reviewboard https://reviews.apache.org/r/36

[jira] [Updated] (KAFKA-2312) Use AtomicLong opposed to AtomicReference to store currentThread in consumer

[ https://issues.apache.org/jira/browse/KAFKA-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Brooks updated KAFKA-2312: -- Attachment: KAFKA-2312.patch > Use AtomicLong opposed to AtomicReference to store currentThread in consu

[jira] [Updated] (KAFKA-2312) Use AtomicLong opposed to AtomicReference to store currentThread in consumer

[ https://issues.apache.org/jira/browse/KAFKA-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Brooks updated KAFKA-2312: -- Assignee: Tim Brooks Status: Patch Available (was: Open) > Use AtomicLong opposed to AtomicRefere

[jira] [Created] (KAFKA-2312) Use AtomicLong opposed to AtomicReference to store currentThread in consumer

Tim Brooks created KAFKA-2312: - Summary: Use AtomicLong opposed to AtomicReference to store currentThread in consumer Key: KAFKA-2312 URL: https://issues.apache.org/jira/browse/KAFKA-2312 Project: Kafka

[jira] [Commented] (KAFKA-2102) Remove unnecessary synchronization when managing metadata

[ https://issues.apache.org/jira/browse/KAFKA-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616158#comment-14616158 ] Tim Brooks commented on KAFKA-2102: --- I can probably take another look at this later this

[jira] [Updated] (KAFKA-2311) Consumer's ensureNotClosed method not thread safe

[ https://issues.apache.org/jira/browse/KAFKA-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Brooks updated KAFKA-2311: -- Assignee: Tim Brooks Status: Patch Available (was: Open) > Consumer's ensureNotClosed method not

[jira] [Commented] (KAFKA-2311) Consumer's ensureNotClosed method not thread safe

[ https://issues.apache.org/jira/browse/KAFKA-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616155#comment-14616155 ] Tim Brooks commented on KAFKA-2311: --- Created reviewboard https://reviews.apache.org/r/36

[jira] [Updated] (KAFKA-2311) Consumer's ensureNotClosed method not thread safe

[ https://issues.apache.org/jira/browse/KAFKA-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Brooks updated KAFKA-2311: -- Attachment: KAFKA-2311.patch > Consumer's ensureNotClosed method not thread safe > -

[jira] [Created] (KAFKA-2311) Consumer's ensureNotClosed method not thread safe

Tim Brooks created KAFKA-2311: - Summary: Consumer's ensureNotClosed method not thread safe Key: KAFKA-2311 URL: https://issues.apache.org/jira/browse/KAFKA-2311 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-2129) Consumer could make multiple concurrent metadata requests

[ https://issues.apache.org/jira/browse/KAFKA-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616136#comment-14616136 ] Tim Brooks commented on KAFKA-2129: --- Since post-2168 it seems to be explicitly documente

[jira] [Commented] (KAFKA-2101) Metric metadata-age is reset on a failed update

[ https://issues.apache.org/jira/browse/KAFKA-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566770#comment-14566770 ] Tim Brooks commented on KAFKA-2101: --- As I mentioned earlier, this overlaps some with the

[jira] [Updated] (KAFKA-2101) Metric metadata-age is reset on a failed update

[ https://issues.apache.org/jira/browse/KAFKA-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Brooks updated KAFKA-2101: -- Assignee: Tim Brooks Status: Patch Available (was: Open) > Metric metadata-age is reset on a fail

[jira] [Updated] (KAFKA-2101) Metric metadata-age is reset on a failed update

[ https://issues.apache.org/jira/browse/KAFKA-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Brooks updated KAFKA-2101: -- Attachment: KAFKA-2101.patch > Metric metadata-age is reset on a failed update > ---

[jira] [Commented] (KAFKA-2101) Metric metadata-age is reset on a failed update

[ https://issues.apache.org/jira/browse/KAFKA-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566767#comment-14566767 ] Tim Brooks commented on KAFKA-2101: --- Created reviewboard https://reviews.apache.org/r/34

[jira] [Updated] (KAFKA-2129) Consumer could make multiple concurrent metadata requests

[ https://issues.apache.org/jira/browse/KAFKA-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Brooks updated KAFKA-2129: -- Assignee: Tim Brooks Status: Patch Available (was: Open) > Consumer could make multiple concurren

[jira] [Updated] (KAFKA-2129) Consumer could make multiple concurrent metadata requests

[ https://issues.apache.org/jira/browse/KAFKA-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Brooks updated KAFKA-2129: -- Attachment: KAFKA-2129.patch > Consumer could make multiple concurrent metadata requests > -

[jira] [Commented] (KAFKA-2129) Consumer could make multiple concurrent metadata requests

[ https://issues.apache.org/jira/browse/KAFKA-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14517557#comment-14517557 ] Tim Brooks commented on KAFKA-2129: --- Created reviewboard https://reviews.apache.org/r/33

[jira] [Updated] (KAFKA-2129) Consumer could make multiple concurrent metadata requests

[ https://issues.apache.org/jira/browse/KAFKA-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Brooks updated KAFKA-2129: -- Priority: Major (was: Minor) > Consumer could make multiple concurrent metadata requests >

[jira] [Commented] (KAFKA-2129) Consumer could make multiple concurrent metadata requests

[ https://issues.apache.org/jira/browse/KAFKA-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14517553#comment-14517553 ] Tim Brooks commented on KAFKA-2129: --- It kind of looks like this is a larger issue than m

[jira] [Commented] (KAFKA-2101) Metric metadata-age is reset on a failed update

[ https://issues.apache.org/jira/browse/KAFKA-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516263#comment-14516263 ] Tim Brooks commented on KAFKA-2101: --- Okay. Well I made a number of changes related to Me

[jira] [Updated] (KAFKA-2102) Remove unnecessary synchronization when managing metadata

[ https://issues.apache.org/jira/browse/KAFKA-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Brooks updated KAFKA-2102: -- Attachment: KAFKA-2102_2015-04-26_17:25:21.patch > Remove unnecessary synchronization when managing meta

[jira] [Commented] (KAFKA-2102) Remove unnecessary synchronization when managing metadata

[ https://issues.apache.org/jira/browse/KAFKA-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513346#comment-14513346 ] Tim Brooks commented on KAFKA-2102: --- Updated reviewboard https://reviews.apache.org/r/32

[jira] [Created] (KAFKA-2129) Consumer could make multiple concurrent metadata requests

Tim Brooks created KAFKA-2129: - Summary: Consumer could make multiple concurrent metadata requests Key: KAFKA-2129 URL: https://issues.apache.org/jira/browse/KAFKA-2129 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-2102) Remove unnecessary synchronization when managing metadata

[ https://issues.apache.org/jira/browse/KAFKA-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Brooks updated KAFKA-2102: -- Status: Patch Available (was: In Progress) > Remove unnecessary synchronization when managing metadata

[jira] [Commented] (KAFKA-2102) Remove unnecessary synchronization when managing metadata

[ https://issues.apache.org/jira/browse/KAFKA-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14497396#comment-14497396 ] Tim Brooks commented on KAFKA-2102: --- Updated reviewboard https://reviews.apache.org/r/32

[jira] [Updated] (KAFKA-2102) Remove unnecessary synchronization when managing metadata

[ https://issues.apache.org/jira/browse/KAFKA-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Brooks updated KAFKA-2102: -- Attachment: KAFKA-2102_2015-04-15_19:55:45.patch > Remove unnecessary synchronization when managing meta

[jira] [Updated] (KAFKA-2102) Remove unnecessary synchronization when managing metadata

[ https://issues.apache.org/jira/browse/KAFKA-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Brooks updated KAFKA-2102: -- Attachment: five-threads-trunk.txt five-threads-patch.txt eight-threads-t

[jira] [Commented] (KAFKA-2102) Remove unnecessary synchronization when managing metadata

[ https://issues.apache.org/jira/browse/KAFKA-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14497392#comment-14497392 ] Tim Brooks commented on KAFKA-2102: --- I added an updated patch. This patch includes a few

[jira] [Commented] (KAFKA-2102) Remove unnecessary synchronization when managing metadata

[ https://issues.apache.org/jira/browse/KAFKA-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485494#comment-14485494 ] Tim Brooks commented on KAFKA-2102: --- Thanks for the feedback. Unless I misunderstand yo

[jira] [Updated] (KAFKA-2102) Remove unnecessary synchronization when managing metadata

[ https://issues.apache.org/jira/browse/KAFKA-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Brooks updated KAFKA-2102: -- Attachment: KAFKA-2102_2015-04-08_00:20:33.patch > Remove unnecessary synchronization when managing meta

[jira] [Commented] (KAFKA-2102) Remove unnecessary synchronization when managing metadata

[ https://issues.apache.org/jira/browse/KAFKA-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484737#comment-14484737 ] Tim Brooks commented on KAFKA-2102: --- I updated my WIP patch to ensure that all tests are

[jira] [Commented] (KAFKA-2102) Remove unnecessary synchronization when managing metadata

[ https://issues.apache.org/jira/browse/KAFKA-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484735#comment-14484735 ] Tim Brooks commented on KAFKA-2102: --- Updated reviewboard https://reviews.apache.org/r/32

[jira] [Updated] (KAFKA-2102) Remove unnecessary synchronization when managing metadata

[ https://issues.apache.org/jira/browse/KAFKA-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Brooks updated KAFKA-2102: -- Assignee: Tim Brooks Status: Patch Available (was: Open) > Remove unnecessary synchronization whe

[jira] [Updated] (KAFKA-2102) Remove unnecessary synchronization when managing metadata

[ https://issues.apache.org/jira/browse/KAFKA-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Brooks updated KAFKA-2102: -- Attachment: KAFKA-2102.patch > Remove unnecessary synchronization when managing metadata > -

[jira] [Commented] (KAFKA-2102) Remove unnecessary synchronization when managing metadata

[ https://issues.apache.org/jira/browse/KAFKA-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484054#comment-14484054 ] Tim Brooks commented on KAFKA-2102: --- Created reviewboard https://reviews.apache.org/r/32

[jira] [Created] (KAFKA-2102) Remove unnecessary synchronization when managing metadata

Tim Brooks created KAFKA-2102: - Summary: Remove unnecessary synchronization when managing metadata Key: KAFKA-2102 URL: https://issues.apache.org/jira/browse/KAFKA-2102 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-2101) Metric metadata-age is reset on a failed update

Tim Brooks created KAFKA-2101: - Summary: Metric metadata-age is reset on a failed update Key: KAFKA-2101 URL: https://issues.apache.org/jira/browse/KAFKA-2101 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-2090) Remove duplicate check to metadataFetchInProgress

[ https://issues.apache.org/jira/browse/KAFKA-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Brooks updated KAFKA-2090: -- Attachment: KAFKA-2090.patch > Remove duplicate check to metadataFetchInProgress > -

[jira] [Commented] (KAFKA-2090) Remove duplicate check to metadataFetchInProgress

[ https://issues.apache.org/jira/browse/KAFKA-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14394750#comment-14394750 ] Tim Brooks commented on KAFKA-2090: --- Created reviewboard https://reviews.apache.org/r/32

[jira] [Created] (KAFKA-2090) Remove duplicate check to metadataFetchInProgress

Tim Brooks created KAFKA-2090: - Summary: Remove duplicate check to metadataFetchInProgress Key: KAFKA-2090 URL: https://issues.apache.org/jira/browse/KAFKA-2090 Project: Kafka Issue Type: Improve

[jira] [Commented] (KAFKA-2050) Avoid calling .size() on java.util.ConcurrentLinkedQueue

[ https://issues.apache.org/jira/browse/KAFKA-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14381251#comment-14381251 ] Tim Brooks commented on KAFKA-2050: --- Okay. I submitted it. I had some trouble. But I thi

[jira] [Updated] (KAFKA-2050) Avoid calling .size() on java.util.ConcurrentLinkedQueue

[ https://issues.apache.org/jira/browse/KAFKA-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Brooks updated KAFKA-2050: -- Attachment: KAFKA-2050.patch > Avoid calling .size() on java.util.ConcurrentLinkedQueue > --

[jira] [Commented] (KAFKA-2050) Avoid calling .size() on java.util.ConcurrentLinkedQueue

[ https://issues.apache.org/jira/browse/KAFKA-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14381250#comment-14381250 ] Tim Brooks commented on KAFKA-2050: --- Created reviewboard https://reviews.apache.org/r/32

[jira] [Updated] (KAFKA-2050) Avoid calling .size() on java.util.ConcurrentLinkedQueue

[ https://issues.apache.org/jira/browse/KAFKA-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Brooks updated KAFKA-2050: -- Attachment: dont_call_queue_size.patch > Avoid calling .size() on java.util.ConcurrentLinkedQueue >

[jira] [Created] (KAFKA-2050) Avoid calling .size() on java.util.ConcurrentLinkedQueue

Tim Brooks created KAFKA-2050: - Summary: Avoid calling .size() on java.util.ConcurrentLinkedQueue Key: KAFKA-2050 URL: https://issues.apache.org/jira/browse/KAFKA-2050 Project: Kafka Issue Type: