Making snapshot store/restore rate dynamic

[kkewwei]

Description

How to use:

1.create repository

POST /_snapshot/my-fs-repository/
{
  "type": "fs",
  "settings": {
    "location": "/Users/xxx/Downloads/snap_data1/1",
     "max_restore_bytes_per_sec": "100mb",
     "max_snapshot_bytes_per_sec": "100mb"
  }
}

2.adjust the store and restore rate

POST /_snapshot/my-fs-repository/
{
  "type": "fs",
  "settings": {
    "location": "/Users/xxx/Downloads/snap_data1/1",
     "max_restore_bytes_per_sec": "50mb",
     "max_snapshot_bytes_per_sec": "50mb"
  }
}

or 

POST /_snapshot/my-fs-repository/
{
  "type": "fs",
  "settings": {
     "max_restore_bytes_per_sec": "50mb",
     "max_snapshot_bytes_per_sec": "50mb"
  }
}

Note:

• Only max_snapshot_bytes_per_sec and max_restore_bytes_per_sec in settings can be changed, which will adjust the rate of ongoing snapshot. Other parameters within the settings can be left default or kept consistent.
• If other parameters within the settings are also changed, it will have no impact on the rate of existing snapshots.

Related Issues

Resolves #17488

Check List

• Functionality includes testing.
• API changes companion pull request created, if applicable.
• Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

❌ Gradle check result for fc25085: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 7a20142: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

✅ Gradle check result for 7a20142: SUCCESS

[github-actions]

❌ Gradle check result for 3b763c5: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 88dad9f: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for bd1f43c: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for bd1f43c:

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

✅ Gradle check result for bd1f43c: SUCCESS