Blogs

Query performance of vRealize Log Insight may degrade while under average or low load.

Corrupted data buckets in the inventory of vRealize Log Insight can cause slow querying.

To Improve performance, remove the corrupted buckets from the vRealize Log Insight inventory.

To identifying and remove corrupted buckets from the inventory, use one of these options:

Continue reading “Improve Query performance by removing corrupted buckets in vRealize Log Insight”

root@localhost [ ~ ]# /usr/lib/loginsight/application/lib/apache-cassandra-3.11.10/bin/nodetool -u <USER> -pw <PASSWORD> statusDatacenter: datacenter1=======================Status=Up/Down|/ State=Normal/Leaving/Joining/Moving--  Address        Load       Tokens       Owns (effective)  Host ID                               RackUN  10.126.59.242  1.06 MiB   256          100.0%            5eb505ea-1792-418d-8106-9c6af5a5494c  rack1 To gather cassandra credentials root@localhost [ ~ ]# /usr/lib/loginsight/application/lib/apache-cassandra-3.11.10/bin/credentials-look-up <cassandra-user value="lisuper" /> <cassandra-password value="deeswvk1+E" />

Remove the existing master node from the cluster

• Log into each vRealize Log Insight node as root via SSH or Console.
• Stop the Log insight service on all nodes:

service loginsight stop

Note: The following steps are not to be performed on the master node as it will be removed from the cluster. Continue reading “vRealize Loginsight : How to remove faulty Master node”