dsetool core_indexing_status

Retrieves the dynamic indexing status of a search index on a DSE Search node and displays the percent complete and an estimated completion time in milliseconds.

Restriction: Command is supported only on nodes with DSE Search workloads.

Synopsis

dsetool core_indexing_status [<keyspace_name>.]<table_name> [--all] [--progress]
Syntax legend
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.

Retrieves the dynamic indexing status (INDEXING, FINISHED, or FAILED) of the specified index or indexes.

Also identifies the reason the reindexing occurred. The possible reason for a reindexing event is categorized as one of the following:

  • BOOTSTRAP

  • NEW_SSTABLES

  • USER_REQUEST

Parameters:

[keyspace_name.]table_name

The search index table name is required. The keyspace name is optional. The case of keyspace and table names is preserved. You must use the correct case for the keyspace and table names.

--all

Retrieve the dynamic indexing status of the specified search index on all nodes.

--progress

Display the percent complete, an estimated completion time in milliseconds, and the reason for the reindexing. This option is ignored and is assumed true. The command always displays the status information.

Examples

These examples use the demo keyspace and health_data table.

To view the indexing status for the local node:

dsetool core_indexing_status demo.health_data

Results:

[demo.health_data]: INDEXING, 38% complete, ETA 452303 milliseconds (7 minutes 32 seconds),
                    reason: USER_REQUEST

To view the indexing status for a search index on a specified node:

dsetool -h 200.192.10.11 core_indexing_status demo.health_data

To view indexing status of all search indexes in the data center:

dsetool core_indexing_status demo.health_data --all

The results for 3 nodes in the data center:

Address 	 Core Indexing Status
200.192.10.11 	 FINISHED
200.192.10.12 	 FINISHED
200.192.10.23 	 FINISHED

Was this helpful?

Give Feedback

How can we improve the documentation?

© Copyright IBM Corporation 2025 | Privacy policy | Terms of use Manage Privacy Choices

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: Contact IBM