SmartData 2.6.X delivers multiple new features and optimizes performance. For example, Tablestore and Raft instances can be used as the metadata storage backends of Namespace Service. Namespace Service can be deployed in high availability (HA) mode. The read/write performance, block storage mode, and cache mode of JindoFS are optimized.

New metadata storage methods

In earlier versions, you can use only RocksDB as a metadata storage backend. In SmartData 2.6.X, you can also use Tablestore or Raft instances as metadata storage backends. This way, JindoFS achieves the storage of metadata in the cloud.

RocksDB is the default metadata storage method. It is simple and efficient when you use JindoFS in cache mode and do not require Namespace Service in HA mode or high performance of metadata storage. If Tablestore or Raft instances are used, you can deploy Namespace Service in HA mode.

For more information about each metadata storage method, see the following topics:

Optimization of JindoFS usage modes

JindoFS supports the block storage mode and cache mode:
  • Block storage mode: You can use JindoFS in this mode in the same way as in versions earlier than E-MapReduce (EMR) V3.26.3. For more information, see Use JindoFS in block storage mode.
  • Cache mode: Multiple file access methods are supported in this mode. For example, you can use the same method to access files as in block storage mode. You can also use the original file access method of OSS. For more information, see Use JindoFS in cache mode.

Supported permissions

In block storage mode, you can run UNIX commands or use Ranger to manage permissions:
  • UNIX allows you to grant the rwxrwxrwx permission on files.
  • Ranger allows you to use wildcards in paths when you configure a permission.

For more information about permissions, see Manage JindoFS permissions.