Open topic with navigation
HPE Dropbox Connector provides asynchronous actions. Each asynchronous action has a queue to store requests until threads become available to process them. These queues are usually stored in a datastore file or in an external database hosted on a database server. However, to increase performance you can store these queues in memory.
Storing action queues in memory means that the queues (including queued actions and the results of finished actions) are lost if HPE Dropbox Connector stops unexpectedly, for example due to a power failure. This could result in some requests being lost, and if the queues are restored to a previous state some actions could run more than once.
Storing queues in memory will increase memory use. The amount of memory required depends on the size of the queues. Ensure that the server has sufficient memory.
You can not store action queues in memory if you want multiple components to share the same queues.
If you stop HPE Dropbox Connector cleanly, HPE Dropbox Connector writes the action queues from memory to disk so that it can resume processing when it is next started.
To configure HPE Dropbox Connector to store asynchronous action queues in memory, follow these steps.
To store action queues in memory
If you have set any of the following parameters, remove them:
Set the following configuration parameters.
||A Boolean value that specifies whether to keep the queues for asynchronous actions in memory. Set this parameter to
||(Optional) The time interval (in minutes) at which the action queues are written to disk. Writing the queues to disk can reduce the number of queued actions that would be lost if HPE Dropbox Connector stops unexpectedly, but configuring a frequent backup will increase the load on the datastore and might reduce performance.|
[Actions] UseInMemoryDatastore=TRUE InMemoryDatastoreBackupIntervalMins=30
Save and close the configuration file.
When you start HPE Dropbox Connector, it stores action queues in memory.