[ https://issues.apache.org/jira/browse/KAFKA-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436188#comment-13436188 ]
Jun Rao commented on KAFKA-385: ------------------------------- +1 on patch v4. > RequestPurgatory enhancements - expire/checkSatisfy issue; add jmx beans > ------------------------------------------------------------------------ > > Key: KAFKA-385 > URL: https://issues.apache.org/jira/browse/KAFKA-385 > Project: Kafka > Issue Type: Bug > Reporter: Joel Koshy > Assignee: Joel Koshy > Labels: bugs > Fix For: 0.8 > > Attachments: example_dashboard.jpg, graphite_explorer.jpg, > KAFKA-385-v1.patch, KAFKA-385-v2.patch, KAFKA-385-v3.patch, > KAFKA-385-v3.patch, KAFKA-385-v3-with-lazy-fix.patch, KAFKA-385-v4.patch > > > As discussed in KAFKA-353: > 1 - There is potential for a client-side race condition in the > implementations of expire and checkSatisfied. We can just synchronize on the > DelayedItem. > 2 - Would be good to add jmx beans to facilitate monitoring RequestPurgatory > stats. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira