anchor.diff:  The `search_type` can be set in a similar manner to globally apply to
   all search requests.
   
  -The msearch's `max_concurrent_searches` request parameter can be used to control
  -the maximum number of concurrent searches the multi search api will execute.
  -This default is based on the number of data nodes and the default search thread pool size.
  -
  -The request parameter `max_concurrent_shard_requests` can be used to control
  -the maximum number of concurrent shard requests that each sub search request
  -will execute per node. This parameter should be used to protect a single
  -request from overloading a cluster (e.g., a default request will hit all
  -indices in a cluster which could cause shard request rejections if the number
  -of shards per node is high). This default value is `5`.In certain scenarios
  -parallelism isn't achieved through concurrent request such that this protection
  -will result in poor performance. For instance in an environment where only a
  -very low number of concurrent search requests are expected it might help to
  -increase this value to a higher number.
  -
  -[float]
  +
   [[msearch-security]]
   ==== Security
   
   See <<url-access-control>>
   
  -[float]
  +
   [[template-msearch]]
   ==== Template support
   
   Much like described in <<search-template>> for the _search resource, _msearch
  -also provides support for templates. Submit them like follows:
  +also provides support for templates. Submit them like follows for inline 
  +templates:
   
   [source,js]
   -----------------------------------------------
  
positive.code: // CONSOLE
  // TEST[setup:twitter]
  
  for inline templates.
  
  You can also create search templates:
  
  
negative.code: // CONSOLE
  // TEST[continued]
  
  
  [[multi-search-partial-responses]]
  ==== Partial responses
  
  To ensure fast responses, the multi search API will respond with partial results 
  if one or more shards fail. See <<shard-failures, Shard failures>> for more 
  information.
  