Setting up the objectizer service interval

Take the following steps to set up the objectizer service interval.

The default interval between the completion of an objectizer cycle and the starting of the next cycle is 30 minutes. However, it needs to be planned properly based on the following information:

The frequency and the number of new file ingestions that might be objectized.
The number of protocol nodes that are deployed.
How quickly the ingested file needs to be objectized.

Remember: Objectization is a resource-intensive process.

The resource utilization is related to the number of containers that have unified file and object access enabled. The schedule of running the objectization process needs to be planned carefully. Running it too frequently might impact your protocol node's resource utilization. Schedule it during off business hours, especially when there are only a few protocol nodes (such as 2) with basic resource configuration. Or, schedule it with an interval of 30 minutes or more when you have protocol nodes with adequate resources (where the number of protocol nodes is more than 2).

Remember: Set the objectizer service interval to a no less than 30 minutes irrespective of the setup. If you need to urgently objectize files, you can use the mmobj file-access command to objectize the specified files.

Set up the objectization interval by using the mmobj config change as follows:
```
mmobj config change --ccrfile spectrum-scale-objectizer.conf \
--section DEFAULT --property objectization_interval --value 2400
```
This command sets an interval of 40 minutes between the completion of an objectization cycle and the start of the next cycle.

Verify that the objectization time interval is changed using the mmobj config list as follows:

mmobj config list --ccrfile spectrum-scale-objectizer.conf --section DEFAULT 
--property objectization_interval