Ozone has a set of command line tools that can be used to manage ozone.
All these commands are invoked via the ozone script.
Daemon commands:
Client commands:
hdfs dfs)Admin commands:
Test tools:
For more information see the following subpages:
Genconf tool generates a template ozone-site.xml file at the specified path. This template file can be edited to replace with proper values. ozone genconf <path>
Generate ConfigurationsAudit Parser tool can be used for querying the ozone audit logs. This tool creates a sqllite database at the specified path. If the database already exists, it will avoid creating a database. The database contains only one table called audit defined as: CREATE TABLE IF NOT EXISTS audit ( datetime text, level varchar(7), logger varchar(7), user text, ip text, op text, params text, result varchar(7), exception text, UNIQUE(datetime,level,logger,user,ip,op,params,result)) Usage: ozone auditparser <path to db file> [COMMAND] [PARAM]
Audit ParserSCM is the block service for Ozone. It is also the workhorse for ozone. But user process never talks to SCM. However, being able to read the state of SCM is useful. SCMCLI allows the developer to access SCM directly. Please note: Improper usage of this tool can destroy your cluster. Unless you know exactly what you are doing, Please do not use this tool. In other words, this is a developer only tool.
SCMCLITesting is one of the most important part during the development of a distributed system. We have the following type of test. This page includes our existing test tool which are part of the Ozone source base. Note: we have more tests (like TCP-DS, TCP-H tests via Spark or Hive) which are not included here because they use external tools only. Unit test As every almost every java project we have the good old unit tests inside each of our projects.
Testing tools