Documentation Index

Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt

Use this file to discover all available pages before exploring further.

DB Server

Prev Next

Available in VPC

In DB Server, you can create or delete Cloud MongoDB Server, as well as check the list of MongoDB Server in operation. In addition, you can change the specifications of the MongoDB Server in operation or manage admin (user) accounts.

DB server interface

The basics of using DB Server are as follows:

clouddbformongodb-dbserver-screen_vpc_ko

Component Description
① Menu name Current menu name and number of MongoDB Servers in operation.
② Basic features Create MongoDB Server, view details of Cloud DB for MongoDB, or refresh the DB Server interface.
③ Post-creation features Restart, delete, monitor, and manage MongoDB Server in operation.
④ MongoDB Server list Check the list of MongoDB Servers in operation and their information.
⑤ Search Search the server you want by the service name from the MongoDB Server list.

View MongoDB Server list

You can view information of each server from the list of MongoDB Servers that have been created and are currently in operation. To view the information:

Note

You can view the list only when there are 1 or more servers in operation. If you do not have any servers created and operating, no list appears on the DB Server interface.

  1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MongoDB.

  2. Click the DB Server menu.

  3. When the list of created MongoDB Servers appears, check the summary or click a MongoDB Server to see details.
    clouddbformongodb-dbserver-screen1_vpc_ko

    • DB service name: MongoDB Cluster group identified by the MongoDB service name.
    • Cluster Role: Roles of the MongoDB Cluster.
    • DB Server name: Name of the MongoDB Server.
    • DB Role/Role: Roles of the MongoDB Server.
    • DB Server type: Type of the MongoDB Server and its available memory.
    • Monitoring: Go to the Monitoring interface.
    • DB Status: Go to the DB server's View details interface.
    • DB access port: Port number used by the MongoDB Server.
    • Private domain: Private domain information.
    • Public domain: Public domain information.
    • Data storage: Size of the data storage in use (available capacity).
    • Data storage type: Type of data storage in use.
    • Data storage capacity: Available capacity and usage of the data storage in use.
    • Status: Status of the MongoDB Server.
      • Creating: Status in which the MongoDB Server is being created with the information you entered.
      • Configuring: Status in which the MongoDB Server is created and configured with the information you entered.
      • Running: Status in which the creation and configuration of the MongoDB Server has been completed with the information you entered, and access to MongoDB from the application server is available.
      • Deleting: Status in which the MongoDB Server created with the information you entered is being deleted.
      • Stopping: Status in which the MongoDB Server created with the information you entered is being stopped.
      • Restarting: Status in which the MongoDB Server created with the information you entered is restarting.
      • Failover pending: Status in which the system is waiting for user-initiated failover of the primary member during operations such as an OS upgrade.
    • Creation date: Date when the MongoDB Server was created and the initial point when the server status entered the creating status.
    • Running date: Date when the MongoDB Server operation started and the initial point when the DB server status entered the running status.
    • ACG: ACG name and ID used in the MongoDB Server.
      • clouddbforredis_ico-01_vpc_ko: Click to move to Server > ACG.
      • [View rules]: Click to view the detailed rules applied.
    • DB engine version: Version information of the MongoDB installed on the Server.
    • Cluster Type: Roles of the MongoDB cluster.
    • Replica Set (Shard) Name: Name of the Replica Set (Shard).
    • VPC: VPC name used in the MongoDB Server.
    • Subnet: Name of the subnet being used by the MongoDB Server.
    • Backup storage period (backup time): The configured backup file storage period and backup cycle, if the backup feature is enabled.
      • clouddbforredis_ico-01_vpc_ko: Click to enable or disable the backup feature or set the file retention period and backup cycle.
Caution

If you clear the backup, all existing backup files are deleted.

Note

The differences between sharding and single replica set are as follows:

  • In single replica set, the client directly accesses the DB Server to perform data read/write.
  • In sharding, the client accesses the router server called mongos and performs necessary data read/write tasks through mongos, and transfers the results to the client. Sharding consists of n shards, and each shard is configured in the same way as single replica set.

Create MongoDB Server

To create a MongoDB Server in the NAVER Cloud Platform console:

  1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MongoDB.

  2. Click the DB Server menu.

  3. Click [Create DB Server].
    clouddbformongodb-dbserver-create_vpc_ko

  4. When the service subscription interface appears, proceed with the following steps in order:

Note

Click [Subscribe] from the NAVER Cloud Platform portal's Services > Database > Cloud DB for MongoDB to go directly to the interface in Step 3.

1. Cluster settings

To set the information for the MongoDB cluster to be created:

  1. When the cluster settings interface appears, check the type of DBMS you want to install to the server from DBMS type.
    clouddbformongodb-dbserver-cluster_vpc1_ko
  2. Select the server generation.
  3. Select the MongoDB version you want to install.
  4. Select the type of the MongoDB cluster.
    • Stand-Alone: Supports configuration for test and development environment.
    • Single Replica Set: A Mongod process group that maintains the same data set and provides high availability.
    • Sharding: A configuration that distributes the storage of data in multiple replica sets.
    • The settings can't be changed after you create the MongoDB Server.
  5. Set the rest of the items required when you create the MongoDB.
    • DB Server name: Enter the name of the MongoDB Server to create.
      • Enter between 3 and 15 characters using English letters, numbers, and hyphens (-).
      • Duplicate names are not allowed.
      • Random text is added to avoid duplicate host names.
    • DB service name: Enter the name of the MongoDB Server group to create.
      • Enter between 3 and 15 characters using Korean letters, English letters, numbers, and hyphens (-).
      • Duplicate names are not allowed.
    • VPC: Select the VPC to be used for the creation of the server and MongoDB.
      • [Refresh]: Click to refresh the list of the created VPC list.
      • [Create VPC]: Click if you haven't created any VPC and need to create one.
    • Subnet: Select a private subnet to be used when accessing the VPC.
      • [Refresh]: Click to refresh the list of the created VPC list.
      • [Create Subnet]: Click to create a new Subnet.
    • Data storage type: Select or check the storage type.
      • G2 server generation: Select from available storage types (SSD, HDD) for storing DB data (cannot be changed after creation).
      • G3 server generation: Fix as SSD.
    • Data storage: Check storage capacity for DB data storage.
      • 10 GB is allocated upon initial creation of the MongoDB Server.
      • The capacity is automatically added in 10 GB units and charged as data increases.
      • Supports up to 2000 GB.
  6. Check the applicable pricing plan information when using Cloud DB for MongoDB.
    • Pricing plan: An hourly pricing plan, which is billed based on the hours used, is applied by default, and it is changed depending on the server specifications and storage capacity.
    • For more information, click Pricing information.
  7. Check the MongoDB version and license information.
  8. Specify the ACG settings for the MongoDB Server access.
    • Access Control Group (ACG) is created automatically.
    • The detailed settings for the ACG are available from Server > ACG in the console.
  9. Click [Next].

2. Server settings

To set the information for MongoDB Server:

  1. When the server settings interface appears, set items required to create the MongoDB Server.

    • If you've selected stand-alone for the cluster type, set the following items:
      clouddbformongodb-dbserver-standalone_vpc_ko
      • Stand-Alone Server Spec: Select the specifications for the stand-alone server.
      • Port: Enter the port number for the stand-alone server between 10000 and 65535.
        • Default: 17017.
        • The default MongoDB port number of "27017" is not recommended due to security vulnerabilities.
    • If you've selected single replica set for the cluster type, set the following items:
      clouddbformongodb-dbserver-singlereplicaset_vpc_ko
      • Number of members per replica set (primary & secondary): Select the number of member servers in each shard (3 to 7 including the arbiter server).
      • Member Server Spec: Select the specifications of the member server.
      • Number of Arbiters per Replica Set: Select the number of arbiter servers per shard (0-1 unit).
        • If a Secondary member experiences replication lag or a failure in a cluster with Primary-Secondary-Arbiter configuration, the server cannot respond to requests with read concern: majority or write concern: { w: majority }. (The benefits of server redundancy may be limited.)
        • For a cluster with Primary-Secondary-Arbiter configuration, use read concern : local, write concern : { w: 1, j: true }.
        • The Primary-Secondary-Arbiter configuration is not recommended for production environments.
      • Arbiter Server Spec: Select the specifications of the arbiter server.
      • Port: Enter the port number for each server between 10000 and 65535.
        • Default: 17017.
        • The default MongoDB port number of "27017" is not recommended due to security vulnerabilities.
    • If you've selected Sharding for the cluster type, set the following items:
      clouddbformongodb-dbserver-sharding_vpc_ko
      • Number of members per replica set (primary & secondary): Select the number of member servers in each shard (3 to 7 including the arbiter server).
      • Member Server Spec: Select the specifications of the member server.
      • Number of Arbiters per Replica Set: Select the number of arbiter servers per shard (0-1 unit).
        • If a Secondary member experiences replication lag or a failure in a cluster with Primary-Secondary-Arbiter configuration, the server cannot respond to requests with read concern: majority or write concern: { w: majority }. (The benefits of server redundancy may be limited.)
        • For a cluster with Primary-Secondary-Arbiter configuration, use read concern : local, write concern : { w: 1, j: true }.
        • The Primary-Secondary-Arbiter configuration is not recommended for production environments.
      • Arbiter Server Spec: Select the specifications of the arbiter server.
      • Number of shards: Select the number of shards.
        • 2 or 3 can be selected upon initial installation.
        • Up to 5 shards can be added in the management interface after installation.
        • If you need more than 5 shards, make an inquiry to Customer Support.
      • Number of Mongos (Router) Servers: Select the number of Mongos Servers (2-5 units).
      • Mongos Server Spec: Select the spec of the Mongos server.
      • Number of Config Servers: Check the number of Config Servers (3 fixed units).
      • Config Server Spec: Select the specifications of the Config Server.
      • Port: Enter the port number for each server between 10000 and 65535.
        • Default: 17017.
        • The default MongoDB port number of "27017" is not recommended due to security vulnerabilities.

  2. Click [Next].

3. DB settings

To set the information for the MongoDB to be installed:

  1. When the DB settings interface appears, set items required to create the MongoDB Server.
    clouddbformongodb-dbserver-dbset_vpc_ko

    • USER_ID: Enter the account ID of the MongoDB server admin.

      • Enter between 4 and 16 characters using English letters and numbers.
      • The first character must be an English letter.
      • You cannot use predefined reserved words.

    • USER password: Enter the account password of the MongoDB Server admin.

      • Enter 8 to 20 characters using at least 1 English letter, number, and special character.
      • You cannot use special characters ` & + \ " ' / or spaces.

    • DB Config settings: View the optimized basic settings provided by NAVER.

    • DB Data Compress: Select the data compression algorithm provided by MongoDB.

      • Using the default value is recommended.

    • Collect DB Log: View the provision of log collection and viewer features for error logs and slow query logs.

      • Cloud Log Analytics integrations.
  2. Set whether to use backup for the server.
    • Backup file retention period: Select by clicking the period to store the backup file in a separate backup storage.
      • For point-in-time recovery, the backup file is stored for the maximum set retention period + 24 hours.
    • Backup time: Select the backup execution time.
      • The backup is performed once a day at the specified time using mongodump provided by MongoDB.
      • The backup is started every day within 15 minutes from the time specified by the user.
      • If you select this, additional fees are incurred depending on the storage capacity used.
  3. Click [Next].
  4. When Subscribe to Cloud Log Analytics appears, view the content, and click [OK].
    • If you need to subscribe to Cloud Log Analytics, click [Subscribe to Cloud Log Analytics].
    • For more information on Cloud Log Analytics, see Cloud Log Analytics user guide.

4. Final confirmation

  1. When the final confirmation interface appears, check the configured cluster information and server information.
    clouddbformongodb-dbserver-confirm_vpc_ko
    • Click [Previous] to edit the settings.
  2. Click [Create].
  3. Check the status of the MongoDB created in the DB Server interface's MongoDB list.
    • Creating: Status in which the MongoDB Server is created with the information you entered.
    • Configuring: Status in which the MongoDB Server is created and configured with the information you entered.
    • Running: Status in which the creation and configuration of the MongoDB Server has been completed with the information you entered, and access to MongoDB from the application server is available.
Note

To view the latest status from Step 3, click [Refresh].

Caution

It may take several minutes or longer as the system progresses through Creating and Configuring before reaching the Running status where actual usage becomes available.

Restart MongoDB Server

You can easily and conveniently restart MongoDB Server. You can't access servers while they're being restarted. To restart:

  1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MongoDB.
  2. Click the DB Server menu.
  3. Click the MongoDB Server you want to restart, and click [Restart].
  4. When the Restart DB Server popup appears, check the name of the DB Server to restart, and click [Yes].
  5. Check the status of the MongoDB Server from the MongoDB Server list in the DB Server interface.
    • Stopping: Status in which the MongoDB Server is being stopped.
    • Restarting: Status in which the MongoDB Server is being restarted.
Note
  • It may take a certain amount of time (minutes) as the system progresses through Stopping and Restarting before reaching the Operating status where actual usage becomes available.
  • The role of the restarting server may cause a failover. You are notified by SMS and email when a failover occurs.

Delete MongoDB Server

You can delete a MongoDB Server that has been created and is in operation. If you're using the replica set or sharding type clusters, all of the clusters are deleted together. If you're using the backup feature, the backup files are also deleted. To delete a MongoDB Server:

  1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MongoDB.
  2. Click the DB Server menu.
  3. Click the MongoDB Server you want to delete and click [Delete DB Cluster].
  4. When the Delete DB Cluster popup appears, enter the name of the DB Server to delete, and click [Yes].
  5. Check the status of the MongoDB Server from the MongoDB Server list in the DB Server interface.
    • Deleting: Status in which a MongoDB Server is being deleted.
Note

The actual deletion from the list after going through the Deleting status may take a certain amount of time (minutes).

Monitor MongoDB Server

NAVER Cloud Platform's Cloud DB for MongoDB provides a monitoring service through the dashboards on each server. This allows you to intuitively check servers in operation and data status, and efficiently manage them.

Note

For more information on Monitoring, see Monitoring.

To go to the monitoring interface of the MongoDB Server that has been created and is in operation:

  1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MongoDB.
  2. Click the DB Server menu.
  3. Click the MongoDB Server you want to monitor, and click [Monitoring].
  4. Click and select the dashboard you want to monitor.
    clouddbformongodb-dbserver-monitoring_vpc_ko

Manage MongoDB Server

While operating the created MongoDB Server, there may come situations where you need to change the options of the server or DB configured upon creation. Cloud DB for MongoDB supports changes or upgrades of a certain number of specifications simply through a few clicks, even for MongoDB Server that has already been created.

Note

By default, managing a MongoDB Server is available when the server status is Running.

To manage a MongoDB Server that has been created and is in operation:

  1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MongoDB.
  2. Click the MongoDB Server menu.
  3. Click the MongoDB Server you want to manage, and click [Manage DB].
  4. Click and select the item you want to manage.
    clouddbformongodb-dbserver-manage_vpc_ko

Manage DB user

Cloud DB for MongoDB provides user management features that enables you to conveniently add, edit, and delete user accounts that use the server. You can add up to 10 user accounts at each time of creation, change, or deletion.

To add, edit, and delete user accounts:

  1. When the Manage DB user popup appears, perform the required tasks for the user account.
    clouddbformongodb-dbserver-dbuser_vpc_ko
    • Add user account: Select Create, enter the information for USER_ID, database, DB permissions, and password, and click [Add DB user].
    • Delete user account: Select Change/delete, and click [Delete] in the row of the user account to be deleted.
    • Edit user account information: Select Change/delete in the row of the user account to be edited, click [Edit] to edit, and click [Save].
  2. Click [Yes].
  3. Check the status of a MongoDB for which you've set users from the MongoDB list in the DB Server interface.
    • Configuring: Status in which the MongoDB Server is configured with the information you entered.
    • Running: Status in which the configuration of the MongoDB Server has been completed with the information you entered, and access to MongoDB from the application server is available.

Manage admin user

When creating a MongoDB Server, the ID and password for the server admin account are created by default. However, while operating the server, you may need to reset the password of the admin account.

To change the admin account password, enter the new password in the Admin user management popup, and click [Yes].

clouddbformongodb-dbserver-admin_vpc_ko

Change secondary

You can change the Member server configuration of the replica set (shard), including the config server.

Note
  • The combined number of secondary and arbiter servers can be from a minimum of 3 to a maximum of 7, and only 1 arbiter server can be configured.
  • The Primary-Secondary-Arbiter configuration is not recommended, since it may cause service failures in special circumstances.
  • When adding a secondary, the addition process is performed in the initial sync method provided by MongoDB, and it may require a considerable amount of time depending on the size of the existing data.

To change a secondary server:

  1. When the Change secondary (arbiter) popup appears, check the number of current secondary (arbiter) servers.
  2. Click and select the quantity you want to change to.
    clouddbformongodb-dbserver-secondary_vpc_ko
  3. Click [OK].
  4. Check the status of MongoDB for which you changed the secondary from the MongoDB list in the DB Server interface.
    • Creating: Status in which the MongoDB is being created with the information you entered.
    • Configuring: Status in which the MongoDB Server is configured with the information you entered.
    • Running: Status in which the configuration of the MongoDB Server has been completed with the information you entered, and access to MongoDB from the application server is available.

Add shards

You can add up to 5 shards within the MongoDB Service.

Note

Since deleting shards may cause data loss, Cloud DB for MongoDB does not provide a shard deletion feature.

To add shards:

  1. When the Add shards popup appears, check the current number of shards.
  2. Click and select the number of shards you want to change to.
    clouddbformongodb-dbserver-shard_vpc_ko
  3. Click [Yes].
  4. Check the status of a MongoDB that added shards from the MongoDB Server list in the DB Server interface.
    • Creating: Status in which the MongoDB is being created with the information you entered.
    • Running: Status in which the configuration of the MongoDB Server has been completed with the information you entered, and access to MongoDB from the application server is available.

Change mongos

You can change the number of Mongos in the MongoDB Service. The number of Mongos can be configured from a minimum of 2 to a maximum of 5.

To change the number of Mongos:

  1. When the Change number of Mongos popup appears, check the current number of mongos servers.
  2. Click and select the number of mongos servers you want to change to.
    clouddbformongodb-dbserver-mongos_vpc_ko
  3. Click [OK].
  4. Check the status of a MongoDB for which you changed mongos count from the MongoDB list in the DB Server interface.
    • Creating: Status in which the MongoDB is being created with the information you entered.
    • Running: Status in which the configuration of the MongoDB Server has been completed with the information you entered, and access to MongoDB from the application server is available.

Change config server

You can change the number of config server for the MongoDB Service. The number of config server can be from a minimum of 3 to a maximum of 7.

To change the number of config server:

  1. When the Change number of config server popup appears, view the number of config server.
  2. Click and select the quantity you want to change to.
    clouddbformongodb-dbserver-config_vpc_ko
  3. Click [OK].
  4. Check the status of a MongoDB for which you changed the number of config servers from the MongoDB list in the DB Server interface.
    • Creating: Status in which the MongoDB is being created with the information you entered.
    • Configuring: Status in which the MongoDB Server is configured with the information you entered.
    • Running: Status in which the configuration of the MongoDB Server has been completed with the information you entered, and access to MongoDB from the application server is available.

Change DB specifications

You can change the server specifications for the MongoDB Server you've created. Additional fees are incurred when applying specifications upgrades.

Caution
  • The servers restart when you change server specifications. As access is unavailable during the restart, it is recommended to view the data after the restart is completed.
  • When you change the server specifications, the primary, secondary, and arbiter are all changed.
  • When the primary server specification changes, a failover occurs and you are notified by SMS and email.

To change the specifications:

  1. When the Change DB specifications popup appears, check the current server specifications.
  2. Click and select the server specifications you want to change to.
    clouddbformongodb-dbserver-dbspec_vpc_ko
  3. Click [OK].
  4. Check the status of a MongoDB for which you changed specifications from the MongoDB list in the DB Server interface.
    • Configuring: Status in which the MongoDB Server is configured with the information you entered.
    • Upgrade: Status in which the MongoDB Server is being upgraded with the information you entered.
    • Downgrading: Status in which the MongoDB Server is being downgraded with the information you entered.
    • Running: Status in which the configuration of the MongoDB Server has been completed with the information you entered, and access to MongoDB from the application server is available.

Manage public domain

You can allocate or remove public domains required for external access to MongoDB Server.

Caution

Using public domains may cause security vulnerabilities, so configure limited access to the MongoDB Server using methods such as ACG settings.

Note

A temporary disruption may occur when allocating public domain in replica set cluster.
Editing of the host file is required for replica sets to access public domains.
Refer to Create DB access string.

  1. When the Manage public domain or Remove public domain popup appears, check the name of the DB Server you will allocate a public domain to or remove a domain from.
    clouddbformongodb-dbserver-public_vpc_ko
  2. Click [Yes].
  3. Check the status of a MongoDB for which you allocated or removed a public domain from the MongoDB list in the DB Server interface.
    • Configuring: Status in which the MongoDB Server is configured with the information you entered.
    • Running: Status in which the configuration of the MongoDB Server has been completed with the information you entered, and access to MongoDB from the application server is available.
  4. The editing of the host file is required for replica sets.
    See Create DB access string.

Primary DB Failover

If the primary MongoDB Server fails, then the user can directly use the failover feature to stepdown the primary server. During the process of the primary being elected again, the primary may not exist for several seconds or longer, which may have an effect on service.

To stepdown the primary server:

  1. When the Primary DB failover popup appears, check the selected server and the shard number.
    clouddbformongodb-dbserver-failover_vpc_ko
  2. Click [Yes].
  3. Check the MongoDB's DB role from the MongoDB list in the DB Server interface.
    • Configuring: Status in which the MongoDB Server is configured with the information you entered.
    • Running: Status in which the configuration of the MongoDB Server has been completed with the information you entered, and access to MongoDB from the application server is available.

MongoDB Engine Upgrade

You can upgrade the MongoDB version. The version upgrade is applied to the entire DB Service.
When the version is updated, a temporary disruption may occur due to a failover, and you are notified by SMS and email.
In the case of a sharding cluster, the upgrade proceeds one by one in the order of config -> shard -> mongos.
All replica sets (config and shard in replica set cluster and sharding cluster) are upgraded in the order of secondary/arbiter -> primary.
During the upgrade, the target server access is not available, and when upgrading the primary server, it is switched to secondary to keep service access to a minimum.

  1. Click Manage DB > Version Upgrade.
  2. Select the version to upgrade and click [Yes].
    clouddbformongodb-dbserver-upgrade_ko_vpc.png
  3. If a major version upgrade is required, you can select a higher major version by checking [Major version upgrade].
Note

In the case that there is a sharding cluster, a version upgrade can be performed with the balancer turned off. If the balancer is turned on during the version upgrade, halt the balancer temporarily and proceed with the operation. Turn off the balancer before the version upgrade and then turn it back on after the task is finished.
For more information on how to set up a balancer, see MongoDB stopBalancer setup reference guide (English).

Caution
  • For major version upgrades, configure the development environment in advance, and proceed with the application version compatibility review and feature test sufficiently.
  • After a version upgrade, restoration to the previous version is not available.
  • If you perform [Restore backup] after upgrading the version, even the backup copy before the upgrade is restored to the upgraded version of the cluster. If you want to keep the backup of the previous version, save the backup copy separately through [Export Object Storage] within the backup storage period.

Create DB access string

You can create a sample of a string required for external access to MongoDB Servers.

To create an access string:

  1. When the Create DB access string popup appears, check the created string.
  2. Edit the client's host file to access a replica set through a public domain.
    • You can access it using the access string after adding the viewed information to the hosts file.
    • If the replica set is not using a public domain, you cannot view host file information.
      clouddbformongodb-dbserver-string_vpc_ko
  3. Click [OK].

Manage operating system

Update the operating system of the DB Server to the latest version provided by NAVER Cloud Platform.
The operating system update is applied to the entire DB Service and proceeds one server at a time in the following order: secondary -> arbiter -> primary -> Mongos. To update the primary DB Server, you need to use the [Failover and OS upgrade] button. For more information, see the guide below.

Caution

In this case, you are not performing a failover using primary DB failover within the DB management features. Use the failover and OS upgrade feature in the server information.

  • Operating system updates are only available when they are in a high availability configuration.
  • Once the OS update is complete, you cannot roll back to the previous version.
  • After the operating system update, monitoring data and event history for the servers from before the update are no longer available in the console. If you need to back up the monitoring data and event history prior to the upgrade, refer to the widget data download feature in the Cloud Insight user guide and the export log feature in the Cloud Log Analytics user guide.
  • Custom notification settings configured for the DB Cluster are not transferred automatically. If you have any manually configured notification items, reconfigure them after the operating system update is complete.
  • If a backup is in progress, it is temporarily suspended and resumed on the next backup schedule after the target server update is complete.
  • After the operating system update, the Private IP address is changed. To avoid service impact due to IP changes, it is recommended to access your DB via a private domain. If you are using the Private IP address for access, make sure to update your connection settings after the OS update.
  • If neither the operating system nor the kernel version is up to date, an operating system update is performed.
  • An operating system update proceeds by replacing the servers, whereas a kernel update proceeds by rebooting the existing servers without replacement.

Update the operating system of the secondary server

Secondary and arbiter servers are updated one at a time, and access to the servers is blocked while the update is in progress.
In the case of replica sets, all secondary and arbiter servers are updated, and in the case of sharding, all secondary and arbiter servers in the shard and config server are updated.

Note
  • The more secondary servers you have, the longer the update may take.
  • The duration of the update may also vary depending on the size of the data storage. The run time is the same as adding a secondary server, which you can check in advance.
Caution
  • The secondary is not accessible during the update process. In the case of the PSA structure, change the read preference to primary or secondaryPreferred, or add a secondary to minimize the impact of the secondary operation. Depending on your read concern or write concern settings, consider adding a secondary before the operation.
  • Check the availability of the secondary and add a secondary before the operation if necessary.
  1. To update the server's operating system version, click OS management, review the popup, and click [Next].
  • Operating system update
    os_management_1_ko.png
  • Kernel update
    Image
Caution
  • If the subnet that includes the DB Service does not have enough available IPs, the OS update cannot be performed.
  • Make sure that the subnet includes enough available IPs for all DB Servers in the DB Service that require the OS update before proceeding.
  1. After reviewing the precautions for the operating system update, click the checkbox.
  2. Once you've confirmed all items, click [Upgrade].
  • Operating system update
    os_management_2_ko.png
  • Kernel update
    Image
  1. You can view the update in progress through DB Server status.

os_management_3_ko.png

Update the operating system of the primary server

After performing a failover, update the OS of the secondary (prior primary) server.
In the case of replica sets, 1 primary server is updated, and in the case of sharding, all primary servers and Mongos servers in the shard and config server are updated.

Caution
  • Primary Server access is unavailable during the failover performed to update the OS of the Primary Server.
  • Mongos access is unavailable while the update is performed to update the OS of Mongos. Mongos is also updated one instance at a time.

  1. To update the operating system version of the primary and Mongos server, select the primary server and click [Failover and OS upgrade].
    os_management_4_ko.png

  2. After reviewing the precautions for updating the primary server's OS, click [Upgrade].
    os_management_5_ko.png

  3. You can monitor the update progress through the DB Server status.
    os_management_6_ko.png

Business Registration Number: 129-86-31394 E-commerce Permit Number:No. 2009-GyeonggiSeongnam-0510
CEO: Kim Yuwon Address: NAVER Green Factory 17th–26th Floors, Buljeong-ro 6, Bundang-gu, Seongnam-si, Gyeonggi-do 13561, Republic of Korea. Customer Support Number: 1544-5876
© NAVER Cloud Corp. All Rights Reserved.