|
8 | 8 | * This is the Snapshot Lifecycle Management (SLM) main package. SLM is part of the wider ILM feature, reusing quite a bit of the
|
9 | 9 | * functionality for itself in some places, which is why the two features are contained in the same plugin.
|
10 | 10 | *
|
11 |
| - * This package contains the {@link org.elasticsearch.xpack.snapshotlifecycle.SnapshotLifecycleService} and |
12 |
| - * {@link org.elasticsearch.xpack.snapshotlifecycle.SnapshotLifecycleTask}, as well as the Rest and Transport actions for the |
| 11 | + * This package contains the {@link org.elasticsearch.xpack.slm.SnapshotLifecycleService} and |
| 12 | + * {@link org.elasticsearch.xpack.slm.SnapshotLifecycleTask}, as well as the Rest and Transport actions for the |
13 | 13 | * feature set.
|
14 | 14 | * This package contains the primary execution logic and most of the user facing
|
15 | 15 | * surface area for the plugin, but not everything. The model objects for the cluster state as well as several supporting classes are
|
16 | 16 | * contained in the {@link org.elasticsearch.xpack.core.snapshotlifecycle} package.
|
17 | 17 | *
|
18 |
| - * <p>{@link org.elasticsearch.xpack.snapshotlifecycle.SnapshotLifecycleService} maintains an internal |
| 18 | + * <p>{@link org.elasticsearch.xpack.slm.SnapshotLifecycleService} maintains an internal |
19 | 19 | * {@link org.elasticsearch.xpack.core.scheduler.SchedulerEngine SchedulerEngine} that handles scheduling snapshots. The service
|
20 | 20 | * executes on the currently elected master node. It listens to the cluster state, detecting new policies to schedule, and unscheduling
|
21 | 21 | * policies when they are deleted or if ILM is stopped. The bulk of this scheduling management is handled within
|
22 |
| - * {@link org.elasticsearch.xpack.snapshotlifecycle.SnapshotLifecycleService#maybeScheduleSnapshot(SnapshotLifecyclePolicyMetadata)} |
| 22 | + * {@link org.elasticsearch.xpack.slm.SnapshotLifecycleService#maybeScheduleSnapshot(SnapshotLifecyclePolicyMetadata)} |
23 | 23 | * which is executed on all snapshot policies each update.
|
24 | 24 | *
|
25 |
| - * <p>The {@link org.elasticsearch.xpack.snapshotlifecycle.SnapshotLifecycleTask} object is what receives an event when a scheduled policy |
| 25 | + * <p>The {@link org.elasticsearch.xpack.slm.SnapshotLifecycleTask} object is what receives an event when a scheduled policy |
26 | 26 | * is triggered for execution. It constructs a snapshot request and runs it as the user who originally set up the policy. The bulk of this
|
27 | 27 | * logic is contained in the
|
28 |
| - * {@link org.elasticsearch.xpack.snapshotlifecycle.SnapshotLifecycleTask#maybeTakeSnapshot(String, Client, ClusterService, |
| 28 | + * {@link org.elasticsearch.xpack.slm.SnapshotLifecycleTask#maybeTakeSnapshot(String, Client, ClusterService, |
29 | 29 | * SnapshotHistoryStore)} method. After a snapshot request has been submitted, it persists the result (success or failure) in a history
|
30 | 30 | * store (an index), caching the latest success and failure information in the cluster state. It is important to note that this task
|
31 | 31 | * fires the snapshot request off and forgets it; It does not wait until the entire snapshot completes. Any success or failure that this
|
32 | 32 | * task sees will be from the initial submission of the snapshot request only.
|
33 | 33 | */
|
34 |
| -package org.elasticsearch.xpack.snapshotlifecycle; |
| 34 | +package org.elasticsearch.xpack.slm; |
35 | 35 |
|
36 | 36 | import org.elasticsearch.client.Client;
|
37 | 37 | import org.elasticsearch.cluster.service.ClusterService;
|
|
0 commit comments