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 'pass:macros[all]';, rolling is required.

{
    "skip_synced_flush": true,
    "allow_inline_resize": true,
    "group_by": "string",
    "shard_init_wait_time": 0
}