dsetool tieredtablestats

Outputs tiered storage information, including SSTables, tiers, timestamps, and sizes. Provides information on every table that uses tiered storage.

Synopsis

dsetool tieredtablestats <keyspace_name>.<table_name> [-v]

Syntax legend

Syntax conventions Description

Syntax conventions	Description
Italic, bold, or `< >`	Syntax diagrams and code samples use one or more of these styles to mark placeholders for variable values. Replace placeholders with a valid option or your own user-defined value. In CQL statements, angle brackets are required to enclose data types in a set, list, map, or tuple. Separate the data types with a comma. For example: `<datatype2` In Search CQL statements, angle brackets are used to identify the entity and literal value to overwrite the XML element in the schema and `solrconfig` files, such as `@<xml_entity>='<xml_entity_type>'`.
`[ ]`	Square brackets surround optional command arguments. Do not type the square brackets.
`( )`	Parentheses identify a group to choose from. Do not type the parentheses.
`\|`	A pipe separates alternative elements. Type any one of the elements. Do not type the pipe.
`...`	Indicates that you can repeat the syntax element as often as required.
`'`	Single quotation marks must surround literal strings in CQL statements. Use single quotation marks to preserve upper case. + For Search CQL only: Single quotation marks surround an entire XML schema declaration, such as `'<<schema> ... </schema>>'`
`{ }`	Map collection. Curly braces enclose maps (`{ <key_datatype>:<value_datatype> }`) or key value pairs (`{ <key>:<value> }`). A colon separates the key and the value.
`;`	Ends a CQL statement.
`--`	Separate command line options from command arguments with two hyphens. This syntax is useful when arguments might be mistaken for command line options.

Italic, bold, or < >

Syntax diagrams and code samples use one or more of these styles to mark placeholders for variable values. Replace placeholders with a valid option or your own user-defined value.

In CQL statements, angle brackets are required to enclose data types in a set, list, map, or tuple. Separate the data types with a comma. For example: <datatype2

In Search CQL statements, angle brackets are used to identify the entity and literal value to overwrite the XML element in the schema and solrconfig files, such as @<xml_entity>='<xml_entity_type>'.

[ ]

Square brackets surround optional command arguments. Do not type the square brackets.

( )

Parentheses identify a group to choose from. Do not type the parentheses.

|

A pipe separates alternative elements. Type any one of the elements. Do not type the pipe.

...

Indicates that you can repeat the syntax element as often as required.

'

Single quotation marks must surround literal strings in CQL statements. Use single quotation marks to preserve upper case. + For Search CQL only: Single quotation marks surround an entire XML schema declaration, such as '<<schema> ... </schema>>'

{ }

Map collection. Curly braces enclose maps ({ <key_datatype>:<value_datatype> }) or key value pairs ({ <key>:<value> }). A colon separates the key and the value.

;

Ends a CQL statement.

--

Separate command line options from command arguments with two hyphens. This syntax is useful when arguments might be mistaken for command line options.

keyspace_name.table_name: Required. The keyspace and table names of the search index. Keyspace and table names are case-sensitive. Enclose names that contain uppercase in double quotation marks.
-v: Output statistics for each SSTable, in addition to the tier summaries.

Examples

To monitor all tables using tiered storage:

dsetool tieredtablestats

Output of command:

ks.tbl
  Tier 0:
    Summary:
      max_data_age: 1449178580284
      max_timestamp: 1449168678515945
      min_timestamp: 1449168678515945
      reads_120_min: 5.2188117172945374E-5
      reads_15_min: 4.415612774014863E-7
      size: 4839
    SSTables:
      /mnt2/ks/tbl-257cecf1988311e58be1ff4e6f1f6740/ma-3-big-Data.db:
        estimated_keys: 256
        level: 0
        max_data_age: 1449178580284
        max_timestamp: 1449168678515945
        min_timestamp: 1449168678515945
        reads_120_min: 5.2188117172945374E-5
        reads_15_min: 4.415612774014863E-7
        rows: 1
        size: 4839
  Tier 1:
    Summary:
      max_data_age: 1449178580284
      max_timestamp: 1449168749912092
      min_timestamp: 1449168749912092
      reads_120_min: 0.0
      reads_15_min: 0.0
      size: 4839
    SSTables:
      /mnt3/ks/tbl-257cecf1988311e58be1ff4e6f1f6740/ma-4-big-Data.db:
        estimated_keys: 256
        level: 0
        max_data_age: 1449178580284
        max_timestamp: 1449168749912092
        min_timestamp: 1449168749912092
        reads_120_min: 0.0
        reads_15_min: 0.0
        rows: 1
        size: 4839

To monitor the health_data table using tiered storage:

dsetool tieredtablestats demo.health_data

To monitor the health_data table with output for each SSTable:

dsetool tieredtablestats demo.health_data -v