zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Han (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-3439) Observability improvements on client / server connection close
Date Sat, 22 Jun 2019 00:19:00 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Han updated ZOOKEEPER-3439:
-----------------------------------
    Labels: Twitter  (was: )

> 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
>
> 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)

Mime
View raw message