Github user karanmehta93 commented on a diff in the pull request:
https://github.com/apache/zookeeper/pull/307#discussion_r127127351
--- Diff:
src/java/main/org/apache/zookeeper/server/FinalRequestProcessor.java ---
@@ -430,6 +432,7 @@ public void processRequest(Request request) {
// the client and leader disagree on where the client is most
// recently attached (and therefore invalid SESSION MOVED
generated)
cnxn.sendCloseSession();
+ request.checkLatency();
--- End diff --
@eribeiro
That is exactly the reason that I created my own function after the
`cnxn.sendCloseSession()` since I was interested in end to end latency, and
didn't use the `zks.serverStats().updateLatency(request.createTime);` method. I
would also like to know opinion from others on this.
Should we scope this JIRA for adding threshold as a general and create a
new JIRA for extending the scope to include percentiles with new data-structure
inside the `ServerStats` class?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
