Axon 参考指南
  • 介绍
  • 架构概览
    • DDD & CQRS 概念
    • 事件溯源
    • 事件驱动的微服务
  • Axon Server
  • 发行说明
    • Axon Framework
      • Major Releases
      • Minor Releases
    • Axon Server
      • Major Releases
      • Minor Releases Standard Edition
      • Minor Releases Enterprise Edition
    • Axon Framework Extensions
      • AMQP
        • Major Releases
      • CDI
        • Major Releases
      • JGroups
        • Major Releases
      • Kafka
        • Major Releases
        • Minor Releases
      • Kotlin
        • Experimental Releases
      • Mongo
        • Major Releases
        • Minor Releases
      • Reactor
        • Major Releases
        • Minor Releases
      • Spring Cloud
        • Major Releases
        • Minor Releases
      • Tracing
        • Major Releases
        • Minor Releases
  • Getting Started
    • 快速开始
  • Axon Framework
    • 介绍
    • 消息传递概念
      • 消息剖析
      • 消息关联
      • 消息拦截
      • 支持带注解的处理程序
      • 异常处理
      • 工作单元
    • 命令
      • 建模
        • 聚合
        • 多实体聚合
        • 聚合状态存储
        • 从另一个聚合创建聚合
        • 聚合多态性
        • 解决冲突
      • 命令调度器
      • 命令处理程序
      • 基础设施
      • 配置
    • 事件
      • 事件调度器
      • 事件处理程序
      • 事件处理器
        • 订阅事件处理器
        • 流式事件处理器
      • 事件总线和事件存储
      • 事件版本控制
    • 查询
      • 查询处理
      • 查询调度器
      • 查询处理程序
      • 实现
      • 配置
    • 长时处理过程(Sagas)
      • 实现
      • 关联
      • 基础设施
    • Deadlines
      • Deadline Managers
      • Event Schedulers
    • 测试
      • 命令 / 事件
      • 长时处理过程(Sagas)
    • 序列化
    • 调整
      • 事件快照
      • 事件处理
      • 命令处理
    • 监控和指标
    • Spring Boot 集成
    • 模块
  • Axon Server
    • 介绍
    • 安装
      • 本地安装
        • Axon Server SE
        • Axon Server EE
      • Docker / K8s
        • Axon Server SE
        • Axon Server EE
    • 管理
      • 配置
        • System Properties
        • Command Line Interface
        • REST API
        • GRPC API
      • Monitoring
        • Actuator Endpoints
        • gRPC Metrics
        • Heartbeat Monitoring
      • Clusters
      • Replication Groups
      • Multi-Context
      • Tagging
      • Backup and Messaging-only Nodes
      • Backups
      • Recovery
      • Plugins
      • Error Codes
    • 安全
      • SSL
      • 访问控制
      • 访问控制 - 标准版
      • 访问控制 - 企业版
      • 访问控制 - 客户端应用程序
      • 访问控制 - 命令行
      • 访问控制 - REST API
      • 访问控制 - LDAP
      • 访问控制 - OAuth 2.0
    • 性能
      • 事件段
      • 流量控制
    • 迁移
      • Standard to Enterprise Edition
      • Non-Axon Server to Axon Server
  • Extensions
    • Spring AMQP
    • JGroups
    • Kafka
    • Kotlin
    • Mongo
    • Reactor
      • Reactor Gateways
    • Spring Cloud
    • Tracing
  • Appendices
    • A. RDBMS Tuning
    • B. Message Handler Tuning
      • 参数解析器
      • 处理程序增强
    • C. 元数据注解
    • D. 标识符生成
    • E. Axon Server Query Language
由 GitBook 提供支持
在本页
  1. Axon Server
  2. 管理

Recovery

Note

This feature is only available in Axon Server Enterprise version 4.3 onwards.

In case of a major network change, when the host names of all Axon Server nodes have changed, or when you want to move an Axon Server cluster to a new environment, you will have to start Axon Server in recovery mode. This is needed as Axon Server maintains the information about the nodes in the cluster in its control database, and this needs to be updated on all nodes.

Axon Server will start in recovery mode when it finds a file called recovery.json in its startup directory, or in a location defined by the property axoniq.axonserver.recoveryfile. The recovery file must contain a JSON array of the nodes in the cluster with their host names and port numbers, for example:

[
  {
   "name": "axonserver-1",
   "hostName": "axonserver-1",
   "internalHostName": "axonserver-1.internal",
   "grpcInternalPort": 8224,
   "httpPort": 8024,
   "grpcPort": 8124
  },
  {
   "name": "axonserver-2",
   "hostName": "axonserver-2",
   "internalHostName": "axonserver-2.internal",
   "grpcInternalPort": 8224,
   "httpPort": 8024,
   "grpcPort": 8124
  },
  {
   "name": "axonserver-3",
   "hostName": "axonserver-3",
   "internalHostName": "axonserver-3.internal",
   "grpcInternalPort": 8224,
   "httpPort": 8024,
   "grpcPort": 8124
  }
]

The hostName defines the hostname that clients will use to connect to the Axon Server node. The internalHostName contains the name one Axon Server uses to connect to the other. Any elements that have not changed (except for the name) may be omitted, so if you want to use the same port numbers you can omit the grpcInternalPort, httpPort and grpcPort elements.

In the sample above, the node names for the Axon Server nodes will remain the same as they were before. As Axon Server derives its node name from the host name, when not explicitly set in properties, this may cause an issue when host names are changed. To change the node names for Axon Server nodes, add an oldName element in the JSON file.

[
  {
   "name": "new-axonserver-1",
   "oldName": "axonserver-1",
   "hostName": "new-axonserver-1",
   "internalHostName":" new-axonserver-1.internal"
  },
  {
   "name": "new-axonserver-2",
   "oldName": "axonserver-2",
   "hostName": "new-axonserver-2",
   "internalHostName": "new-axonserver-2.internal"
  }, 
  {
   "name": "new-axonserver-3",
   "oldName": "axonserver-3",
   "hostName": "new-axonserver-3",
   "internalHostName": "new-axonserver-3.internal"
  }
]
上一页Backups下一页Plugins

最后更新于2年前