dds_umn_20240415
Reviewed-by: Wagner, Fabian <fabian.wagner@t-systems.com> Co-authored-by: Ru, Li Yi <liyiru7@huawei.com> Co-committed-by: Ru, Li Yi <liyiru7@huawei.com>
@ -61,7 +61,7 @@
|
||||
"node_id":"dds_01_0011.xml",
|
||||
"product_code":"dds",
|
||||
"code":"4",
|
||||
"des":"Each DDS cluster is an independent document database. A sharded cluster consists of a config node, and multiple mongos and shard nodes.Data read and write requests are fo",
|
||||
"des":"Each DDS cluster is an independent document database. A sharded cluster consists of a config node, and multiple dds mongos and shard nodes.Data read and write requests ar",
|
||||
"doc_type":"usermanual",
|
||||
"kw":"Cluster,System Architecture,User Guide",
|
||||
"search_title":"",
|
||||
@ -133,7 +133,7 @@
|
||||
"node_id":"dds_01_0002.xml",
|
||||
"product_code":"dds",
|
||||
"code":"8",
|
||||
"des":"Each DDS cluster consists of a config node, and multiple mongos and shard nodes. The following diagram shows the node relationships.A mongos is a router for reading and w",
|
||||
"des":"Each DDS cluster consists of a config node, and multiple dds mongos and shard nodes. The following diagram shows the node relationships.A dds mongos is a router for readi",
|
||||
"doc_type":"usermanual",
|
||||
"kw":"Cluster,Basic Concepts,User Guide",
|
||||
"search_title":"",
|
||||
@ -493,7 +493,7 @@
|
||||
"node_id":"dds_02_0022.xml",
|
||||
"product_code":"dds",
|
||||
"code":"28",
|
||||
"des":"This section explains how to add a security group rule to control access to and from the DDS DB instances associated with a security group.The default security group rule",
|
||||
"des":"This section explains how to add a security group rule to control access to and from the DDS DB instances associated with a security group.DDS is compatible with MongoDB.",
|
||||
"doc_type":"usermanual",
|
||||
"kw":"DDS DB instances,Setting a Security Group,Connecting to a Cluster Instance Over Private Networks,Use",
|
||||
"search_title":"",
|
||||
@ -601,7 +601,7 @@
|
||||
"node_id":"dds_02_0019.xml",
|
||||
"product_code":"dds",
|
||||
"code":"34",
|
||||
"des":"This section explains how to add a security group rule to control access to and from the DDS DB instances associated with a security group.The default security group rule",
|
||||
"des":"This section explains how to add a security group rule to control access to and from the DDS DB instances associated with a security group.DDS is compatible with MongoDB.",
|
||||
"doc_type":"usermanual",
|
||||
"kw":"DDS DB instances,Setting a Security Group,Connecting to a Cluster Instance Over Public Networks,User",
|
||||
"search_title":"",
|
||||
@ -619,7 +619,7 @@
|
||||
"node_id":"dds_02_0006.xml",
|
||||
"product_code":"dds",
|
||||
"code":"35",
|
||||
"des":"This section describes how to connect to a cluster instance using the MongoDB client and Robo 3T over public networks.The MongoDB client and Robo 3T can connect to a DB i",
|
||||
"des":"This section describes how to connect to a cluster instance using the MongoDB client and Robo 3T over public networks.DDS is compatible with MongoDB.The MongoDB client an",
|
||||
"doc_type":"usermanual",
|
||||
"kw":"DB instance,Connecting to a Cluster Instance Over Public Networks,Connecting to a Cluster Instance O",
|
||||
"search_title":"",
|
||||
@ -745,7 +745,7 @@
|
||||
"node_id":"en-us_topic_0105284966.xml",
|
||||
"product_code":"dds",
|
||||
"code":"42",
|
||||
"des":"This section describes how to connect to a replica set instance using the MongoDB client over private networks.You can directly perform operations on the primary and seco",
|
||||
"des":"This section describes how to connect to a replica set instance using the MongoDB client over private networks.DDS is compatible with MongoDB.You can directly perform ope",
|
||||
"doc_type":"usermanual",
|
||||
"kw":"DDS DB instance,DDS DB instance,Connecting to a Replica Set Instance Over Private Networks,Connectin",
|
||||
"search_title":"",
|
||||
@ -853,7 +853,7 @@
|
||||
"node_id":"dds_02_0047.xml",
|
||||
"product_code":"dds",
|
||||
"code":"48",
|
||||
"des":"This section describes how to connect to a replica set instance using the MongoDB client and Robo 3T over public networks.You can directly perform operations on the prima",
|
||||
"des":"This section describes how to connect to a replica set instance using the MongoDB client and Robo 3T over public networks.DDS is compatible with MongoDB.You can directly ",
|
||||
"doc_type":"usermanual",
|
||||
"kw":"DDS DB instance,Connecting to a Replica Set Instance Over Public Networks,Connecting to a Replica Se",
|
||||
"search_title":"",
|
||||
@ -979,7 +979,7 @@
|
||||
"node_id":"dds_02_0028.xml",
|
||||
"product_code":"dds",
|
||||
"code":"55",
|
||||
"des":"This section describes how to connect to a single-node instance using the MongoDB client over private networks.The MongoDB client can connect to a DB instance with an une",
|
||||
"des":"This section describes how to connect to a single-node instance using the MongoDB client over private networks.DDS is compatible with MongoDB.The MongoDB client can conne",
|
||||
"doc_type":"usermanual",
|
||||
"kw":"DDS DB instance,DDS DB instance,Connecting to a Single Node Instance Over Private Networks,Connectin",
|
||||
"search_title":"",
|
||||
@ -1087,7 +1087,7 @@
|
||||
"node_id":"dds_02_0048.xml",
|
||||
"product_code":"dds",
|
||||
"code":"61",
|
||||
"des":"This section describes how to connect to a single-node instance using the MongoDB client and Robo 3T over public networks.The MongoDB client and Robo 3T can connect to a ",
|
||||
"des":"This section describes how to connect to a single-node instance using the MongoDB client and Robo 3T over public networks.DDS is compatible with MongoDB.The MongoDB clien",
|
||||
"doc_type":"usermanual",
|
||||
"kw":"DDS DB instance,Connecting to a Single Node Instance Over Public Networks,Connecting to a Single Nod",
|
||||
"search_title":"",
|
||||
@ -1219,7 +1219,7 @@
|
||||
"node_id":"dds_02_0100.xml",
|
||||
"product_code":"dds",
|
||||
"code":"68",
|
||||
"des":"A cluster instance of Community Edition consists of mongos, shard, and config nodes. When your services need to read and write data from and into databases, connect to th",
|
||||
"des":"A cluster instance of Community Edition consists of dds mongos, shard, and config nodes. When your services need to read and write data from and into databases, connect t",
|
||||
"doc_type":"usermanual",
|
||||
"kw":"Enabling IP Addresses of shard and config Nodes,Connection Management,User Guide",
|
||||
"search_title":"",
|
||||
@ -1327,7 +1327,7 @@
|
||||
"node_id":"dds_03_0052.xml",
|
||||
"product_code":"dds",
|
||||
"code":"74",
|
||||
"des":"DDS is accessible through an EIP in a public network or an ECS in a private network.MongoDB can export data from a database into a JSON file. Such a JSON file can then be",
|
||||
"des":"DDS is accessible through an EIP in a public network or an ECS in a private network.DDS is compatible with MongoDB.MongoDB can export data from a database into a JSON fil",
|
||||
"doc_type":"usermanual",
|
||||
"kw":"Migrating Data,User Guide",
|
||||
"search_title":"",
|
||||
@ -2047,7 +2047,7 @@
|
||||
"node_id":"dds_03_0040.xml",
|
||||
"product_code":"dds",
|
||||
"code":"114",
|
||||
"des":"This section describes how to view the progress and result of asynchronous tasks on the Task Center page.Creating a snapshot backupCreating a cluster InstanceCreating a r",
|
||||
"des":"This section describes how to view the progress and result of asynchronous tasks on the Task Center page.Creating a cluster InstanceCreating a replica set instanceCreatin",
|
||||
"doc_type":"usermanual",
|
||||
"kw":"Task Center,User Guide",
|
||||
"search_title":"",
|
||||
|
@ -27,7 +27,7 @@
|
||||
"code":"3"
|
||||
},
|
||||
{
|
||||
"desc":"Each DDS cluster is an independent document database. A sharded cluster consists of a config node, and multiple mongos and shard nodes.Data read and write requests are fo",
|
||||
"desc":"Each DDS cluster is an independent document database. A sharded cluster consists of a config node, and multiple dds mongos and shard nodes.Data read and write requests ar",
|
||||
"product_code":"dds",
|
||||
"title":"Cluster",
|
||||
"uri":"dds_01_0011.html",
|
||||
@ -63,7 +63,7 @@
|
||||
"code":"7"
|
||||
},
|
||||
{
|
||||
"desc":"Each DDS cluster consists of a config node, and multiple mongos and shard nodes. The following diagram shows the node relationships.A mongos is a router for reading and w",
|
||||
"desc":"Each DDS cluster consists of a config node, and multiple dds mongos and shard nodes. The following diagram shows the node relationships.A dds mongos is a router for readi",
|
||||
"product_code":"dds",
|
||||
"title":"Cluster",
|
||||
"uri":"dds_01_0002.html",
|
||||
@ -243,7 +243,7 @@
|
||||
"code":"27"
|
||||
},
|
||||
{
|
||||
"desc":"This section explains how to add a security group rule to control access to and from the DDS DB instances associated with a security group.The default security group rule",
|
||||
"desc":"This section explains how to add a security group rule to control access to and from the DDS DB instances associated with a security group.DDS is compatible with MongoDB.",
|
||||
"product_code":"dds",
|
||||
"title":"Setting a Security Group",
|
||||
"uri":"dds_02_0022.html",
|
||||
@ -297,7 +297,7 @@
|
||||
"code":"33"
|
||||
},
|
||||
{
|
||||
"desc":"This section explains how to add a security group rule to control access to and from the DDS DB instances associated with a security group.The default security group rule",
|
||||
"desc":"This section explains how to add a security group rule to control access to and from the DDS DB instances associated with a security group.DDS is compatible with MongoDB.",
|
||||
"product_code":"dds",
|
||||
"title":"Setting a Security Group",
|
||||
"uri":"dds_02_0019.html",
|
||||
@ -306,7 +306,7 @@
|
||||
"code":"34"
|
||||
},
|
||||
{
|
||||
"desc":"This section describes how to connect to a cluster instance using the MongoDB client and Robo 3T over public networks.The MongoDB client and Robo 3T can connect to a DB i",
|
||||
"desc":"This section describes how to connect to a cluster instance using the MongoDB client and Robo 3T over public networks.DDS is compatible with MongoDB.The MongoDB client an",
|
||||
"product_code":"dds",
|
||||
"title":"Connecting to a Cluster Instance Over Public Networks",
|
||||
"uri":"dds_02_0006.html",
|
||||
@ -369,7 +369,7 @@
|
||||
"code":"41"
|
||||
},
|
||||
{
|
||||
"desc":"This section describes how to connect to a replica set instance using the MongoDB client over private networks.You can directly perform operations on the primary and seco",
|
||||
"desc":"This section describes how to connect to a replica set instance using the MongoDB client over private networks.DDS is compatible with MongoDB.You can directly perform ope",
|
||||
"product_code":"dds",
|
||||
"title":"Connecting to a Replica Set Instance Over Private Networks",
|
||||
"uri":"en-us_topic_0105284966.html",
|
||||
@ -423,7 +423,7 @@
|
||||
"code":"47"
|
||||
},
|
||||
{
|
||||
"desc":"This section describes how to connect to a replica set instance using the MongoDB client and Robo 3T over public networks.You can directly perform operations on the prima",
|
||||
"desc":"This section describes how to connect to a replica set instance using the MongoDB client and Robo 3T over public networks.DDS is compatible with MongoDB.You can directly ",
|
||||
"product_code":"dds",
|
||||
"title":"Connecting to a Replica Set Instance Over Public Networks",
|
||||
"uri":"dds_02_0047.html",
|
||||
@ -486,7 +486,7 @@
|
||||
"code":"54"
|
||||
},
|
||||
{
|
||||
"desc":"This section describes how to connect to a single-node instance using the MongoDB client over private networks.The MongoDB client can connect to a DB instance with an une",
|
||||
"desc":"This section describes how to connect to a single-node instance using the MongoDB client over private networks.DDS is compatible with MongoDB.The MongoDB client can conne",
|
||||
"product_code":"dds",
|
||||
"title":"Connecting to a Single Node Instance Over Private Networks",
|
||||
"uri":"dds_02_0028.html",
|
||||
@ -540,7 +540,7 @@
|
||||
"code":"60"
|
||||
},
|
||||
{
|
||||
"desc":"This section describes how to connect to a single-node instance using the MongoDB client and Robo 3T over public networks.The MongoDB client and Robo 3T can connect to a ",
|
||||
"desc":"This section describes how to connect to a single-node instance using the MongoDB client and Robo 3T over public networks.DDS is compatible with MongoDB.The MongoDB clien",
|
||||
"product_code":"dds",
|
||||
"title":"Connecting to a Single Node Instance Over Public Networks",
|
||||
"uri":"dds_02_0048.html",
|
||||
@ -603,7 +603,7 @@
|
||||
"code":"67"
|
||||
},
|
||||
{
|
||||
"desc":"A cluster instance of Community Edition consists of mongos, shard, and config nodes. When your services need to read and write data from and into databases, connect to th",
|
||||
"desc":"A cluster instance of Community Edition consists of dds mongos, shard, and config nodes. When your services need to read and write data from and into databases, connect t",
|
||||
"product_code":"dds",
|
||||
"title":"Enabling IP Addresses of shard and config Nodes",
|
||||
"uri":"dds_02_0100.html",
|
||||
@ -657,7 +657,7 @@
|
||||
"code":"73"
|
||||
},
|
||||
{
|
||||
"desc":"DDS is accessible through an EIP in a public network or an ECS in a private network.MongoDB can export data from a database into a JSON file. Such a JSON file can then be",
|
||||
"desc":"DDS is accessible through an EIP in a public network or an ECS in a private network.DDS is compatible with MongoDB.MongoDB can export data from a database into a JSON fil",
|
||||
"product_code":"dds",
|
||||
"title":"Migrating Data",
|
||||
"uri":"dds_03_0052.html",
|
||||
@ -1017,7 +1017,7 @@
|
||||
"code":"113"
|
||||
},
|
||||
{
|
||||
"desc":"This section describes how to view the progress and result of asynchronous tasks on the Task Center page.Creating a snapshot backupCreating a cluster InstanceCreating a r",
|
||||
"desc":"This section describes how to view the progress and result of asynchronous tasks on the Task Center page.Creating a cluster InstanceCreating a replica set instanceCreatin",
|
||||
"product_code":"dds",
|
||||
"title":"Task Center",
|
||||
"uri":"dds_03_0040.html",
|
||||
|
@ -1,10 +1,10 @@
|
||||
<a name="dds_01_0002"></a><a name="dds_01_0002"></a>
|
||||
|
||||
<h1 class="topictitle1">Cluster</h1>
|
||||
<div id="body1529654902838"><p id="dds_01_0002__p03931746111514">Each DDS cluster consists of a config node, and multiple mongos and shard nodes. The following diagram shows the node relationships.</p>
|
||||
<div class="fignone" id="dds_01_0002__fig20857165904711"><span class="figcap"><b>Figure 1 </b>Diagram of node relationships</span><br><span><img id="dds_01_0002__image48576592473" src="en-us_image_0000001096133880.png"></span></div>
|
||||
<div class="section" id="dds_01_0002__section2471635113117"><h4 class="sectiontitle">mongos</h4><p id="dds_01_0002__p5397278143035">A mongos is a router for reading and writing data, providing a unified interface for accessing DB instances.</p>
|
||||
<ul id="dds_01_0002__ul7747113611462"><li id="dds_01_0002__li1782033319534">Each DB instance has 2 to 32 mongos. You can specify the quantity.</li><li id="dds_01_0002__li474733612462">A mongos reads configuration settings from configs and allocates read and write requests to shards. You can connect to a mongos directly.</li></ul>
|
||||
<div id="body1529654902838"><p id="dds_01_0002__p03931746111514">Each DDS cluster consists of a config node, and multiple dds mongos and shard nodes. The following diagram shows the node relationships.</p>
|
||||
<div class="fignone" id="dds_01_0002__fig921302217450"><span class="figcap"><b>Figure 1 </b>Diagram of node relationships</span><br><span><img id="dds_01_0002__image1921411225458" src="en-us_image_0000001845343652.png"></span></div>
|
||||
<div class="section" id="dds_01_0002__section2471635113117"><h4 class="sectiontitle">dds mongos</h4><p id="dds_01_0002__p5397278143035">A dds mongos is a router for reading and writing data, providing a unified interface for accessing DB instances.</p>
|
||||
<ul id="dds_01_0002__ul7747113611462"><li id="dds_01_0002__li1782033319534">Each DB instance has 2 to 32 dds mongos. You can specify the quantity.</li><li id="dds_01_0002__li474733612462">A dds mongos reads configuration settings from configs and allocates read and write requests to shards. You can connect to a dds mongos directly.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="dds_01_0002__section109912514314"><h4 class="sectiontitle">config</h4><p id="dds_01_0002__p49633946153220">A config stores configuration settings for DB instances and consists of one replica set.</p>
|
||||
<ul id="dds_01_0002__ul17872294911"><li id="dds_01_0002__li158713234917">The availability of a config is the prerequisite to deploying a DB instance or modifying the instance information.</li><li id="dds_01_0002__li787112154919">You cannot connect to a config directly.</li></ul>
|
||||
|
@ -2,14 +2,14 @@
|
||||
|
||||
<h1 class="topictitle1">Functions and Features</h1>
|
||||
<div id="body1522807549935"><div class="section" id="dds_01_0006__section735914516588"><h4 class="sectiontitle">Three Architectures</h4><p id="dds_01_0006__p32189385914">DDS supports three deployment architectures: cluster, replica set, and single node. They meet requirements of different service scenarios.</p>
|
||||
<ul id="dds_01_0006__ul122452013116"><li id="dds_01_0006__li2245400115">Cluster<p id="dds_01_0006__p105491324012"><a name="dds_01_0006__li2245400115"></a><a name="li2245400115"></a>A cluster consists of three types of nodes: mongos, shard, and config. You can select the number and configuration of mongos and shard nodes to create cluster instances with different levels of service performance.</p>
|
||||
<ul id="dds_01_0006__ul122452013116"><li id="dds_01_0006__li2245400115">Cluster<p id="dds_01_0006__p105491324012"><a name="dds_01_0006__li2245400115"></a><a name="li2245400115"></a>A cluster consists of three types of nodes: dds mongos, shard, and config. You can select the number and configuration of dds mongos and shard nodes to create cluster instances with different levels of service performance.</p>
|
||||
</li></ul>
|
||||
<ul id="dds_01_0006__ul181191932112"><li id="dds_01_0006__li81201439119">Replica set<p id="dds_01_0006__p134215451306"><a name="dds_01_0006__li81201439119"></a><a name="li81201439119"></a>DDS automatically builds the replica set architecture, and you can directly operate the primary and secondary nodes. DDS provides you with advanced functions such as high availability (HA) and disaster recovery (DR) switchover, and is invisible to applications.</p>
|
||||
</li></ul>
|
||||
<ul id="dds_01_0006__ul225212511116"><li id="dds_01_0006__li625235312">Single node<p id="dds_01_0006__p11554145612014"><a name="dds_01_0006__li625235312"></a><a name="li625235312"></a>A database that is deployed on a single VM does not have the HA feature. To ensure data consistency during full backup, tables are locked to prevent data from being changed. The single-node architecture features low costs and is a preferred option for R&D and testing environment, learning and training environment, and internal systems of small-sized enterprises.</p>
|
||||
</li></ul>
|
||||
</div>
|
||||
<div class="section" id="dds_01_0006__section43893088141312"><h4 class="sectiontitle">Elastic Scaling</h4><p id="dds_01_0006__p6512111309">With the development of your services, you can change CPU and memory specifications of instances, expand storage space, and add mongos and shard nodes of cluster DB instances in real time. You are advised to perform the change during off-peak hours to avoid the impact of changes on your services.</p>
|
||||
<div class="section" id="dds_01_0006__section43893088141312"><h4 class="sectiontitle">Elastic Scaling</h4><p id="dds_01_0006__p6512111309">With the development of your services, you can change CPU and memory specifications of instances, expand storage space, and add dds mongos and shard nodes of cluster DB instances in real time. You are advised to perform the change during off-peak hours to avoid the impact of changes on your services.</p>
|
||||
</div>
|
||||
<div class="section" id="dds_01_0006__section1193519218375"><h4 class="sectiontitle">Key Features</h4>
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="dds_01_0006__table635792473717" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Key feature description</caption><thead align="left"><tr id="dds_01_0006__row19470192463717"><th align="left" class="cellrowborder" valign="top" width="23%" id="mcps1.3.3.2.2.3.1.1"><p id="dds_01_0006__p164701624173719">Features</p>
|
||||
|
@ -1,10 +1,10 @@
|
||||
<a name="dds_01_0011"></a><a name="dds_01_0011"></a>
|
||||
|
||||
<h1 class="topictitle1">Cluster</h1>
|
||||
<div id="body50525752"><p id="dds_01_0011__p16715644165033">Each DDS cluster is an independent document database. A sharded cluster consists of a config node, and multiple mongos and shard nodes.</p>
|
||||
<p id="dds_01_0011__p4243244165318">Data read and write requests are forwarded by the mongos nodes, which read configuration settings from config, and then allocate the read and write requests to the shards, making it easy to cope with high concurrency scenarios. In addition, each config node, along with the shards in its cluster, is replicated in triplicate to ensure high availability. The following figure shows the DDS cluster architecture.</p>
|
||||
<div class="fignone" id="dds_01_0011__fig1930710481542"><span class="figcap"><b>Figure 1 </b>Cluster architecture</span><br><span><img id="dds_01_0011__image1530774814410" src="en-us_image_0000001143133849.png"></span></div>
|
||||
<ul id="dds_01_0011__ul3754275165450"><li id="dds_01_0011__li18981955141813">A driver handles all interactions between your application and the database in a language appropriate to the application. For details, see <a href="https://docs.mongodb.com/drivers/" target="_blank" rel="noopener noreferrer">official documents</a>.</li><li id="dds_01_0011__li18678526165450">Each mongos is a single node, but you can provision multiple mongos nodes for load balancing and failovers. A single cluster can contain 2 to 32 mongos nodes.</li><li id="dds_01_0011__li9025895165450">Each shard is a three-node replica set, and each cluster can contain 2 to 32 shards.</li><li id="dds_01_0011__li58596018165450">A config node is a necessary part of a cluster instance, and is also deployed as a replica set. The config node stores instance configuration data.</li><li id="dds_01_0011__li37457807165450">The number of mongos and shard nodes can be increased from the management console. You do not need to use native commands.</li><li id="dds_01_0011__li5795164065810">You can <a href="dds_02_0100.html">enable IP addresses of shards and the config node</a> to directly access the shards and the config node.</li><li id="dds_01_0011__li17418689165450">A three-node replica set cannot be directly upgraded to a cluster.</li></ul>
|
||||
<div id="body50525752"><p id="dds_01_0011__p16715644165033">Each DDS cluster is an independent document database. A sharded cluster consists of a config node, and multiple dds mongos and shard nodes.</p>
|
||||
<p id="dds_01_0011__p4243244165318">Data read and write requests are forwarded by the dds mongos nodes, which read configuration settings from config, and then allocate the read and write requests to the shards, making it easy to cope with high concurrency scenarios. In addition, each config node, along with the shards in its cluster, is replicated in triplicate to ensure high availability. The following figure shows the DDS cluster architecture.</p>
|
||||
<div class="fignone" id="dds_01_0011__fig9404173712409"><span class="figcap"><b>Figure 1 </b>Cluster architecture</span><br><span><img id="dds_01_0011__image1540553794015" src="en-us_image_0000001891581965.png"></span></div>
|
||||
<ul id="dds_01_0011__ul3754275165450"><li id="dds_01_0011__li18981955141813">A driver handles all interactions between your application and the database in a language appropriate to the application. For details, see <a href="https://docs.mongodb.com/drivers/" target="_blank" rel="noopener noreferrer">official documents</a>.</li><li id="dds_01_0011__li18678526165450">Each dds mongos is a single node, but you can provision multiple dds mongos nodes for load balancing and failovers. A single cluster can contain 2 to 32 dds mongos nodes.</li><li id="dds_01_0011__li9025895165450">Each shard is a three-node replica set, and each cluster can contain 2 to 32 shards.</li><li id="dds_01_0011__li58596018165450">A config node is a necessary part of a cluster instance, and is also deployed as a replica set. The config node stores instance configuration data.</li><li id="dds_01_0011__li37457807165450">The number of dds mongos and shard nodes can be increased from the management console. You do not need to use native commands.</li><li id="dds_01_0011__li5795164065810">You can <a href="dds_02_0100.html">enable IP addresses of shards and the config node</a> to directly access the shards and the config node.</li><li id="dds_01_0011__li17418689165450">A three-node replica set cannot be directly upgraded to a cluster.</li></ul>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
|
@ -6,7 +6,7 @@
|
||||
<p id="dds_01_0015__p1487912434411">Advantages:</p>
|
||||
<ul id="dds_01_0015__ul03831011184419"><li id="dds_01_0015__li103831511164419">Supports embedded documents that eliminate the need to use joins to reduce application development complexity. Flexible schemas also facilitate rapid development and iteration.</li><li id="dds_01_0015__li1384171124412">Sharded clusters provide enough capacity to store data into the TB range.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="dds_01_0015__section1665833194319"><h4 class="sectiontitle">IoT</h4><p id="dds_01_0015__p954711193331">DDS is compatible with MongoDB and provides the high-performance and asynchronous data write function. In certain scenarios, DDS can process data in the memory database. In addition, cluster instances can dynamically add the number of mongos and shard nodes or upgrade specifications. The performance and storage space can be quickly expanded, making cluster instances suitable for IoT scenarios with high concurrent writes.</p>
|
||||
<div class="section" id="dds_01_0015__section1665833194319"><h4 class="sectiontitle">IoT</h4><p id="dds_01_0015__p954711193331">DDS is compatible with MongoDB and provides the high-performance and asynchronous data write function. In certain scenarios, DDS can process data in the memory database. In addition, cluster instances can dynamically add the number of dds mongos and shard nodes or upgrade specifications. The performance and storage space can be quickly expanded, making cluster instances suitable for IoT scenarios with high concurrent writes.</p>
|
||||
<p id="dds_01_0015__p11547131913331">Intelligent IoT terminals need to collect various types of data, store device logs, and analyze information in multiple dimensions. In recent years, IoT services have grown rapidly, with huge volumes of data and increasing access traffic that require horizontal expansion capabilities for data storage.</p>
|
||||
<p id="dds_01_0015__p16547131910333">DDS provides the secondary index to meet dynamic query requirements and uses the MapReduce aggregation framework that is compatible with MongoDB to analyze data from multiple dimensions.</p>
|
||||
<p id="dds_01_0015__p16291153516386">Advantages:</p>
|
||||
|
@ -44,7 +44,7 @@
|
||||
</tr>
|
||||
<tr id="dds_01_0022__row791814564293"><td class="cellrowborder" valign="top" width="27.26%" headers="mcps1.3.2.2.3.1.1 "><p id="dds_01_0022__p0919056182920">Nodes</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="72.74000000000001%" headers="mcps1.3.2.2.3.1.2 "><p id="dds_01_0022__p291975622911">Mongos and shard nodes that are successfully added cannot be deleted.</p>
|
||||
<td class="cellrowborder" valign="top" width="72.74000000000001%" headers="mcps1.3.2.2.3.1.2 "><p id="dds_01_0022__p291975622911">dds mongos and shard nodes that are successfully added cannot be deleted.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="dds_01_0022__row43544108123535"><td class="cellrowborder" valign="top" width="27.26%" headers="mcps1.3.2.2.3.1.1 "><p id="dds_01_0022__p37411822123535">Restarting a DB instance or a node</p>
|
||||
|
@ -34,7 +34,7 @@
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="tablenoborder"><a name="dds_01_0024__table3885614174718"></a><a name="table3885614174718"></a><table cellpadding="4" cellspacing="0" summary="" id="dds_01_0024__table3885614174718" frame="border" border="1" rules="all"><caption><b>Table 2 </b>shard and mongos specifications</caption><thead align="left"><tr id="dds_01_0024__row17886314134712"><th align="left" class="cellrowborder" valign="top" width="31.5%" id="mcps1.3.4.2.4.1.1"><p id="dds_01_0024__p826522732919">vCPUs</p>
|
||||
<div class="tablenoborder"><a name="dds_01_0024__table3885614174718"></a><a name="table3885614174718"></a><table cellpadding="4" cellspacing="0" summary="" id="dds_01_0024__table3885614174718" frame="border" border="1" rules="all"><caption><b>Table 2 </b>shard and dds mongos specifications</caption><thead align="left"><tr id="dds_01_0024__row17886314134712"><th align="left" class="cellrowborder" valign="top" width="31.5%" id="mcps1.3.4.2.4.1.1"><p id="dds_01_0024__p826522732919">vCPUs</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="35.480000000000004%" id="mcps1.3.4.2.4.1.2"><p id="dds_01_0024__p152651227112911">Memory (GB)</p>
|
||||
</th>
|
||||
@ -80,9 +80,9 @@
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
<div class="section" id="dds_01_0024__section360115715426"><h4 class="sectiontitle">Replica Set</h4><p id="dds_01_0024__p927813045418">The specifications supported by a replica set are the same as those supported by shard and mongos. For details, see <a href="#dds_01_0024__table3885614174718">Table 2</a>.</p>
|
||||
<div class="section" id="dds_01_0024__section360115715426"><h4 class="sectiontitle">Replica Set</h4><p id="dds_01_0024__p927813045418">The specifications supported by a replica set are the same as those supported by shard and dds mongos. For details, see <a href="#dds_01_0024__table3885614174718">Table 2</a>.</p>
|
||||
</div>
|
||||
<div class="section" id="dds_01_0024__section16156162715411"><h4 class="sectiontitle">Single Node</h4><p id="dds_01_0024__p123481219582">The specifications supported by a single node are the same as those supported by shard and mongos. For details, see <a href="#dds_01_0024__table3885614174718">Table 2</a>.</p>
|
||||
<div class="section" id="dds_01_0024__section16156162715411"><h4 class="sectiontitle">Single Node</h4><p id="dds_01_0024__p123481219582">The specifications supported by a single node are the same as those supported by shard and dds mongos. For details, see <a href="#dds_01_0024__table3885614174718">Table 2</a>.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
@ -45,7 +45,7 @@
|
||||
</tr>
|
||||
<tr id="dds_01_0026__row1645416322510"><td class="cellrowborder" valign="top" width="22.56%" headers="mcps1.3.1.2.2.3.1.1 "><p id="dds_01_0026__p6454732350">Adding node</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="77.44%" headers="mcps1.3.1.2.2.3.1.2 "><p id="dds_01_0026__p1745410321355">shard or mongos nodes are being added to a DDS cluster instance.</p>
|
||||
<td class="cellrowborder" valign="top" width="77.44%" headers="mcps1.3.1.2.2.3.1.2 "><p id="dds_01_0026__p1745410321355">shard or dds mongos nodes are being added to a DDS cluster instance.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="dds_01_0026__row345414322059"><td class="cellrowborder" valign="top" width="22.56%" headers="mcps1.3.1.2.2.3.1.1 "><p id="dds_01_0026__p13454193212519">Deleting node</p>
|
||||
|
@ -1,7 +1,7 @@
|
||||
<a name="dds_02_0006"></a><a name="dds_02_0006"></a>
|
||||
|
||||
<h1 class="topictitle1">Connecting to a Cluster Instance Over Public Networks</h1>
|
||||
<div id="body1568789840716"><div class="section" id="dds_02_0006__section46429645141251"><h4 class="sectiontitle">Scenarios</h4><p id="dds_02_0006__p125004821516">This section describes how to connect to a cluster instance using the MongoDB client and Robo 3T over public networks.</p>
|
||||
<div id="body1568789840716"><div class="section" id="dds_02_0006__section46429645141251"><h4 class="sectiontitle">Scenarios</h4><p id="dds_02_0006__p125004821516">This section describes how to connect to a cluster instance using the MongoDB client and Robo 3T over public networks.DDS is compatible with MongoDB.</p>
|
||||
<p id="dds_02_0006__p69231113101918">The MongoDB client and Robo 3T can connect to a DB instance with an unencrypted connection or an encrypted connection (SSL). To improve data transmission security, you are advised to connect to DB instances using the SSL connection.</p>
|
||||
<p id="dds_02_0006__p293321134111"><strong id="dds_02_0006__b113673415591">Different OS scenarios</strong>: Examples include Linux and Windows clients.</p>
|
||||
</div>
|
||||
|
@ -50,7 +50,7 @@
|
||||
<tr id="dds_02_0012__row319181316237"><td class="cellrowborder" valign="top" width="26%" headers="mcps1.3.2.2.3.2.1.2.3.1.1 "><p id="dds_02_0012__p1672886816349">Storage Engine</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="74%" headers="mcps1.3.2.2.3.2.1.2.3.1.2 "><ul id="dds_02_0012__ul109418294235"><li id="dds_02_0012__li8942142922318">WiredTiger<p id="dds_02_0012__p11175126192414"><a name="dds_02_0012__li8942142922318"></a><a name="li8942142922318"></a>WiredTiger is the default storage engine of DDS 3.2, 3.4 and 4.0. WiredTiger provides different granularity concurrency control and compression mechanism for data management. It can provide the best performance and storage efficiency for different kinds of applications.</p>
|
||||
</li><li id="dds_02_0012__li19723447162416">RocksDB<p id="dds_02_0012__p3871944172517"><a name="dds_02_0012__li19723447162416"></a><a name="li19723447162416"></a>RocksDB is the default storage engine of DDS 4.2 and 4.4. RocksDB supports efficient point lookup, range scan, and high-speed write. RocksDB can be used as the underlying data storage engine of MongoDB and is suitable for scenarios with a large number of write operations.</p>
|
||||
</li><li id="dds_02_0012__li19723447162416">RocksDB<p id="dds_02_0012__p3871944172517"><a name="dds_02_0012__li19723447162416"></a><a name="li19723447162416"></a>RocksDB is the default storage engine of DDS 4.2 and 4.4. RocksDB supports efficient point lookup, range scan, and high-speed write. RocksDB can be used as the underlying data storage engine of DDS and is suitable for scenarios with a large number of write operations.</p>
|
||||
</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
@ -64,7 +64,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="74%" headers="mcps1.3.2.2.3.2.1.2.3.1.2 "><ul id="dds_02_0012__ul133881550588"><li id="dds_02_0012__li2388145105810"><strong id="dds_02_0012__b842352706102944">Disabled</strong>: Disable the encryption function.</li><li id="dds_02_0012__li52191547135210"><strong id="dds_02_0012__b150747644695932">Enabled</strong>: Enable encryption. This feature improves data security but slightly affects read/write performance.<p id="dds_02_0012__p172191947135211"><strong id="dds_02_0012__b54342102195932">Key Name</strong>: Select or create a private key, which is the tenant key.</p>
|
||||
</li></ul>
|
||||
<div class="note" id="dds_02_0012__note2431518191315"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="dds_02_0012__ul1362121393110"><li id="dds_02_0012__li1156124454620">After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.</li><li id="dds_02_0012__li845663616343">To check whether the disk is encrypted, you can view <strong id="dds_02_0012__b21996298184">Disk Encrypted</strong> in the DB instance list.</li><li id="dds_02_0012__li16886718103912">If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.</li><li id="dds_02_0012__li1660761315330">For details about how to create a key, see the "Creating a CMK" section in the <em id="dds_02_0012__i84235269720595">Key Management Service User Guide</em>.</li></ul>
|
||||
<div class="note" id="dds_02_0012__note2431518191315"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="dds_02_0012__ul1362121393110"><li id="dds_02_0012__li1156124454620">After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.</li><li id="dds_02_0012__li54721944136">Backups of replica sets are physical backups. If disk encryption is enabled, backup data will be encrypted.</li><li id="dds_02_0012__li845663616343">To check whether the disk is encrypted, you can view <strong id="dds_02_0012__b21996298184">Disk Encrypted</strong> in the DB instance list.</li><li id="dds_02_0012__li16886718103912">If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.</li><li id="dds_02_0012__li1660761315330">For details about how to create a key, see the "Creating a CMK" section in the <em id="dds_02_0012__i84235269720595">Key Management Service User Guide</em>.</li></ul>
|
||||
</div></div>
|
||||
</td>
|
||||
</tr>
|
||||
|
@ -34,7 +34,7 @@
|
||||
<tr id="dds_02_0016__en-us_topic_0044018333_row1013512731419"><td class="cellrowborder" valign="top" width="26%" headers="mcps1.3.2.2.3.2.1.2.3.1.1 "><p id="dds_02_0016__en-us_topic_0044018333_p151351316101415">DB Instance Type</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="74%" headers="mcps1.3.2.2.3.2.1.2.3.1.2 "><p id="dds_02_0016__en-us_topic_0044018333_p0135181618149">Select <strong id="dds_02_0016__en-us_topic_0044018333_b842352706152955">Cluster</strong>.</p>
|
||||
<p id="dds_02_0016__en-us_topic_0044018333_p11135716181417">A cluster instance includes three types of nodes: mongos, shard, and config. Each shard and config is a three-node replica set to ensure high availability.</p>
|
||||
<p id="dds_02_0016__en-us_topic_0044018333_p11135716181417">A cluster instance includes three types of nodes: dds mongos, shard, and config. Each shard and config is a three-node replica set to ensure high availability.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="dds_02_0016__en-us_topic_0044018333_row1024495916243"><td class="cellrowborder" valign="top" width="26%" headers="mcps1.3.2.2.3.2.1.2.3.1.1 "><p id="dds_02_0016__en-us_topic_0044018333_p2453532616243">Compatible MongoDB Version</p>
|
||||
@ -50,7 +50,7 @@
|
||||
<tr id="dds_02_0016__en-us_topic_0044018333_row319181316237"><td class="cellrowborder" valign="top" width="26%" headers="mcps1.3.2.2.3.2.1.2.3.1.1 "><p id="dds_02_0016__en-us_topic_0044018333_p1672886816349">Storage Engine</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="74%" headers="mcps1.3.2.2.3.2.1.2.3.1.2 "><ul id="dds_02_0016__en-us_topic_0044018333_ul109418294235"><li id="dds_02_0016__en-us_topic_0044018333_li8942142922318">WiredTiger<p id="dds_02_0016__en-us_topic_0044018333_p11175126192414"><a name="dds_02_0016__en-us_topic_0044018333_li8942142922318"></a><a name="en-us_topic_0044018333_li8942142922318"></a>WiredTiger is the default storage engine of DDS 3.2, 3.4 and 4.0. WiredTiger provides different granularity concurrency control and compression mechanism for data management. It can provide the best performance and storage efficiency for different kinds of applications.</p>
|
||||
</li><li id="dds_02_0016__en-us_topic_0044018333_li19723447162416">RocksDB<p id="dds_02_0016__en-us_topic_0044018333_p3871944172517"><a name="dds_02_0016__en-us_topic_0044018333_li19723447162416"></a><a name="en-us_topic_0044018333_li19723447162416"></a>RocksDB is the default storage engine of DDS 4.2 and 4.4. RocksDB supports efficient point lookup, range scan, and high-speed write. RocksDB can be used as the underlying data storage engine of MongoDB and is suitable for scenarios with a large number of write operations.</p>
|
||||
</li><li id="dds_02_0016__en-us_topic_0044018333_li19723447162416">RocksDB<p id="dds_02_0016__en-us_topic_0044018333_p3871944172517"><a name="dds_02_0016__en-us_topic_0044018333_li19723447162416"></a><a name="en-us_topic_0044018333_li19723447162416"></a>RocksDB is the default storage engine of DDS 4.2 and 4.4. RocksDB supports efficient point lookup, range scan, and high-speed write. RocksDB can be used as the underlying data storage engine of DDS and is suitable for scenarios with a large number of write operations.</p>
|
||||
</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
@ -63,7 +63,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="74%" headers="mcps1.3.2.2.3.2.1.2.3.1.2 "><ul id="dds_02_0016__en-us_topic_0044018333_ul133881550588"><li id="dds_02_0016__en-us_topic_0044018333_li2388145105810"><strong id="dds_02_0016__en-us_topic_0044018333_b842352706102944">Disabled</strong>: Disable the encryption function.</li><li id="dds_02_0016__en-us_topic_0044018333_li52191547135210"><strong id="dds_02_0016__en-us_topic_0044018333_b150747644695932">Enabled</strong>: Enable encryption. This feature improves data security but slightly affects read/write performance.<p id="dds_02_0016__en-us_topic_0044018333_p172191947135211"><strong id="dds_02_0016__en-us_topic_0044018333_b54342102195932">Key Name</strong>: Select or create a private key, which is the tenant key.</p>
|
||||
</li></ul>
|
||||
<div class="note" id="dds_02_0016__en-us_topic_0044018333_note2431518191315"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="dds_02_0016__en-us_topic_0044018333_ul1362121393110"><li id="dds_02_0016__en-us_topic_0044018333_li1156124454620">After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.</li><li id="dds_02_0016__en-us_topic_0044018333_li845663616343">To check whether the disk is encrypted, you can view <strong id="dds_02_0016__en-us_topic_0044018333_b21996298184">Disk Encrypted</strong> in the DB instance list.</li><li id="dds_02_0016__en-us_topic_0044018333_li16886718103912">If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.</li><li id="dds_02_0016__en-us_topic_0044018333_li1660761315330">For details about how to create a key, see the "Creating a CMK" section in the <em id="dds_02_0016__en-us_topic_0044018333_i84235269720595">Key Management Service User Guide</em>.</li></ul>
|
||||
<div class="note" id="dds_02_0016__en-us_topic_0044018333_note2431518191315"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="dds_02_0016__en-us_topic_0044018333_ul1362121393110"><li id="dds_02_0016__en-us_topic_0044018333_li1156124454620">After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.</li><li id="dds_02_0016__en-us_topic_0044018333_li1799163511214">Backups of cluster instances are physical backups. If disk encryption is enabled, backup data will be encrypted.</li><li id="dds_02_0016__en-us_topic_0044018333_li845663616343">To check whether the disk is encrypted, you can view <strong id="dds_02_0016__en-us_topic_0044018333_b21996298184">Disk Encrypted</strong> in the DB instance list.</li><li id="dds_02_0016__en-us_topic_0044018333_li16886718103912">If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.</li><li id="dds_02_0016__en-us_topic_0044018333_li1660761315330">For details about how to create a key, see the "Creating a CMK" section in the <em id="dds_02_0016__en-us_topic_0044018333_i84235269720595">Key Management Service User Guide</em>.</li></ul>
|
||||
</div></div>
|
||||
</td>
|
||||
</tr>
|
||||
@ -77,19 +77,19 @@
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="dds_02_0016__en-us_topic_0044018333_row26958383161127"><td class="cellrowborder" valign="top" width="28.999999999999996%" headers="mcps1.3.2.2.3.2.2.2.3.1.1 "><p id="dds_02_0016__en-us_topic_0044018333_p17841537161129">mongos node class</p>
|
||||
<tbody><tr id="dds_02_0016__en-us_topic_0044018333_row26958383161127"><td class="cellrowborder" valign="top" width="28.999999999999996%" headers="mcps1.3.2.2.3.2.2.2.3.1.1 "><p id="dds_02_0016__en-us_topic_0044018333_p17841537161129">dds mongos node class</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="71%" headers="mcps1.3.2.2.3.2.2.2.3.1.2 "><p id="dds_02_0016__en-us_topic_0044018333_p8316353151114">For details about the mongos CPU and memory, see section <a href="dds_01_0024.html">DB Instance Specifications</a>. After a DB instance is created, you can change its CPU and memory. For details, see section <a href="en-us_topic_0104472218.html">Changing a Cluster DB Instance Class</a>.</p>
|
||||
<td class="cellrowborder" valign="top" width="71%" headers="mcps1.3.2.2.3.2.2.2.3.1.2 "><p id="dds_02_0016__en-us_topic_0044018333_p8316353151114">For details about the dds mongos CPU and memory, see section <a href="dds_01_0024.html">DB Instance Specifications</a>. After a DB instance is created, you can change its CPU and memory. For details, see section <a href="en-us_topic_0104472218.html">Changing a Cluster DB Instance Class</a>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="dds_02_0016__en-us_topic_0044018333_row66640864173420"><td class="cellrowborder" valign="top" width="28.999999999999996%" headers="mcps1.3.2.2.3.2.2.2.3.1.1 "><p id="dds_02_0016__en-us_topic_0044018333_p44330033173420">mongos nodes</p>
|
||||
<tr id="dds_02_0016__en-us_topic_0044018333_row66640864173420"><td class="cellrowborder" valign="top" width="28.999999999999996%" headers="mcps1.3.2.2.3.2.2.2.3.1.1 "><p id="dds_02_0016__en-us_topic_0044018333_p44330033173420">dds mongos nodes</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="71%" headers="mcps1.3.2.2.3.2.2.2.3.1.2 "><p id="dds_02_0016__en-us_topic_0044018333_p1202224316210">The number of mongos nodes. The value ranges from 2 to 32. After a DB instance is created, you can add mongos nodes if necessary. For details, see section <a href="en-us_topic_increase_nodes.html">Adding Nodes to a Cluster</a>.</p>
|
||||
<td class="cellrowborder" valign="top" width="71%" headers="mcps1.3.2.2.3.2.2.2.3.1.2 "><p id="dds_02_0016__en-us_topic_0044018333_p1202224316210">The number of dds mongos nodes. The value ranges from 2 to 32. After a DB instance is created, you can add dds mongos nodes if necessary. For details, see section <a href="en-us_topic_increase_nodes.html">Adding Nodes to a Cluster</a>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="dds_02_0016__en-us_topic_0044018333_row4199175144117"><td class="cellrowborder" valign="top" width="28.999999999999996%" headers="mcps1.3.2.2.3.2.2.2.3.1.1 "><p id="dds_02_0016__en-us_topic_0044018333_p1019925110415">mongos parameter template</p>
|
||||
<tr id="dds_02_0016__en-us_topic_0044018333_row4199175144117"><td class="cellrowborder" valign="top" width="28.999999999999996%" headers="mcps1.3.2.2.3.2.2.2.3.1.1 "><p id="dds_02_0016__en-us_topic_0044018333_p1019925110415">dds mongos parameter template</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="71%" headers="mcps1.3.2.2.3.2.2.2.3.1.2 "><p id="dds_02_0016__en-us_topic_0044018333_p683830114214">The parameters that apply to the mongos nodes. After a DB instance is created, you can change the parameter template of a node to bring out the best performance.</p>
|
||||
<td class="cellrowborder" valign="top" width="71%" headers="mcps1.3.2.2.3.2.2.2.3.1.2 "><p id="dds_02_0016__en-us_topic_0044018333_p683830114214">The parameters that apply to the dds mongos nodes. After a DB instance is created, you can change the parameter template of a node to bring out the best performance.</p>
|
||||
<p id="dds_02_0016__en-us_topic_0044018333_p109814306422">For details, see <a href="en-us_topic_configuration.html">Modifying a Parameter Template</a>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
@ -1,7 +1,7 @@
|
||||
<a name="dds_02_0019"></a><a name="dds_02_0019"></a>
|
||||
|
||||
<h1 class="topictitle1">Setting a Security Group</h1>
|
||||
<div id="body1522808547321"><div class="section" id="dds_02_0019__dds_02_0022_section3152058916230"><h4 class="sectiontitle">Scenarios</h4><p id="dds_02_0019__dds_02_0022_p43222116204125">This section explains how to add a security group rule to control access to and from the <span class="keyword" id="dds_02_0019__dds_02_0022_keyword943913121715">DDS DB instances</span> associated with a security group.</p>
|
||||
<div id="body1522808547321"><div class="section" id="dds_02_0019__dds_02_0022_section3152058916230"><h4 class="sectiontitle">Scenarios</h4><p id="dds_02_0019__dds_02_0022_p43222116204125">This section explains how to add a security group rule to control access to and from the <span class="keyword" id="dds_02_0019__dds_02_0022_keyword943913121715">DDS DB instances</span> associated with a security group.DDS is compatible with MongoDB.</p>
|
||||
</div>
|
||||
<div class="section" id="dds_02_0019__dds_02_0022_section14550984204232"><h4 class="sectiontitle">Precautions</h4><p id="dds_02_0019__dds_02_0022_p5854544204125">The default security group rule allows all outgoing data packets. <span id="dds_02_0019__dds_02_0022_text19411194672218">ECS</span><span id="dds_02_0019__dds_02_0022_text136741350172218"></span>s and DDS DB instances in the same security group can access each other. After a security group is created, you can create different rules for that security group, which allows you to control access to the DB instances that are in it.</p>
|
||||
<p id="dds_02_0019__dds_02_0022_p41200900204125">To access a DB instance in a security group from a source outside of that group, you need to create an inbound rule.</p>
|
||||
|
@ -1,7 +1,7 @@
|
||||
<a name="dds_02_0022"></a><a name="dds_02_0022"></a>
|
||||
|
||||
<h1 class="topictitle1">Setting a Security Group</h1>
|
||||
<div id="body1522808547321"><div class="section" id="dds_02_0022__section3152058916230"><h4 class="sectiontitle">Scenarios</h4><p id="dds_02_0022__p43222116204125">This section explains how to add a security group rule to control access to and from the <span class="keyword" id="dds_02_0022__keyword943913121715">DDS DB instances</span> associated with a security group.</p>
|
||||
<div id="body1522808547321"><div class="section" id="dds_02_0022__section3152058916230"><h4 class="sectiontitle">Scenarios</h4><p id="dds_02_0022__p43222116204125">This section explains how to add a security group rule to control access to and from the <span class="keyword" id="dds_02_0022__keyword943913121715">DDS DB instances</span> associated with a security group.DDS is compatible with MongoDB.</p>
|
||||
</div>
|
||||
<div class="section" id="dds_02_0022__section14550984204232"><h4 class="sectiontitle">Precautions</h4><p id="dds_02_0022__p5854544204125">The default security group rule allows all outgoing data packets. <span id="dds_02_0022__text19411194672218">ECS</span><span id="dds_02_0022__text136741350172218"></span>s and DDS DB instances in the same security group can access each other. After a security group is created, you can create different rules for that security group, which allows you to control access to the DB instances that are in it.</p>
|
||||
<p id="dds_02_0022__p41200900204125">To access a DB instance in a security group from a source outside of that group, you need to create an inbound rule.</p>
|
||||
|
@ -50,7 +50,7 @@
|
||||
<tr id="dds_02_0023__row319181316237"><td class="cellrowborder" valign="top" width="21.05%" headers="mcps1.3.2.2.3.2.1.2.3.1.1 "><p id="dds_02_0023__p1672886816349">Storage Engine</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="78.95%" headers="mcps1.3.2.2.3.2.1.2.3.1.2 "><ul id="dds_02_0023__ul109418294235"><li id="dds_02_0023__li8942142922318">WiredTiger<p id="dds_02_0023__p11175126192414"><a name="dds_02_0023__li8942142922318"></a><a name="li8942142922318"></a>WiredTiger is the default storage engine of DDS 3.2, 3.4 and 4.0. WiredTiger provides different granularity concurrency control and compression mechanism for data management. It can provide the best performance and storage efficiency for different kinds of applications.</p>
|
||||
</li><li id="dds_02_0023__li19723447162416">RocksDB<p id="dds_02_0023__p3871944172517"><a name="dds_02_0023__li19723447162416"></a><a name="li19723447162416"></a>RocksDB is the default storage engine of DDS 4.2 and 4.4. RocksDB supports efficient point lookup, range scan, and high-speed write. RocksDB can be used as the underlying data storage engine of MongoDB and is suitable for scenarios with a large number of write operations.</p>
|
||||
</li><li id="dds_02_0023__li19723447162416">RocksDB<p id="dds_02_0023__p3871944172517"><a name="dds_02_0023__li19723447162416"></a><a name="li19723447162416"></a>RocksDB is the default storage engine of DDS 4.2 and 4.4. RocksDB supports efficient point lookup, range scan, and high-speed write. RocksDB can be used as the underlying data storage engine of DDS and is suitable for scenarios with a large number of write operations.</p>
|
||||
</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
@ -62,7 +62,7 @@
|
||||
<tr id="dds_02_0023__row6259484511219"><td class="cellrowborder" valign="top" width="21.05%" headers="mcps1.3.2.2.3.2.1.2.3.1.1 "><p id="dds_02_0023__p2648269711219">Disk Encryption</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="78.95%" headers="mcps1.3.2.2.3.2.1.2.3.1.2 "><ul id="dds_02_0023__ul133881550588"><li id="dds_02_0023__li2388145105810"><strong id="dds_02_0023__b842352706102944">Disabled</strong>: Disable the encryption function.</li><li id="dds_02_0023__li47064331556"><strong id="dds_02_0023__b18684115810158">Enabled</strong>: Enable the encryption function. This feature improves data security but slightly affects read/write performance.<p id="dds_02_0023__p1950185719127"><strong id="dds_02_0023__b842352706103156">Key Name</strong>: Select or create a private key, which is the tenant key.</p>
|
||||
<div class="note" id="dds_02_0023__note2431518191315"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="dds_02_0023__en-us_topic_0044018333_ul1362121393110"><li id="dds_02_0023__en-us_topic_0044018333_li1156124454620">After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.</li><li id="dds_02_0023__en-us_topic_0044018333_li845663616343">To check whether the disk is encrypted, you can view <strong id="dds_02_0023__en-us_topic_0044018333_b21996298184">Disk Encrypted</strong> in the DB instance list.</li><li id="dds_02_0023__en-us_topic_0044018333_li16886718103912">If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.</li><li id="dds_02_0023__en-us_topic_0044018333_li1660761315330">For details about how to create a key, see the "Creating a CMK" section in the <em id="dds_02_0023__en-us_topic_0044018333_i84235269720595">Key Management Service User Guide</em>.</li></ul>
|
||||
<div class="note" id="dds_02_0023__note1448773071910"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="dds_02_0023__ul155537120203"><li id="dds_02_0023__li10553131220208">After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.</li><li id="dds_02_0023__li266413492204">The backup of a single-node instance is a logical backup. Enabling disk encryption will not encrypt the backup data.</li><li id="dds_02_0023__li1554121215208">To check whether the disk is encrypted, you can view Disk Encrypted in the DB instance list.</li><li id="dds_02_0023__li175541412192017">If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.</li><li id="dds_02_0023__li1155412129200">For details about how to create a key, see the "Creating a CMK" section in the Key Management Service User Guide.</li></ul>
|
||||
</div></div>
|
||||
</li></ul>
|
||||
</td>
|
||||
|
@ -1,7 +1,7 @@
|
||||
<a name="dds_02_0028"></a><a name="dds_02_0028"></a>
|
||||
|
||||
<h1 class="topictitle1">Connecting to a Single Node Instance Over Private Networks</h1>
|
||||
<div id="body1524559356644"><div class="section" id="dds_02_0028__en-us_topic_0085335422_section46429645141251"><h4 class="sectiontitle">Scenarios</h4><p id="dds_02_0028__p125004821516">This section describes how to connect to a single-node instance using the MongoDB client over private networks.</p>
|
||||
<div id="body1524559356644"><div class="section" id="dds_02_0028__en-us_topic_0085335422_section46429645141251"><h4 class="sectiontitle">Scenarios</h4><p id="dds_02_0028__p125004821516">This section describes how to connect to a single-node instance using the MongoDB client over private networks.DDS is compatible with MongoDB.</p>
|
||||
<p id="dds_02_0028__p1432214314142">The MongoDB client can connect to a DB instance with an unencrypted connection or an encrypted connection (SSL). To improve data transmission security, you are advised to connect to DB instances using the SSL connection.</p>
|
||||
<p id="dds_02_0028__p293321134111"><strong id="dds_02_0028__b26861333143110">Different OS scenarios</strong>: Examples include Linux and Windows clients.</p>
|
||||
|
||||
|
@ -3,13 +3,13 @@
|
||||
<h1 class="topictitle1">Binding an EIP</h1>
|
||||
<div id="body1522136462404"><div class="section" id="dds_02_0046__section055104935914"><h4 class="sectiontitle"><strong id="dds_02_0046__b10875147182618">Scenarios</strong></h4><p id="dds_02_0046__p171361239153218">After you create a DB instance, you can bind it to an <span id="dds_02_0046__text5347529164615">EIP</span><span id="dds_02_0046__text148921833154616"></span> to allow external access. If you want to prohibit external access later, you can also unbind the EIP from the DB instance.</p>
|
||||
</div>
|
||||
<div class="section" id="dds_02_0046__section1130510262514"><h4 class="sectiontitle">Precautions</h4><ul id="dds_02_0046__ul15712132844"><li id="dds_02_0046__li13712152748">Before accessing a database, you need to apply for an <span id="dds_02_0046__text12115114904613">EIP</span><span id="dds_02_0046__text16115164920463"></span> on the VPC console. Then, add an inbound rule to allow the IP addresses or IP address ranges of ECSs. For details, see section <a href="dds_02_0019.html">Setting a Security Group</a>.</li><li id="dds_02_0046__li137122023418">In the cluster instance, only mongos can be bound to an <span id="dds_02_0046__text1493612568465">EIP</span><span id="dds_02_0046__text99362563461"></span>. To change the <span id="dds_02_0046__text97581238476">EIP</span><span id="dds_02_0046__text1875815311474"></span> that has been bound to a node, you need to unbind it from the node first.</li></ul>
|
||||
<div class="section" id="dds_02_0046__section1130510262514"><h4 class="sectiontitle">Precautions</h4><ul id="dds_02_0046__ul15712132844"><li id="dds_02_0046__li13712152748">Before accessing a database, you need to apply for an <span id="dds_02_0046__text12115114904613">EIP</span><span id="dds_02_0046__text16115164920463"></span> on the VPC console. Then, add an inbound rule to allow the IP addresses or IP address ranges of ECSs. For details, see section <a href="dds_02_0019.html">Setting a Security Group</a>.</li><li id="dds_02_0046__li137122023418">In the cluster instance, only dds mongos can be bound to an <span id="dds_02_0046__text1493612568465">EIP</span><span id="dds_02_0046__text99362563461"></span>. To change the <span id="dds_02_0046__text97581238476">EIP</span><span id="dds_02_0046__text1875815311474"></span> that has been bound to a node, you need to unbind it from the node first.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="dds_02_0046__section3199593620428"><a name="dds_02_0046__section3199593620428"></a><a name="section3199593620428"></a><h4 class="sectiontitle">Binding an <span id="dds_02_0046__text177791721153913">EIP</span><span id="dds_02_0046__text4780421123918"></span></h4><ol id="dds_02_0046__ol12603704105129"><li id="dds_02_0046__li46324476105129"><span>On the <strong id="dds_02_0046__b84235270615219">Instance Management</strong> page, click the target cluster instance.</span></li><li id="dds_02_0046__li349825362319"><span>In the navigation pane on the left, choose <span class="uicontrol" id="dds_02_0046__uicontrol15916566265"><b>Connections</b></span>. In the <strong id="dds_02_0046__b743512366392">Basic Information</strong> area, locate the target mongos node and click <strong id="dds_02_0046__b1643633673919">Bind EIP</strong> in the <strong id="dds_02_0046__b5438153693917">Operation</strong> column.</span><p><p id="dds_02_0046__p01821156154813">Or in the <strong id="dds_02_0046__b17561158144012">Node Information</strong> area on the <strong id="dds_02_0046__b153761534110">Basic Information</strong> page, locate the target mongos node and choose <strong id="dds_02_0046__b051943016416">More</strong> > <strong id="dds_02_0046__b124701337412">Bind EIP</strong> in the <strong id="dds_02_0046__b62371336144110">Operation</strong> column.</p>
|
||||
</p></li><li id="dds_02_0046__li14267104105129"><span>In the displayed dialog box, all available unbound EIPs are listed. Select the required <span id="dds_02_0046__text1373018458489">EIP</span><span id="dds_02_0046__text127302045134810"></span> and click <strong id="dds_02_0046__b132941115422">OK</strong>. If no available EIPs are displayed, click <strong id="dds_02_0046__b12732191694419">View EIP</strong> and create an <span id="dds_02_0046__text713712644915">EIP</span><span id="dds_02_0046__text161371768492"></span> on the VPC console.</span></li><li id="dds_02_0046__li17560260102159"><span>In the <strong id="dds_02_0046__b46581858114416">EIP</strong> column on the <strong id="dds_02_0046__b18732205534411">mongos</strong> tab, view the <span id="dds_02_0046__text4815132834917">EIP</span><span id="dds_02_0046__text2815122894918"></span> that is successfully bound.</span><p><p id="dds_02_0046__p32760134103252">To unbind an EIP from the DB instance, see <a href="#dds_02_0046__section186511510267">Unbinding an EIP</a>.</p>
|
||||
<div class="section" id="dds_02_0046__section3199593620428"><a name="dds_02_0046__section3199593620428"></a><a name="section3199593620428"></a><h4 class="sectiontitle">Binding an <span id="dds_02_0046__text177791721153913">EIP</span><span id="dds_02_0046__text4780421123918"></span></h4><ol id="dds_02_0046__ol12603704105129"><li id="dds_02_0046__li46324476105129"><span>On the <strong id="dds_02_0046__b84235270615219">Instance Management</strong> page, click the target cluster instance.</span></li><li id="dds_02_0046__li349825362319"><span>In the navigation pane on the left, choose <span class="uicontrol" id="dds_02_0046__uicontrol15916566265"><b>Connections</b></span>. In the <strong id="dds_02_0046__b743512366392">Basic Information</strong> area, locate the target dds mongos node and click <strong id="dds_02_0046__b1643633673919">Bind EIP</strong> in the <strong id="dds_02_0046__b5438153693917">Operation</strong> column.</span><p><p id="dds_02_0046__p01821156154813">Or in the <strong id="dds_02_0046__b17561158144012">Node Information</strong> area on the <strong id="dds_02_0046__b153761534110">Basic Information</strong> page, locate the target dds mongos node and choose <strong id="dds_02_0046__b051943016416">More</strong> > <strong id="dds_02_0046__b124701337412">Bind EIP</strong> in the <strong id="dds_02_0046__b62371336144110">Operation</strong> column.</p>
|
||||
</p></li><li id="dds_02_0046__li14267104105129"><span>In the displayed dialog box, all available unbound EIPs are listed. Select the required <span id="dds_02_0046__text1373018458489">EIP</span><span id="dds_02_0046__text127302045134810"></span> and click <strong id="dds_02_0046__b132941115422">OK</strong>. If no available EIPs are displayed, click <strong id="dds_02_0046__b12732191694419">View EIP</strong> and create an <span id="dds_02_0046__text713712644915">EIP</span><span id="dds_02_0046__text161371768492"></span> on the VPC console.</span></li><li id="dds_02_0046__li17560260102159"><span>In the <strong id="dds_02_0046__b46581858114416">EIP</strong> column on the dds mongos tab, view the <span id="dds_02_0046__text4815132834917">EIP</span><span id="dds_02_0046__text2815122894918"></span> that is successfully bound.</span><p><p id="dds_02_0046__p32760134103252">To unbind an EIP from the DB instance, see <a href="#dds_02_0046__section186511510267">Unbinding an EIP</a>.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="dds_02_0046__section186511510267"><a name="dds_02_0046__section186511510267"></a><a name="section186511510267"></a><h4 class="sectiontitle">Unbinding an <span id="dds_02_0046__text16988121194516">EIP</span><span id="dds_02_0046__text89891121144512"></span></h4><ol id="dds_02_0046__ol31276680102616"><li id="dds_02_0046__li35235350102616"><span>On the <strong id="dds_02_0046__b34027572411917">Instance Management</strong> page, click the target cluster instance.</span></li><li id="dds_02_0046__li15539153193217"><span>In the navigation pane on the left, choose <span class="uicontrol" id="dds_02_0046__uicontrol8299182120338"><b>Connections</b></span>. In the <strong id="dds_02_0046__b553193234517">Basic Information</strong> area, locate the target mongos node and click <strong id="dds_02_0046__b165414329451">Unbind EIP</strong> in the <strong id="dds_02_0046__b75573218456">Operation</strong> column.</span><p><p id="dds_02_0046__p10693102185417">Or in the <strong id="dds_02_0046__b1745464113455">Node Information</strong> area on the <strong id="dds_02_0046__b845474184520">Basic Information</strong> page, locate the target mongos node and choose <strong id="dds_02_0046__b0455841134512">More</strong> > <strong id="dds_02_0046__b1645618411455">Unbind EIP</strong> in the <strong id="dds_02_0046__b11457144164515">Operation</strong> column.</p>
|
||||
<div class="section" id="dds_02_0046__section186511510267"><a name="dds_02_0046__section186511510267"></a><a name="section186511510267"></a><h4 class="sectiontitle">Unbinding an <span id="dds_02_0046__text16988121194516">EIP</span><span id="dds_02_0046__text89891121144512"></span></h4><ol id="dds_02_0046__ol31276680102616"><li id="dds_02_0046__li35235350102616"><span>On the <strong id="dds_02_0046__b34027572411917">Instance Management</strong> page, click the target cluster instance.</span></li><li id="dds_02_0046__li15539153193217"><span>In the navigation pane on the left, choose <span class="uicontrol" id="dds_02_0046__uicontrol8299182120338"><b>Connections</b></span>. In the <strong id="dds_02_0046__b553193234517">Basic Information</strong> area, locate the target dds mongos node and click <strong id="dds_02_0046__b165414329451">Unbind EIP</strong> in the <strong id="dds_02_0046__b75573218456">Operation</strong> column.</span><p><p id="dds_02_0046__p10693102185417">Or in the <strong id="dds_02_0046__b1745464113455">Node Information</strong> area on the <strong id="dds_02_0046__b845474184520">Basic Information</strong> page, locate the target dds mongos node and choose <strong id="dds_02_0046__b0455841134512">More</strong> > <strong id="dds_02_0046__b1645618411455">Unbind EIP</strong> in the <strong id="dds_02_0046__b11457144164515">Operation</strong> column.</p>
|
||||
</p></li><li id="dds_02_0046__li56439840102720"><span>In the displayed dialog box, click <strong id="dds_02_0046__b395412212479">Yes</strong>.</span><p><p id="dds_02_0046__p21771104103056">To bind an EIP to the DB instance again, see <a href="#dds_02_0046__section3199593620428">Binding an EIP</a>.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
|
@ -1,7 +1,7 @@
|
||||
<a name="dds_02_0047"></a><a name="dds_02_0047"></a>
|
||||
|
||||
<h1 class="topictitle1">Connecting to a Replica Set Instance Over Public Networks</h1>
|
||||
<div id="body1568881417594"><div class="section" id="dds_02_0047__en-us_topic_0085335422_section46429645141251"><h4 class="sectiontitle"><strong id="dds_02_0047__b3230773327">Scenarios</strong></h4><p id="dds_02_0047__p2055118186348">This section describes how to connect to a replica set instance using the MongoDB client and Robo 3T over public networks.</p>
|
||||
<div id="body1568881417594"><div class="section" id="dds_02_0047__en-us_topic_0085335422_section46429645141251"><h4 class="sectiontitle"><strong id="dds_02_0047__b3230773327">Scenarios</strong></h4><p id="dds_02_0047__p2055118186348">This section describes how to connect to a replica set instance using the MongoDB client and Robo 3T over public networks.DDS is compatible with MongoDB.</p>
|
||||
<p id="dds_02_0047__p912664163410">You can directly perform operations on the primary and secondary nodes. Primary nodes are used for processing read and write requests. Secondary nodes replicate data from the primary and are used for processing read requests only.</p>
|
||||
<p id="dds_02_0047__p2551818153416">The MongoDB client and Robo 3T can connect to a DB instance with an unencrypted connection or an encrypted connection (SSL). To improve data transmission security, you are advised to connect to DB instances using the SSL connection.</p>
|
||||
<p id="dds_02_0047__p12551118173416"><strong id="dds_02_0047__b67401533193210">Different OS scenarios</strong>: Examples include Linux and Windows clients.</p>
|
||||
|
@ -1,7 +1,7 @@
|
||||
<a name="dds_02_0048"></a><a name="dds_02_0048"></a>
|
||||
|
||||
<h1 class="topictitle1">Connecting to a Single Node Instance Over Public Networks</h1>
|
||||
<div id="body1568881417594"><div class="section" id="dds_02_0048__en-us_topic_0085335422_section46429645141251"><h4 class="sectiontitle"><strong id="dds_02_0048__b44681658414">Scenarios</strong></h4><p id="dds_02_0048__p2055118186348">This section describes how to connect to a single-node instance using the MongoDB client and Robo 3T over public networks.</p>
|
||||
<div id="body1568881417594"><div class="section" id="dds_02_0048__en-us_topic_0085335422_section46429645141251"><h4 class="sectiontitle"><strong id="dds_02_0048__b44681658414">Scenarios</strong></h4><p id="dds_02_0048__p2055118186348">This section describes how to connect to a single-node instance using the MongoDB client and Robo 3T over public networks.DDS is compatible with MongoDB.</p>
|
||||
<p id="dds_02_0048__p2551818153416">The MongoDB client and Robo 3T can connect to a DB instance with an unencrypted connection or an encrypted connection (SSL). To improve data transmission security, you are advised to connect to DB instances using the SSL connection.</p>
|
||||
<p id="dds_02_0048__p12551118173416"><strong id="dds_02_0048__b18177165483515">Different OS scenarios</strong>: Examples include Linux and Windows clients.</p>
|
||||
|
||||
|
@ -50,7 +50,7 @@
|
||||
<tr id="dds_02_0052__dds_02_0012_row319181316237"><td class="cellrowborder" valign="top" width="26%" headers="mcps1.3.2.2.3.2.1.2.3.1.1 "><p id="dds_02_0052__dds_02_0012_p1672886816349">Storage Engine</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="74%" headers="mcps1.3.2.2.3.2.1.2.3.1.2 "><ul id="dds_02_0052__dds_02_0012_ul109418294235"><li id="dds_02_0052__dds_02_0012_li8942142922318">WiredTiger<p id="dds_02_0052__dds_02_0012_p11175126192414"><a name="dds_02_0052__dds_02_0012_li8942142922318"></a><a name="dds_02_0012_li8942142922318"></a>WiredTiger is the default storage engine of DDS 3.2, 3.4 and 4.0. WiredTiger provides different granularity concurrency control and compression mechanism for data management. It can provide the best performance and storage efficiency for different kinds of applications.</p>
|
||||
</li><li id="dds_02_0052__dds_02_0012_li19723447162416">RocksDB<p id="dds_02_0052__dds_02_0012_p3871944172517"><a name="dds_02_0052__dds_02_0012_li19723447162416"></a><a name="dds_02_0012_li19723447162416"></a>RocksDB is the default storage engine of DDS 4.2 and 4.4. RocksDB supports efficient point lookup, range scan, and high-speed write. RocksDB can be used as the underlying data storage engine of MongoDB and is suitable for scenarios with a large number of write operations.</p>
|
||||
</li><li id="dds_02_0052__dds_02_0012_li19723447162416">RocksDB<p id="dds_02_0052__dds_02_0012_p3871944172517"><a name="dds_02_0052__dds_02_0012_li19723447162416"></a><a name="dds_02_0012_li19723447162416"></a>RocksDB is the default storage engine of DDS 4.2 and 4.4. RocksDB supports efficient point lookup, range scan, and high-speed write. RocksDB can be used as the underlying data storage engine of DDS and is suitable for scenarios with a large number of write operations.</p>
|
||||
</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
@ -64,7 +64,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="74%" headers="mcps1.3.2.2.3.2.1.2.3.1.2 "><ul id="dds_02_0052__dds_02_0012_ul133881550588"><li id="dds_02_0052__dds_02_0012_li2388145105810"><strong id="dds_02_0052__dds_02_0012_b842352706102944">Disabled</strong>: Disable the encryption function.</li><li id="dds_02_0052__dds_02_0012_li52191547135210"><strong id="dds_02_0052__dds_02_0012_b150747644695932">Enabled</strong>: Enable encryption. This feature improves data security but slightly affects read/write performance.<p id="dds_02_0052__dds_02_0012_p172191947135211"><strong id="dds_02_0052__dds_02_0012_b54342102195932">Key Name</strong>: Select or create a private key, which is the tenant key.</p>
|
||||
</li></ul>
|
||||
<div class="note" id="dds_02_0052__dds_02_0012_note2431518191315"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="dds_02_0052__dds_02_0012_ul1362121393110"><li id="dds_02_0052__dds_02_0012_li1156124454620">After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.</li><li id="dds_02_0052__dds_02_0012_li845663616343">To check whether the disk is encrypted, you can view <strong id="dds_02_0052__dds_02_0012_b21996298184">Disk Encrypted</strong> in the DB instance list.</li><li id="dds_02_0052__dds_02_0012_li16886718103912">If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.</li><li id="dds_02_0052__dds_02_0012_li1660761315330">For details about how to create a key, see the "Creating a CMK" section in the <em id="dds_02_0052__dds_02_0012_i84235269720595">Key Management Service User Guide</em>.</li></ul>
|
||||
<div class="note" id="dds_02_0052__dds_02_0012_note2431518191315"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="dds_02_0052__dds_02_0012_ul1362121393110"><li id="dds_02_0052__dds_02_0012_li1156124454620">After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.</li><li id="dds_02_0052__dds_02_0012_li54721944136">Backups of replica sets are physical backups. If disk encryption is enabled, backup data will be encrypted.</li><li id="dds_02_0052__dds_02_0012_li845663616343">To check whether the disk is encrypted, you can view <strong id="dds_02_0052__dds_02_0012_b21996298184">Disk Encrypted</strong> in the DB instance list.</li><li id="dds_02_0052__dds_02_0012_li16886718103912">If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.</li><li id="dds_02_0052__dds_02_0012_li1660761315330">For details about how to create a key, see the "Creating a CMK" section in the <em id="dds_02_0052__dds_02_0012_i84235269720595">Key Management Service User Guide</em>.</li></ul>
|
||||
</div></div>
|
||||
</td>
|
||||
</tr>
|
||||
|
@ -50,7 +50,7 @@
|
||||
<tr id="dds_02_0079__dds_02_0023_row319181316237"><td class="cellrowborder" valign="top" width="21.05%" headers="mcps1.3.2.2.3.2.1.2.3.1.1 "><p id="dds_02_0079__dds_02_0023_p1672886816349">Storage Engine</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="78.95%" headers="mcps1.3.2.2.3.2.1.2.3.1.2 "><ul id="dds_02_0079__dds_02_0023_ul109418294235"><li id="dds_02_0079__dds_02_0023_li8942142922318">WiredTiger<p id="dds_02_0079__dds_02_0023_p11175126192414"><a name="dds_02_0079__dds_02_0023_li8942142922318"></a><a name="dds_02_0023_li8942142922318"></a>WiredTiger is the default storage engine of DDS 3.2, 3.4 and 4.0. WiredTiger provides different granularity concurrency control and compression mechanism for data management. It can provide the best performance and storage efficiency for different kinds of applications.</p>
|
||||
</li><li id="dds_02_0079__dds_02_0023_li19723447162416">RocksDB<p id="dds_02_0079__dds_02_0023_p3871944172517"><a name="dds_02_0079__dds_02_0023_li19723447162416"></a><a name="dds_02_0023_li19723447162416"></a>RocksDB is the default storage engine of DDS 4.2 and 4.4. RocksDB supports efficient point lookup, range scan, and high-speed write. RocksDB can be used as the underlying data storage engine of MongoDB and is suitable for scenarios with a large number of write operations.</p>
|
||||
</li><li id="dds_02_0079__dds_02_0023_li19723447162416">RocksDB<p id="dds_02_0079__dds_02_0023_p3871944172517"><a name="dds_02_0079__dds_02_0023_li19723447162416"></a><a name="dds_02_0023_li19723447162416"></a>RocksDB is the default storage engine of DDS 4.2 and 4.4. RocksDB supports efficient point lookup, range scan, and high-speed write. RocksDB can be used as the underlying data storage engine of DDS and is suitable for scenarios with a large number of write operations.</p>
|
||||
</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
@ -62,7 +62,7 @@
|
||||
<tr id="dds_02_0079__dds_02_0023_row6259484511219"><td class="cellrowborder" valign="top" width="21.05%" headers="mcps1.3.2.2.3.2.1.2.3.1.1 "><p id="dds_02_0079__dds_02_0023_p2648269711219">Disk Encryption</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="78.95%" headers="mcps1.3.2.2.3.2.1.2.3.1.2 "><ul id="dds_02_0079__dds_02_0023_ul133881550588"><li id="dds_02_0079__dds_02_0023_li2388145105810"><strong id="dds_02_0079__dds_02_0023_b842352706102944">Disabled</strong>: Disable the encryption function.</li><li id="dds_02_0079__dds_02_0023_li47064331556"><strong id="dds_02_0079__dds_02_0023_b18684115810158">Enabled</strong>: Enable the encryption function. This feature improves data security but slightly affects read/write performance.<p id="dds_02_0079__dds_02_0023_p1950185719127"><strong id="dds_02_0079__dds_02_0023_b842352706103156">Key Name</strong>: Select or create a private key, which is the tenant key.</p>
|
||||
<div class="note" id="dds_02_0079__dds_02_0023_note2431518191315"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="dds_02_0079__dds_02_0023_en-us_topic_0044018333_ul1362121393110"><li id="dds_02_0079__dds_02_0023_en-us_topic_0044018333_li1156124454620">After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.</li><li id="dds_02_0079__dds_02_0023_en-us_topic_0044018333_li845663616343">To check whether the disk is encrypted, you can view <strong id="dds_02_0079__dds_02_0023_en-us_topic_0044018333_b21996298184">Disk Encrypted</strong> in the DB instance list.</li><li id="dds_02_0079__dds_02_0023_en-us_topic_0044018333_li16886718103912">If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.</li><li id="dds_02_0079__dds_02_0023_en-us_topic_0044018333_li1660761315330">For details about how to create a key, see the "Creating a CMK" section in the <em id="dds_02_0079__dds_02_0023_en-us_topic_0044018333_i84235269720595">Key Management Service User Guide</em>.</li></ul>
|
||||
<div class="note" id="dds_02_0079__dds_02_0023_note1448773071910"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="dds_02_0079__dds_02_0023_ul155537120203"><li id="dds_02_0079__dds_02_0023_li10553131220208">After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.</li><li id="dds_02_0079__dds_02_0023_li266413492204">The backup of a single-node instance is a logical backup. Enabling disk encryption will not encrypt the backup data.</li><li id="dds_02_0079__dds_02_0023_li1554121215208">To check whether the disk is encrypted, you can view Disk Encrypted in the DB instance list.</li><li id="dds_02_0079__dds_02_0023_li175541412192017">If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.</li><li id="dds_02_0079__dds_02_0023_li1155412129200">For details about how to create a key, see the "Creating a CMK" section in the Key Management Service User Guide.</li></ul>
|
||||
</div></div>
|
||||
</li></ul>
|
||||
</td>
|
||||
|
@ -1,7 +1,7 @@
|
||||
<a name="dds_02_0100"></a><a name="dds_02_0100"></a>
|
||||
|
||||
<h1 class="topictitle1">Enabling IP Addresses of shard and config Nodes</h1>
|
||||
<div id="body1585039985339"><div class="section" id="dds_02_0100__section45891259194718"><h4 class="sectiontitle">Scenarios</h4><p id="dds_02_0100__p197615192220">A cluster instance of Community Edition consists of mongos, shard, and config nodes. When your services need to read and write data from and into databases, connect to the mongos node. In certain scenarios, you need to read data from the shard or config node. Therefore, obtaining the IP address of the corresponding node is necessary.</p>
|
||||
<div id="body1585039985339"><div class="section" id="dds_02_0100__section45891259194718"><h4 class="sectiontitle">Scenarios</h4><p id="dds_02_0100__p197615192220">A cluster instance of Community Edition consists of dds mongos, shard, and config nodes. When your services need to read and write data from and into databases, connect to the dds mongos node. In certain scenarios, you need to read data from the shard or config node. Therefore, obtaining the IP address of the corresponding node is necessary.</p>
|
||||
<p id="dds_02_0100__p8060118">This section describes how to obtain the IP addresses of the shard and config nodes.</p>
|
||||
</div>
|
||||
<div class="section" id="dds_02_0100__section12401231171410"><h4 class="sectiontitle">Before You Start</h4>
|
||||
|
@ -10,7 +10,7 @@
|
||||
</p></li><li id="dds_03_0003__l57619a6f46fb4d3da03a966e6e197e54"><span>In the displayed dialog box, click <span class="parmname" id="dds_03_0003__parmname76964790591510"><b>Yes</b></span>.</span></li><li id="dds_03_0003__li5877485919459"><span>View the restart status.</span><p><ol type="a" id="dds_03_0003__ol21264366192427"><li id="dds_03_0003__li35806698192429">On the <strong id="dds_03_0003__b903604656102525">Instance Management</strong> page, the instance status is <strong id="dds_03_0003__b842352706103045">Restarting</strong>.</li><li id="dds_03_0003__li57748098192427">On the <span class="uicontrol" id="dds_03_0003__uicontrol181327725791942"><b>Basic Information</b></span> page, all nodes of the cluster instance cannot be restarted.</li></ol>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="dds_03_0003__section42490975183655"><h4 class="sectiontitle">Restarting a Node (Cluster)</h4><ol id="dds_03_0003__o61aba0ec8639408d93edfa0f2e7bc30a"><li id="dds_03_0003__li510217230279"><span><a href="dds_02_0043.html">Log in to the DDS console.</a></span></li><li id="dds_03_0003__l8ace08773a9442af864967ce7beab047"><span>On the <strong id="dds_03_0003__b1708346183920">Instance Management</strong> page, click the target cluster instance.</span></li><li id="dds_03_0003__l6a3f6334c2484524beb87828d465befa"><span>In the <span class="uicontrol" id="dds_03_0003__uicontrol127921324174213"><b>Node Information</b></span> area on the <span class="uicontrol" id="dds_03_0003__uicontrol1710532134210"><b>Basic Information</b></span> page, click the <span class="uicontrol" id="dds_03_0003__uicontrol1696172384117"><b>mongos</b></span>, <span class="uicontrol" id="dds_03_0003__uicontrol5697102313416"><b>shard</b></span>, or <span class="uicontrol" id="dds_03_0003__uicontrol13697192320411"><b>config</b></span> tab, locate the target node, and in the <strong id="dds_03_0003__b98401327133917">Operation</strong> column, click <span class="uicontrol" id="dds_03_0003__uicontrol56977233416"><b>Restart</b></span>.</span></li><li id="dds_03_0003__li1775217447164"><span>In the displayed dialog box, click <strong id="dds_03_0003__b1163685714436">Yes</strong>.</span></li><li id="dds_03_0003__li34731609193128"><span>View the node status.</span><p><p id="dds_03_0003__p12965523112838">When one node status is <span class="uicontrol" id="dds_03_0003__uicontrol233484214448"><b>Restarting</b></span>, other nodes of the instance cannot be restarted.</p>
|
||||
<div class="section" id="dds_03_0003__section42490975183655"><h4 class="sectiontitle">Restarting a Node (Cluster)</h4><ol id="dds_03_0003__o61aba0ec8639408d93edfa0f2e7bc30a"><li id="dds_03_0003__li510217230279"><span><a href="dds_02_0043.html">Log in to the DDS console.</a></span></li><li id="dds_03_0003__l8ace08773a9442af864967ce7beab047"><span>On the <strong id="dds_03_0003__b1708346183920">Instance Management</strong> page, click the target cluster instance.</span></li><li id="dds_03_0003__l6a3f6334c2484524beb87828d465befa"><span>In the <span class="uicontrol" id="dds_03_0003__uicontrol127921324174213"><b>Node Information</b></span> area on the <span class="uicontrol" id="dds_03_0003__uicontrol1710532134210"><b>Basic Information</b></span> page, click the <strong id="dds_03_0003__b6347123325216">dds mongos</strong>, <span class="uicontrol" id="dds_03_0003__uicontrol5697102313416"><b>shard</b></span>, or <span class="uicontrol" id="dds_03_0003__uicontrol13697192320411"><b>config</b></span> tab, locate the target node, and in the <strong id="dds_03_0003__b98401327133917">Operation</strong> column, click <span class="uicontrol" id="dds_03_0003__uicontrol56977233416"><b>Restart</b></span>.</span></li><li id="dds_03_0003__li1775217447164"><span>In the displayed dialog box, click <strong id="dds_03_0003__b1163685714436">Yes</strong>.</span></li><li id="dds_03_0003__li34731609193128"><span>View the node status.</span><p><p id="dds_03_0003__p12965523112838">When one node status is <span class="uicontrol" id="dds_03_0003__uicontrol233484214448"><b>Restarting</b></span>, other nodes of the instance cannot be restarted.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
|
@ -6,7 +6,7 @@
|
||||
<div class="section" id="dds_03_0018__section42700170172320"><h4 class="sectiontitle">Reverting Nodes in Batches</h4><ol id="dds_03_0018__ol36161728172320"><li id="dds_03_0018__li312682313217"><span><a href="dds_02_0043.html">Log in to the DDS console.</a></span></li><li id="dds_03_0018__li57020104172320"><span>On the <strong id="dds_03_0018__b842352706112915">Instance Management</strong> page, locate the cluster instance to which nodes fail to be added and choose <strong id="dds_03_0018__b842352706113017">More</strong> > <strong id="dds_03_0018__b842352706113020">Revert</strong> in the <strong id="dds_03_0018__b84235270611302">Operation</strong> column.</span></li><li id="dds_03_0018__li1560732781513"><span>In the displayed dialog box, click <strong id="dds_03_0018__b1953719025517">Yes</strong>.</span><p><p id="dds_03_0018__p848232891512">During reversal, the instance status is <strong id="dds_03_0018__b842352706144335">Deleting node</strong>. This process takes about 1 to 3 minutes.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="dds_03_0018__section44097393172320"><h4 class="sectiontitle">Deleting Failed Cluster Instance Nodes</h4><ol id="dds_03_0018__ol15119103172320"><li id="dds_03_0018__li1036917305316"><span><a href="dds_02_0043.html">Log in to the DDS console.</a></span></li><li id="dds_03_0018__li1854200172320"><span>On the <strong id="dds_03_0018__b84235270615219">Instance Management</strong> page, click the target cluster instance to which the node fails to be added.</span></li><li id="dds_03_0018__li9534931172320"><span>In the <strong id="dds_03_0018__b842352706145037">Node Information</strong> area on the <strong id="dds_03_0018__b842352706145027">Basic Information</strong> tab, click the <strong id="dds_03_0018__b842352706145046">mongos</strong> or <strong id="dds_03_0018__b842352706145049">shard</strong> tab, locate the mongos or shard that failed to be added, and choose <strong id="dds_03_0018__b842352706145122">More</strong> > <strong id="dds_03_0018__b842352706145126">Delete</strong>.</span></li><li id="dds_03_0018__li11468294171"><span>In the displayed dialog box, click <span class="parmname" id="dds_03_0018__parmname17955163010196"><b>Yes</b></span>.</span><p><p id="dds_03_0018__p9296910161714">During deletion, the node status is <strong id="dds_03_0018__b32009954314">Deleting node</strong>. This process takes about 1 to 3 minutes.</p>
|
||||
<div class="section" id="dds_03_0018__section44097393172320"><h4 class="sectiontitle">Deleting Failed Cluster Instance Nodes</h4><ol id="dds_03_0018__ol15119103172320"><li id="dds_03_0018__li1036917305316"><span><a href="dds_02_0043.html">Log in to the DDS console.</a></span></li><li id="dds_03_0018__li1854200172320"><span>On the <strong id="dds_03_0018__b84235270615219">Instance Management</strong> page, click the target cluster instance to which the node fails to be added.</span></li><li id="dds_03_0018__li9534931172320"><span>In the <strong id="dds_03_0018__b842352706145037">Node Information</strong> area on the <strong id="dds_03_0018__b842352706145027">Basic Information</strong> tab, click the <strong id="dds_03_0018__b27852018135015">dds mongos</strong> or <strong id="dds_03_0018__b842352706145049">shard</strong> tab, locate the dds mongos or shard that failed to be added, and choose <strong id="dds_03_0018__b842352706145122">More</strong> > <strong id="dds_03_0018__b842352706145126">Delete</strong>.</span></li><li id="dds_03_0018__li11468294171"><span>In the displayed dialog box, click <span class="parmname" id="dds_03_0018__parmname17955163010196"><b>Yes</b></span>.</span><p><p id="dds_03_0018__p9296910161714">During deletion, the node status is <strong id="dds_03_0018__b32009954314">Deleting node</strong>. This process takes about 1 to 3 minutes.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
|
@ -3,7 +3,7 @@
|
||||
<h1 class="topictitle1">Task Center</h1>
|
||||
<div id="body1529486721075"><div class="section" id="dds_03_0040__section36712096194014"><h4 class="sectiontitle"><strong id="dds_03_0040__b84235270694112">Scenarios</strong></h4><p id="dds_03_0040__p125632222023">This section describes how to view the progress and result of asynchronous tasks on the <span class="uicontrol" id="dds_03_0040__uicontrol119474981310495"><b>Task Center</b></span> page.</p>
|
||||
</div>
|
||||
<div class="section" id="dds_03_0040__section1851414322510"><h4 class="sectiontitle">Tasks Overview</h4><ul id="dds_03_0040__ul747711518519"><li id="dds_03_0040__li8557144418613">Creating a snapshot backup</li><li id="dds_03_0040__li7603144267">Creating a cluster Instance</li><li id="dds_03_0040__li156041944365">Creating a replica set instance</li><li id="dds_03_0040__li176055441618">Creating a single node instance</li><li id="dds_03_0040__li76066447618">Scaling up storage space</li><li id="dds_03_0040__li5606144418613">Changing the Community Edition instance</li><li id="dds_03_0040__li260713441364">Adding nodes</li><li id="dds_03_0040__li206085441620">Adding standby nodes to a replica set</li><li id="dds_03_0040__li14608444369">Restarting a cluster instance</li><li id="dds_03_0040__li960914411619">Restarting cluster nodes</li><li id="dds_03_0040__li3610184410614">Restart a cluster node</li><li id="dds_03_0040__li661112447613">Restarting a replica set instance</li><li id="dds_03_0040__li1361134415620">Restarting a single-node instance</li><li id="dds_03_0040__li66124440617">Switch Primary and Secondary Nodes</li><li id="dds_03_0040__li96131644268">Change Private IP Address</li><li id="dds_03_0040__li20614164414613">Changing a security group</li><li id="dds_03_0040__li961454414615">Changing a database port</li><li id="dds_03_0040__li66152440614">Bind EIP</li><li id="dds_03_0040__li1461774411615">Change AZ</li><li id="dds_03_0040__li361734414612">Enabling the shard/config IP address</li><li id="dds_03_0040__li116185448615">Modifying the oplog size</li><li id="dds_03_0040__li1261919443613">Restoring to a new cluster instance</li><li id="dds_03_0040__li15619844161">Restoring to a new replica set instance</li><li id="dds_03_0040__li186201344665">Restoring to a new single-node instance</li><li id="dds_03_0040__li262114441268">Restoring a replica set instance to a point in time</li><li id="dds_03_0040__li1862216441665">Creating a physical backup</li><li id="dds_03_0040__li19622744264">Creating a snapshot backup</li><li id="dds_03_0040__li262310441961">Restore Database and Table</li></ul>
|
||||
<div class="section" id="dds_03_0040__section1851414322510"><h4 class="sectiontitle">Tasks Overview</h4><ul id="dds_03_0040__ul747711518519"><li id="dds_03_0040__li7603144267">Creating a cluster Instance</li><li id="dds_03_0040__li156041944365">Creating a replica set instance</li><li id="dds_03_0040__li176055441618">Creating a single node instance</li><li id="dds_03_0040__li76066447618">Scaling up storage space</li><li id="dds_03_0040__li21539141417">Scaling down storage space</li><li id="dds_03_0040__li5606144418613">Changing the Community Edition instance class</li><li id="dds_03_0040__li17736954416">Changing the Enhanced Edition instance class</li><li id="dds_03_0040__li260713441364">Adding nodes</li><li id="dds_03_0040__li14608444369">Restarting a cluster instance</li><li id="dds_03_0040__li960914411619">Restarting cluster nodes</li><li id="dds_03_0040__li3610184410614">Restart a node</li><li id="dds_03_0040__li661112447613">Restarting a replica set instance</li><li id="dds_03_0040__li1361134415620">Restarting a single-node instance</li><li id="dds_03_0040__li1261919443613">Restoring to a new cluster instance</li><li id="dds_03_0040__li15619844161">Restoring to a new replica set instance</li><li id="dds_03_0040__li186201344665">Restoring to a new single-node instance</li><li id="dds_03_0040__li1648008165119">Restoring a cluster instance to a point in time</li><li id="dds_03_0040__li262114441268">Restoring a replica set instance to a point in time</li><li id="dds_03_0040__li102311232526">Restoring a single-node instance to a point in time</li><li id="dds_03_0040__li206085441620">Adding standby nodes to a replica set</li><li id="dds_03_0040__li66124440617">Switch Primary and Secondary Nodes</li><li id="dds_03_0040__li96131644268">Change Private IP Address</li><li id="dds_03_0040__li20614164414613">Changing a security group</li><li id="dds_03_0040__li961454414615">Changing a database port</li><li id="dds_03_0040__li66152440614">Bind EIP</li><li id="dds_03_0040__li57841240165313">Unbind EIP</li><li id="dds_03_0040__li14429183311219">Switch SSL</li><li id="dds_03_0040__li1461774411615">Change AZ</li><li id="dds_03_0040__li361734414612">Enabling the shard/config IP address</li><li id="dds_03_0040__li116185448615">Modifying the oplog size</li><li id="dds_03_0040__li1862216441665">Creating a physical backup</li><li id="dds_03_0040__li19622744264">Creating a snapshot backup</li><li id="dds_03_0040__li7329133115712">Restoring data</li><li id="dds_03_0040__li20179535716">Restoring data to a point in time</li><li id="dds_03_0040__li262310441961">Restore database and tables</li><li id="dds_03_0040__li7897259135">Restoring to the original instance</li><li id="dds_03_0040__li164557311418">Restoring to a new instance</li><li id="dds_03_0040__li25393396613">Restoring to the original instance to a specific point in time</li><li id="dds_03_0040__li9917173817712">Restoring to a new instance to a specific point in time</li><li id="dds_03_0040__li37751152474">Recycling backups</li><li id="dds_03_0040__li46715198171">Installing database patches</li><li id="dds_03_0040__li43711920151710">Adding read replicas</li><li id="dds_03_0040__li47143259172">Deleting read replicas from a replica set instance</li></ul>
|
||||
<div class="note" id="dds_03_0040__note9595204512517"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="dds_03_0040__p2059594519515">Tasks that fail to be executed will be retained for seven days by default.</p>
|
||||
</div></div>
|
||||
</div>
|
||||
|
@ -6,7 +6,7 @@
|
||||
<div class="section" id="dds_03_0042__section1039212672714"><h4 class="sectiontitle">Restoration Precautions</h4><ul id="dds_03_0042__ul18422104415358"><li id="dds_03_0042__li16422204473519">When you restore the DB instance from a backup file, a full backup file is downloaded from OBS and then restored to the DB instance at an average speed of 40 MB/s.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="dds_03_0042__section730153355516"><h4 class="sectiontitle">Method 1</h4><ol id="dds_03_0042__ol13021633195518"><li id="dds_03_0042__li1370714260281"><span><a href="dds_02_0043.html">Log in to the DDS console.</a></span></li><li id="dds_03_0042__li1467205216550"><span>On the <strong id="dds_03_0042__b9753155263912">Instance Management</strong> page, click the target cluster instance.</span></li><li id="dds_03_0042__li1448536633"><span>In the navigation pane on the left, click <span class="uicontrol" id="dds_03_0042__uicontrol12794185410396"><b>Backups & Restorations</b></span>.</span></li><li id="dds_03_0042__li124692052105512"><span>On the <strong id="dds_03_0042__b84235270695954">Backups & Restorations</strong> page, locate the target backup and click <strong id="dds_03_0042__b84235270610031">Restore</strong> in the <strong id="dds_03_0042__b842352706162543">Operation</strong> column.</span></li><li id="dds_03_0042__li831613345514"><span>Select either of the following restoration methods and click <strong id="dds_03_0042__b1263063112417">OK</strong>.</span><p><ul id="dds_03_0042__ul63176338558"><li id="dds_03_0042__li1231773385512">Create New Instance<p id="dds_03_0042__p231863355512"><a name="dds_03_0042__li1231773385512"></a><a name="li1231773385512"></a>The <strong id="dds_03_0042__b785285157134352">Create New Instance</strong> page is displayed for you to create a DB instance using the backup data. The new DB instance is independent from the original one.</p>
|
||||
<ul id="dds_03_0042__ul113192331551"><li id="dds_03_0042__li265707132412">The database type, DB instance type, compatible MongoDB version, storage engine, storage type, and shard quantity must be the same as those of the original and cannot be changed.</li><li id="dds_03_0042__li15260547183511">The number of mongos nodes is 2 by default and ranges from 2 to 32. You can specify the quantity.</li><li id="dds_03_0042__li11323333155515">The storage space is the same as that of the original instance by default. You can only increase the storage space.</li><li id="dds_03_0042__li1032733365511">Other settings have default values and can be modified. For details, see section <a href="en-us_topic_0044018333.html">Creating a Cluster Instance</a>.</li></ul>
|
||||
<ul id="dds_03_0042__ul113192331551"><li id="dds_03_0042__li265707132412">The database type, DB instance type, compatible MongoDB version, storage engine, storage type, and shard quantity must be the same as those of the original and cannot be changed.</li><li id="dds_03_0042__li15260547183511">The number of dds mongos nodes is 2 by default and ranges from 2 to 32. You can specify the quantity.</li><li id="dds_03_0042__li11323333155515">The storage space is the same as that of the original instance by default. You can only increase the storage space.</li><li id="dds_03_0042__li1032733365511">Other settings have default values and can be modified. For details, see section <a href="en-us_topic_0044018333.html">Creating a Cluster Instance</a>.</li></ul>
|
||||
</li><li id="dds_03_0042__li1333013314556">Restore to Original<div class="notice" id="dds_03_0042__note1433133317555"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><ul id="dds_03_0042__ul1788224124220"><li id="dds_03_0042__li287102418427">Restoring to the original DB instance will overwrite all existing data and the DB instance will be temporarily unavailable during the restoration.</li><li id="dds_03_0042__li187182420429">The administrator password of the database instance remains unchanged after the restoration.</li><li id="dds_03_0042__li1572152117260">If IP address is enabled both for the shards and config, the related password has to be changed for both of them.</li></ul>
|
||||
</div></div>
|
||||
</li></ul>
|
||||
@ -15,7 +15,7 @@
|
||||
<div class="section" id="dds_03_0042__section494701373510"><h4 class="sectiontitle">Method 2</h4><ol id="dds_03_0042__o294a3f1667454757ae89c4cc2cb2f68c"><li id="dds_03_0042__li10914348172811"><span><a href="dds_02_0043.html">Log in to the DDS console.</a></span></li><li id="dds_03_0042__li13270015417"><span>In the navigation pane on the left, click <span class="uicontrol" id="dds_03_0042__uicontrol753861384715"><b>Backup Management</b></span>.</span></li><li id="dds_03_0042__li17813133313618"><span>On the <strong id="dds_03_0042__b133291400">Backup Management</strong> page, locate the target backup on the <strong id="dds_03_0042__b19161101481919">Clusters</strong> tab and click <span class="uicontrol" id="dds_03_0042__uicontrol0537439164719"><b>Restore</b></span> in the <strong id="dds_03_0042__b1900982919">Operation</strong> column.</span><p><ul id="dds_03_0042__ul1953385217127"><li id="dds_03_0042__li45337523127">If you use an automated backup, go to <a href="#dds_03_0042__l02b85d494b33478aa0354867be338dda">4</a>.</li><li id="dds_03_0042__li19533352111213">If you use a manual backup, check whether the original instance of the manual backup exists:<ul id="dds_03_0042__ul3533052191218"><li id="dds_03_0042__li2533205218129">If so, then go to <a href="#dds_03_0042__l02b85d494b33478aa0354867be338dda">4</a>.</li><li id="dds_03_0042__li9533175261210">If not, then you can only restore the backup to a new DB instance. Go to <a href="#dds_03_0042__li969750316413">Create New Instance</a> step under <a href="#dds_03_0042__l02b85d494b33478aa0354867be338dda">4</a>.</li></ul>
|
||||
</li></ul>
|
||||
</p></li><li id="dds_03_0042__l02b85d494b33478aa0354867be338dda"><a name="dds_03_0042__l02b85d494b33478aa0354867be338dda"></a><a name="l02b85d494b33478aa0354867be338dda"></a><span>Select either of the following restoration methods and click <strong id="dds_03_0042__b3746148162312">OK</strong>.</span><p><ul id="dds_03_0042__ul5144714316413"><li id="dds_03_0042__li969750316413"><a name="dds_03_0042__li969750316413"></a><a name="li969750316413"></a>Create New Instance<p id="dds_03_0042__dds_03_0042_p231863355512"><a name="dds_03_0042__li969750316413"></a><a name="li969750316413"></a>The <strong id="dds_03_0042__dds_03_0042_b785285157134352">Create New Instance</strong> page is displayed for you to create a DB instance using the backup data. The new DB instance is independent from the original one.</p>
|
||||
<ul id="dds_03_0042__dds_03_0042_ul113192331551"><li id="dds_03_0042__dds_03_0042_li265707132412">The database type, DB instance type, compatible MongoDB version, storage engine, storage type, and shard quantity must be the same as those of the original and cannot be changed.</li><li id="dds_03_0042__dds_03_0042_li15260547183511">The number of mongos nodes is 2 by default and ranges from 2 to 32. You can specify the quantity.</li><li id="dds_03_0042__dds_03_0042_li11323333155515">The storage space is the same as that of the original instance by default. You can only increase the storage space.</li><li id="dds_03_0042__dds_03_0042_li1032733365511">Other settings have default values and can be modified. For details, see section <a href="en-us_topic_0044018333.html">Creating a Cluster Instance</a>.</li></ul>
|
||||
<ul id="dds_03_0042__dds_03_0042_ul113192331551"><li id="dds_03_0042__dds_03_0042_li265707132412">The database type, DB instance type, compatible MongoDB version, storage engine, storage type, and shard quantity must be the same as those of the original and cannot be changed.</li><li id="dds_03_0042__dds_03_0042_li15260547183511">The number of dds mongos nodes is 2 by default and ranges from 2 to 32. You can specify the quantity.</li><li id="dds_03_0042__dds_03_0042_li11323333155515">The storage space is the same as that of the original instance by default. You can only increase the storage space.</li><li id="dds_03_0042__dds_03_0042_li1032733365511">Other settings have default values and can be modified. For details, see section <a href="en-us_topic_0044018333.html">Creating a Cluster Instance</a>.</li></ul>
|
||||
</li><li id="dds_03_0042__li51284314164125">Restore to Original<div class="notice" id="dds_03_0042__dds_03_0042_note1433133317555"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><ul id="dds_03_0042__dds_03_0042_ul1788224124220"><li id="dds_03_0042__dds_03_0042_li287102418427">Restoring to the original DB instance will overwrite all existing data and the DB instance will be temporarily unavailable during the restoration.</li><li id="dds_03_0042__dds_03_0042_li187182420429">The administrator password of the database instance remains unchanged after the restoration.</li><li id="dds_03_0042__dds_03_0042_li1572152117260">If IP address is enabled both for the shards and config, the related password has to be changed for both of them.</li></ul>
|
||||
</div></div>
|
||||
</li></ul>
|
||||
|
@ -2,6 +2,7 @@
|
||||
|
||||
<h1 class="topictitle1">Migrating Data</h1>
|
||||
<div id="body1483590975886"><div class="section" id="dds_03_0052__section25341248175518"><h4 class="sectiontitle"><strong id="dds_03_0052__b84235270694112">Scenarios</strong></h4><p id="dds_03_0052__p179130313313">DDS is accessible through an EIP in a public network or an ECS in a private network.</p>
|
||||
<p id="dds_03_0052__p1987917225233">DDS is compatible with MongoDB.</p>
|
||||
<p id="dds_03_0052__p6231217193316">MongoDB can export data from a database into a JSON file. Such a JSON file can then be used to import the data to MongoDB databases. This section describes how to import the data from the JSON files to DDS using the mongoimport tool on the ECS or from some other devices that can access DDS.</p>
|
||||
</div>
|
||||
<div class="section" id="dds_03_0052__section8361919133059"><h4 class="sectiontitle"><strong id="dds_03_0052__b1953218375354">Prerequisites</strong></h4><ol id="dds_03_0052__ol2066643918543"><li id="dds_03_0052__li4066879018543">An ECS or a device that can access DDS is ready for use.<ul id="dds_03_0052__ul1290878172911"><li id="dds_03_0052__li0324616723">To connect your DDS DB instance through a private network:<p id="dds_03_0052__p128286417211"><a name="dds_03_0052__li0324616723"></a><a name="li0324616723"></a>Create and log in to an ECS. For details, see "Creating and Logging In to a Windows ECS" or "Creating and Logging In to a Linux ECS" in the <em id="dds_03_0052__i382815413216">Elastic Cloud Server User Guide</em>.</p>
|
||||
@ -18,7 +19,7 @@
|
||||
<p id="dds_03_0052__p3262912019332">Enter the database administrator password when prompted:</p>
|
||||
<pre class="screen" id="dds_03_0052__screen12074070144047">Enter password:</pre>
|
||||
<p id="dds_03_0052__p64501241172158">The following is an example. After the command is executed, the <strong id="dds_03_0052__b842352706125455">exportfile.json</strong> file will be generated:</p>
|
||||
<p id="dds_03_0052__p1113995103829"><strong id="dds_03_0052__b1751311417223">mongoexport --host 192.168.1.21 --port 8635 --ssl --sslAllowInvalidCertificates --type json --authenticationDatabase admin -u rwuser --db test02 --collection Test --out /tmp/mongodb/export/exportfile.json</strong></p>
|
||||
<p id="dds_03_0052__p1113995103829"><strong id="dds_03_0052__b1751311417223">mongoexport --host 192.168.1.21 --port 8635 --ssl --sslAllowInvalidCertificates --type json --authenticationDatabase admin -u rwuser --db test02 --collection Test --out /tmp/***/export/exportfile.json</strong></p>
|
||||
</p></li><li id="dds_03_0052__li5438645142216"><span>Check the result.</span><p><p id="dds_03_0052__p1043914456224">If information similar to the following is displayed, the data is successfully exported. <strong id="dds_03_0052__b842352706165959">x</strong> indicates the number of exported data records.</p>
|
||||
<pre class="screen" id="dds_03_0052__screen643917454228">exported x records</pre>
|
||||
</p></li><li id="dds_03_0052__li920101610480"><span>Compress the exported .json file.</span><p><p id="dds_03_0052__p15952100131610"><strong id="dds_03_0052__b1417981014599">gzip exportfile.json</strong></p>
|
||||
@ -36,7 +37,7 @@
|
||||
<p id="dds_03_0052__p97276105334">Enter the database administrator password when prompted:</p>
|
||||
<pre class="screen" id="dds_03_0052__screen4226648614415">Enter password:</pre>
|
||||
<p id="dds_03_0052__p372722118456">The following is an example:</p>
|
||||
<p id="dds_03_0052__p822259510380"><strong id="dds_03_0052__b5082800817258">mongoimport --host 192.168.1.21 --port 8635 --ssl --sslAllowInvalidCertificates --type json --authenticationDatabase admin -u rwuser --db test02 --collection Test --file /tmp/mongodb/export/exportfile.json</strong></p>
|
||||
<p id="dds_03_0052__p822259510380"><strong id="dds_03_0052__b5082800817258">mongoimport --host 192.168.1.21 --port 8635 --ssl --sslAllowInvalidCertificates --type json --authenticationDatabase admin -u rwuser --db test02 --collection Test --file /tmp/***/export/exportfile.json</strong></p>
|
||||
</p></li><li id="dds_03_0052__li6390418685132"><span>Check the result.</span><p><p id="dds_03_0052__p53979779102325">If information similar to the following is displayed, the data is successfully imported. <strong id="dds_03_0052__b670496285">x</strong> indicates the number of imported data records.</p>
|
||||
<pre class="screen" id="dds_03_0052__screen4571661618329">imported x records</pre>
|
||||
</p></li></ol>
|
||||
|
@ -36,7 +36,7 @@
|
||||
<tr id="dds_change_history__row182910246322"><td class="cellrowborder" valign="top" width="24.62%" headers="mcps1.3.1.1.3.1.1 "><p id="dds_change_history__p19969113115327">2022-03-29</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75.38%" headers="mcps1.3.1.1.3.1.2 "><p id="dds_change_history__p19969123113326">Modified the following content:</p>
|
||||
<ul id="dds_change_history__ul199691031143210"><li id="dds_change_history__li096933112321">Modified the shard and mongos specifications in sections <a href="dds_01_0024.html#dds_01_0024__section87233314314">Cluster</a></li><li id="dds_change_history__li29691531153212">Added the description of adding or deleting tags in sections <a href="dds_03_0029.html">Key Operations Recorded by CTS</a></li></ul>
|
||||
<ul id="dds_change_history__ul199691031143210"><li id="dds_change_history__li096933112321">Modified the shard and dds mongos specifications in sections <a href="dds_01_0024.html#dds_01_0024__section87233314314">Cluster</a></li><li id="dds_change_history__li29691531153212">Added the description of adding or deleting tags in sections <a href="dds_03_0029.html">Key Operations Recorded by CTS</a></li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="dds_change_history__row1331435561414"><td class="cellrowborder" valign="top" width="24.62%" headers="mcps1.3.1.1.3.1.1 "><p id="dds_change_history__p1431595519149">2022-03-22</p>
|
||||
@ -82,7 +82,7 @@
|
||||
<tr id="dds_change_history__row835515031715"><td class="cellrowborder" valign="top" width="24.62%" headers="mcps1.3.1.1.3.1.1 "><p id="dds_change_history__p379319352152">2020-10-15</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75.38%" headers="mcps1.3.1.1.3.1.2 "><p id="dds_change_history__p12056317564">Modified the following content:</p>
|
||||
<ul id="dds_change_history__ul1280913212525"><li id="dds_change_history__li127931635161515">Supported a maximum of 20 tags for each instance in sections <a href="en-us_topic_0044018333.html">Creating a Cluster Instance</a>, <a href="dds_02_0012.html">Creating a Replica Set Instance</a>, and <a href="dds_03_0023.html">Tag Management</a>.</li><li id="dds_change_history__li1979383591510">Supported a maximum of 16 mongos and 16 shards in a cluster instance in sections <a href="dds_01_0011.html">Cluster</a>, <a href="dds_01_0002.html">Cluster</a>, <a href="en-us_topic_0044018333.html">Creating a Cluster Instance</a>, and <a href="en-us_topic_increase_nodes.html">Adding Nodes to a Cluster</a>.</li><li id="dds_change_history__li17931635131510">Optimized the procedures based on the Connections tab in sections <a href="dds_02_0046.html">Binding an EIP</a>, <a href="dds_02_0053.html">Binding an EIP</a>, <a href="dds_03_0074.html">Enabling or Disabling SSL</a>, <a href="dds_03_change_database_port.html">Changing the Database Port</a>, and <a href="dds_03_change_security_group.html">Changing a Security Group</a>.</li></ul>
|
||||
<ul id="dds_change_history__ul1280913212525"><li id="dds_change_history__li127931635161515">Supported a maximum of 20 tags for each instance in sections <a href="en-us_topic_0044018333.html">Creating a Cluster Instance</a>, <a href="dds_02_0012.html">Creating a Replica Set Instance</a>, and <a href="dds_03_0023.html">Tag Management</a>.</li><li id="dds_change_history__li1979383591510">Supported a maximum of 16 dds mongos and 16 shards in a cluster instance in sections <a href="dds_01_0011.html">Cluster</a>, <a href="dds_01_0002.html">Cluster</a>, <a href="en-us_topic_0044018333.html">Creating a Cluster Instance</a>, and <a href="en-us_topic_increase_nodes.html">Adding Nodes to a Cluster</a>.</li><li id="dds_change_history__li17931635131510">Optimized the procedures based on the Connections tab in sections <a href="dds_02_0046.html">Binding an EIP</a>, <a href="dds_02_0053.html">Binding an EIP</a>, <a href="dds_03_0074.html">Enabling or Disabling SSL</a>, <a href="dds_03_change_database_port.html">Changing the Database Port</a>, and <a href="dds_03_change_security_group.html">Changing a Security Group</a>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="dds_change_history__row11202141812389"><td class="cellrowborder" valign="top" width="24.62%" headers="mcps1.3.1.1.3.1.1 "><p id="dds_change_history__p9795153514158">2019-11-07</p>
|
||||
@ -182,7 +182,7 @@
|
||||
<td class="cellrowborder" valign="top" width="75.38%" headers="mcps1.3.1.1.3.1.2 "><p id="dds_change_history__p1240111318290">Added the following content:</p>
|
||||
<ul id="dds_change_history__ul1740191382917"><li id="dds_change_history__li74031319292"><a href="dds_01_0012.html">Replica Set</a></li><li id="dds_change_history__li140171372916"><a href="dds_02_0012.html">Creating a Replica Set Instance</a></li><li id="dds_change_history__li1940161352919"><a href="dds_03_0043.html">Restoring a Replica Set Instance from a Backup</a></li><li id="dds_change_history__li154141312912"><a href="dds_faq_0006.html">What Is the Time Delay for Primary/Secondary Synchronization in a Replica Set?</a></li><li id="dds_change_history__li441613192912"><a href="dds_03_0023.html">Tag Management</a></li></ul>
|
||||
<p id="dds_change_history__p1141161382917">Modified the following content:</p>
|
||||
<ul id="dds_change_history__ul741121372915"><li id="dds_change_history__li124171352914">Supported the creation of the replica set DB instance in sections <a href="dds_03_0075.html">Changing a DB Instance Name</a>, <a href="dds_03_0003.html">Restarting a DB Instance or a Node</a>, <a href="dds_03_0004.html">Deleting a DB Instance</a>, <a href="en-us_topic_backup_restore.html">Setting Automated Backup Policy</a>, <a href="dds_03_0007.html">Creating a Manual Backup</a>, <a href="dds_03_0008.html">Deleting a Manual Backup</a>, <a href="dds_03_0009.html">Deleting an Automated Backup</a>, <a href="en-us_topic_increase_storage.html">Scaling Up Storage Space</a>, <a href="dds_03_0019.html">Connection Management</a>, and <a href="dds_03_0026.html">DDS Metrics</a>.</li><li id="dds_change_history__li14411413202918">Supported disk encryption in sections <a href="en-us_topic_0044018333.html">Creating a Cluster Instance</a> and <a href="dds_02_0012.html">Creating a Replica Set Instance</a>.</li><li id="dds_change_history__li6428136294">Changed the length of the instance name to 4 to 64 characters in sections <a href="en-us_topic_0044018333.html">Creating a Cluster Instance</a>, <a href="dds_02_0012.html">Creating a Replica Set Instance</a>, and <a href="dds_03_0075.html">Changing a DB Instance Name</a>.</li><li id="dds_change_history__li54211312917">Supported the batch querying of error logs of all nodes, all mongos, all shards, and all configs of a cluster instance and supported the querying of error logs of all nodes of a replica set instance in section <a href="en-us_topic_error_log.html">Error Log</a>.</li><li id="dds_change_history__li104241372910">Supported the batch querying of slow query logs of all nodes of a replica set instance in section <a href="en-us_topic_slow_query_log.html">Slow Query Log</a>.</li></ul>
|
||||
<ul id="dds_change_history__ul741121372915"><li id="dds_change_history__li124171352914">Supported the creation of the replica set DB instance in sections <a href="dds_03_0075.html">Changing a DB Instance Name</a>, <a href="dds_03_0003.html">Restarting a DB Instance or a Node</a>, <a href="dds_03_0004.html">Deleting a DB Instance</a>, <a href="en-us_topic_backup_restore.html">Setting Automated Backup Policy</a>, <a href="dds_03_0007.html">Creating a Manual Backup</a>, <a href="dds_03_0008.html">Deleting a Manual Backup</a>, <a href="dds_03_0009.html">Deleting an Automated Backup</a>, <a href="en-us_topic_increase_storage.html">Scaling Up Storage Space</a>, <a href="dds_03_0019.html">Connection Management</a>, and <a href="dds_03_0026.html">DDS Metrics</a>.</li><li id="dds_change_history__li14411413202918">Supported disk encryption in sections <a href="en-us_topic_0044018333.html">Creating a Cluster Instance</a> and <a href="dds_02_0012.html">Creating a Replica Set Instance</a>.</li><li id="dds_change_history__li6428136294">Changed the length of the instance name to 4 to 64 characters in sections <a href="en-us_topic_0044018333.html">Creating a Cluster Instance</a>, <a href="dds_02_0012.html">Creating a Replica Set Instance</a>, and <a href="dds_03_0075.html">Changing a DB Instance Name</a>.</li><li id="dds_change_history__li54211312917">Supported the batch querying of error logs of all nodes, all dds mongos, all shards, and all configs of a cluster instance and supported the querying of error logs of all nodes of a replica set instance in section <a href="en-us_topic_error_log.html">Error Log</a>.</li><li id="dds_change_history__li104241372910">Supported the batch querying of slow query logs of all nodes of a replica set instance in section <a href="en-us_topic_slow_query_log.html">Slow Query Log</a>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="dds_change_history__row081373520151"><td class="cellrowborder" valign="top" width="24.62%" headers="mcps1.3.1.1.3.1.1 "><p id="dds_change_history__p881353551517">2018-07-03</p>
|
||||
|
@ -2,7 +2,7 @@
|
||||
|
||||
<h1 class="topictitle1">What Is the Number of DDS Database Connections?</h1>
|
||||
<div id="body1482404620316"><p id="dds_faq_0012__p056318351337">The number of connections indicates the number of applications that can be simultaneously connected to the database. The number of connections is irrelevant to the maximum number of users allowed by your applications or websites.</p>
|
||||
<ul id="dds_faq_0012__ul1732973417514"><li id="dds_faq_0012__li15329334858">For a cluster instance, the number of connections indicates the number of connections between the client and the mongos.</li><li id="dds_faq_0012__li132983411519">For a replica set instance, the number of connections indicates the number of connections between the client and the primary and secondary nodes.</li><li id="dds_faq_0012__li183298347516">For a single-node instance, the number of connections indicates the number of connections between the client and the node.</li></ul>
|
||||
<ul id="dds_faq_0012__ul1732973417514"><li id="dds_faq_0012__li15329334858">For a cluster instance, the number of connections indicates the number of connections between the client and the dds mongos.</li><li id="dds_faq_0012__li132983411519">For a replica set instance, the number of connections indicates the number of connections between the client and the primary and secondary nodes.</li><li id="dds_faq_0012__li183298347516">For a single-node instance, the number of connections indicates the number of connections between the client and the node.</li></ul>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
|
Before Width: | Height: | Size: 12 KiB |
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 14 KiB |
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 14 KiB |
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 15 KiB |
Before Width: | Height: | Size: 15 KiB |
BIN
docs/dds/umn/en-us_image_0000001845343652.png
Normal file
After Width: | Height: | Size: 16 KiB |
BIN
docs/dds/umn/en-us_image_0000001891581965.png
Normal file
After Width: | Height: | Size: 18 KiB |
@ -34,7 +34,7 @@
|
||||
<tr id="en-us_topic_0044018333__row1013512731419"><td class="cellrowborder" valign="top" width="26%" headers="mcps1.3.2.2.3.2.1.2.3.1.1 "><p id="en-us_topic_0044018333__p151351316101415">DB Instance Type</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="74%" headers="mcps1.3.2.2.3.2.1.2.3.1.2 "><p id="en-us_topic_0044018333__p0135181618149">Select <strong id="en-us_topic_0044018333__b842352706152955">Cluster</strong>.</p>
|
||||
<p id="en-us_topic_0044018333__p11135716181417">A cluster instance includes three types of nodes: mongos, shard, and config. Each shard and config is a three-node replica set to ensure high availability.</p>
|
||||
<p id="en-us_topic_0044018333__p11135716181417">A cluster instance includes three types of nodes: dds mongos, shard, and config. Each shard and config is a three-node replica set to ensure high availability.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="en-us_topic_0044018333__row1024495916243"><td class="cellrowborder" valign="top" width="26%" headers="mcps1.3.2.2.3.2.1.2.3.1.1 "><p id="en-us_topic_0044018333__p2453532616243">Compatible MongoDB Version</p>
|
||||
@ -50,7 +50,7 @@
|
||||
<tr id="en-us_topic_0044018333__row319181316237"><td class="cellrowborder" valign="top" width="26%" headers="mcps1.3.2.2.3.2.1.2.3.1.1 "><p id="en-us_topic_0044018333__p1672886816349">Storage Engine</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="74%" headers="mcps1.3.2.2.3.2.1.2.3.1.2 "><ul id="en-us_topic_0044018333__ul109418294235"><li id="en-us_topic_0044018333__li8942142922318">WiredTiger<p id="en-us_topic_0044018333__p11175126192414"><a name="en-us_topic_0044018333__li8942142922318"></a><a name="li8942142922318"></a>WiredTiger is the default storage engine of DDS 3.2, 3.4 and 4.0. WiredTiger provides different granularity concurrency control and compression mechanism for data management. It can provide the best performance and storage efficiency for different kinds of applications.</p>
|
||||
</li><li id="en-us_topic_0044018333__li19723447162416">RocksDB<p id="en-us_topic_0044018333__p3871944172517"><a name="en-us_topic_0044018333__li19723447162416"></a><a name="li19723447162416"></a>RocksDB is the default storage engine of DDS 4.2 and 4.4. RocksDB supports efficient point lookup, range scan, and high-speed write. RocksDB can be used as the underlying data storage engine of MongoDB and is suitable for scenarios with a large number of write operations.</p>
|
||||
</li><li id="en-us_topic_0044018333__li19723447162416">RocksDB<p id="en-us_topic_0044018333__p3871944172517"><a name="en-us_topic_0044018333__li19723447162416"></a><a name="li19723447162416"></a>RocksDB is the default storage engine of DDS 4.2 and 4.4. RocksDB supports efficient point lookup, range scan, and high-speed write. RocksDB can be used as the underlying data storage engine of DDS and is suitable for scenarios with a large number of write operations.</p>
|
||||
</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
@ -63,7 +63,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="74%" headers="mcps1.3.2.2.3.2.1.2.3.1.2 "><ul id="en-us_topic_0044018333__ul133881550588"><li id="en-us_topic_0044018333__li2388145105810"><strong id="en-us_topic_0044018333__b842352706102944">Disabled</strong>: Disable the encryption function.</li><li id="en-us_topic_0044018333__li52191547135210"><strong id="en-us_topic_0044018333__b150747644695932">Enabled</strong>: Enable encryption. This feature improves data security but slightly affects read/write performance.<p id="en-us_topic_0044018333__p172191947135211"><strong id="en-us_topic_0044018333__b54342102195932">Key Name</strong>: Select or create a private key, which is the tenant key.</p>
|
||||
</li></ul>
|
||||
<div class="note" id="en-us_topic_0044018333__note2431518191315"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="en-us_topic_0044018333__ul1362121393110"><li id="en-us_topic_0044018333__li1156124454620">After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.</li><li id="en-us_topic_0044018333__li845663616343">To check whether the disk is encrypted, you can view <strong id="en-us_topic_0044018333__b21996298184">Disk Encrypted</strong> in the DB instance list.</li><li id="en-us_topic_0044018333__li16886718103912">If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.</li><li id="en-us_topic_0044018333__li1660761315330">For details about how to create a key, see the "Creating a CMK" section in the <em id="en-us_topic_0044018333__i84235269720595">Key Management Service User Guide</em>.</li></ul>
|
||||
<div class="note" id="en-us_topic_0044018333__note2431518191315"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="en-us_topic_0044018333__ul1362121393110"><li id="en-us_topic_0044018333__li1156124454620">After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.</li><li id="en-us_topic_0044018333__li1799163511214">Backups of cluster instances are physical backups. If disk encryption is enabled, backup data will be encrypted.</li><li id="en-us_topic_0044018333__li845663616343">To check whether the disk is encrypted, you can view <strong id="en-us_topic_0044018333__b21996298184">Disk Encrypted</strong> in the DB instance list.</li><li id="en-us_topic_0044018333__li16886718103912">If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.</li><li id="en-us_topic_0044018333__li1660761315330">For details about how to create a key, see the "Creating a CMK" section in the <em id="en-us_topic_0044018333__i84235269720595">Key Management Service User Guide</em>.</li></ul>
|
||||
</div></div>
|
||||
</td>
|
||||
</tr>
|
||||
@ -77,19 +77,19 @@
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="en-us_topic_0044018333__row26958383161127"><td class="cellrowborder" valign="top" width="28.999999999999996%" headers="mcps1.3.2.2.3.2.2.2.3.1.1 "><p id="en-us_topic_0044018333__p17841537161129">mongos node class</p>
|
||||
<tbody><tr id="en-us_topic_0044018333__row26958383161127"><td class="cellrowborder" valign="top" width="28.999999999999996%" headers="mcps1.3.2.2.3.2.2.2.3.1.1 "><p id="en-us_topic_0044018333__p17841537161129">dds mongos node class</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="71%" headers="mcps1.3.2.2.3.2.2.2.3.1.2 "><p id="en-us_topic_0044018333__p8316353151114">For details about the mongos CPU and memory, see section <a href="dds_01_0024.html">DB Instance Specifications</a>. After a DB instance is created, you can change its CPU and memory. For details, see section <a href="en-us_topic_0104472218.html">Changing a Cluster DB Instance Class</a>.</p>
|
||||
<td class="cellrowborder" valign="top" width="71%" headers="mcps1.3.2.2.3.2.2.2.3.1.2 "><p id="en-us_topic_0044018333__p8316353151114">For details about the dds mongos CPU and memory, see section <a href="dds_01_0024.html">DB Instance Specifications</a>. After a DB instance is created, you can change its CPU and memory. For details, see section <a href="en-us_topic_0104472218.html">Changing a Cluster DB Instance Class</a>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="en-us_topic_0044018333__row66640864173420"><td class="cellrowborder" valign="top" width="28.999999999999996%" headers="mcps1.3.2.2.3.2.2.2.3.1.1 "><p id="en-us_topic_0044018333__p44330033173420">mongos nodes</p>
|
||||
<tr id="en-us_topic_0044018333__row66640864173420"><td class="cellrowborder" valign="top" width="28.999999999999996%" headers="mcps1.3.2.2.3.2.2.2.3.1.1 "><p id="en-us_topic_0044018333__p44330033173420">dds mongos nodes</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="71%" headers="mcps1.3.2.2.3.2.2.2.3.1.2 "><p id="en-us_topic_0044018333__p1202224316210">The number of mongos nodes. The value ranges from 2 to 32. After a DB instance is created, you can add mongos nodes if necessary. For details, see section <a href="en-us_topic_increase_nodes.html">Adding Nodes to a Cluster</a>.</p>
|
||||
<td class="cellrowborder" valign="top" width="71%" headers="mcps1.3.2.2.3.2.2.2.3.1.2 "><p id="en-us_topic_0044018333__p1202224316210">The number of dds mongos nodes. The value ranges from 2 to 32. After a DB instance is created, you can add dds mongos nodes if necessary. For details, see section <a href="en-us_topic_increase_nodes.html">Adding Nodes to a Cluster</a>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="en-us_topic_0044018333__row4199175144117"><td class="cellrowborder" valign="top" width="28.999999999999996%" headers="mcps1.3.2.2.3.2.2.2.3.1.1 "><p id="en-us_topic_0044018333__p1019925110415">mongos parameter template</p>
|
||||
<tr id="en-us_topic_0044018333__row4199175144117"><td class="cellrowborder" valign="top" width="28.999999999999996%" headers="mcps1.3.2.2.3.2.2.2.3.1.1 "><p id="en-us_topic_0044018333__p1019925110415">dds mongos parameter template</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="71%" headers="mcps1.3.2.2.3.2.2.2.3.1.2 "><p id="en-us_topic_0044018333__p683830114214">The parameters that apply to the mongos nodes. After a DB instance is created, you can change the parameter template of a node to bring out the best performance.</p>
|
||||
<td class="cellrowborder" valign="top" width="71%" headers="mcps1.3.2.2.3.2.2.2.3.1.2 "><p id="en-us_topic_0044018333__p683830114214">The parameters that apply to the dds mongos nodes. After a DB instance is created, you can change the parameter template of a node to bring out the best performance.</p>
|
||||
<p id="en-us_topic_0044018333__p109814306422">For details, see <a href="en-us_topic_configuration.html">Modifying a Parameter Template</a>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
@ -26,7 +26,7 @@
|
||||
<pre class="screen" id="en-us_topic_0044018334__screen1055614111419">Enter password:</pre>
|
||||
</li><li id="en-us_topic_0044018334__li1055161412145">Method 2: Using standard URI format.<p id="en-us_topic_0044018334__p356111491415"><a name="en-us_topic_0044018334__li1055161412145"></a><a name="li1055161412145"></a><strong id="en-us_topic_0044018334__b756121413144">mong</strong><strong id="en-us_topic_0044018334__b185610147147">o m</strong><strong id="en-us_topic_0044018334__b15561314181417">ongodb://rwuser:<password>@</strong><em id="en-us_topic_0044018334__i156161461415"><</em><em id="en-us_topic_0044018334__i10568142148">DB_HOST</em><em id="en-us_topic_0044018334__i556171481419">></em><strong id="en-us_topic_0044018334__b95661421412">:</strong><em id="en-us_topic_0044018334__i16561148141"><</em><em id="en-us_topic_0044018334__i13561314151416">DB_PORT</em><em id="en-us_topic_0044018334__i135616141143">></em><strong id="en-us_topic_0044018334__b856131461418">,</strong><em id="en-us_topic_0044018334__i556111411147"><</em><em id="en-us_topic_0044018334__i55615142148">DB_HOST</em><em id="en-us_topic_0044018334__i1756161421419">></em><strong id="en-us_topic_0044018334__b9562147149">:</strong><em id="en-us_topic_0044018334__i95621441414"><</em><em id="en-us_topic_0044018334__i75617141141">DB_PORT</em><em id="en-us_topic_0044018334__i35614141148">></em><strong id="en-us_topic_0044018334__b1757014181417">/test?authSource=admin</strong> <strong id="en-us_topic_0044018334__b115717144143">--ssl --sslCAFile</strong> <em id="en-us_topic_0044018334__i11571614161417"><</em><em id="en-us_topic_0044018334__i65791441419">FILE_PATH</em><em id="en-us_topic_0044018334__i0577142141">></em> <strong id="en-us_topic_0044018334__b18571914191418">--sslAllowInvalidHostnames</strong></p>
|
||||
<p id="en-us_topic_0044018334__p15541153864316">The connection information can be obtained in the <span class="uicontrol" id="en-us_topic_0044018334__uicontrol193163119165"><b>Address</b></span> column on the <span class="uicontrol" id="en-us_topic_0044018334__uicontrol46471843163"><b>Instance Management</b></span> page.</p>
|
||||
<p id="en-us_topic_0044018334__p15852132744319">A connection address indicates that one of the mongos nodes will be randomly connected. If you use this method to connect to a DB instance, use the MongoDB client of version later than 3.4.</p>
|
||||
<p id="en-us_topic_0044018334__p15852132744319">A connection address indicates that one of the dds mongos nodes will be randomly connected. If you use this method to connect to a DB instance, use the MongoDB client of version later than 3.4.</p>
|
||||
</li></ul>
|
||||
<div class="note" id="en-us_topic_0044018334__note1957314131416"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="en-us_topic_0044018334__ul115731415143"><li id="en-us_topic_0044018334__li558131419149"><strong id="en-us_topic_0044018334__b226713556815">DB_HOST</strong> indicates the IP address of the remotely connected DB instance. Obtain the value from the <span class="uicontrol" id="en-us_topic_0044018334__uicontrol3268155285"><b>Private IP Address</b></span> column in the node list on the <span class="uicontrol" id="en-us_topic_0044018334__uicontrol32682055989"><b>Connections</b></span> page.</li><li id="en-us_topic_0044018334__li195811411416"><strong id="en-us_topic_0044018334__b078034553719">DB_PORT</strong> indicates the port number. Obtain the value from <span class="uicontrol" id="en-us_topic_0044018334__uicontrol1478194573714"><b>Database Port</b></span> in the <span class="uicontrol" id="en-us_topic_0044018334__uicontrol1278344510379"><b>Basic Information</b></span> area on the <strong id="en-us_topic_0044018334__b13818121210417">Connections</strong> page.</li><li id="en-us_topic_0044018334__li845117911471"><strong id="en-us_topic_0044018334__b1645111915477">DB_HOST</strong> and<strong id="en-us_topic_0044018334__b11451591474"> DB_PORT</strong> can also be obtained from the Node Information area on the Basic Information page.</li><li id="en-us_topic_0044018334__li15581214101417"><strong id="en-us_topic_0044018334__b18302125815169">DB_USER</strong> indicates the database account name. The default value is <strong id="en-us_topic_0044018334__b7303155851610">rwuser</strong>.</li><li id="en-us_topic_0044018334__li3589131519216"><strong id="en-us_topic_0044018334__b14590015122110"><em id="en-us_topic_0044018334__i1959014152219"><password></em></strong> indicates the password of the database account. If the password contains at signs (@),exclamation marks (!), or percent signs (%), replace them with hexadecimal URL codes %40, %21, and %25 respectively.</li><li id="en-us_topic_0044018334__li122761750202211">If user inputs this command then the password will be stored in logfiles and can be found in linux history, and in process list. So please note that plaintext passwords are risky.</li><li id="en-us_topic_0044018334__li85813148148"><strong id="en-us_topic_0044018334__b84235270618026">FILE_PATH</strong> indicates the path where the root certificate is stored.</li></ul>
|
||||
</div></div>
|
||||
@ -43,7 +43,7 @@
|
||||
<pre class="screen" id="en-us_topic_0044018334__screen9370437195515">Enter password:</pre>
|
||||
</li><li id="en-us_topic_0044018334__li122297367491"><a name="en-us_topic_0044018334__li122297367491"></a><a name="li122297367491"></a>Method 2: Using standard URI format<p id="en-us_topic_0044018334__p1861164210158"><a name="en-us_topic_0044018334__li122297367491"></a><a name="li122297367491"></a><strong id="en-us_topic_0044018334__b090483712147">mongo</strong> <strong id="en-us_topic_0044018334__b3904123701413">mongodb://rwuser:</strong><password><strong id="en-us_topic_0044018334__b1390853716141">@</strong><em id="en-us_topic_0044018334__i5911183761412"><</em><em id="en-us_topic_0044018334__i991283712146">DB_HOST</em><em id="en-us_topic_0044018334__i13913133717149">1></em><strong id="en-us_topic_0044018334__b6913173715142">:</strong><em id="en-us_topic_0044018334__i159187377147"><</em><em id="en-us_topic_0044018334__i1591913701417">DB_PORT</em><em id="en-us_topic_0044018334__i177921824195911">1></em><strong id="en-us_topic_0044018334__b779302416597">,</strong><em id="en-us_topic_0044018334__i479292405917"><em id="en-us_topic_0044018334__i7792224185910"><</em><em id="en-us_topic_0044018334__i19792152416599">DB_HOST</em><em id="en-us_topic_0044018334__i379210249592">2></em></em><strong id="en-us_topic_0044018334__b137474463169">:</strong><em id="en-us_topic_0044018334__i117451646121616"><em id="en-us_topic_0044018334__i77451246191619"><</em><em id="en-us_topic_0044018334__i57456464163">DB_PORT</em><em id="en-us_topic_0044018334__i17745124617164">2></em></em><strong id="en-us_topic_0044018334__b4923173721411">/test?authSource=admin</strong></p>
|
||||
<p id="en-us_topic_0044018334__p1083104710171">The connection information can be obtained in the <span class="uicontrol" id="en-us_topic_0044018334__uicontrol1375182011312"><b>Address</b></span> column on the <span class="uicontrol" id="en-us_topic_0044018334__uicontrol937792093113"><b>Instance Management</b></span> page.</p>
|
||||
<p id="en-us_topic_0044018334__p1118564314176">A connection address indicates that one of the mongos nodes will be randomly connected. If you use this method to connect to a DB instance, use the MongoDB client of version later than 3.4.</p>
|
||||
<p id="en-us_topic_0044018334__p1118564314176">A connection address indicates that one of the dds mongos nodes will be randomly connected. If you use this method to connect to a DB instance, use the MongoDB client of version later than 3.4.</p>
|
||||
</li></ul>
|
||||
<div class="note" id="en-us_topic_0044018334__note21381431122218"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="en-us_topic_0044018334__ul18138931152220"><li id="en-us_topic_0044018334__li8735051125619"><strong id="en-us_topic_0044018334__b1798202832120">DB_HOST</strong> indicates the IP address of the remotely connected DB instance. Obtain the value from the <span class="uicontrol" id="en-us_topic_0044018334__uicontrol1798492892118"><b>Private IP Address</b></span> column in the node list on the <span class="uicontrol" id="en-us_topic_0044018334__uicontrol298415283213"><b>Connections</b></span> page.</li><li id="en-us_topic_0044018334__li9743125175616"><strong id="en-us_topic_0044018334__b1785319082219">DB_PORT</strong> indicates the port number. Obtain the value from <span class="uicontrol" id="en-us_topic_0044018334__uicontrol88537032216"><b>Database Port</b></span> in the <span class="uicontrol" id="en-us_topic_0044018334__uicontrol08545011223"><b>Basic Information</b></span> area on the <strong id="en-us_topic_0044018334__b1985513018225">Connections</strong> page.</li><li id="en-us_topic_0044018334__li1784422195514"><strong id="en-us_topic_0044018334__b1721511785612">DB_HOST</strong> and<strong id="en-us_topic_0044018334__b6356141555618"> DB_PORT</strong> can also be obtained from the Node Information area on the Basic Information page.</li><li id="en-us_topic_0044018334__li10747135112566"><strong id="en-us_topic_0044018334__b208201423151716">DB_USER</strong> indicates the database account name. The default value is <strong id="en-us_topic_0044018334__b48209236172">rwuser</strong>.</li><li id="en-us_topic_0044018334__li39416434266"><strong id="en-us_topic_0044018334__b1951543172615"><em id="en-us_topic_0044018334__i1595174312610"><password></em></strong> indicates the password of the database account. If the password contains at signs (@),exclamation marks (!), or percent signs (%), replace them with hexadecimal URL codes %40, %21, and %25 respectively.</li><li id="en-us_topic_0044018334__li155958442267">If user inputs this command then the password will be stored in logfiles and can be found in linux history, and in process list. So please note that plaintext passwords are risky.</li></ul>
|
||||
</div></div>
|
||||
|
@ -1,7 +1,7 @@
|
||||
<a name="en-us_topic_0104472218"></a><a name="en-us_topic_0104472218"></a>
|
||||
|
||||
<h1 class="topictitle1">Changing a Cluster DB Instance Class</h1>
|
||||
<div id="body1522320377097"><div class="section" id="en-us_topic_0104472218__section9704305161032"><h4 class="sectiontitle">Changing mongos</h4><ol id="en-us_topic_0104472218__ol42339322155159"><li id="en-us_topic_0104472218__li312682313217"><span><a href="dds_02_0043.html">Log in to the DDS console.</a></span></li><li id="en-us_topic_0104472218__li45509579155159"><span>On the <strong id="en-us_topic_0104472218__b11135124713135">Instance Management</strong> page, click the target cluster instance.</span></li><li id="en-us_topic_0104472218__li24704686155159"><span>In the <strong id="en-us_topic_0104472218__b842352706145845">Node Information</strong> area on the <strong id="en-us_topic_0104472218__b842352706183537">Basic Information</strong> page, click the <strong id="en-us_topic_0104472218__b8423527061554">mongos</strong> tab, locate the target mongos, and click <strong id="en-us_topic_0104472218__b84235270615534">Change Instance Class</strong> in the <strong id="en-us_topic_0104472218__b84235270615538">Operation</strong> column.</span></li><li id="en-us_topic_0104472218__li21015586155159"><span>On the displayed page, select the new instance class and click <strong id="en-us_topic_0104472218__b369312544116">Submit</strong>.</span></li><li id="en-us_topic_0104472218__li42784471155159"><span>View the DB instance class change result.</span><p><ul id="en-us_topic_0104472218__ul16649141214137"><li id="en-us_topic_0104472218__li2061071220412">When the CPU or memory of a DB instance is being changed, the status displayed in the <strong id="en-us_topic_0104472218__b842352706211812">Status</strong> column is <strong id="en-us_topic_0104472218__b842352706211847">Changing instance class</strong>. This process takes up to 10 minutes.</li><li id="en-us_topic_0104472218__li126101122417">In the upper right corner of the DB instance list, click <span><img id="en-us_topic_0104472218__image3272639392546" src="en-us_image_0000001095974074.png"></span> to refresh the list. The instance status changes to <strong id="en-us_topic_0104472218__b84235270615140">Available</strong>.</li><li id="en-us_topic_0104472218__li6351746133917">In the <strong id="en-us_topic_0104472218__b84235270692853">Node Information</strong> area on the <strong id="en-us_topic_0104472218__b84235270692859">Basic Information</strong> page, click the <strong id="en-us_topic_0104472218__b84235270692937">mongos</strong> tab and view the new instance class.</li></ul>
|
||||
<div id="body1522320377097"><div class="section" id="en-us_topic_0104472218__section9704305161032"><h4 class="sectiontitle">Changing dds mongos</h4><ol id="en-us_topic_0104472218__ol42339322155159"><li id="en-us_topic_0104472218__li312682313217"><span><a href="dds_02_0043.html">Log in to the DDS console.</a></span></li><li id="en-us_topic_0104472218__li45509579155159"><span>On the <strong id="en-us_topic_0104472218__b11135124713135">Instance Management</strong> page, click the target cluster instance.</span></li><li id="en-us_topic_0104472218__li24704686155159"><span>In the <strong id="en-us_topic_0104472218__b842352706145845">Node Information</strong> area on the <strong id="en-us_topic_0104472218__b842352706183537">Basic Information</strong> page, click the dds mongos tab, locate the target dds mongos, and click <strong id="en-us_topic_0104472218__b84235270615534">Change Instance Class</strong> in the <strong id="en-us_topic_0104472218__b84235270615538">Operation</strong> column.</span></li><li id="en-us_topic_0104472218__li21015586155159"><span>On the displayed page, select the new instance class and click <strong id="en-us_topic_0104472218__b369312544116">Submit</strong>.</span></li><li id="en-us_topic_0104472218__li42784471155159"><span>View the DB instance class change result.</span><p><ul id="en-us_topic_0104472218__ul16649141214137"><li id="en-us_topic_0104472218__li2061071220412">When the CPU or memory of a DB instance is being changed, the status displayed in the <strong id="en-us_topic_0104472218__b842352706211812">Status</strong> column is <strong id="en-us_topic_0104472218__b842352706211847">Changing instance class</strong>. This process takes up to 10 minutes.</li><li id="en-us_topic_0104472218__li126101122417">In the upper right corner of the DB instance list, click <span><img id="en-us_topic_0104472218__image3272639392546" src="en-us_image_0000001095974074.png"></span> to refresh the list. The instance status changes to <strong id="en-us_topic_0104472218__b84235270615140">Available</strong>.</li><li id="en-us_topic_0104472218__li6351746133917">In the <strong id="en-us_topic_0104472218__b84235270692853">Node Information</strong> area on the <strong id="en-us_topic_0104472218__b84235270692859">Basic Information</strong> page, click the <strong id="en-us_topic_0104472218__b19241446155119">dds mongos</strong> tab and view the new instance class.</li></ul>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0104472218__section5378330161152"><h4 class="sectiontitle">Changing shard</h4><ol id="en-us_topic_0104472218__ol5947368818435"><li id="en-us_topic_0104472218__li109759343214"><span><a href="dds_02_0043.html">Log in to the DDS console.</a></span></li><li id="en-us_topic_0104472218__li55933813133123"><span>On the <strong id="en-us_topic_0104472218__b17764151613321">Instance Management</strong> page, click the target cluster instance.</span></li><li id="en-us_topic_0104472218__li45387312153631"><span>In the <strong id="en-us_topic_0104472218__b967356750">Node Information</strong> area on the <strong id="en-us_topic_0104472218__b1982618456">Basic Information</strong> page, click the <strong id="en-us_topic_0104472218__b1743717218">shard</strong> tab, locate the target shard, and click <strong id="en-us_topic_0104472218__b1976088005">Change Instance Class</strong> in the <strong id="en-us_topic_0104472218__b442274314">Operation</strong> column.</span></li><li id="en-us_topic_0104472218__lf939df2e325d47d490c6ffdacf5f0b19"><span>On the displayed page, select the new instance class and click <strong id="en-us_topic_0104472218__b819811158132">Submit</strong>.</span></li><li id="en-us_topic_0104472218__li984592715347"><span>View the DB instance class change result.</span><p><ul id="en-us_topic_0104472218__ul13215131916455"><li id="en-us_topic_0104472218__li122157197451">When the CPU or memory of a DB instance is being changed, the status displayed in the <strong id="en-us_topic_0104472218__b491762403">Status</strong> column is <strong id="en-us_topic_0104472218__b749651480">Changing instance class</strong>. This process takes up to 30 minutes.</li><li id="en-us_topic_0104472218__li13217121912450">In the upper right corner of the DB instance list, click <span><img id="en-us_topic_0104472218__en-us_topic_0104472218_image3272639392546" src="en-us_image_0000001095974074.png"></span> to refresh the list. The instance status changes to <strong id="en-us_topic_0104472218__en-us_topic_0104472218_b84235270615140">Available</strong>.</li><li id="en-us_topic_0104472218__li621913193458">Go to the <strong id="en-us_topic_0104472218__b512251629">Basic Information</strong> page of the cluster instance you scaled up, click the <strong id="en-us_topic_0104472218__b770471440">shard</strong> tab in the <strong id="en-us_topic_0104472218__b182604835394321">Node Information</strong> area, and view the new instance class.</li></ul>
|
||||
|
@ -1,7 +1,7 @@
|
||||
<a name="en-us_topic_0105284966"></a><a name="en-us_topic_0105284966"></a>
|
||||
|
||||
<h1 class="topictitle1">Connecting to a Replica Set Instance Over Private Networks</h1>
|
||||
<div id="body1522808555900"><div class="section" id="en-us_topic_0105284966__en-us_topic_0085335422_section46429645141251"><h4 class="sectiontitle">Scenarios</h4><p id="en-us_topic_0105284966__p125004821516">This section describes how to connect to a replica set instance using the MongoDB client over private networks.</p>
|
||||
<div id="body1522808555900"><div class="section" id="en-us_topic_0105284966__en-us_topic_0085335422_section46429645141251"><h4 class="sectiontitle">Scenarios</h4><p id="en-us_topic_0105284966__p125004821516">This section describes how to connect to a replica set instance using the MongoDB client over private networks.DDS is compatible with MongoDB.</p>
|
||||
<p id="en-us_topic_0105284966__p14321218172814">You can directly perform operations on the primary and secondary nodes. Primary nodes are used for processing read and write requests. Secondary nodes replicate data from the primary and are used for processing read requests only.</p>
|
||||
<p id="en-us_topic_0105284966__p69231113101918">The MongoDB client can connect to a DB instance with an unencrypted connection or an encrypted connection (SSL). To improve data transmission security, you are advised to connect to DB instances using the SSL connection.</p>
|
||||
<p id="en-us_topic_0105284966__p293321134111"><strong id="en-us_topic_0105284966__b2245193717456">Different OS scenarios</strong>: The following uses Linux <span id="en-us_topic_0105284966__text1617119144013">ECS</span><span id="en-us_topic_0105284966__text1623741213405"></span> and Window client as an example.</p>
|
||||
|
@ -3,7 +3,7 @@
|
||||
<h1 class="topictitle1">Error Log</h1>
|
||||
<div id="body1511602808166"><div class="section" id="en-us_topic_error_log__section1990143732919"><h4 class="sectiontitle"><strong id="en-us_topic_error_log__b1649848205317">Scenarios</strong></h4><p id="en-us_topic_error_log__p19638201045">DDS log management allows you to view database-level logs, including warning- and error-level logs generated during database running, which help you analyze system problems.</p>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_error_log__section772615166584"><h4 class="sectiontitle">Procedure</h4><ol id="en-us_topic_error_log__o1b3fdf74ba07459092651b245f718877"><li id="en-us_topic_error_log__li312682313217"><span><a href="dds_02_0043.html">Log in to the DDS console.</a></span></li><li id="en-us_topic_error_log__l0d6250f2f7984e1397f678c44785ee80"><span>On the <strong id="en-us_topic_error_log__b17914131144120">Instance Management</strong> page, click the target DB instance.</span></li><li id="en-us_topic_error_log__li174993116615"><span>In the navigation pane on the left, click <span class="uicontrol" id="en-us_topic_error_log__uicontrol128401113415"><b>Error Logs</b></span>.</span></li><li id="en-us_topic_error_log__lda60992a951c4b7c9d2347bb25ab1281"><span>On the displayed page, click <strong id="en-us_topic_error_log__b6571182110281">Error Logs</strong>. Then, view the log details.</span><p><ul id="en-us_topic_error_log__ul23261698104647"><li id="en-us_topic_error_log__li611316456591">For a cluster instance, you can view error logs of the mongos, shard, and config nodes.</li><li id="en-us_topic_error_log__li1598161332916">For a replica set instance, you can view the error logs of the primary, secondary, and hidden nodes.</li><li id="en-us_topic_error_log__li9469214219">For a single node instance, you can view error logs of the current node.</li><li id="en-us_topic_error_log__li292312511389">You can view up to 2,000 error logs of a specified node type, at a specified level, and within a specified period.</li></ul>
|
||||
<div class="section" id="en-us_topic_error_log__section772615166584"><h4 class="sectiontitle">Procedure</h4><ol id="en-us_topic_error_log__o1b3fdf74ba07459092651b245f718877"><li id="en-us_topic_error_log__li312682313217"><span><a href="dds_02_0043.html">Log in to the DDS console.</a></span></li><li id="en-us_topic_error_log__l0d6250f2f7984e1397f678c44785ee80"><span>On the <strong id="en-us_topic_error_log__b17914131144120">Instance Management</strong> page, click the target DB instance.</span></li><li id="en-us_topic_error_log__li174993116615"><span>In the navigation pane on the left, click <span class="uicontrol" id="en-us_topic_error_log__uicontrol128401113415"><b>Error Logs</b></span>.</span></li><li id="en-us_topic_error_log__lda60992a951c4b7c9d2347bb25ab1281"><span>On the displayed page, click <strong id="en-us_topic_error_log__b6571182110281">Error Logs</strong>. Then, view the log details.</span><p><ul id="en-us_topic_error_log__ul23261698104647"><li id="en-us_topic_error_log__li611316456591">For a cluster instance, you can view error logs of the dds mongos, shard, and config nodes.</li><li id="en-us_topic_error_log__li1598161332916">For a replica set instance, you can view the error logs of the primary, secondary, and hidden nodes.</li><li id="en-us_topic_error_log__li9469214219">For a single node instance, you can view error logs of the current node.</li><li id="en-us_topic_error_log__li292312511389">You can view up to 2,000 error logs of a specified node type, at a specified level, and within a specified period.</li></ul>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
|
@ -3,10 +3,10 @@
|
||||
<h1 class="topictitle1">Adding Nodes to a Cluster </h1>
|
||||
<div id="body5174319"><div class="section" id="en-us_topic_increase_nodes__section34286219201027"><h4 class="sectiontitle"><strong id="en-us_topic_increase_nodes__b84235270694112">Scenarios</strong></h4><p id="en-us_topic_increase_nodes__p56118182112321">This section describes how to add nodes to a cluster instance.</p>
|
||||
</div>
|
||||
<div class="note" id="en-us_topic_increase_nodes__note2200417585627"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="en-us_topic_increase_nodes__ul898913115493"><li id="en-us_topic_increase_nodes__li10988113110497">You can add nodes when the instance status is <strong id="en-us_topic_increase_nodes__b842352706195638">Available</strong>, <strong id="en-us_topic_increase_nodes__b842352706195643">Deleting backup</strong>, or <strong id="en-us_topic_increase_nodes__b842352706195634">Checking restoration</strong>.</li><li id="en-us_topic_increase_nodes__li10989431114910">A DB instance cannot be deleted when nodes are being added.</li><li id="en-us_topic_increase_nodes__li14300203024910">Mongos and shard nodes that are successfully added cannot be deleted.</li></ul>
|
||||
<div class="note" id="en-us_topic_increase_nodes__note2200417585627"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="en-us_topic_increase_nodes__ul898913115493"><li id="en-us_topic_increase_nodes__li10988113110497">You can add nodes when the instance status is <strong id="en-us_topic_increase_nodes__b842352706195638">Available</strong>, <strong id="en-us_topic_increase_nodes__b842352706195643">Deleting backup</strong>, or <strong id="en-us_topic_increase_nodes__b842352706195634">Checking restoration</strong>.</li><li id="en-us_topic_increase_nodes__li10989431114910">A DB instance cannot be deleted when nodes are being added.</li><li id="en-us_topic_increase_nodes__li14300203024910">dds mongos and shard nodes that are successfully added cannot be deleted.</li></ul>
|
||||
</div></div>
|
||||
<div class="section" id="en-us_topic_increase_nodes__section51046890162836"><h4 class="sectiontitle">Add mongos</h4><ol id="en-us_topic_increase_nodes__ol62015781164958"><li id="en-us_topic_increase_nodes__li312682313217"><span><a href="dds_02_0043.html">Log in to the DDS console.</a></span></li><li id="en-us_topic_increase_nodes__li928348165455"><span>On the <strong id="en-us_topic_increase_nodes__b19156182972517">Instance Management</strong> page, click the target cluster instance.</span></li><li id="en-us_topic_increase_nodes__li12001153152315"><span>On the <span class="uicontrol" id="en-us_topic_increase_nodes__uicontrol23094277720135"><b>mongos</b></span> tab in the <span class="uicontrol" id="en-us_topic_increase_nodes__uicontrol23094277720227"><b>Node Information</b></span> area, click <span class="uicontrol" id="en-us_topic_increase_nodes__uicontrol23094277720516"><b>Add mongos</b></span>.</span></li><li id="en-us_topic_increase_nodes__li1740312111008"><span>On the displayed page, specify <strong id="en-us_topic_increase_nodes__b0404101118014">Node Class</strong>, <strong id="en-us_topic_increase_nodes__b4404171117019">Nodes</strong>, and <strong id="en-us_topic_increase_nodes__b19271215274">Parameter Template</strong> and click <strong id="en-us_topic_increase_nodes__b49411047152819">Submit</strong>.</span><p><p id="en-us_topic_increase_nodes__p685136203317">A cluster instance of Community Edition supports up to 32 mongos nodes.</p>
|
||||
</p></li><li id="en-us_topic_increase_nodes__li55760807163532"><span>View the result of adding nodes.</span><p><ul id="en-us_topic_increase_nodes__ul9610612340"><li id="en-us_topic_increase_nodes__li2061071220412">This process takes up to 15 minutes. The status of the DB instance in the instance list is <strong id="en-us_topic_increase_nodes__b842352706144613">Adding node</strong>.</li><li id="en-us_topic_increase_nodes__li126101122417">In the upper right corner of the DB instance list, click <span><img id="en-us_topic_increase_nodes__image689313534144716" src="en-us_image_0000001142773957.png"></span> to refresh the list. The instance status changes to <strong id="en-us_topic_increase_nodes__b84235270615140">Available</strong>.</li><li id="en-us_topic_increase_nodes__li861018121940">On the <span class="uicontrol" id="en-us_topic_increase_nodes__uicontrol1112396650144750"><b>mongos</b></span> tab in the <span class="uicontrol" id="en-us_topic_increase_nodes__uicontrol1293120927144750"><b>Node Information</b></span> area, view the information about the node you added.</li><li id="en-us_topic_increase_nodes__li17610171216410">If the mongos fail to be added, you can revert them in batches or delete them one by one. For details, see section <a href="dds_03_0018.html">Reverting and Deleting Failed Cluster Instance Nodes</a>.</li></ul>
|
||||
<div class="section" id="en-us_topic_increase_nodes__section51046890162836"><h4 class="sectiontitle">Add dds mongos</h4><ol id="en-us_topic_increase_nodes__ol62015781164958"><li id="en-us_topic_increase_nodes__li312682313217"><span><a href="dds_02_0043.html">Log in to the DDS console.</a></span></li><li id="en-us_topic_increase_nodes__li928348165455"><span>On the <strong id="en-us_topic_increase_nodes__b19156182972517">Instance Management</strong> page, click the target cluster instance.</span></li><li id="en-us_topic_increase_nodes__li12001153152315"><span>On the dds mongos tab in the <span class="uicontrol" id="en-us_topic_increase_nodes__uicontrol23094277720227"><b>Node Information</b></span> area, click <span class="uicontrol" id="en-us_topic_increase_nodes__uicontrol23094277720516"><b>Add dds mongos</b></span>.</span></li><li id="en-us_topic_increase_nodes__li1740312111008"><span>On the displayed page, specify <strong id="en-us_topic_increase_nodes__b0404101118014">Node Class</strong>, <strong id="en-us_topic_increase_nodes__b4404171117019">Nodes</strong>, and <strong id="en-us_topic_increase_nodes__b19271215274">Parameter Template</strong> and click <strong id="en-us_topic_increase_nodes__b49411047152819">Submit</strong>.</span><p><p id="en-us_topic_increase_nodes__p685136203317">A cluster instance of Community Edition supports up to 32 dds mongos nodes.</p>
|
||||
</p></li><li id="en-us_topic_increase_nodes__li55760807163532"><span>View the result of adding nodes.</span><p><ul id="en-us_topic_increase_nodes__ul9610612340"><li id="en-us_topic_increase_nodes__li2061071220412">This process takes up to 15 minutes. The status of the DB instance in the instance list is <strong id="en-us_topic_increase_nodes__b842352706144613">Adding node</strong>.</li><li id="en-us_topic_increase_nodes__li126101122417">In the upper right corner of the DB instance list, click <span><img id="en-us_topic_increase_nodes__image689313534144716" src="en-us_image_0000001142773957.png"></span> to refresh the list. The instance status changes to <strong id="en-us_topic_increase_nodes__b84235270615140">Available</strong>.</li><li id="en-us_topic_increase_nodes__li861018121940">On the dds mongos tab in the <span class="uicontrol" id="en-us_topic_increase_nodes__uicontrol1293120927144750"><b>Node Information</b></span> area, view the information about the node you added.</li><li id="en-us_topic_increase_nodes__li17610171216410">If the dds mongos fail to be added, you can revert them in batches or delete them one by one. For details, see section <a href="dds_03_0018.html">Reverting and Deleting Failed Cluster Instance Nodes</a>.</li></ul>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_increase_nodes__section3495337616353"><h4 class="sectiontitle">Add shard</h4><ol id="en-us_topic_increase_nodes__ol1265120616353"><li id="en-us_topic_increase_nodes__li15619614133116"><span><a href="dds_02_0043.html">Log in to the DDS console.</a></span></li><li id="en-us_topic_increase_nodes__li4675199116353"><span>On the <strong id="en-us_topic_increase_nodes__en-us_topic_increase_nodes_b19156182972517">Instance Management</strong> page, click the target cluster instance.</span></li><li id="en-us_topic_increase_nodes__li1224112457374"><span>On the <span class="uicontrol" id="en-us_topic_increase_nodes__uicontrol687267979"><b>shard</b></span> tab in the <span class="uicontrol" id="en-us_topic_increase_nodes__uicontrol1050905372"><b>Node Information</b></span> area, click <span class="uicontrol" id="en-us_topic_increase_nodes__uicontrol6396814"><b>Add shard</b></span>.</span></li><li id="en-us_topic_increase_nodes__li5230540616353"><span>Specify <strong id="en-us_topic_increase_nodes__b842352706201843">Node Class</strong>, <strong id="en-us_topic_increase_nodes__b842352706201847">Storage Space</strong>, <strong id="en-us_topic_increase_nodes__b1917216411008">Nodes</strong>, and <strong id="en-us_topic_increase_nodes__b1343414217299">Parameter Template</strong> and click <strong id="en-us_topic_increase_nodes__b12922102133212">Submit</strong>.</span><p><ul id="en-us_topic_increase_nodes__ul4815011916353"><li id="en-us_topic_increase_nodes__li18309176164249">The storage space you applied for will contain the system overhead. The storage space can be configured from 10 GB to 2000 GB and must be an integer multiple of 10.</li><li id="en-us_topic_increase_nodes__li6277104218332">A cluster instance of Community Edition supports up to 32 shard nodes.</li></ul>
|
||||
|
@ -3,7 +3,7 @@
|
||||
<h1 class="topictitle1">What Is DDS?</h1>
|
||||
<div id="body52215961"><p id="en-us_topic_introduction__p37073266161026">Document Database Service (DDS) is a high availability DBaaS, which provides a secure, reliable and scalable solution, compatible with MongoDB community version 4.0.3 as baseline version.It provides functions such as one-click deployment, <span class="keyword" id="en-us_topic_introduction__keyword14492131173011">elastic capacity expansion</span>, <span class="keyword" id="en-us_topic_introduction__keyword13656940203011">disaster recovery</span>, backup, restoration, monitoring, and alarm reporting.</p>
|
||||
<p id="en-us_topic_introduction__p65223945161026">DDS has the following features:</p>
|
||||
<ul id="en-us_topic_introduction__ul50144594161026"><li id="en-us_topic_introduction__li35180331161026">DDS automatically establishes the three-node <span class="keyword" id="en-us_topic_introduction__keyword18736914174216">replica set</span> architecture. It supports fast deployment, <span class="keyword" id="en-us_topic_introduction__keyword93813256425">high availability (HA) data storage</span>, <span class="keyword" id="en-us_topic_introduction__keyword394920308428">data redundancy</span>, and failover.</li><li id="en-us_topic_introduction__li13418762102713">DDS provides sharded cluster instances comprised of a config node paired with multiple shards and mongos nodes. These clusters can be easily scaled up to enhance read and write performance.</li><li id="en-us_topic_introduction__li48187524161026">DDS lets you back up or restore a database from the management console in just a few clicks.</li><li id="en-us_topic_introduction__li5574606710">DDS provides performance metrics and you can configure alarm notifications to make it easier to keep abreast of instance statuses.</li></ul>
|
||||
<ul id="en-us_topic_introduction__ul50144594161026"><li id="en-us_topic_introduction__li35180331161026">DDS automatically establishes the three-node <span class="keyword" id="en-us_topic_introduction__keyword18736914174216">replica set</span> architecture. It supports fast deployment, <span class="keyword" id="en-us_topic_introduction__keyword93813256425">high availability (HA) data storage</span>, <span class="keyword" id="en-us_topic_introduction__keyword394920308428">data redundancy</span>, and failover.</li><li id="en-us_topic_introduction__li13418762102713">DDS provides sharded cluster instances comprised of a config node paired with multiple shards and dds mongos nodes. These clusters can be easily scaled up to enhance read and write performance.</li><li id="en-us_topic_introduction__li48187524161026">DDS lets you back up or restore a database from the management console in just a few clicks.</li><li id="en-us_topic_introduction__li5574606710">DDS provides performance metrics and you can configure alarm notifications to make it easier to keep abreast of instance statuses.</li></ul>
|
||||
<p id="en-us_topic_introduction__p15752318719">For details about the compatible DB engines and versions, see <a href="dds_01_0014.html">Database Engine and Version</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|