zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enrico Olivelli (Jira)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-920) L7 (application layer) ping support
Date Fri, 06 Sep 2019 15:46:09 GMT

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

Enrico Olivelli updated ZOOKEEPER-920:
    Fix Version/s:     (was: 3.5.6)

> L7 (application layer) ping support
> -----------------------------------
>                 Key: ZOOKEEPER-920
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-920
>             Project: ZooKeeper
>          Issue Type: New Feature
>          Components: c client
>    Affects Versions: 3.3.1
>            Reporter: Chang Song
>            Assignee: Chang Song
>            Priority: Minor
>             Fix For: 3.6.0, 3.5.7
>         Attachments: ZOOKEEPER-920.patch
> Zookeeper is used in applications where fault tolerance is important. Its client i/o
thread send/recv heartbeats to/fro Zookeeper ensemble to stay connected. However healthy heartbeat
does not always means that the application that uses Zookeeper client is in good health, it
only means that ZK client thread is in good health.
> This I needed something that can tagged onto Zookeeper ping that represents L7 (application)
health as well.
> I have modified C client source to support this in minimal way. I am new to Zookeeper,
so please code review this code.  I am actually using this code in our in-house solution.
> https://github.com/tru64ufs/zookeeper/commit/2196d6d5114a2fd2c0a3bc9a55f4494d47d2aece
> Thank you very much.

This message was sent by Atlassian Jira

View raw message