anchor.diff:  significant overhead associated with this pre-filter phase.
   ================================
   
  +[role="xpack"]
  +[testenv="basic"]
  +[[monitoring_frozen_indices]]
   == Monitoring frozen indices
   
   Frozen indices are ordinary indices that use search throttling and a memory efficient shard implementation. For API's like the
  -`<<cat-indices>>` frozen indicies may identified by an index's `search.throttled` property (`sth`).
  +<<cat-indices>> frozen indices may identified by an index's `search.throttled` property (`sth`).
   
   [source,js]
   --------------------------------------------------
  
positive.code: execution on a per shard level. Depending on the data in an index, a frozen index may execute searches in the seconds to minutes range, when the same index in an unfrozen state may execute the same search request in milliseconds.
  --
  
  == Best Practices
  
  Since frozen indices provide a much higher disk to heap ratio at the expense of search latency, it is advisable to allocate frozen indices to
  dedicated nodes to prevent searches on frozen indices influencing traffic on low latency nodes. There is significant overhead in loading
  
negative.code: [role="xpack"]
  [testenv="basic"]
  [[frozen-indices]]
  = Frozen indices
  
  [partintro]
  --
  