[
https://issues.apache.org/jira/browse/ZOOKEEPER-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Han resolved ZOOKEEPER-3439.
------------------------------------
Resolution: Fixed
Fix Version/s: 3.6.0
Issue resolved by pull request 997
[https://github.com/apache/zookeeper/pull/997]
> Observability improvements on client / server connection close
> --------------------------------------------------------------
>
> Key: ZOOKEEPER-3439
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3439
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.6.0
> Reporter: Michael Han
> Assignee: Michael Han
> Priority: Major
> Labels: Twitter, pull-request-available
> Fix For: 3.6.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Currently when server close a client connection there is not enough
> information recorded (except few exception logs) which makes it hard to do
> postmortems. On the other side, having a complete view of the aggregated
> connection closing reason will provide more signals based on which we can
> better operate the clusters (e.g. predicate an incident might happen based on
> the trending of the connection closing reasons).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
