`nodetool invalidatecountercache`

Where is the cassandra-env.sh file?

The location of the cassandra-env.sh file depends on the type of installation:

Installation Type Location

Installation Type	Location
Package installations + Installer-Services installations	`/etc/dse/cassandra/cassandra-env.sh`
Tarball installations + Installer-No Services installations	`<installation_location>/resources/cassandra/conf/cassandra-env.sh`

Package installations + Installer-Services installations

/etc/dse/cassandra/cassandra-env.sh

Tarball installations + Installer-No Services installations

<installation_location>/resources/cassandra/conf/cassandra-env.sh

Clears the counter cache.

Synopsis

nodetool [options] invalidatecountercache

Tarball and Installer No-Services path:

<installation_location>/resources/cassandra/bin

Connection options
Short	Long	Description
`-h`	`--host`	Hostname or IP address.
`-p`	`--port`	Port number.
`-pwf`	`--password-file`	Password file path.
`-pw`	`--password`	Password.
`-u`	`--username`	Remote JMX agent username.
`--`	Separates an option from an argument that could be mistaken for an option.

For tarball installations, execute the command from the <installation_location>/bin directory.
If a username and password for RMI authentication are set explicitly in the cassandra-env.sh file for the host, then you must specify credentials.
nodetool invalidatecountercache operates on a single node in the cluster if -h is not used to identify one or more other nodes. If the node from which you issue the command is the intended target, you do not need the -h option to identify the target; otherwise, for remote invocation, identify the target node, or nodes, using -h.

The nodetool invalidatecountercache command clears the counter cache, and the system starts saving all counter keys.

 $ nodetool -u username -pw password invalidatecountercache