PageRenderTime 49ms CodeModel.GetById 19ms RepoModel.GetById 0ms app.codeStats 0ms

/ZOOKEEPER/3.5.0/RELEASENOTES.3.5.0.md

https://gitlab.com/andrewmusselman/eco-release-metadata
Markdown | 332 lines | 157 code | 175 blank | 0 comment | 0 complexity | aa24894cb522e201bb1df4c912e3bf9a MD5 | raw file
    

  1. 

  2. <!---
    3. 

  3. # Licensed to the Apache Software Foundation (ASF) under one
    4. 

  4. # or more contributor license agreements.  See the NOTICE file
    5. 

  5. # distributed with this work for additional information
    6. 

  6. # regarding copyright ownership.  The ASF licenses this file
    7. 

  7. # to you under the Apache License, Version 2.0 (the
    8. 

  8. # "License"); you may not use this file except in compliance
    9. 

  9. # with the License.  You may obtain a copy of the License at
    10. 

  10. #
    11. 

  11. #     http://www.apache.org/licenses/LICENSE-2.0
    12. 

  12. #
    13. 

  13. # Unless required by applicable law or agreed to in writing, software
    14. 

  14. # distributed under the License is distributed on an "AS IS" BASIS,
    15. 

  15. # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    16. 

  16. # See the License for the specific language governing permissions and
    17. 

  17. # limitations under the License.
    18. 

  18. -->
    19. 

  19. # Apache Zookeeper  3.5.0 Release Notes
    20. 

  20. 

  21. These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements.
    22. 

  22. 

  23. 

  24. ---
    25. 

  25. 

  26. * [ZOOKEEPER-1972](https://issues.apache.org/jira/browse/ZOOKEEPER-1972) | *Major* | **Fix invalid volatile long/int increment (++)**
    27. 

  27. 

  28. Awesome! thanks Hongchao! Committed to trunk
    29. 

  29. 

  30. 

  31. ---
    32. 

  32. 

  33. * [ZOOKEEPER-1835](https://issues.apache.org/jira/browse/ZOOKEEPER-1835) | *Major* | **dynamic configuration file renaming fails on Windows**
    34. 

  34. 

  35. Patch described in this comment below:
    36. 

  36. https://issues.apache.org/jira/browse/ZOOKEEPER-1835?focusedCommentId=13848420&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13848420
    37. 

  37. 

  38. 

  39. ---
    40. 

  40. 

  41. * [ZOOKEEPER-1819](https://issues.apache.org/jira/browse/ZOOKEEPER-1819) | *Minor* | **DeserializationPerfTest calls method with wrong arguments**
    42. 

  42. 

  43. Fix DeserializationPerfTest which was not testing the desired scenarios.
    44. 

  44. 

  45. 

  46. ---
    47. 

  47. 

  48. * [ZOOKEEPER-1812](https://issues.apache.org/jira/browse/ZOOKEEPER-1812) | *Minor* | **ZooInspector reconnection always fails if first connection fails**
    49. 

  49. 

  50. Fixed ZooInspector reconnection
    51. 

  51. 

  52. 

  53. ---
    54. 

  54. 

  55. * [ZOOKEEPER-1811](https://issues.apache.org/jira/browse/ZOOKEEPER-1811) | *Major* | **The ZooKeeperSaslClient service name principal is hardcoded to "zookeeper"**
    56. 

  56. 

  57. Adds a new system property "zookeeper.sasl.client.username" that can be used to configure the ZK Kerberos (SASL) client user principal name to something other than "zookeeper" (default) for any environments that use non-standard naming for its principals.
    58. 

  58. 

  59. 

  60. ---
    61. 

  61. 

  62. * [ZOOKEEPER-1771](https://issues.apache.org/jira/browse/ZOOKEEPER-1771) | *Minor* | **ZooInspector authentication**
    63. 

  63. 

  64. Added authentication for ZooInspector.
    65. 

  65. 

  66. 

  67. ---
    68. 

  68. 

  69. * [ZOOKEEPER-1718](https://issues.apache.org/jira/browse/ZOOKEEPER-1718) | *Critical* | **Support JLine 2**
    70. 

  70. 

  71. JLine upgraded to version 2.11
    72. 

  72. 

  73. 

  74. ---
    75. 

  75. 

  76. * [ZOOKEEPER-1666](https://issues.apache.org/jira/browse/ZOOKEEPER-1666) | *Major* | **Avoid Reverse DNS lookup if the hostname in connection string is literal IP address.**
    77. 

  77. 

  78. Try to avoid reverse name service look up when the connection string consists of literal IP addresses but not real host names.
    79. 

  79. 

  80. 

  81. ---
    82. 

  82. 

  83. * [ZOOKEEPER-1632](https://issues.apache.org/jira/browse/ZOOKEEPER-1632) | *Minor* | **fix memory leaks in cli\_st**
    84. 

  84. 

  85. The fix for this issue solves the memory leak spotted in the absence of errors. In the case the completion function is not registered because of an error (e.g., see zoo\_async), the line duplicate won't be freed.
    86. 

    87. 

  87. 

  88. ---
    89. 

  89. 

  90. * [ZOOKEEPER-1562](https://issues.apache.org/jira/browse/ZOOKEEPER-1562) | *Trivial* | **Memory leaks in zoo\_multi API**
    91. 

  91. 

  92. zoo\_multi API used to leak memory while deserializing the response from zookeeper server.
    93. 

  93. Completion entries for individual operation in zoo\_multi transaction weren't getting cleaned causing memory leak. This patch resolves this memory leak by destroying completion entries in deserialize\_multi function.
    94. 

    95. 

  95. 

  96. ---
    97. 

  97. 

  98. * [ZOOKEEPER-1557](https://issues.apache.org/jira/browse/ZOOKEEPER-1557) | *Major* | **jenkins jdk7 test failure in testBadSaslAuthNotifiesWatch**
    99. 

  99. 

  100. Committed to 3.4.6/trunk. Thanks Eugene.
    101. 

  101. 

  102. 

  103. ---
    104. 

  104. 

  105. * [ZOOKEEPER-1509](https://issues.apache.org/jira/browse/ZOOKEEPER-1509) | *Major* | **Please update documentation to reflect updated FreeBSD support.**
    106. 

  106. 

  107. Update documentation to reflect full FreeBSD support.
    108. 

  108. 

  109. 

  110. ---
    111. 

  111. 

  112. * [ZOOKEEPER-1506](https://issues.apache.org/jira/browse/ZOOKEEPER-1506) | *Blocker* | **Re-try DNS hostname -\> IP resolution if node connection fails**
    113. 

  113. 

  114. Tests pass with this patch.
    115. 

  115. This patch is for the branch-3.4 branch ONLY.
    116. 

  116. 

  117. 

  118. ---
    119. 

  119. 

  120. * [ZOOKEEPER-1459](https://issues.apache.org/jira/browse/ZOOKEEPER-1459) | *Major* | **Standalone ZooKeeperServer is not closing the transaction log files on shutdown**
    121. 

  121. 

  122. **WARNING: No release note provided for this incompatible change.**
    123. 

  123. 

  124. 

  125. ---
    126. 

  126. 

  127. * [ZOOKEEPER-1408](https://issues.apache.org/jira/browse/ZOOKEEPER-1408) | *Minor* | **CLI: sort output of ls command**
    128. 

  128. 

  129. The output of ls-command in CLI does not contain the []-frame any more. Instead the nodes are sorted.
    130. 

  130. 

  131. 

  132. ---
    133. 

  133. 

  134. * [ZOOKEEPER-1367](https://issues.apache.org/jira/browse/ZOOKEEPER-1367) | *Blocker* | **Data inconsistencies and unexpired ephemeral nodes after cluster restart**
    135. 

  135. 

  136. Fix Data inconsistencies and unexpired ephemeral nodes after cluster restart.
    137. 

  137. 

  138. 

  139. ---
    140. 

  140. 

  141. * [ZOOKEEPER-1344](https://issues.apache.org/jira/browse/ZOOKEEPER-1344) | *Critical* | **ZooKeeper client multi-update command is not considering the Chroot request**
    142. 

  142. 

  143. **WARNING: No release note provided for this incompatible change.**
    144. 

  144. 

  145. 

  146. ---
    147. 

  147. 

  148. * [ZOOKEEPER-1340](https://issues.apache.org/jira/browse/ZOOKEEPER-1340) | *Major* | **multi problem - typical user operations are generating ERROR level messages in the server**
    149. 

  149. 

  150. Unwanted ERROR messages in the logs.
    151. 

  151. 

  152. 

  153. ---
    154. 

  154. 

  155. * [ZOOKEEPER-1336](https://issues.apache.org/jira/browse/ZOOKEEPER-1336) | *Major* | **javadoc for multi is confusing, references functionality that doesn't seem to exist**
    156. 

  156. 

  157. Improved Javadoc for multi API's.
    158. 

    159. 

  159. 

  160. ---
    161. 

  161. 

  162. * [ZOOKEEPER-1327](https://issues.apache.org/jira/browse/ZOOKEEPER-1327) | *Major* | **there are still remnants of hadoop urls**
    163. 

  163. 

  164. Remove links to Hadoop wiki's in ZooKeeper docs.
    165. 

    166. 

  166. 

  167. ---
    168. 

  168. 

  169. * [ZOOKEEPER-1322](https://issues.apache.org/jira/browse/ZOOKEEPER-1322) | *Major* | **Cleanup/fix logging in Quorum code.**
    170. 

  170. 

  171. Improved logging in Quorum Code.
    172. 

  172. 

  173. 

  174. ---
    175. 

  175. 

  176. * [ZOOKEEPER-1305](https://issues.apache.org/jira/browse/ZOOKEEPER-1305) | *Major* | **zookeeper.c:prepend\_string func can dereference null ptr**
    177. 

  177. 

  178. return ZBADARGUMENTS when passed NULL zhandle instead of dereferencing null pointer.
    179. 

  179. 

  180. 

  181. ---
    182. 

  182. 

  183. * [ZOOKEEPER-1294](https://issues.apache.org/jira/browse/ZOOKEEPER-1294) | *Major* | **One of the zookeeper server is not accepting any requests**
    184. 

  184. 

  185. **WARNING: No release note provided for this incompatible change.**
    186. 

  186. 

  187. 

  188. ---
    189. 

  189. 

  190. * [ZOOKEEPER-1291](https://issues.apache.org/jira/browse/ZOOKEEPER-1291) | *Major* | **AcceptedEpoch not updated at leader before it proposes the epoch to followers**
    191. 

  191. 

  192. Revision 1198053
    193. 

  193. 

  194. 

  195. ---
    196. 

  196. 

  197. * [ZOOKEEPER-1282](https://issues.apache.org/jira/browse/ZOOKEEPER-1282) | *Major* | **Learner.java not following Zab 1.0 protocol - setCurrentEpoch should be done upon receipt of NEWLEADER (before acking it) and not upon receipt of UPTODATE**
    198. 

  198. 

  199. Revision 1198053
    200. 

  200. 

  201. 

  202. ---
    203. 

  203. 

  204. * [ZOOKEEPER-1277](https://issues.apache.org/jira/browse/ZOOKEEPER-1277) | *Critical* | **servers stop serving when lower 32bits of zxid roll over**
    205. 

  205. 

  206. Workaround: there is a simple workaround for this issue. Force a leader re-election before the lower 32bits reach 0xffffffff
    207. 

  207. 

  208. Most users won't even see this given the number of writes on a typical installation - say you are doing 500 writes/second, you'd see this after ~3 months if the quorum is stable, any changes (such as upgrading the server software) would cause the xid to be reset, thereby staving off this issue for another period.
    209. 

  209. 

  210. 

  211. ---
    212. 

  212. 

  213. * [ZOOKEEPER-1264](https://issues.apache.org/jira/browse/ZOOKEEPER-1264) | *Blocker* | **FollowerResyncConcurrencyTest failing intermittently**
    214. 

  214. 

  215. Revision 1198053
    216. 

  216. 

  217. 

  218. ---
    219. 

  219. 

  220. * [ZOOKEEPER-1263](https://issues.apache.org/jira/browse/ZOOKEEPER-1263) | *Major* | **fix handling of min/max session timeout value initialization**
    221. 

  221. 

  222. trunk: http://svn.apache.org/viewvc?view=revision&revision=1581522
    223. 

  223. 

  224. 

  225. ---
    226. 

  226. 

  227. * [ZOOKEEPER-1262](https://issues.apache.org/jira/browse/ZOOKEEPER-1262) | *Major* | **Documentation for Lock recipe has major flaw**
    228. 

  228. 

  229. Updated recipes to document how to use a GUID to manage a recoverable create() error.
    230. 

  230. 

  231. 

  232. ---
    233. 

  233. 

  234. * [ZOOKEEPER-1239](https://issues.apache.org/jira/browse/ZOOKEEPER-1239) | *Major* | **add logging/stats to identify fsync stalls**
    235. 

  235. 

  236. committed to 3.3.4, 3.4, trunk rev 1202360
    237. 

  237. 

  238. 

  239. ---
    240. 

  240. 

  241. * [ZOOKEEPER-1208](https://issues.apache.org/jira/browse/ZOOKEEPER-1208) | *Blocker* | **Ephemeral node not removed after the client session is long gone**
    242. 

  242. 

  243. trunk version 1201832
    244. 

  244. 

  245. 

  246. ---
    247. 

  247. 

  248. * [ZOOKEEPER-1189](https://issues.apache.org/jira/browse/ZOOKEEPER-1189) | *Major* | **For an invalid snapshot file(less than 10bytes size) RandomAccessFile stream is leaking.**
    249. 

  249. 

  250. **WARNING: No release note provided for this incompatible change.**
    251. 

  251. 

  252. 

  253. ---
    254. 

  254. 

  255. * [ZOOKEEPER-1185](https://issues.apache.org/jira/browse/ZOOKEEPER-1185) | *Major* | **Send AuthFailed event to client if SASL authentication fails**
    256. 

  256. 

  257. This patch fixes SaslAuthFailTest.testBadSaslAuthNotifiesWatch() to test for the AuthFailed event : previously, the test was incorrectly not testing for this event.
    258. 

  258. 

  259. It also removes the testBadSaslAuthNotifiesWatch() method from the SaslAuthTest class : this method belongs in SaslAuthFailTest, not SaslAuthTest. The former tests unsuccessful SASL authentication; the latter, successful SASL authentication.
    260. 

  260. 

  261. 

  262. ---
    263. 

  263. 

  264. * [ZOOKEEPER-1181](https://issues.apache.org/jira/browse/ZOOKEEPER-1181) | *Major* | **Fix problems with Kerberos TGT renewal**
    265. 

  265. 

  266. -Fixes two findbugs warnings related to holding a lock while sleeping.
    267. 

  267. -Addresses Camille's point: merge two almost-identical retry methods into a single retry method.
    268. 

    269. 

  269. 

  270. ---
    271. 

  271. 

  272. * [ZOOKEEPER-1179](https://issues.apache.org/jira/browse/ZOOKEEPER-1179) | *Critical* | **NettyServerCnxn does not properly close socket on 4 letter word requests**
    273. 

  273. 

  274. Thanks Rakesh, you are right, this error is not happening anymore. Flavio, I'm closing this.
    275. 

    276. 

  276. 

  277. ---
    278. 

  278. 

  279. * [ZOOKEEPER-1149](https://issues.apache.org/jira/browse/ZOOKEEPER-1149) | *Blocker* | **users cannot migrate from 3.4-\>3.3-\>3.4 server code against a single datadir**
    280. 

  280. 

  281. The ZooKeeper server cannot be migrated from version 3.4 to version 3.3 and then back to version 3.4 without user intervention.
    282. 

  282. 

  283. Upgrading from 3.3 to 3.4 is supported as is downgrading from 3.4 to 3.3. However moving from 3.4 to 3.3 and back to 3.4 will fail. 3.4 is checking the datadir for "acceptedEpoch" and "currentEpoch" files and comparing these against the snapshot and log files contained in the same directory. These epoch files are new in 3.4.
    284. 

  284. 

  285. As a result:
    286. 

  286. 1) upgrading from 3.3 to 3.4 is fine - the files don't exist, the server creates them
    287. 

  287. 2) downgrading from 3.4 to 3.3 - this is also fine as version 3.3 ignores these files
    288. 

  288. 3) however, 3.4-\>3.3-\>3.4 fails because 3.4 will see invalid \*Epoch files in the datadir (as 3.3 would have ignored them, applying changes to snap/log w/o updating them)
    289. 

  289. 

  290. A workaround for this problem is to delete the epoch files if this situation occurrs - the version 3.4 server will create them similar to case 1) above.
    291. 

  291. 

  292. 

  293. ---
    294. 

  294. 

  295. * [ZOOKEEPER-1100](https://issues.apache.org/jira/browse/ZOOKEEPER-1100) | *Major* | **Killed (or missing) SendThread will cause hanging threads**
    296. 

  296. 

  297. **WARNING: No release note provided for this incompatible change.**
    298. 

  298. 

  299. 

  300. ---
    301. 

  301. 

  302. * [ZOOKEEPER-1062](https://issues.apache.org/jira/browse/ZOOKEEPER-1062) | *Major* | **Net-ZooKeeper: Net::ZooKeeper consumes 100% cpu on wait**
    303. 

  303. 

  304. Cosmetic fixes to the patch
    305. 

  305. 

  306. 

  307. ---
    308. 

  308. 

  309. * [ZOOKEEPER-732](https://issues.apache.org/jira/browse/ZOOKEEPER-732) | *Minor* | **Improper translation of error into Python exception**
    310. 

  310. 

  311. Client that uses python binding may receive SystemError on session expiration.
    312. 

  312. 

  313. 

  314. ---
    315. 

  315. 

  316. * [ZOOKEEPER-271](https://issues.apache.org/jira/browse/ZOOKEEPER-271) | *Minor* | **Better command line parsing in ZookeeperMain.**
    317. 

  317. 

  318. There are three incompatibilities introduced by this commit into the client shell:
    319. 

  319. 

  320. 1) now requires commons-cli
    321. 

  321. 2) get no longer returns stat information by default, however there is a "-s" option that will result in the stat being included
    322. 

  322. 3) a deprecated message is reported in some cases, when the old command format is used. As a result the output of the command may be different compared to client output prior to this change.
    323. 

  323. 

  324. 

  325. ---
    326. 

  326. 

  327. * [ZOOKEEPER-87](https://issues.apache.org/jira/browse/ZOOKEEPER-87) | *Critical* | **Follower does not shut itself down if its too far behind the leader.**
    328. 

  328. 

  329. The value of syncLimit should be reviewed before this change is introduced in the cluster. Since it now detects followers that are lagging behind, clusters in which this was happening will now see followers being disconnected from time to time. This will normally be solved by increasing the syncLimit value.
    330. 

  330. 

  331. 

  332. 

  333.