Auto-sync: update nexus workspace
This commit is contained in:
51
wiki/concepts/Override-Status.md
Normal file
51
wiki/concepts/Override-Status.md
Normal file
@@ -0,0 +1,51 @@
|
||||
---
|
||||
title: "Override Status"
|
||||
type: concept
|
||||
tags:
|
||||
- AWS
|
||||
- Scheduling
|
||||
- Control
|
||||
- AWS-Instance-Scheduler
|
||||
sources:
|
||||
- ctp-topic-27-aws-instance-scheduler
|
||||
last_updated: 2026-05-12
|
||||
---
|
||||
|
||||
## Override Status
|
||||
|
||||
AWS Instance Scheduler 中的高级配置机制,允许管理员强制覆盖正常的调度规则,将实例保持在特定状态(通常为停止状态)。
|
||||
|
||||
## Core Mechanism
|
||||
|
||||
通过在实例上设置 `Override` 标签来激活:
|
||||
|
||||
- **`Override = true`**:强制将实例保持在停止状态,即使在预设的启动时间内也不启动
|
||||
- **`Override = false`**:恢复正常调度逻辑
|
||||
|
||||
## Use Cases
|
||||
|
||||
### 1. 紧急维护场景
|
||||
- 实例正在进行紧急安全补丁更新
|
||||
- 临时禁用调度以避免干扰关键操作
|
||||
|
||||
### 2. 资源保留场景
|
||||
- 保留特定环境(如 UAT/预生产)在特定时期保持运行
|
||||
- 临时排除特定实例从自动调度
|
||||
|
||||
### 3. 故障规避
|
||||
- 实例上运行的任务无法接受意外重启
|
||||
- 生产等效环境需要更精细的控制
|
||||
|
||||
## Relationship to Tagging
|
||||
|
||||
Override Status 通过 `Override` 标签实现,是 Instance Scheduler [[Tagging]] 机制的重要组成部分:
|
||||
|
||||
| 标签键 | 作用 | 优先级 |
|
||||
|--------|------|--------|
|
||||
| `Schedule` | 指定调度名称 | 正常调度 |
|
||||
| `Override = true` | 强制停止覆盖 | 最高优先级 |
|
||||
|
||||
## Related Pages
|
||||
- [[AWS-Instance-Scheduler]] — 主要使用场景
|
||||
- [[Tagging]] — 实现机制
|
||||
- [[ctp-topic-27-aws-instance-scheduler]] — 原始来源
|
||||
Reference in New Issue
Block a user