[HDDS-11377] ozone ldb command support for rocksdb

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Tejaskriya Madhan
• Reporter: Tejaskriya Madhan
• Created: 28/Aug/24 06:53
• Updated: 10/Oct/24 12:07

Description

When Ozone bugs are found, we need to manually update OM or SCM RocksDB to recover from the situation. There's no built-in ldb command line in Ozone to modify RocksDB. User will have to install rockDB ldb tool to do this.

Include the "ldb" (levelDB command line) in Ozone tools to enable direct RocksDB changes from a cluster without installing ldb in-house. 

Issue Links

• duplicates: HDDS-8210 For SchemaV3 block_data table, nest blockId inside a containerId map
• duplicates: HDDS-11431 Ozone repair command for adding/updating a record in a db
• relates to: HDDS-8210 For SchemaV3 block_data table, nest blockId inside a containerId map

Sub-Tasks

• Add endKey filter option to ozone debug ldb scan: Resolved
• Introduce debug CLI command to show the value schema of any rocksDB: Resolved
• Add --fields filter option to ozone debug ldb scan: Resolved
• Implement equals operation for --filter option to ozone ldb scan: Resolved
• Implement lesser/greater operation for --filter option of ldb scan command: Resolved
• Implement regex matching operation for --filter option of ldb scan command: Resolved
• Remove lib/gson-2.10.1.jar: Resolved
• Document ozone debug ldb command: Resolved
• Create ozone repair ldb put command for om.db: Open
• ozone ldb changes having audit log: Open