forked from docs/doc-exports
Wang , Deng Ke
519944c837
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: Wang , Deng Ke <wangdengke2@huawei.com> Co-committed-by: Wang , Deng Ke <wangdengke2@huawei.com>
19 lines
2.9 KiB
HTML
19 lines
2.9 KiB
HTML
<a name="dds_01_0012"></a><a name="dds_01_0012"></a>
|
|
|
|
<h1 class="topictitle1">Replica Set Architecture</h1>
|
|
<div id="body1495008759160"><p id="dds_01_0012__p7418203421717">A replica set consists of a set of mongod processes and provides a collection of data nodes to ensure data redundancy and reliability.</p>
|
|
<div class="note" id="dds_01_0012__note384375010261"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="dds_01_0012__p188447506264">For details about the mongod process, visit <a href="https://docs.mongodb.com/v3.2/tutorial/manage-mongodb-processes/index.html" target="_blank" rel="noopener noreferrer">https://docs.mongodb.com/v3.2/tutorial/manage-mongodb-processes/index.html</a>.</p>
|
|
</div></div>
|
|
<p id="dds_01_0012__p4922292317836">A replica set consists of three nodes: primary, secondary, and hidden. The three-node architecture is automatically set up, and the three nodes synchronize data with each other automatically to ensure data reliability.</p>
|
|
<ul id="dds_01_0012__ul7572160172233"><li id="dds_01_0012__li1040581172233">The primary node is used to read and write requests.</li><li id="dds_01_0012__li9365232172233">The secondary node is used to read requests.</li><li id="dds_01_0012__li17178226172233">The hidden node is used to back up data.</li></ul>
|
|
<p id="dds_01_0012__p440813339588">You can directly perform operations on the primary and secondary nodes. If a primary node goes down or becomes faulty, a secondary node is automatically assigned to the primary role and continues normal operation. If a secondary node is unavailable, a hidden node will take the role of the secondary to ensure high availability. The following figure shows the replica set architecture.</p>
|
|
<div class="fignone" id="dds_01_0012__fig4417616382"><span class="figcap"><b>Figure 1 </b>Replica set architecture</span><br><span><img id="dds_01_0012__image144172161811" src="en-us_image_0284275085.png"></span></div>
|
|
<ul id="dds_01_0012__ul63108919111140"><li id="dds_01_0012__li31109359111140">Supports multiple management and control tasks, such as creating instances, changing configurations, and backing up instances. The system flexibly controls and tracks tasks, and manages exceptions based on the operations delivered by users.</li><li id="dds_01_0012__li11548782111140">Collects performance monitoring information about DB instances, including basic metrics, storage space, access requests, and the number of operations.</li><li id="dds_01_0012__li36830180111140">Collects slow query logs and access control logs, recording DB instance running status.</li><li id="dds_01_0012__li63036170111140">Backs up DB instance data and uploads it to OBS buckets. Currently, DDS supports automated and manual backup. Automated backups are kept for seven days by default.</li></ul>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dds_01_0021.html">System Architecture</a></div>
|
|
</div>
|
|
</div>
|
|
|