Release Notes

Slack Docker Pulls GitHub edit source

March 24, 2023

Highlights

Revert of Default TTL Behavior Change

In the previous release, the default TTL behavior was modified but a backwards compatibility issue was discovered. This version changes it back to the original behavior of deleting the data from both Alluxio and the underlying storage as opposed to only deleting the data from Alluxio. See more details in the corresponding github PR.

Improvements and Bugfixes Since 2.9.2

Notable Configuration Property Changes

Property Key Old 2.9.2 value New 2.9.3 value PR
alluxio.proxy.s3.multipart.upload.cleaner.enabled true false #16937
alluxio.proxy.s3.v2.version.enabled true false #16937
alluxio.user.file.create.ttl.action DELETE_ALLUXIO FREE #17039

Benchmark

  • Add LoadMetadata and CreateTree operation to StressMasterBench (#17042)(ace82a)

Build

Client

FUSE/POSIX

  • Fix fuse metadata command ClassCastException (#17035)(5425c2)

Journal and Metadata Sync

Job Service

Docker and K8s

  • Add UseContainerSupport flag to default value.yaml of k8s helm chart (#17055)(b16a3f)
  • Bump CSI package version to fix security alert (#17117)(1ad1cc)

Log

  • Add more details in Log4j default settings (#17072)(595a55)

Master

Metrics

RPC

  • Support getBlockInfo excluding mount-related info (#17006)(276644)

S3 API

CLI

  • Enhance the capacity report to show worker registration info (#16927)(df0ae1)

UFS

  • Fix property identity typo error (#17109)(fd7350)
  • Fix content hash for GCS v2 stream (#17089)(b59df3)
  • Remove HdfsUnderFileSystemFactory from service loading in COSN UFS jar (#17024)(c9ed63)

Acknowledgements

We want to thank the community for their valuable contributions to the Alluxio 2.9.3 release. Especially, we would like to thank:

Haoning Sun (Haoning-Sun), Kaijie Chen (kaijchen), Xinran Dong (007DXR), Yaolong Liu (codings-dan), humengyu (humengyu2012), Xinyu Deng (voddle), Baolong Mao (maobaolong), Tianbao Ding (flaming-archer), fengshunli, and jianghuazhu.

Enjoy the new release and look forward to hearing your feedback on our Community Slack Channel.