[
https://issues.apache.org/jira/browse/ZOOKEEPER-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081519#comment-16081519
]
Andrew Purtell commented on ZOOKEEPER-2770:
-------------------------------------------
[~tdunning] It's pretty common in other projects (e.g. HBase, Hadoop, that
constellation of projects...) to use JIRA to propose a change. When we (we =
Trend Micro) worked on SASL authentication we went right to JIRA. I wouldn't
have thought to propose the idea first on dev@. Now we (we = Salesforce, FWIW,
Karan is a newcomer and a colleague) have this minor change we'd like to submit
for your consideration. It's a small change, so small the code speaks for
itself IMHO. If you think we must make a proposal on dev@ for this change to be
considered, I'd suggest this is not the norm in my experience at Apache, but
we'd be happy to do so.
> ZooKeeper slow operation log
> ----------------------------
>
> Key: ZOOKEEPER-2770
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2770
> Project: ZooKeeper
> Issue Type: Improvement
> Reporter: Karan Mehta
> Attachments: ZOOKEEPER-2770.001.patch, ZOOKEEPER-2770.002.patch,
> ZOOKEEPER-2770.003.patch
>
>
> Log the client and request details if the server discovers, when finally
> processing the request, that the current time minus arrival time of the
> request is beyond a configured threshold.
> Look at the HBase {{responseTooSlow}} feature for inspiration.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
