Release Notes
February 4, 2022
Highlights
Address Some Memory Leaks & Crashes Involving RocksDB
- Areas of the codebase utilizing classes from the RocksDB library were updated to properly handle memory management (918e739).
Update Package Dependencies to Address Security Vulnerabilities
- Update hadoop dependencies (af1e33e)
- Bump gson version (dd017dc)
- Update protobuf version (176152c)(1e234dd)
- Update kubernetes packages (7d2f142)
- Update jersey version (2f3dffe)
- Update guava to fix some CVEs (fcb0b4c)
- Update log4j to 2.17.1 (a25b0ca)
- Address CVE-2022-23848 (44d591b)(221f0ed)
Improvements Since 2.7.2
- Add worker startup timeout property key (067e9d4)
- Add stacks page in worker web UI (fa54b1b)
- Support
statfs
for JNIFuse (d3e231a) - Support web server/metrics sink in standby masters (a10823a)
- Support Alluxio allowed Fuse truncates (4c8b555)
- Add
LoadTableCommand
(f645405) - Support build Ozone 1.2.1, remove shaded-ozone module (8993e46)
- Make the
checkConsistency
command check more cases (20a7f4e) - Make recursive options consistent in the filesystem shell (99e76a8)
Bugfixes Since 2.7.2
- Fix the bug which load metadata failed when the path is special (ea1cdc5)
- Fix Hub + k8s issues due to bad formatting and missing
log4j.properties
(f49dc8b) - Fix metrics
Worker.ActiveClients
counter error (7b64a95) - Fix argument in alluxio-fuse unmount when argument has trailing slash (85ac996)
- Fix wrong method call to get username and wrong parameter assignment (afe74e0)
- Fix the concurrent read/write in
Fuse.open(READ_WRITE)
(bb37aa8) - Fix journal dumper not work (3cb47b4)
- Fix a NPE error when running test (7f164c8)
- Fix incorrect calc of
cacheHitRatio
(80cbd8d)
Acknowledgements
We want to thank the community for their valuable contributions to the Alluxio 2.7.3 release. Especially, we would like to thank:
Baolong Mao (maobaolong), Haoning Sun (Haoning-Sun), Kevin Cai (kevincai), l-shen (ljl1988com), Lei Qian (qian0817), striverpan, XiChen (xichen01), Yaolong Liu (codings-dan)
Enjoy the new release and look forward to hearing your feedback on our Community Slack Channel.