There are two options to synchronize SAM and the Notification cache: Stopping the SAM publisher to clear the Notification cache or stopping SAM to clear the Notification cache.
Stopping the SAM publisher to clear the Notification cache:
This method of clearing the Notification cache has less impact on the system as only SAM publisher is stopped.
Steps to implement:
- Stop the publisher as
$Smarts_Basedir/bin# dmctl -s <PRES-SAM_Domain> invoke SM_AMQPNotificationPublisher::SM-AMQPNotificationPublisher stop
- Clear the Notifications cache by typing these commands:
- $Smarts_Basedir/bin# sm_service stop smarts-elasticsearch
- $Smarts_Basedir/bin# sm_service stop smarts-tomcat
- $Smarts_Basedir# rm -rf local/repos/emc-alerts-es/nodes
- $Smarts_Basedir/bin# sm_service start smarts-elasticsearch
- $Smarts_Basedir/bin# sm_service start smarts-tomcat
- Start the publisher:
$Smarts_Basedir/bin# dmctl -s <PRES-SAM_Domain>
invoke SM_AMQPNotificationPublisher::SM-AMQPNotificationPublisher start
Stopping SAM to clear the Notification cache:
This method of clearing the Notification cache has a substantial impact on the system, as SAM domain needs to be stopped.
Steps to implement:
- Stop the SAM service as
$Smarts_Basedir/bin# sm_service stop ic-sam-pres
- Clear the Notifications cache by typing these commands:
- $Smarts_Basedir/bin# sm_service stop smarts-elasticsearch
- $Smarts_Basedir/bin# sm_service stop smarts-tomcat
- $Smarts_Basedir# rm -rf local/repos/emc-alerts-es/nodes
- $Smarts_Basedir/bin# sm_service start smarts-elasticsearch
- $Smarts_Basedir/bin# sm_service start smarts-tomcat
- Start the SAM service as
$Smarts_Basedir/bin# sm_service start ic-sam-pres