The options for performing a plan change. Specify only one property each time. The default is grow_and_shrink.


autodetect (AutodetectStrategyConfig)
A strategy that lets constructor choose the most optimal way to execute the plan.
grow_and_shrink (GrowShrinkStrategyConfig)
A strategy that creates instances with the new plan, migrates data from the old instances, then shuts down the old instances. GrowShrinkStrategyConfig is safer than 'rolling' and ensures single node availability during a plan change, but can be a lot slower on larger clusters.
rolling (RollingStrategyConfig)
Performs inline, rolling configuration changes that mutate existing containers. TIP: This is the fastest way to update a plan, but can fail for complex plan changes, such as topology changes. Also, this is less safe for configuration changes that leave a cluster in a non running state. NOTE: When you perform a major version upgrade, and 'group_by' is set to '*all*';, rolling is required.
rolling_grow_and_shrink (RollingGrowShrinkStrategyConfig)
A strategy that creates new Elasticsearch instances, Kibana instances, and APM Servers with the new plan, then migrates the node data to minimize the amount of spare capacity.


   "autodetect" : {},
   "grow_and_shrink" : {},
   "rolling" : {
      "allow_inline_resize" : true,
      "group_by" : "string",
      "shard_init_wait_time" : 0,
      "skip_synced_flush" : true
   "rolling_grow_and_shrink" : {}