2022-05-24 | HDDS-3630 | Merge Container RocksDB in DN | Use one RocksDB to hold all container metadata on a DN data volume | implemented |
2021-04-12 | HDDS-2939 | Ozone FS namespace / prefix table | Use additional prefix table for indexed data retrieval | implemented |
2021-02-15 | HDDS-3698 | Non Rolling upgrade support in Ozone. | ‘Non rolling’ upgrade support in Ozone. | implemented |
2021-02-15 | HDDS-4470 | Ozone Manager Prepare for Upgrade | ‘Prepare upgrade’ step to make sure all the OMs use the same version of the software to update their DBs (apply transaction) for a given request. | implemented |
2021-02-15 | | Upgrade - Developer Primer | Helpful resources for those who are bringing layout changes. | |
2020-11-09 | HDDS-4440 | Proposed persistent OM connection for S3 gateway | Proposal to use per-request authentication and persistent connections between S3g and OM | accepted |
2020-06-30 | HDDS-3816 | Erasure Coding in Ozone | Use Erasure Coding algorithm for efficient storage | draft |
2020-06-30 | HDDS-2665 | Implement new Ozone FileSystem scheme ofs:// | A new schema structure for Hadoop compatible file system | implemented |
2020-06-08 | HDDS-3755 | Storage Class | New abstraction to configure replication methods. | draft |
2020-04-02 | HDDS-3331 | Ozone Volume Management | A simplified version of mapping between S3 buckets and Ozone volume/buckets | accepted |
2020-03-25 | HDDS-3001 | NFS support Ozone | Adopt NFS gateway of HDFS and provide NFS file system view | draft |
2020-03-05 | HDDS-2823 | SCM HA support | HA for Storage Container Manager using Ratis to replicate data | implementing |
2020-01-09 | HDDS-2867 | Generic Extensible Token support for Ozone | Extend existing token architecture to all entities of Ozone | accepted |
2019-11-07 | HDDS-2416 | Ozone Trash Feature | Feature provides a user with the ability to recover keys that may have been deleted accidentally. (similar to the HDFS trash feature). | implementing |
2019-08-19 | HDDS-1996 | Recon server v2 | Second phase of Recon development. Recon acts as a passive SCM. | implemented |
2019-07-31 | HDDS-1881 | Decommissioning in Ozone | Formal process to shut down machines in a safe way after the required replications. | implementing |
2019-06-20 | HDDS-2012 | Ozone GDPR framework | Crypto key management to handle GDPR “right to be forgotten” feature | implemented |
2019-06-20 | HDDS-1672 | Ozone locks in OM | Hierarchical locking structure for OM elements (volumes/keys/buckets) | implemented |
2019-06-07 | HDDS-1659 | Ozone Enhancement Proposals | Definition of the process to share new technical proposals with the Ozone community. | implemented |
2019-05-25 | HDDS-1467 | Configless Ozone service management | Distribute only minimal configuration and download all the remaining before start | accepted |
2019-05-21 | HDDS-1564 | Ozone multi-raft support | Datanodes can be part of multiple independent RAFT groups / pipelines | implemented |
2019-04-25 | HDDS-1466 | Type-safe configuration API | Inject configuration values based on annotations instead of using constants and Hadoop API | implemented |
2019-02-19 | HDDS-1084 | Recon server 1 | Second phase of Recon development. Recon acts as a passive SCM. | implemented |
2019-02-08 | HDDS-1041 | Ozone Encryption At Rest | Transparent Data Encryption encrypts the data before store it | implemented |
2018-11-16 | HDDS-698 | Topology-awareness | Placement policy to use rack information for read and write | implemented |
2018-09-27 | HDDS-434 | S3 protocol support for Ozone | Support any AWS S3 compatible client with dedicated REST endpoint | implemented |
2018-09-18 | HDDS-505 | Ozone Manager HA | Support HA for Ozone Manager with the help of RATIS | implemented |