### Human: Can you tell about Alert - A1120 - CuratorJobRunningTooLong. ### Assistant: Investigating CuratorJobRunningTooLong issues on a Nutanix cluster.. This Nutanix article provides the information required for troubleshooting the alert CuratorJobRunningTooLong for your Nutanix cluster.
Alert Overview
The Curator Job Running Too Long alert A1120 is generated if the active Curator jobs have been running for too long. An alert will be raised if a Curator scan runs for more than 21600 seconds (6 hours) and then after every 12600 seconds (3.5 hours). 
Sample Alert

For status: INFO

Block Serial Number: 19SMXXXXXXXX 

Output messaging

Check ID130015DescriptionThe Curator job has been running for too long.Causes of failureVariousResolutionsContact Nutanix support if this issue persists.ImpactBackground cluster maintenance tasks might get affected in the future. The root cause should be addressed as soon as possible.Alert IDA1120Alert TitleCurator Job Running Too LongAlert MessageCurator job name with id execution_id has been running for a long time i.e. elapsed_time_secs seconds.. Troubleshooting

Curator scan times depend on the cluster size (number of nodes), global metadata size, and metadata scan speed in the Map phase of the Map/Reduce job, among other things.For more information on local vs global metadata, see Scalable metadata chapter in the Nutanix bible.

In order to check metadata size, run the following command: 

nutanix@CVM:~$ nodetool -h 0 ring

Example output:

nutanix@CVM:~$ nodetool -h 0 ring

One possible reason for high metadata usage can be using the Deduplication feature for workloads not suitable for it. For more information on Deduplication Best Practices, see the corresponding chapter in Prism Web Console Guide.Another reason for long-running Curator Jobs, or failing Curator scans, might be the RPO settings on clusters having dense nodes.Check both the frequency and retention policy for the snapshots, if data protection features are in use:

1 hour vs 6 hours vs 24 hours RPO,for 1 hour RPO, if supported, the 12/1/1/1 retention should not be exceeded. 
In case if cluster contains dense nodes, run the NCC dense_node_configuration_checks and refer to KB 7196 for more details.

Resolving the issue

If you need assistance or in case the above-mentioned steps do not resolve the issue, consider engaging Nutanix Support.Collect additional information and attach them to the support case.

Collecting Additional Information

Before collecting additional information, upgrade NCC. For information on upgrading NCC, see KB 2871.Collect the NCC output file ncc-output-latest.log. For information on collecting the output file, see KB 2871.Collect Logbay bundle using the following command. For more information on Logbay, see KB 6691. 
	nutanix@CVM:~$ nodetool -h 0 ring
	

Attaching Files to the Case

When viewing the support case on the support portal, use the Reply option and upload the files from there.If the size of the NCC log bundle being uploaded is greater than 5 GB, Nutanix recommends using the Nutanix FTP server due to supported size limitations. See KB 1294.. ### Human: Now explain this as a Nutanix support agent summarizing the answer step by step. In case, you don't know the answer say - I don't know.