anchor.diff:  |=======================================================================
   |Name |Description |Requires Restart
   
  -|`analysis_limits`: `model_memory_limit` |The approximate maximum amount of
  -memory resources required for analytical processing. See <<ml-apilimits>>. | Yes
  +|`analysis_limits`: `model_memory_limit` |The approximate maximum amount of 
  +memory resources required for analytical processing. See <<ml-apilimits>>. You 
  +can update the `analysis_limits` only while the job is closed. The 
  +`model_memory_limit` property value cannot be decreased below the current usage. 
  +| Yes
   
   |`background_persist_interval` |Advanced configuration option. The time between
   each periodic persistence of the model. See <<ml-job-resource>>. | Yes
  
positive.code: 
  Updates certain properties of a job.
  
  ==== Request
  
  `POST _xpack/ml/anomaly_detectors/<job_id>/_update`
  
  
  ==== Path Parameters
  
  `job_id` (required)::
    (string) Identifier for the job
  
  ==== Request Body
  
  The following properties can be updated after the job is created:
  
  
negative.code: 
  [NOTE]
  --
  * If the `memory_status` property in the `model_size_stats` object has a value
  of `hard_limit`, this means that it was unable to process some data. You might
  want to re-run this job with an increased `model_memory_limit`.
  --
  
  [[ml-update-job-prereqs]]
  ==== {api-prereq-title}
  
  You must have `manage_ml`, or `manage` cluster privileges to use this API.
  For more information, see
  {xpack-ref}/security-privileges.html[Security privileges].
  
  [[ml-update-job-example]]
  ==== {api-examples-title}
  
  The following example updates the `total-requests` job:
  
  