Pacemaker 2 - en to zh_CN translation catalogue (98 entries)

en: Instance attributes available for all "stonith"-class resources
zh_CN:  可用于所有stonith类资源的实例属性

en: Intended for use in regression testing only
zh_CN: 仅适用于回归测试

en: Send logs to the additional named logfile
zh_CN: 将日志发送到其他命名日志文件

en: Pacemaker version on cluster node elected Designated Controller (DC)
zh_CN: 集群选定的控制器节点(DC)的 Pacemaker 版本

en: Used for informational and diagnostic purposes.
zh_CN: 用于提供信息和诊断.

en: An arbitrary name for the cluster
zh_CN: 任意的集群名称

en: This optional value is mostly for users' convenience as desired in administration, but may also be used in Pacemaker configuration rules via the #cluster-name node attribute, and by higher-level tools and resource agents.
zh_CN: 该可选值主要是为了方便用户根据管理的需要使用, 可以通过 #cluster-name 节点属性在 Pacemaker 配置规则中使用, 以及被更高级的工具和资源代理使用.

en: How long to wait for a response from other nodes during start-up
zh_CN: 启动过程中等待其他节点响应的时间

en: The optimal value will depend on the speed and load of your network and the type of switches used.
zh_CN: 其最佳值将取决于您的网络速度和负载以及使用的交换机类型.

en: Polling interval to recheck cluster state and evaluate rules with date specifications
zh_CN: 重新检查集群状态及评估日期规范规则的轮询间隔

en: How a cluster node should react if notified of its own fencing
zh_CN: 集群节点在收到针对自己的 fence 操作结果通知时应如何反应

en: Declare an election failed if it is not decided within this much time. If you need to adjust this value, it probably indicates the presence of a bug.
zh_CN: 如果集群在本项设置时间内没有作出决定则宣布选举失败. 这可能表明当前存在错误, 您需要调整该值.

en: Exit immediately if shutdown does not complete within this much time. If you need to adjust this value, it probably indicates the presence of a bug.
zh_CN: 如果在这段时间内关机仍未完成, pacemaker 将立即退出. 这可能表明当前存在错误, 您需要调整该值.

en: If you need to adjust this value, it probably indicates the presence of a bug.
zh_CN: 这可能表明当前存在错误, 您需要调整该值.

en: Delay cluster recovery for this much time to allow for additional events to occur. Useful if your configuration is sensitive to the order in which ping updates arrive.
zh_CN: 集群恢复将被推迟指定的时间间隔, 以等待更多事件发生. 如果您的配置对 ping 更新到达的顺序很敏感, 则可以使用此选项.

en: What to do when the cluster does not have quorum
zh_CN: 当集群没有达到必需票数时该如何做

en: Whether to lock resources to a cleanly shut down node
zh_CN: 是否锁定资源到完全关闭的节点

en: When true, resources active on a node when it is cleanly shut down are kept "locked" to that node (not allowed to run elsewhere) until they start again on that node after it rejoins (or for at most shutdown-lock-limit, if set). Stonith resources and Pacemaker Remote connections are never locked. Clone and bundle instances and the promoted role of promotable clones are currently never locked, though support could be added in a future release.
zh_CN: 设置为 true 时, 在完全关闭的节点上活动的资源将被 "locked" 到该节点 (不允许在其它方运行), 直到该节点重新加入后它们再次在该节点上启动 (最长为 shutdown-lock-limit，如果已设置). Stonith 资源和 Pacemaker Remote 连接永远不会被锁定. 克隆和捆绑实例以及可提升克隆的提升角色目前不会被锁定, 尽管可能在未来的发行版中添加支持.

en: Do not lock resources to a cleanly shut down node longer than this
zh_CN: 资源会被锁定到完全关闭的节点的最长时间

en: If shutdown-lock is true and this is set to a nonzero time duration, shutdown locks will expire after this much time has passed since the shutdown was initiated, even if the node has not rejoined.
zh_CN: 如果 shutdown-lock 为 true, 并且将此选项设置为非零时间间隔, 则自关闭操作执行经过此时间后，shutdown lock 将过期, 即使该节点尚未重新加入也是如此.

en: Enable Access Control Lists (ACLs) for the CIB
zh_CN: 为 CIB 启用访问控制列表 (ACL)

en: Whether resources can run on any node by default
zh_CN: 默认情况下资源是否可以在任何节点上运行

en: Whether the cluster should refrain from monitoring, starting, and stopping resources
zh_CN: 集群是否应避免监视, 启动和停止资源

en: Whether a start failure should prevent a resource from being recovered on the same node
zh_CN: 资源启动失败是否应阻止在同一节点上恢复该资源

en: When true, the cluster will immediately ban a resource from a node if it fails to start there. When false, the cluster will instead check the resource's fail count against its migration-threshold.
zh_CN: 当为true, 如果资源启动失败, 集群将立即禁止节点启动该资源, 当为false, 集群将检查资源的失败次数是否超过了其 migration-threshold.

en: Whether the cluster should check for active resources during start-up
zh_CN: 集群是否在启动期间检查活动的资源

en: If false, unresponsive nodes are immediately assumed to be harmless, and resources that were active on them may be recovered elsewhere. This can result in a "split-brain" situation, potentially leading to data loss and/or service unavailability.
zh_CN: 如果为 false, 则立即假定无响应的节点是无害的, 并且可以在其它位置恢复在其上活动的资源. 这可能会导致 "split-brain" 情况, 从而可能导致数据丢失和(或)服务不可用.

en: How long to wait for on, off, and reboot fence actions to complete by default
zh_CN: 默认情况下, 等待 on, off, 和 reboot fence 操作完成的时间

en: Whether watchdog integration is enabled
zh_CN: 是否启用 watchdog 集成设置

en: This is set automatically by the cluster according to whether SBD is detected to be in use. User-configured values are ignored. The value `true` is meaningful if diskless SBD is used and `stonith-watchdog-timeout` is nonzero. In that case, if fencing is required, watchdog-based self-fencing will be performed via SBD without requiring a fencing resource explicitly configured.
zh_CN: 集群会根据是否检测到 SBD 正在使用来自动设置此值. 用户配置的值将被忽略. 如果使用了无盘 SBD 并且 `stonith-watchdog-timeout` 不为零, 则值 `true` 才有实际意义. 在这种情况下, 如果需要fence, 将通过 SBD 执行基于 watchdog 的自我 fence, 而不需要明确配置 fence 资源.

en: How many times fencing can fail before it will no longer be immediately re-attempted on a target
zh_CN: fence 操作失败多少次会停止立即尝试

en: Allow performing fencing operations in parallel
zh_CN: 允许并行执行 fencing 操作

en: Apply fencing delay targeting the lost nodes with the highest total resource priority
zh_CN: 针对具有最高总资源优先级的丢失节点应用fencing延迟

en: Apply specified delay for the fencings that are targeting the lost nodes with the highest total resource priority in case we don't have the majority of the nodes in our cluster partition, so that the more significant nodes potentially win any fencing match, which is especially meaningful under split-brain of 2-node cluster. A promoted resource instance takes the base priority + 1 on calculation if the base priority is not 0. Any static/random delays that are introduced by `pcmk_delay_base/max` configured for the corresponding fencing resources will be added to this delay. This delay should be significantly greater than, safely twice, the maximum `pcmk_delay_base/max`. By default, priority fencing delay is disabled.
zh_CN: 如果我们所在的集群分区并不拥有大多数集群节点，则针对丢失节点的fence操作应用指定的延迟，这样更重要的节点就能够赢得fence竞赛。这对于双节点集群在split-brain状况下尤其有意义。如果基本优先级不为0，在计算时主资源实例获得基本优先级+1。任何对于相应的 fence 资源由 pcmk_delay_base/max 配置所引入的静态/随机延迟会被添加到此延迟。为了安全, 这个延迟应该明显大于 pcmk_delay_base/max 的最大设置值，例如两倍。默认情况下，优先级fencing延迟已禁用。

en: How long to wait for a node that has joined the cluster to join the controller process group
zh_CN: 等待已加入集群的节点加入控制器进程组的时间

en: Fence nodes that do not join the controller process group within this much time after joining the cluster, to allow the cluster to continue managing resources. A value of 0 means never fence pending nodes. Setting the value to 2h means fence nodes after 2 hours.
zh_CN: 如果节点加入集群后在此时间内不加入控制器进程组，Fence该节点，以便群集继续管理资源。值为0表示永远不 fence 待定节点。将值设置为2h表示2小时后 fence 待定节点。

en: Maximum time for node-to-node communication
zh_CN: 最大节点间通信时间

en: The node elected Designated Controller (DC) will consider an action failed if it does not get a response from the node executing the action within this time (after considering the action's own timeout). The "correct" value will depend on the speed and load of your network and cluster nodes.
zh_CN: 如果一个操作未在该时间内（并且考虑操作本身的超时时长）从执行该操作的节点获得响应，则会被选为指定控制器（DC）的节点认定为失败。"正确" 值将取决于速度和您的网络和集群节点的负载。

en: Maximum amount of system load that should be used by cluster nodes
zh_CN: 集群节点应该使用的最大系统负载量

en: The cluster will slow down its recovery process when the amount of system resources used (currently CPU) approaches this limit
zh_CN: 当使用的系统资源量（当前指 CPU）接近此限制时, 集群将减慢其恢复过程

en: Maximum number of jobs that can be scheduled per node (defaults to 2x cores)
zh_CN: 每个节点可以调度的最大作业数（默认为2x内核数）

en: The "correct" value will depend on the speed and load of your network and cluster nodes. If set to 0, the cluster will impose a dynamically calculated limit when any node has a high load.
zh_CN: "正确" 值将取决于速度和您的网络与集群节点的负载。如果设置为0，当任何节点具有高负载时，集群将施加一个动态计算的限制。

en: The number of live migration actions that the cluster is allowed to execute in parallel on a node (-1 means no limit)
zh_CN: 允许集群在一个节点上并行执行的实时迁移操作的数量(-1表示没有限制)

en: Maximum IPC message backlog before disconnecting a cluster daemon
zh_CN: 断开集群守护程序之前的最大IPC消息积压

en: Raise this if log has "Evicting client" messages for cluster daemon PIDs (a good value is the number of resources in the cluster multiplied by the number of nodes).
zh_CN: 如果日志中有针对集群守护程序PID的消息“Evicting client”，（则建议将值设为集群中的资源数量乘以节点数量）

en: Whether to stop resources that were removed from the configuration
zh_CN: 是否停止配置已被删除的资源

en: Whether to cancel recurring actions removed from the configuration
zh_CN: 是否取消配置已被删除的的重复操作

en: The number of scheduler inputs resulting in errors to save
zh_CN: 保存导致错误的调度程序输入的数量

en: Zero to disable, -1 to store unlimited.
zh_CN: 零表示禁用，-1表示存储不受限制。

en: The number of scheduler inputs resulting in warnings to save
zh_CN: 保存导致警告的调度程序输入的数量

en: The number of scheduler inputs without errors or warnings to save
zh_CN: 保存没有错误或警告的调度程序输入的数量

en: Requires external entities to create node attributes (named with the prefix "#health") with values "red", "yellow", or "green".
zh_CN: 需要外部实体创建具有“red”,“yellow”或“green”值的节点属性(前缀为“#health”)

en: Base health score assigned to a node
zh_CN: 分配给节点的基本健康分数

en: Only used when "node-health-strategy" is set to "progressive".
zh_CN: 仅在“node-health-strategy”设置为“progressive”时使用。

en: The score to use for a node health attribute whose value is "green"
zh_CN: 为节点健康属性值为“green”所使用的分数

en: Only used when "node-health-strategy" is set to "custom" or "progressive".
zh_CN: 仅在“node-health-strategy”设置为“custom”或“progressive”时使用。

en: The score to use for a node health attribute whose value is "yellow"
zh_CN: 为节点健康属性值为“yellow”所使用的分数

en: The score to use for a node health attribute whose value is "red"
zh_CN: 为节点健康属性值为“red”所使用的分数

en: Nodes targeted by this device
zh_CN: 此设备针对的节点

en: Enable a delay of no more than the time specified before executing fencing actions.
zh_CN: 在执行 fence 操作前启用不超过指定时间的延迟

en: Enable a delay of no more than the time specified before executing fencing actions. Pacemaker derives the overall delay by taking the value of pcmk_delay_base and adding a random delay value such that the sum is kept below this maximum.
zh_CN: 在执行 fence 操作前启用不超过指定时间的延迟. Pacemaker通过获取 pcmk_delay_base 的值并添加随机延迟值来得出总延迟, 并且确保总和不超过此最大值.

en: Enable a base delay for fencing actions and specify base delay value.
zh_CN: 为 fence 操作启用一个指定的基础延迟.

en: The maximum number of actions can be performed in parallel on this device
zh_CN: 可以在该设备上并发执行的最多操作数量

en: Display software version and exit
zh_CN: 显示软件版本信息

en: Increase debug output (may be specified multiple times)
zh_CN: 显示更多调试信息（可多次指定）

en: FORMAT
zh_CN: 格式

en: Specify file name for output (or "-" for stdout)
zh_CN: 指定输出的文件名 或指定'-' 表示标准输出

en: DEST
zh_CN: 目标

en: Output Options:
zh_CN: 输出选项

en: Show output help
zh_CN: 显示输出帮助

en: Aborting because no messages received in %d seconds
zh_CN: 中止，因为在%d秒内没有接收到消息

en: Invalid check level setting: %s
zh_CN: 无效的检查级别设置：%s

en: Resource '%s' not moved: active in %d locations (promoted in %d).
    To prevent '%s' from running on a specific location, specify a node.To prevent '%s' from being promoted at a specific location, specify a node and the --promoted option.
zh_CN: 资源'%s'未移动：在%d个位置运行（其中在%d个位置为主实例）
    若要阻止'%s'在特定位置运行，请指定一个节点。若要防止'%s'在指定位置升级，指定一个节点并使用--promoted选项

en: Resource '%s' not moved: active in %d locations.
    To prevent '%s' from running on a specific location, specify a node.
zh_CN: 资源%s未移动:在%d个位置运行
    若要防止'%s'运行在特定位置，指定一个节点

en: Could not get modified CIB: %s
zh_CN: 无法获得修改的CIB：%s

en: No cluster connection to Pacemaker Remote node %s detected
zh_CN: 未检测到至pacemaker远程节点%s的集群连接

en: Could not create executor connection
zh_CN: 无法创建到pacemaker-execd守护进程的连接

en: '%s' is not a valid agent specification
zh_CN: '%s' 是一个无效的代理

en: --resource cannot be used with --class, --agent, and --provider
zh_CN: --resource 不能与 --class, --agent, --provider一起使用

en: --class, --agent, and --provider can only be used with --validate and --force-*
zh_CN: --class, --agent和--provider只能被用于--validate和--force-*

en: stonith does not support providers
zh_CN: stonith 不支持提供者

en: %s is not a known stonith agent
zh_CN: %s 不是一个已知stonith代理

en: %s:%s:%s is not a known resource
zh_CN: %s:%s:%s 不是一个已知资源

en: Error creating output format %s: %s
zh_CN: 创建输出格式错误 %s:%s

en: --expired requires --clear or -U
zh_CN: --expired需要和--clear或-U一起使用

en: Error parsing '%s' as a name=value pair
zh_CN: '%s'解析错误，格式为name=value

en: Must supply a resource id with -r
zh_CN: 必须使用-r指定资源id

en: Must supply a node name with -N
zh_CN: 必须使用-N指定节点名称

en: Could not create CIB connection
zh_CN: 无法创建到CIB的连接

en: Could not connect to the CIB: %s
zh_CN: 不能连接到CIB：%s

en: Resource '%s' not found
zh_CN: 没有发现'%s'资源

en: Cannot operate on clone resource instance '%s'
zh_CN: 不能操作克隆资源实例'%s'

en: Node '%s' not found
zh_CN: 没有发现%s节点

en: Error connecting to the controller: %s
zh_CN: 连接到控制器错误：%s

en: You need to supply a value with the -v option
zh_CN: 需要使用-v选项提供一个值

en: You need to specify a resource type with -t
zh_CN: 需要使用-t指定资源类型

en: Unimplemented command: %d
zh_CN: 无效的命令：%d

en: Error performing operation: %s
zh_CN: 执行操作错误：%s
