Replication

数据库复制可确保冗余、备份和自动故障转移。 复制发生在名为副本集的服务器群组中。

Replica Set Use and Operation

Consider these higher level introductions to replica sets:

• Replica Set Fundamental Concepts
• Replica Set Architectures and Deployment Patterns
• Replica Set Considerations and Behaviors for Applications and Development
  • 写入关注
  • 读取首选项
• Replica Set Internals and Behaviors

The following document describes master-slave replication, which is deprecated. Use replica sets instead of master-slave in all new deployments.

• Master Slave Replication

For documentation of MongoDB’s operational segregation capabilities for replica set deployments see the Data Center Awareness

Replica Set Tutorials and Procedures

The following tutorials describe a number of common replica set maintenance and operational practices in greater detail.

• 副本集管理
  • 部署副本集
  • Convert a Standalone to a Replica Set
  • 向副本集添加成员
  • Remove Members from Replica Set
  • Replace a Replica Set Member
  • Adjust Priority for Replica Set Member
  • Resync a Member of a Replica Set
  • 部署地理分布式副本集
  • 更改 Oplog 的大小
  • 强制成员成为主成员
  • Manage Chained Replication
  • 在副本集中更改主机名
  • Troubleshoot Replica Sets
  • Add an Arbiter to Replica Set
  • 将次成员转换为仲裁程序
  • Configure a Delayed Replica Set Member
  • Configure a Replica Set Member as Hidden
  • Configure a Non-Voting Replica Set Member
  • Prevent Replica Set Member from Becoming Primary
  • Configure a Secondary’s Sync Target
  • Configure Replica Set Tag Sets
  • 重新配置包含不可用成员的副本集

Replica Set Reference Material

Additionally, consider the following reference material for replica sets.

• 副本集设置
• Replica Set Commands
• Replica Set Features and Version Compatibility

另见

/reference/command/replSetGetStatus and db.getReplicationInfo().

• <   Search String Content for Text
• Replica Set Fundamental Concepts  >