2f91e2aab7
We can be a little more efficient when aborting a snapshot. Since we know the new repository data after finalizing the aborted snapshot when can pass it down to the snapshot completion listeners. This way, we don't have to fork off to the snapshot threadpool to get the repository data when the listener completes and can directly submit the delete task with high priority straight from the cluster state thread. |
||
|---|---|---|
| .. | ||
| config/repository-s3 | ||
| licenses | ||
| src | ||
| build.gradle | ||