You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by rakeshadr <gi...@git.apache.org> on 2018/05/07 15:22:48 UTC
[GitHub] zookeeper pull request #377: [ZOOKEEPER-2901] TTL Nodes don't work with Serv...
Github user rakeshadr commented on a diff in the pull request:
https://github.com/apache/zookeeper/pull/377#discussion_r186415246
--- Diff: src/docs/src/documentation/content/xdocs/zookeeperAdmin.xml ---
@@ -950,6 +952,39 @@ server.3=zoo3:2888:3888</programlisting>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term>zookeeper.extendedTypesEnabled</term>
+
+ <listitem>
+ <para>(Java system property only: <emphasis
+ role="bold">zookeeper.extendedTypesEnabled</emphasis>)</para>
+
+ <para><emphasis role="bold">New in 3.5.4, 3.6.0:</emphasis> Define to "true" to enable
+ extended features such as the creation of <ulink url="zookeeperProgrammers.html#TTL+Nodes">TTL Nodes</ulink>.
+ They are disabled by default. IMPORTANT: when enabled server IDs must
+ be less than 255 due to internal limitations.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>zookeeper.emulate353TTLNodes</term>
--- End diff --
Yes, good point. We need to mention this as `deprecated `and highlight the intention of removing them in future. As per "https://cwiki.apache.org/confluence/display/ZOOKEEPER/Roadmap", are we able to remove it in 3.5.5 ?
Also, in future how user with TTLNodes can be upgraded to a to a higher 3.5.5+ or 3.6.0+ version directly from 3.5.3 ?
Also, could you please raise a jira task to propose the best way to remove this workaround config and keep track of it, if not raised yet.
---