[
https://issues.apache.org/jira/browse/ZOOKEEPER-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17717447#comment-17717447
]
Kezhu Wang commented on ZOOKEEPER-4690:
---------------------------------------
Hmm, that is sad. I dived into the code and found
{{{}DataNode.getClientEphemeralOwner{}}}. Seems like {{Stat.ephemeralOwner}}
was supposed to cooperate solely with ephemeral nodes in client side. In this
sense, {{EphemeralType}} sounds like pure server knowledge. For ttl nodes,
clients have to do bookkeeping themselves, eg. nodes to ttls.
I guess this might be a "won't do" or long-term wish as there is little room
for this.
* {{Stat}} is mixedly used as both public API and proto record. It is a big
deal to separate the two. ZOOKEEPER-102 ZOOKEEPER-894
* {{Stat.ephemeralOwner}} has its own semantics. ZOOKEEPER-2163 and
ZOOKEEPER-2169 did no break this.
* Most ttls are immutable and clients can do bookkeeping themselves. Though I
do think it is valuable to expose this to client. I was thinking whether we
could establish protocol capabilities in {{ConnectRequest.protocolVersion}}
and/or with other requests. I was impressed on [Kafka's protocol
compatibility|https://kafka.apache.org/protocol.html#protocol_compatibility].
[~randgalt] [~eolivelli] [~Tison] [~maoling] [~symat] [~cnauroth]
> Expose TTL ZNode information
> ----------------------------
>
> Key: ZOOKEEPER-4690
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4690
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.7.1
> Reporter: Ryan Ruel
> Priority: Minor
>
> When a ZNode is created with a TTL, there is currently no way to later read
> the ZNode and determine:
> 1. Is the ZNode configured with a TTL?
> 2. When will the TTL expire?
> This information could be useful, for example, where applications need to
> resurrect TTL-based tombstones into persistent ZNodes. Additionally, it would
> be useful for debugging via the CLI utility.
> I would expect this information to be available via the Stat object.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)