The bulkupdate command sends a request to the scalability server to send the messages to the domain manager in bulk. Each message sent to the domain manager has specified number of submessages depending on the values provided in the configuration policies, Bulk Update: Maximum number of job results in a message and Bulk Update: Maximum units for which detection/job records will be sent in a message. If the configuration policies have not been applied to the scalability server, the default values of the configuration policies are used.
You can run the bulkupdate command whenever you want to send the cached messages in bulk. The command is independent of the bulk update interval and forces the bulk update to take place immediately. Additionally, the command does not reset the specified bulk update interval. For example, consider a scenario where you set the bulk update interval to 10 minutes, and after 5 minutes, you run the sd_sscmd bulkupdate command. In this case, the command forces the bulk update to take place immediately, but it does not reset the bulk update interval. The bulk update takes place again after 5 minutes when the actual bulk update interval of 10 minutes is elapsed.
Important! You can run this command and send the messages in bulk even when the scalability server is not running in the bulk update mode. In this case, the default value for the message size is used to send the messages in bulk.
This command has the following format:
sd_sscmd bulkupdate
Note: The command is valid for a scalability server running on the domain manager as well as for a standalone scalability server.
|
Copyright © 2013 CA.
All rights reserved.
|
|