From 73adfe6d504c72e9ce899f16d1f4ede58f74bd12 Mon Sep 17 00:00:00 2001 From: "Ru, Li Yi" Date: Tue, 30 Jul 2024 09:47:31 +0000 Subject: [PATCH] geminidb_umn MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Reviewed-by: Székely, Ond Co-authored-by: Ru, Li Yi Co-committed-by: Ru, Li Yi --- docs/geminidb/umn/ALL_META.TXT.json | 1265 +++++++++++++++++ docs/geminidb/umn/CLASS.TXT.json | 569 ++++++++ docs/geminidb/umn/PARAMETERS.txt | 3 + .../umn/en-us_image_0000001815045032.png | Bin 0 -> 248 bytes .../umn/en-us_image_0000001815045400.png | Bin 0 -> 214 bytes .../umn/en-us_image_0000001815045404.png | Bin 0 -> 296 bytes .../umn/en-us_image_0000001815204808.png | Bin 0 -> 1004 bytes .../umn/en-us_image_0000001815204812.png | Bin 0 -> 540 bytes .../umn/en-us_image_0000001815204936.png | Bin 0 -> 567 bytes .../umn/en-us_image_0000001815204972.png | Bin 0 -> 389 bytes .../umn/en-us_image_0000001815204976.png | Bin 0 -> 214 bytes .../umn/en-us_image_0000001815205036.png | Bin 0 -> 293 bytes .../umn/en-us_image_0000001815205124.png | Bin 0 -> 1004 bytes .../umn/en-us_image_0000001815205188.png | Bin 0 -> 389 bytes .../umn/en-us_image_0000001861844977.png | Bin 0 -> 1004 bytes .../umn/en-us_image_0000001861924673.png | Bin 0 -> 1004 bytes .../umn/en-us_image_0000001861924833.png | Bin 0 -> 295 bytes .../umn/en-us_image_0000001861925037.png | Bin 0 -> 389 bytes docs/geminidb/umn/nosql_01_0001.html | 11 + docs/geminidb/umn/nosql_01_0002.html | 31 + docs/geminidb/umn/nosql_01_0003.html | 13 + docs/geminidb/umn/nosql_01_0004.html | 21 + docs/geminidb/umn/nosql_01_0006.html | 90 ++ docs/geminidb/umn/nosql_01_0007.html | 30 + docs/geminidb/umn/nosql_01_0008.html | 92 ++ docs/geminidb/umn/nosql_01_0009.html | 51 + docs/geminidb/umn/nosql_01_0010.html | 22 + docs/geminidb/umn/nosql_01_0110.html | 13 + docs/geminidb/umn/nosql_01_101.html | 13 + docs/geminidb/umn/nosql_02_0001.html | 15 + docs/geminidb/umn/nosql_02_0002.html | 174 +++ docs/geminidb/umn/nosql_02_0004.html | 19 + docs/geminidb/umn/nosql_02_0005.html | 50 + docs/geminidb/umn/nosql_02_0006.html | 19 + docs/geminidb/umn/nosql_02_0007.html | 21 + docs/geminidb/umn/nosql_02_0008.html | 20 + docs/geminidb/umn/nosql_02_0009.html | 46 + docs/geminidb/umn/nosql_02_0010.html | 174 +++ docs/geminidb/umn/nosql_02_0011.html | 17 + docs/geminidb/umn/nosql_03_0002.html | 31 + docs/geminidb/umn/nosql_03_0003.html | 17 + docs/geminidb/umn/nosql_03_0004.html | 17 + docs/geminidb/umn/nosql_03_0005.html | 17 + docs/geminidb/umn/nosql_03_0006.html | 19 + docs/geminidb/umn/nosql_03_0007.html | 36 + docs/geminidb/umn/nosql_03_0008.html | 56 + docs/geminidb/umn/nosql_03_0009.html | 23 + docs/geminidb/umn/nosql_03_0010.html | 20 + docs/geminidb/umn/nosql_03_0011.html | 604 ++++++++ docs/geminidb/umn/nosql_03_0012.html | 17 + docs/geminidb/umn/nosql_03_0013.html | 22 + docs/geminidb/umn/nosql_03_0014.html | 51 + docs/geminidb/umn/nosql_03_0015.html | 50 + docs/geminidb/umn/nosql_03_0016.html | 20 + docs/geminidb/umn/nosql_03_0017.html | 199 +++ docs/geminidb/umn/nosql_03_0018.html | 19 + docs/geminidb/umn/nosql_03_0019.html | 18 + docs/geminidb/umn/nosql_03_0025.html | 20 + docs/geminidb/umn/nosql_03_0026.html | 24 + docs/geminidb/umn/nosql_03_0027.html | 15 + docs/geminidb/umn/nosql_03_0028.html | 16 + .../geminidb/umn/nosql_04_change_history.html | 51 + docs/geminidb/umn/nosql_05_0001.html | 35 + docs/geminidb/umn/nosql_05_0002.html | 15 + docs/geminidb/umn/nosql_05_0003.html | 28 + docs/geminidb/umn/nosql_05_0004.html | 22 + docs/geminidb/umn/nosql_05_0005.html | 18 + docs/geminidb/umn/nosql_05_0006.html | 18 + docs/geminidb/umn/nosql_05_0007.html | 14 + docs/geminidb/umn/nosql_05_0008.html | 17 + docs/geminidb/umn/nosql_05_0009.html | 15 + docs/geminidb/umn/nosql_05_0010.html | 15 + docs/geminidb/umn/nosql_05_0011.html | 16 + docs/geminidb/umn/nosql_05_0012.html | 19 + docs/geminidb/umn/nosql_06_0001.html | 39 + docs/geminidb/umn/nosql_cassandra_0001.html | 23 + docs/geminidb/umn/nosql_increase_nodes.html | 19 + docs/geminidb/umn/nosql_increase_storage.html | 20 + docs/geminidb/umn/nosql_introduction.html | 14 + docs/geminidb/umn/nosql_login.html | 10 + docs/geminidb/umn/nosql_user_guide.html | 25 + .../caution_3.0-en-us.png | Bin 0 -> 2752 bytes .../public_sys-resources/danger_3.0-en-us.png | Bin 0 -> 2771 bytes .../umn/public_sys-resources/delta.gif | Bin 0 -> 836 bytes .../umn/public_sys-resources/deltaend.gif | Bin 0 -> 834 bytes .../umn/public_sys-resources/icon-arrowdn.gif | Bin 0 -> 1887 bytes .../umn/public_sys-resources/icon-arrowrt.gif | Bin 0 -> 1890 bytes .../umn/public_sys-resources/icon-caution.gif | Bin 0 -> 1086 bytes .../umn/public_sys-resources/icon-danger.gif | Bin 0 -> 1086 bytes .../umn/public_sys-resources/icon-huawei.gif | Bin 0 -> 2767 bytes .../umn/public_sys-resources/icon-note.gif | Bin 0 -> 983 bytes .../umn/public_sys-resources/icon-notice.gif | Bin 0 -> 962 bytes .../umn/public_sys-resources/icon-tip.gif | Bin 0 -> 879 bytes .../umn/public_sys-resources/icon-warning.gif | Bin 0 -> 1086 bytes .../public_sys-resources/note_3.0-en-us.png | Bin 0 -> 1080 bytes .../public_sys-resources/notice_3.0-en-us.png | Bin 0 -> 1672 bytes .../warning_3.0-en-us.png | Bin 0 -> 3164 bytes 97 files changed, 4523 insertions(+) create mode 100644 docs/geminidb/umn/ALL_META.TXT.json create mode 100644 docs/geminidb/umn/CLASS.TXT.json create mode 100644 docs/geminidb/umn/PARAMETERS.txt create mode 100644 docs/geminidb/umn/en-us_image_0000001815045032.png create mode 100644 docs/geminidb/umn/en-us_image_0000001815045400.png create mode 100644 docs/geminidb/umn/en-us_image_0000001815045404.png create mode 100644 docs/geminidb/umn/en-us_image_0000001815204808.png create mode 100644 docs/geminidb/umn/en-us_image_0000001815204812.png create mode 100644 docs/geminidb/umn/en-us_image_0000001815204936.png create mode 100644 docs/geminidb/umn/en-us_image_0000001815204972.png create mode 100644 docs/geminidb/umn/en-us_image_0000001815204976.png create mode 100644 docs/geminidb/umn/en-us_image_0000001815205036.png create mode 100644 docs/geminidb/umn/en-us_image_0000001815205124.png create mode 100644 docs/geminidb/umn/en-us_image_0000001815205188.png create mode 100644 docs/geminidb/umn/en-us_image_0000001861844977.png create mode 100644 docs/geminidb/umn/en-us_image_0000001861924673.png create mode 100644 docs/geminidb/umn/en-us_image_0000001861924833.png create mode 100644 docs/geminidb/umn/en-us_image_0000001861925037.png create mode 100644 docs/geminidb/umn/nosql_01_0001.html create mode 100644 docs/geminidb/umn/nosql_01_0002.html create mode 100644 docs/geminidb/umn/nosql_01_0003.html create mode 100644 docs/geminidb/umn/nosql_01_0004.html create mode 100644 docs/geminidb/umn/nosql_01_0006.html create mode 100644 docs/geminidb/umn/nosql_01_0007.html create mode 100644 docs/geminidb/umn/nosql_01_0008.html create mode 100644 docs/geminidb/umn/nosql_01_0009.html create mode 100644 docs/geminidb/umn/nosql_01_0010.html create mode 100644 docs/geminidb/umn/nosql_01_0110.html create mode 100644 docs/geminidb/umn/nosql_01_101.html create mode 100644 docs/geminidb/umn/nosql_02_0001.html create mode 100644 docs/geminidb/umn/nosql_02_0002.html create mode 100644 docs/geminidb/umn/nosql_02_0004.html create mode 100644 docs/geminidb/umn/nosql_02_0005.html create mode 100644 docs/geminidb/umn/nosql_02_0006.html create mode 100644 docs/geminidb/umn/nosql_02_0007.html create mode 100644 docs/geminidb/umn/nosql_02_0008.html create mode 100644 docs/geminidb/umn/nosql_02_0009.html create mode 100644 docs/geminidb/umn/nosql_02_0010.html create mode 100644 docs/geminidb/umn/nosql_02_0011.html create mode 100644 docs/geminidb/umn/nosql_03_0002.html create mode 100644 docs/geminidb/umn/nosql_03_0003.html create mode 100644 docs/geminidb/umn/nosql_03_0004.html create mode 100644 docs/geminidb/umn/nosql_03_0005.html create mode 100644 docs/geminidb/umn/nosql_03_0006.html create mode 100644 docs/geminidb/umn/nosql_03_0007.html create mode 100644 docs/geminidb/umn/nosql_03_0008.html create mode 100644 docs/geminidb/umn/nosql_03_0009.html create mode 100644 docs/geminidb/umn/nosql_03_0010.html create mode 100644 docs/geminidb/umn/nosql_03_0011.html create mode 100644 docs/geminidb/umn/nosql_03_0012.html create mode 100644 docs/geminidb/umn/nosql_03_0013.html create mode 100644 docs/geminidb/umn/nosql_03_0014.html create mode 100644 docs/geminidb/umn/nosql_03_0015.html create mode 100644 docs/geminidb/umn/nosql_03_0016.html create mode 100644 docs/geminidb/umn/nosql_03_0017.html create mode 100644 docs/geminidb/umn/nosql_03_0018.html create mode 100644 docs/geminidb/umn/nosql_03_0019.html create mode 100644 docs/geminidb/umn/nosql_03_0025.html create mode 100644 docs/geminidb/umn/nosql_03_0026.html create mode 100644 docs/geminidb/umn/nosql_03_0027.html create mode 100644 docs/geminidb/umn/nosql_03_0028.html create mode 100644 docs/geminidb/umn/nosql_04_change_history.html create mode 100644 docs/geminidb/umn/nosql_05_0001.html create mode 100644 docs/geminidb/umn/nosql_05_0002.html create mode 100644 docs/geminidb/umn/nosql_05_0003.html create mode 100644 docs/geminidb/umn/nosql_05_0004.html create mode 100644 docs/geminidb/umn/nosql_05_0005.html create mode 100644 docs/geminidb/umn/nosql_05_0006.html create mode 100644 docs/geminidb/umn/nosql_05_0007.html create mode 100644 docs/geminidb/umn/nosql_05_0008.html create mode 100644 docs/geminidb/umn/nosql_05_0009.html create mode 100644 docs/geminidb/umn/nosql_05_0010.html create mode 100644 docs/geminidb/umn/nosql_05_0011.html create mode 100644 docs/geminidb/umn/nosql_05_0012.html create mode 100644 docs/geminidb/umn/nosql_06_0001.html create mode 100644 docs/geminidb/umn/nosql_cassandra_0001.html create mode 100644 docs/geminidb/umn/nosql_increase_nodes.html create mode 100644 docs/geminidb/umn/nosql_increase_storage.html create mode 100644 docs/geminidb/umn/nosql_introduction.html create mode 100644 docs/geminidb/umn/nosql_login.html create mode 100644 docs/geminidb/umn/nosql_user_guide.html create mode 100644 docs/geminidb/umn/public_sys-resources/caution_3.0-en-us.png create mode 100644 docs/geminidb/umn/public_sys-resources/danger_3.0-en-us.png create mode 100644 docs/geminidb/umn/public_sys-resources/delta.gif create mode 100644 docs/geminidb/umn/public_sys-resources/deltaend.gif create mode 100644 docs/geminidb/umn/public_sys-resources/icon-arrowdn.gif create mode 100644 docs/geminidb/umn/public_sys-resources/icon-arrowrt.gif create mode 100644 docs/geminidb/umn/public_sys-resources/icon-caution.gif create mode 100644 docs/geminidb/umn/public_sys-resources/icon-danger.gif create mode 100644 docs/geminidb/umn/public_sys-resources/icon-huawei.gif create mode 100644 docs/geminidb/umn/public_sys-resources/icon-note.gif create mode 100644 docs/geminidb/umn/public_sys-resources/icon-notice.gif create mode 100644 docs/geminidb/umn/public_sys-resources/icon-tip.gif create mode 100644 docs/geminidb/umn/public_sys-resources/icon-warning.gif create mode 100644 docs/geminidb/umn/public_sys-resources/note_3.0-en-us.png create mode 100644 docs/geminidb/umn/public_sys-resources/notice_3.0-en-us.png create mode 100644 docs/geminidb/umn/public_sys-resources/warning_3.0-en-us.png diff --git a/docs/geminidb/umn/ALL_META.TXT.json b/docs/geminidb/umn/ALL_META.TXT.json new file mode 100644 index 00000000..cf78bbd0 --- /dev/null +++ b/docs/geminidb/umn/ALL_META.TXT.json @@ -0,0 +1,1265 @@ +[ + { + "dockw":"User Guide" + }, + { + "uri":"nosql_user_guide.html", + "node_id":"nosql_user_guide.xml", + "product_code":"nosql", + "code":"1", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Introduction", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Introduction", + "githuburl":"" + }, + { + "uri":"nosql_introduction.html", + "node_id":"nosql_introduction.xml", + "product_code":"nosql", + "code":"2", + "des":"GeminiDB is a distributed, multi-model NoSQL database service with decoupled compute and storage architecture. This high availability database is secure and scalable, can", + "doc_type":"usermanual", + "kw":"What Is GeminiDB?,Introduction,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"What Is GeminiDB?", + "githuburl":"" + }, + { + "uri":"nosql_01_0001.html", + "node_id":"nosql_01_0001.xml", + "product_code":"nosql", + "code":"3", + "des":"GeminiDB is a distributed database with decoupled compute and storage architecture. The compute clusters consist of multiple homogeneous nodes, and data is stored in a di", + "doc_type":"usermanual", + "kw":"System Architecture,Introduction,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"System Architecture", + "githuburl":"" + }, + { + "uri":"nosql_01_0002.html", + "node_id":"nosql_01_0002.xml", + "product_code":"nosql", + "code":"4", + "des":"Data backupData can be backed up automatically or manually. In an automated backup, all of the data in a given DB instance is backed up by the system. In a manual backup,", + "doc_type":"usermanual", + "kw":"Highlights,Introduction,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Highlights", + "githuburl":"" + }, + { + "uri":"nosql_01_0010.html", + "node_id":"nosql_01_0010.xml", + "product_code":"nosql", + "code":"5", + "des":"GeminiDB is compatible with Cassandra APIs. It is designed for write-intensive scenarios, specifically applied in manufacturing, logistics, health care, real estate, ener", + "doc_type":"usermanual", + "kw":"Typical Application Scenarios,Introduction,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Typical Application Scenarios", + "githuburl":"" + }, + { + "uri":"nosql_01_0004.html", + "node_id":"nosql_01_0004.xml", + "product_code":"nosql", + "code":"6", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"DB Instance", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"DB Instance", + "githuburl":"" + }, + { + "uri":"nosql_01_0110.html", + "node_id":"nosql_01_0110.xml", + "product_code":"nosql", + "code":"7", + "des":"A DB instance is the minimum management unit and an independently running database. A DB instance can contain multiple user-created databases, and you can access it using", + "doc_type":"usermanual", + "kw":"Overview,DB Instance,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Overview", + "githuburl":"" + }, + { + "uri":"nosql_01_0007.html", + "node_id":"nosql_01_0007.xml", + "product_code":"nosql", + "code":"8", + "des":"This section lists the GeminiDB-compatible APIs and versions.", + "doc_type":"usermanual", + "kw":"Compatible APIs and Versions,DB Instance,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Compatible APIs and Versions", + "githuburl":"" + }, + { + "uri":"nosql_01_0006.html", + "node_id":"nosql_01_0006.xml", + "product_code":"nosql", + "code":"9", + "des":"The DB instance specifications depend on the selected DB engine.", + "doc_type":"usermanual", + "kw":"DB Instance Specifications,DB Instance,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"DB Instance Specifications", + "githuburl":"" + }, + { + "uri":"nosql_01_0008.html", + "node_id":"nosql_01_0008.xml", + "product_code":"nosql", + "code":"10", + "des":"You can determine whether a DB instance is healthy based on its status displayed on the management console.", + "doc_type":"usermanual", + "kw":"DB Instance Status,DB Instance,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"DB Instance Status", + "githuburl":"" + }, + { + "uri":"nosql_01_101.html", + "node_id":"nosql_01_101.xml", + "product_code":"nosql", + "code":"11", + "des":"GeminiDB provides two types of user permissions by default: user management and resource management.User management refers to the management of users, user groups, and us", + "doc_type":"usermanual", + "kw":"User Permissions,Introduction,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"User Permissions", + "githuburl":"" + }, + { + "uri":"nosql_01_0003.html", + "node_id":"nosql_01_0003.xml", + "product_code":"nosql", + "code":"12", + "des":"A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.A region is a physical data center. Each ", + "doc_type":"usermanual", + "kw":"Regions and AZs,Introduction,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Regions and AZs", + "githuburl":"" + }, + { + "uri":"nosql_01_0009.html", + "node_id":"nosql_01_0009.xml", + "product_code":"nosql", + "code":"13", + "des":"Table 1 shows the relationship between GeminiDB and other services.", + "doc_type":"usermanual", + "kw":"Related Services,Introduction,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Related Services", + "githuburl":"" + }, + { + "uri":"nosql_login.html", + "node_id":"nosql_login.xml", + "product_code":"nosql", + "code":"14", + "des":"You have registered a cloud account for logging in to the GeminiDB management console.If you do not have a cloud account, register an account at the official website. Aft", + "doc_type":"usermanual", + "kw":"Logging In to the GeminiDB Console,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Logging In to the GeminiDB Console", + "githuburl":"" + }, + { + "uri":"nosql_02_0001.html", + "node_id":"nosql_02_0001.xml", + "product_code":"nosql", + "code":"15", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Getting Started with GeminiDB Cassandra", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Getting Started with GeminiDB Cassandra", + "githuburl":"" + }, + { + "uri":"nosql_06_0001.html", + "node_id":"nosql_06_0001.xml", + "product_code":"nosql", + "code":"16", + "des":"You can connect to a GeminiDB Cassandra DB instance over a private or public network.", + "doc_type":"usermanual", + "kw":"Instance Connection Methods,Getting Started with GeminiDB Cassandra,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Instance Connection Methods", + "githuburl":"" + }, + { + "uri":"nosql_02_0006.html", + "node_id":"nosql_02_0006.xml", + "product_code":"nosql", + "code":"17", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Connecting to a GeminiDB Cassandra Instance Over Private Networks", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Connecting to a GeminiDB Cassandra Instance Over Private Networks", + "githuburl":"" + }, + { + "uri":"nosql_02_0002.html", + "node_id":"nosql_02_0002.xml", + "product_code":"nosql", + "code":"18", + "des":"This section describes how to create a DB instance that is compatible with Cassandra APIs.If you need to modify the specifications, click Previous to return to the previo", + "doc_type":"usermanual", + "kw":"Creating a GeminiDB Cassandra Instance,Connecting to a GeminiDB Cassandra Instance Over Private Netw", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Creating a GeminiDB Cassandra Instance", + "githuburl":"" + }, + { + "uri":"nosql_02_0004.html", + "node_id":"nosql_02_0004.xml", + "product_code":"nosql", + "code":"19", + "des":"The default security group rule allows all outgoing data packets. ECSs and GeminiDB instances in the same security group can access each other. After a security group is ", + "doc_type":"usermanual", + "kw":"Configuring Security Group Rules,Connecting to a GeminiDB Cassandra Instance Over Private Networks,U", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Configuring Security Group Rules", + "githuburl":"" + }, + { + "uri":"nosql_02_0005.html", + "node_id":"nosql_02_0005.xml", + "product_code":"nosql", + "code":"20", + "des":"This section uses the Linux operating system as an example to describe how to connect an ECS to a GeminiDB Cassandra instance over private networks.The DB instances must ", + "doc_type":"usermanual", + "kw":"DB instance,Connecting to a GeminiDB Cassandra Instance Over Private Networks,Connecting to a Gemini", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Connecting to a GeminiDB Cassandra Instance Over Private Networks", + "githuburl":"" + }, + { + "uri":"nosql_02_0007.html", + "node_id":"nosql_02_0007.xml", + "product_code":"nosql", + "code":"21", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Connecting to a GeminiDB Cassandra Instance Over Public Networks", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Connecting to a GeminiDB Cassandra Instance Over Public Networks", + "githuburl":"" + }, + { + "uri":"nosql_02_0010.html", + "node_id":"nosql_02_0010.xml", + "product_code":"nosql", + "code":"22", + "des":"This section describes how to create a DB instance that is compatible with Cassandra APIs.If you need to modify the specifications, click Previous to return to the previo", + "doc_type":"usermanual", + "kw":"Creating a GeminiDB Cassandra Instance,Connecting to a GeminiDB Cassandra Instance Over Public Netwo", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Creating a GeminiDB Cassandra Instance", + "githuburl":"" + }, + { + "uri":"nosql_02_0008.html", + "node_id":"nosql_02_0008.xml", + "product_code":"nosql", + "code":"23", + "des":"The Elastic IP service provides independent public IP addresses and bandwidth for Internet access. After you create a GeminiDB Cassandra instance, you can bind an EIP to ", + "doc_type":"usermanual", + "kw":"Binding an EIP,Connecting to a GeminiDB Cassandra Instance Over Public Networks,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Binding an EIP", + "githuburl":"" + }, + { + "uri":"nosql_02_0011.html", + "node_id":"nosql_02_0011.xml", + "product_code":"nosql", + "code":"24", + "des":"The default security group rule allows all outgoing data packets. ECSs and GeminiDB Cassandra instances in the same security group can access each other. After a security", + "doc_type":"usermanual", + "kw":"Configuring Security Group Rules,Connecting to a GeminiDB Cassandra Instance Over Public Networks,Us", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Configuring Security Group Rules", + "githuburl":"" + }, + { + "uri":"nosql_02_0009.html", + "node_id":"nosql_02_0009.xml", + "product_code":"nosql", + "code":"25", + "des":"You can use an ECS or local device to connect to a GeminiDB instance over a public network.This section describes how to use a Linux ECS to connect to a GeminiDB Cassandr", + "doc_type":"usermanual", + "kw":"DB instance,Connecting to a GeminiDB Cassandra Instance Over Public Networks,Connecting to a GeminiD", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Connecting to a GeminiDB Cassandra Instance Over Public Networks", + "githuburl":"" + }, + { + "uri":"nosql_cassandra_0001.html", + "node_id":"nosql_cassandra_0001.xml", + "product_code":"nosql", + "code":"26", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Working with GeminiDB Cassandra API", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Working with GeminiDB Cassandra API", + "githuburl":"" + }, + { + "uri":"nosql_03_0002.html", + "node_id":"nosql_03_0002.xml", + "product_code":"nosql", + "code":"27", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"DB Instance Management", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"DB Instance Management", + "githuburl":"" + }, + { + "uri":"nosql_03_0025.html", + "node_id":"nosql_03_0025.xml", + "product_code":"nosql", + "code":"28", + "des":"This section describes how to change a GeminiDB Cassandra instance name to identify different DB instances.To submit the change, click OK.The new name can be the same as ", + "doc_type":"usermanual", + "kw":"Changing a DB Instance Name,DB Instance Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Changing a DB Instance Name", + "githuburl":"" + }, + { + "uri":"nosql_03_0016.html", + "node_id":"nosql_03_0016.xml", + "product_code":"nosql", + "code":"29", + "des":"For security reasons, change administrator passwords periodically.If the instance status is Available, Backing up, Checking restoration, Scaling up or certain nodes becom", + "doc_type":"usermanual", + "kw":"Resetting the Administrator Password,DB Instance Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Resetting the Administrator Password", + "githuburl":"" + }, + { + "uri":"nosql_03_0003.html", + "node_id":"nosql_03_0003.xml", + "product_code":"nosql", + "code":"30", + "des":"You may need to occasionally restart a DB instance to perform routine maintenance.If the instance status is Available, Abnormal, or Checking restoration, you can restart ", + "doc_type":"usermanual", + "kw":"Restarting a DB Instance,DB Instance Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Restarting a DB Instance", + "githuburl":"" + }, + { + "uri":"nosql_increase_storage.html", + "node_id":"nosql_increase_storage.xml", + "product_code":"nosql", + "code":"31", + "des":"This section describes how to scale up the storage space of a DB instance to suit your service requirements.During the scale-up process, the DB instance will not restart,", + "doc_type":"usermanual", + "kw":"Scaling Up Storage Space,DB Instance Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Scaling Up Storage Space", + "githuburl":"" + }, + { + "uri":"nosql_03_0026.html", + "node_id":"nosql_03_0026.xml", + "product_code":"nosql", + "code":"32", + "des":"This section describes how to change the CPU or memory of your instance to suit your service requirements.Instances can be scaled up or down.Services will be interrupted ", + "doc_type":"usermanual", + "kw":"Changing a DB Instance Class,DB Instance Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Changing a DB Instance Class", + "githuburl":"" + }, + { + "uri":"nosql_increase_nodes.html", + "node_id":"nosql_increase_nodes.xml", + "product_code":"nosql", + "code":"33", + "des":"This section describes how to add nodes to a DB instance to suit your service requirements. You can also delete a node as required. For details, see Deleting Nodes.Adding", + "doc_type":"usermanual", + "kw":"Adding Nodes,DB Instance Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Adding Nodes", + "githuburl":"" + }, + { + "uri":"nosql_03_0004.html", + "node_id":"nosql_03_0004.xml", + "product_code":"nosql", + "code":"34", + "des":"You can delete nodes that are no longer used to release resources.Deleted nodes cannot be recovered. Exercise caution when performing this operation.The status of the ins", + "doc_type":"usermanual", + "kw":"Deleting Nodes,DB Instance Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Deleting Nodes", + "githuburl":"" + }, + { + "uri":"nosql_03_0005.html", + "node_id":"nosql_03_0005.xml", + "product_code":"nosql", + "code":"35", + "des":"This section describes how to delete a DB instance no longer used to release resources.If you delete a DB instance, all the data in it and all automated backups are autom", + "doc_type":"usermanual", + "kw":"Deleting DB Instances,DB Instance Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Deleting DB Instances", + "githuburl":"" + }, + { + "uri":"nosql_03_0014.html", + "node_id":"nosql_03_0014.xml", + "product_code":"nosql", + "code":"36", + "des":"Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags g", + "doc_type":"usermanual", + "kw":"Managing Tags,DB Instance Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Managing Tags", + "githuburl":"" + }, + { + "uri":"nosql_03_0015.html", + "node_id":"nosql_03_0015.xml", + "product_code":"nosql", + "code":"37", + "des":"The COPY command is one of cqlsh commands. It includes COPY TO and COPY FROM. They are used to copy data to and from Cassandra.You can run the COPY TO command to export d", + "doc_type":"usermanual", + "kw":"Using COPY to Import and Export Data,Working with GeminiDB Cassandra API,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Using COPY to Import and Export Data", + "githuburl":"" + }, + { + "uri":"nosql_03_0006.html", + "node_id":"nosql_03_0006.xml", + "product_code":"nosql", + "code":"38", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Backups and Restorations", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Backups and Restorations", + "githuburl":"" + }, + { + "uri":"nosql_03_0007.html", + "node_id":"nosql_03_0007.xml", + "product_code":"nosql", + "code":"39", + "des":"GeminiDB Cassandra creates automated backups to ensure data reliability. If a database or table is maliciously or accidentally deleted, backups can help you ensure you do", + "doc_type":"usermanual", + "kw":"automated backups,Managing Automated Backups,Backups and Restorations,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Managing Automated Backups", + "githuburl":"" + }, + { + "uri":"nosql_03_0008.html", + "node_id":"nosql_03_0008.xml", + "product_code":"nosql", + "code":"40", + "des":"To ensure data reliability, GeminiDB Cassandra API allows you to manually back up DB instances whose status is Available. If a database or table is deleted, maliciously o", + "doc_type":"usermanual", + "kw":"Managing Manual Backups,Backups and Restorations,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Managing Manual Backups", + "githuburl":"" + }, + { + "uri":"nosql_03_0009.html", + "node_id":"nosql_03_0009.xml", + "product_code":"nosql", + "code":"41", + "des":"GeminiDB Cassandra API allows you to restore the existing backup to a new DB instance.Method 1On the Instance Management page, click the target DB instance.On the Backups", + "doc_type":"usermanual", + "kw":"Restoring Data to a New DB Instance,Backups and Restorations,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Restoring Data to a New DB Instance", + "githuburl":"" + }, + { + "uri":"nosql_05_0001.html", + "node_id":"nosql_05_0001.xml", + "product_code":"nosql", + "code":"42", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Parameter Template Management", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Parameter Template Management", + "githuburl":"" + }, + { + "uri":"nosql_05_0002.html", + "node_id":"nosql_05_0002.xml", + "product_code":"nosql", + "code":"43", + "des":"You can use database parameter templates to manage the DB engine configuration. A database parameter template acts as a container for engine configuration values that can", + "doc_type":"usermanual", + "kw":"Creating a Parameter Template,Parameter Template Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Creating a Parameter Template", + "githuburl":"" + }, + { + "uri":"nosql_05_0003.html", + "node_id":"nosql_05_0003.xml", + "product_code":"nosql", + "code":"44", + "des":"This section describes how to modify parameters in the parameter template that you have created to meet your service requirements and achieve optimal performance.Note tha", + "doc_type":"usermanual", + "kw":"Modifying a Parameter Template,Parameter Template Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Modifying a Parameter Template", + "githuburl":"" + }, + { + "uri":"nosql_05_0012.html", + "node_id":"nosql_05_0012.xml", + "product_code":"nosql", + "code":"45", + "des":"You can view the change history of a parameter template.In a newly exported or created parameter template, change history is left blank.You can apply the parameter templa", + "doc_type":"usermanual", + "kw":"Viewing Parameter Change History,Parameter Template Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Viewing Parameter Change History", + "githuburl":"" + }, + { + "uri":"nosql_05_0004.html", + "node_id":"nosql_05_0004.xml", + "product_code":"nosql", + "code":"46", + "des":"You can export a parameter template of a DB instance for future use. To learn how to apply the exported parameter template to a DB instance, refer to section Applying a P", + "doc_type":"usermanual", + "kw":"Exporting a Parameter Template,Parameter Template Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Exporting a Parameter Template", + "githuburl":"" + }, + { + "uri":"nosql_05_0005.html", + "node_id":"nosql_05_0005.xml", + "product_code":"nosql", + "code":"47", + "des":"This section guides you on how to compare two parameter templates of the same node type and DB engine version to know their current settings.If their settings are differe", + "doc_type":"usermanual", + "kw":"Compare,Comparing Parameter Templates,Parameter Template Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Comparing Parameter Templates", + "githuburl":"" + }, + { + "uri":"nosql_05_0006.html", + "node_id":"nosql_05_0006.xml", + "product_code":"nosql", + "code":"48", + "des":"You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values f", + "doc_type":"usermanual", + "kw":"Replicating a Parameter Template,Parameter Template Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Replicating a Parameter Template", + "githuburl":"" + }, + { + "uri":"nosql_05_0007.html", + "node_id":"nosql_05_0007.xml", + "product_code":"nosql", + "code":"49", + "des":"You can reset all parameters in a custom parameter template to their default settings.", + "doc_type":"usermanual", + "kw":"Resetting a Parameter Template,Parameter Template Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Resetting a Parameter Template", + "githuburl":"" + }, + { + "uri":"nosql_05_0008.html", + "node_id":"nosql_05_0008.xml", + "product_code":"nosql", + "code":"50", + "des":"Modifications to parameters in a custom parameter template take effect for DB instances only after you have applied the template to the target DB instances.To apply a def", + "doc_type":"usermanual", + "kw":"Applying a Parameter Template,Parameter Template Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Applying a Parameter Template", + "githuburl":"" + }, + { + "uri":"nosql_05_0009.html", + "node_id":"nosql_05_0009.xml", + "product_code":"nosql", + "code":"51", + "des":"You can view the application records of a parameter template.You can view the name or ID of the DB instance that the parameter template applies to, as well as the applica", + "doc_type":"usermanual", + "kw":"Viewing Application Records of a Parameter Template,Parameter Template Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Viewing Application Records of a Parameter Template", + "githuburl":"" + }, + { + "uri":"nosql_05_0010.html", + "node_id":"nosql_05_0010.xml", + "product_code":"nosql", + "code":"52", + "des":"You can modify the description of a custom parameter template if needed.After you submit the modification, you can view the new description in the Description column on t", + "doc_type":"usermanual", + "kw":"Modifying a Parameter Template Description,Parameter Template Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Modifying a Parameter Template Description", + "githuburl":"" + }, + { + "uri":"nosql_05_0011.html", + "node_id":"nosql_05_0011.xml", + "product_code":"nosql", + "code":"53", + "des":"You can delete a custom parameter template that is no longer in use.Deleted templates cannot be recovered, so exercise caution when performing this operation.Default para", + "doc_type":"usermanual", + "kw":"Deleting a Parameter Template,Parameter Template Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Deleting a Parameter Template", + "githuburl":"" + }, + { + "uri":"nosql_03_0010.html", + "node_id":"nosql_03_0010.xml", + "product_code":"nosql", + "code":"54", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Monitoring and Alarm Reporting", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Monitoring and Alarm Reporting", + "githuburl":"" + }, + { + "uri":"nosql_03_0011.html", + "node_id":"nosql_03_0011.xml", + "product_code":"nosql", + "code":"55", + "des":"This section describes GeminiDB Cassandra metrics reported to Cloud Eye as well as their namespaces and dimensions. You can use APIs provided by Cloud Eye to query the me", + "doc_type":"usermanual", + "kw":"GeminiDB Cassandra Metrics,Monitoring and Alarm Reporting,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"GeminiDB Cassandra Metrics", + "githuburl":"" + }, + { + "uri":"nosql_03_0012.html", + "node_id":"nosql_03_0012.xml", + "product_code":"nosql", + "code":"56", + "des":"You can set alarm rules to customize the monitored objects and notification policies and to stay aware of the database operating status.The alarm rules include alarm rule", + "doc_type":"usermanual", + "kw":"Setting Alarm Rules,Monitoring and Alarm Reporting,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Setting Alarm Rules", + "githuburl":"" + }, + { + "uri":"nosql_03_0013.html", + "node_id":"nosql_03_0013.xml", + "product_code":"nosql", + "code":"57", + "des":"Cloud Eye monitors GeminiDB running statuses. You can obtain the monitoring metrics of GeminiDB on the management console.Monitored data requires a period of time for tra", + "doc_type":"usermanual", + "kw":"Viewing Metrics,Monitoring and Alarm Reporting,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Viewing Metrics", + "githuburl":"" + }, + { + "uri":"nosql_03_0019.html", + "node_id":"nosql_03_0019.xml", + "product_code":"nosql", + "code":"58", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Auditing", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Auditing", + "githuburl":"" + }, + { + "uri":"nosql_03_0017.html", + "node_id":"nosql_03_0017.xml", + "product_code":"nosql", + "code":"59", + "des":"With CTS, you can record operations associated with GeminiDB for later query, audit, and backtrack operations.Table 1 lists the key operations that can be recorded by CTS", + "doc_type":"usermanual", + "kw":"Key Operations Recorded by CTS,Auditing,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Key Operations Recorded by CTS", + "githuburl":"" + }, + { + "uri":"nosql_03_0018.html", + "node_id":"nosql_03_0018.xml", + "product_code":"nosql", + "code":"60", + "des":"After CTS is enabled, CTS starts recording operations on cloud resources. The CTS console stores the last seven days of operation records.This section describes how to qu", + "doc_type":"usermanual", + "kw":"Querying Traces,Auditing,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Querying Traces", + "githuburl":"" + }, + { + "uri":"nosql_03_0027.html", + "node_id":"nosql_03_0027.xml", + "product_code":"nosql", + "code":"61", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Log Management", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Log Management", + "githuburl":"" + }, + { + "uri":"nosql_03_0028.html", + "node_id":"nosql_03_0028.xml", + "product_code":"nosql", + "code":"62", + "des":"GeminiDB allows you to view slow query logs of databases. The unit of the execution time is ms. With slow query logs, you can identify and optimize slowly executed statem", + "doc_type":"usermanual", + "kw":"Slow Query Logs,Log Management,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Slow Query Logs", + "githuburl":"" + }, + { + "uri":"nosql_04_change_history.html", + "node_id":"nosql_04_change_history.xml", + "product_code":"nosql", + "code":"63", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Change History,User Guide", + "search_title":"", + "metedata":[ + { + "IsMulti":"No", + "prodname":"nosql", + "documenttype":"usermanual", + "IsBot":"No" + } + ], + "title":"Change History", + "githuburl":"" + } +] \ No newline at end of file diff --git a/docs/geminidb/umn/CLASS.TXT.json b/docs/geminidb/umn/CLASS.TXT.json new file mode 100644 index 00000000..717edd2c --- /dev/null +++ b/docs/geminidb/umn/CLASS.TXT.json @@ -0,0 +1,569 @@ +[ + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"nosql", + "title":"Introduction", + "uri":"nosql_user_guide.html", + "doc_type":"usermanual", + "p_code":"", + "code":"1" + }, + { + "desc":"GeminiDB is a distributed, multi-model NoSQL database service with decoupled compute and storage architecture. This high availability database is secure and scalable, can", + "product_code":"nosql", + "title":"What Is GeminiDB?", + "uri":"nosql_introduction.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"2" + }, + { + "desc":"GeminiDB is a distributed database with decoupled compute and storage architecture. The compute clusters consist of multiple homogeneous nodes, and data is stored in a di", + "product_code":"nosql", + "title":"System Architecture", + "uri":"nosql_01_0001.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"3" + }, + { + "desc":"Data backupData can be backed up automatically or manually. In an automated backup, all of the data in a given DB instance is backed up by the system. In a manual backup,", + "product_code":"nosql", + "title":"Highlights", + "uri":"nosql_01_0002.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"4" + }, + { + "desc":"GeminiDB is compatible with Cassandra APIs. It is designed for write-intensive scenarios, specifically applied in manufacturing, logistics, health care, real estate, ener", + "product_code":"nosql", + "title":"Typical Application Scenarios", + "uri":"nosql_01_0010.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"5" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"nosql", + "title":"DB Instance", + "uri":"nosql_01_0004.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"6" + }, + { + "desc":"A DB instance is the minimum management unit and an independently running database. A DB instance can contain multiple user-created databases, and you can access it using", + "product_code":"nosql", + "title":"Overview", + "uri":"nosql_01_0110.html", + "doc_type":"usermanual", + "p_code":"6", + "code":"7" + }, + { + "desc":"This section lists the GeminiDB-compatible APIs and versions.", + "product_code":"nosql", + "title":"Compatible APIs and Versions", + "uri":"nosql_01_0007.html", + "doc_type":"usermanual", + "p_code":"6", + "code":"8" + }, + { + "desc":"The DB instance specifications depend on the selected DB engine.", + "product_code":"nosql", + "title":"DB Instance Specifications", + "uri":"nosql_01_0006.html", + "doc_type":"usermanual", + "p_code":"6", + "code":"9" + }, + { + "desc":"You can determine whether a DB instance is healthy based on its status displayed on the management console.", + "product_code":"nosql", + "title":"DB Instance Status", + "uri":"nosql_01_0008.html", + "doc_type":"usermanual", + "p_code":"6", + "code":"10" + }, + { + "desc":"GeminiDB provides two types of user permissions by default: user management and resource management.User management refers to the management of users, user groups, and us", + "product_code":"nosql", + "title":"User Permissions", + "uri":"nosql_01_101.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"11" + }, + { + "desc":"A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.A region is a physical data center. Each ", + "product_code":"nosql", + "title":"Regions and AZs", + "uri":"nosql_01_0003.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"12" + }, + { + "desc":"Table 1 shows the relationship between GeminiDB and other services.", + "product_code":"nosql", + "title":"Related Services", + "uri":"nosql_01_0009.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"13" + }, + { + "desc":"You have registered a cloud account for logging in to the GeminiDB management console.If you do not have a cloud account, register an account at the official website. Aft", + "product_code":"nosql", + "title":"Logging In to the GeminiDB Console", + "uri":"nosql_login.html", + "doc_type":"usermanual", + "p_code":"", + "code":"14" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"nosql", + "title":"Getting Started with GeminiDB Cassandra", + "uri":"nosql_02_0001.html", + "doc_type":"usermanual", + "p_code":"", + "code":"15" + }, + { + "desc":"You can connect to a GeminiDB Cassandra DB instance over a private or public network.", + "product_code":"nosql", + "title":"Instance Connection Methods", + "uri":"nosql_06_0001.html", + "doc_type":"usermanual", + "p_code":"15", + "code":"16" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"nosql", + "title":"Connecting to a GeminiDB Cassandra Instance Over Private Networks", + "uri":"nosql_02_0006.html", + "doc_type":"usermanual", + "p_code":"15", + "code":"17" + }, + { + "desc":"This section describes how to create a DB instance that is compatible with Cassandra APIs.If you need to modify the specifications, click Previous to return to the previo", + "product_code":"nosql", + "title":"Creating a GeminiDB Cassandra Instance", + "uri":"nosql_02_0002.html", + "doc_type":"usermanual", + "p_code":"17", + "code":"18" + }, + { + "desc":"The default security group rule allows all outgoing data packets. ECSs and GeminiDB instances in the same security group can access each other. After a security group is ", + "product_code":"nosql", + "title":"Configuring Security Group Rules", + "uri":"nosql_02_0004.html", + "doc_type":"usermanual", + "p_code":"17", + "code":"19" + }, + { + "desc":"This section uses the Linux operating system as an example to describe how to connect an ECS to a GeminiDB Cassandra instance over private networks.The DB instances must ", + "product_code":"nosql", + "title":"Connecting to a GeminiDB Cassandra Instance Over Private Networks", + "uri":"nosql_02_0005.html", + "doc_type":"usermanual", + "p_code":"17", + "code":"20" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"nosql", + "title":"Connecting to a GeminiDB Cassandra Instance Over Public Networks", + "uri":"nosql_02_0007.html", + "doc_type":"usermanual", + "p_code":"15", + "code":"21" + }, + { + "desc":"This section describes how to create a DB instance that is compatible with Cassandra APIs.If you need to modify the specifications, click Previous to return to the previo", + "product_code":"nosql", + "title":"Creating a GeminiDB Cassandra Instance", + "uri":"nosql_02_0010.html", + "doc_type":"usermanual", + "p_code":"21", + "code":"22" + }, + { + "desc":"The Elastic IP service provides independent public IP addresses and bandwidth for Internet access. After you create a GeminiDB Cassandra instance, you can bind an EIP to ", + "product_code":"nosql", + "title":"Binding an EIP", + "uri":"nosql_02_0008.html", + "doc_type":"usermanual", + "p_code":"21", + "code":"23" + }, + { + "desc":"The default security group rule allows all outgoing data packets. ECSs and GeminiDB Cassandra instances in the same security group can access each other. After a security", + "product_code":"nosql", + "title":"Configuring Security Group Rules", + "uri":"nosql_02_0011.html", + "doc_type":"usermanual", + "p_code":"21", + "code":"24" + }, + { + "desc":"You can use an ECS or local device to connect to a GeminiDB instance over a public network.This section describes how to use a Linux ECS to connect to a GeminiDB Cassandr", + "product_code":"nosql", + "title":"Connecting to a GeminiDB Cassandra Instance Over Public Networks", + "uri":"nosql_02_0009.html", + "doc_type":"usermanual", + "p_code":"21", + "code":"25" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"nosql", + "title":"Working with GeminiDB Cassandra API", + "uri":"nosql_cassandra_0001.html", + "doc_type":"usermanual", + "p_code":"", + "code":"26" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"nosql", + "title":"DB Instance Management", + "uri":"nosql_03_0002.html", + "doc_type":"usermanual", + "p_code":"26", + "code":"27" + }, + { + "desc":"This section describes how to change a GeminiDB Cassandra instance name to identify different DB instances.To submit the change, click OK.The new name can be the same as ", + "product_code":"nosql", + "title":"Changing a DB Instance Name", + "uri":"nosql_03_0025.html", + "doc_type":"usermanual", + "p_code":"27", + "code":"28" + }, + { + "desc":"For security reasons, change administrator passwords periodically.If the instance status is Available, Backing up, Checking restoration, Scaling up or certain nodes becom", + "product_code":"nosql", + "title":"Resetting the Administrator Password", + "uri":"nosql_03_0016.html", + "doc_type":"usermanual", + "p_code":"27", + "code":"29" + }, + { + "desc":"You may need to occasionally restart a DB instance to perform routine maintenance.If the instance status is Available, Abnormal, or Checking restoration, you can restart ", + "product_code":"nosql", + "title":"Restarting a DB Instance", + "uri":"nosql_03_0003.html", + "doc_type":"usermanual", + "p_code":"27", + "code":"30" + }, + { + "desc":"This section describes how to scale up the storage space of a DB instance to suit your service requirements.During the scale-up process, the DB instance will not restart,", + "product_code":"nosql", + "title":"Scaling Up Storage Space", + "uri":"nosql_increase_storage.html", + "doc_type":"usermanual", + "p_code":"27", + "code":"31" + }, + { + "desc":"This section describes how to change the CPU or memory of your instance to suit your service requirements.Instances can be scaled up or down.Services will be interrupted ", + "product_code":"nosql", + "title":"Changing a DB Instance Class", + "uri":"nosql_03_0026.html", + "doc_type":"usermanual", + "p_code":"27", + "code":"32" + }, + { + "desc":"This section describes how to add nodes to a DB instance to suit your service requirements. You can also delete a node as required. For details, see Deleting Nodes.Adding", + "product_code":"nosql", + "title":"Adding Nodes", + "uri":"nosql_increase_nodes.html", + "doc_type":"usermanual", + "p_code":"27", + "code":"33" + }, + { + "desc":"You can delete nodes that are no longer used to release resources.Deleted nodes cannot be recovered. Exercise caution when performing this operation.The status of the ins", + "product_code":"nosql", + "title":"Deleting Nodes", + "uri":"nosql_03_0004.html", + "doc_type":"usermanual", + "p_code":"27", + "code":"34" + }, + { + "desc":"This section describes how to delete a DB instance no longer used to release resources.If you delete a DB instance, all the data in it and all automated backups are autom", + "product_code":"nosql", + "title":"Deleting DB Instances", + "uri":"nosql_03_0005.html", + "doc_type":"usermanual", + "p_code":"27", + "code":"35" + }, + { + "desc":"Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags g", + "product_code":"nosql", + "title":"Managing Tags", + "uri":"nosql_03_0014.html", + "doc_type":"usermanual", + "p_code":"27", + "code":"36" + }, + { + "desc":"The COPY command is one of cqlsh commands. It includes COPY TO and COPY FROM. They are used to copy data to and from Cassandra.You can run the COPY TO command to export d", + "product_code":"nosql", + "title":"Using COPY to Import and Export Data", + "uri":"nosql_03_0015.html", + "doc_type":"usermanual", + "p_code":"26", + "code":"37" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"nosql", + "title":"Backups and Restorations", + "uri":"nosql_03_0006.html", + "doc_type":"usermanual", + "p_code":"26", + "code":"38" + }, + { + "desc":"GeminiDB Cassandra creates automated backups to ensure data reliability. If a database or table is maliciously or accidentally deleted, backups can help you ensure you do", + "product_code":"nosql", + "title":"Managing Automated Backups", + "uri":"nosql_03_0007.html", + "doc_type":"usermanual", + "p_code":"38", + "code":"39" + }, + { + "desc":"To ensure data reliability, GeminiDB Cassandra API allows you to manually back up DB instances whose status is Available. If a database or table is deleted, maliciously o", + "product_code":"nosql", + "title":"Managing Manual Backups", + "uri":"nosql_03_0008.html", + "doc_type":"usermanual", + "p_code":"38", + "code":"40" + }, + { + "desc":"GeminiDB Cassandra API allows you to restore the existing backup to a new DB instance.Method 1On the Instance Management page, click the target DB instance.On the Backups", + "product_code":"nosql", + "title":"Restoring Data to a New DB Instance", + "uri":"nosql_03_0009.html", + "doc_type":"usermanual", + "p_code":"38", + "code":"41" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"nosql", + "title":"Parameter Template Management", + "uri":"nosql_05_0001.html", + "doc_type":"usermanual", + "p_code":"26", + "code":"42" + }, + { + "desc":"You can use database parameter templates to manage the DB engine configuration. A database parameter template acts as a container for engine configuration values that can", + "product_code":"nosql", + "title":"Creating a Parameter Template", + "uri":"nosql_05_0002.html", + "doc_type":"usermanual", + "p_code":"42", + "code":"43" + }, + { + "desc":"This section describes how to modify parameters in the parameter template that you have created to meet your service requirements and achieve optimal performance.Note tha", + "product_code":"nosql", + "title":"Modifying a Parameter Template", + "uri":"nosql_05_0003.html", + "doc_type":"usermanual", + "p_code":"42", + "code":"44" + }, + { + "desc":"You can view the change history of a parameter template.In a newly exported or created parameter template, change history is left blank.You can apply the parameter templa", + "product_code":"nosql", + "title":"Viewing Parameter Change History", + "uri":"nosql_05_0012.html", + "doc_type":"usermanual", + "p_code":"42", + "code":"45" + }, + { + "desc":"You can export a parameter template of a DB instance for future use. To learn how to apply the exported parameter template to a DB instance, refer to section Applying a P", + "product_code":"nosql", + "title":"Exporting a Parameter Template", + "uri":"nosql_05_0004.html", + "doc_type":"usermanual", + "p_code":"42", + "code":"46" + }, + { + "desc":"This section guides you on how to compare two parameter templates of the same node type and DB engine version to know their current settings.If their settings are differe", + "product_code":"nosql", + "title":"Comparing Parameter Templates", + "uri":"nosql_05_0005.html", + "doc_type":"usermanual", + "p_code":"42", + "code":"47" + }, + { + "desc":"You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values f", + "product_code":"nosql", + "title":"Replicating a Parameter Template", + "uri":"nosql_05_0006.html", + "doc_type":"usermanual", + "p_code":"42", + "code":"48" + }, + { + "desc":"You can reset all parameters in a custom parameter template to their default settings.", + "product_code":"nosql", + "title":"Resetting a Parameter Template", + "uri":"nosql_05_0007.html", + "doc_type":"usermanual", + "p_code":"42", + "code":"49" + }, + { + "desc":"Modifications to parameters in a custom parameter template take effect for DB instances only after you have applied the template to the target DB instances.To apply a def", + "product_code":"nosql", + "title":"Applying a Parameter Template", + "uri":"nosql_05_0008.html", + "doc_type":"usermanual", + "p_code":"42", + "code":"50" + }, + { + "desc":"You can view the application records of a parameter template.You can view the name or ID of the DB instance that the parameter template applies to, as well as the applica", + "product_code":"nosql", + "title":"Viewing Application Records of a Parameter Template", + "uri":"nosql_05_0009.html", + "doc_type":"usermanual", + "p_code":"42", + "code":"51" + }, + { + "desc":"You can modify the description of a custom parameter template if needed.After you submit the modification, you can view the new description in the Description column on t", + "product_code":"nosql", + "title":"Modifying a Parameter Template Description", + "uri":"nosql_05_0010.html", + "doc_type":"usermanual", + "p_code":"42", + "code":"52" + }, + { + "desc":"You can delete a custom parameter template that is no longer in use.Deleted templates cannot be recovered, so exercise caution when performing this operation.Default para", + "product_code":"nosql", + "title":"Deleting a Parameter Template", + "uri":"nosql_05_0011.html", + "doc_type":"usermanual", + "p_code":"42", + "code":"53" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"nosql", + "title":"Monitoring and Alarm Reporting", + "uri":"nosql_03_0010.html", + "doc_type":"usermanual", + "p_code":"26", + "code":"54" + }, + { + "desc":"This section describes GeminiDB Cassandra metrics reported to Cloud Eye as well as their namespaces and dimensions. You can use APIs provided by Cloud Eye to query the me", + "product_code":"nosql", + "title":"GeminiDB Cassandra Metrics", + "uri":"nosql_03_0011.html", + "doc_type":"usermanual", + "p_code":"54", + "code":"55" + }, + { + "desc":"You can set alarm rules to customize the monitored objects and notification policies and to stay aware of the database operating status.The alarm rules include alarm rule", + "product_code":"nosql", + "title":"Setting Alarm Rules", + "uri":"nosql_03_0012.html", + "doc_type":"usermanual", + "p_code":"54", + "code":"56" + }, + { + "desc":"Cloud Eye monitors GeminiDB running statuses. You can obtain the monitoring metrics of GeminiDB on the management console.Monitored data requires a period of time for tra", + "product_code":"nosql", + "title":"Viewing Metrics", + "uri":"nosql_03_0013.html", + "doc_type":"usermanual", + "p_code":"54", + "code":"57" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"nosql", + "title":"Auditing", + "uri":"nosql_03_0019.html", + "doc_type":"usermanual", + "p_code":"26", + "code":"58" + }, + { + "desc":"With CTS, you can record operations associated with GeminiDB for later query, audit, and backtrack operations.Table 1 lists the key operations that can be recorded by CTS", + "product_code":"nosql", + "title":"Key Operations Recorded by CTS", + "uri":"nosql_03_0017.html", + "doc_type":"usermanual", + "p_code":"58", + "code":"59" + }, + { + "desc":"After CTS is enabled, CTS starts recording operations on cloud resources. The CTS console stores the last seven days of operation records.This section describes how to qu", + "product_code":"nosql", + "title":"Querying Traces", + "uri":"nosql_03_0018.html", + "doc_type":"usermanual", + "p_code":"58", + "code":"60" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"nosql", + "title":"Log Management", + "uri":"nosql_03_0027.html", + "doc_type":"usermanual", + "p_code":"26", + "code":"61" + }, + { + "desc":"GeminiDB allows you to view slow query logs of databases. The unit of the execution time is ms. With slow query logs, you can identify and optimize slowly executed statem", + "product_code":"nosql", + "title":"Slow Query Logs", + "uri":"nosql_03_0028.html", + "doc_type":"usermanual", + "p_code":"61", + "code":"62" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"nosql", + "title":"Change History", + "uri":"nosql_04_change_history.html", + "doc_type":"usermanual", + "p_code":"", + "code":"63" + } +] \ No newline at end of file diff --git a/docs/geminidb/umn/PARAMETERS.txt b/docs/geminidb/umn/PARAMETERS.txt new file mode 100644 index 00000000..6da8d5f0 --- /dev/null +++ b/docs/geminidb/umn/PARAMETERS.txt @@ -0,0 +1,3 @@ +version="" +language="en-us" +type="" \ No newline at end of file diff --git a/docs/geminidb/umn/en-us_image_0000001815045032.png b/docs/geminidb/umn/en-us_image_0000001815045032.png new file mode 100644 index 0000000000000000000000000000000000000000..b7fd23a5d1fd9e35702afe3d2f8029cb870c5749 GIT binary patch literal 248 zcmeAS@N?(olHy`uVBq!ia0vp^{2QeYOVZ*zY~~$9Si2`q!1UrAX&t>*K*>xmV?Hhx> pP~yxD%v(ZUNKAb2l)Yv`qiA$ZXzNn{1`ISV`@iy0XB4ude`@%$AjK*4NJ7sn6_|GN{Sxeh4su7M@LiSB}ePy2F!)-rgy`njxg HN@xNAtJ+Ak literal 0 HcmV?d00001 diff --git a/docs/geminidb/umn/en-us_image_0000001815045404.png b/docs/geminidb/umn/en-us_image_0000001815045404.png new file mode 100644 index 0000000000000000000000000000000000000000..6160903ac89b81511ca42eac50f702fd218ded47 GIT binary patch literal 296 zcmeAS@N?(olHy`uVBq!ia0vp^5Nn{1`ISV`@iy0XB4ude`@%$AjK*7D9E{-7{-fu5Day2E)O8OO zSM~nZ6WF4C%wbKd%iB`ngV}Pdz2{z-2XEte#;+&x{I7%hk3vC#?uH1KBW_GtQ>GsJ z`fr!16yt@*sck9S9VX@LJn?>DYj^efnt)%PyXzKcZrEEAZ$A0>Oz8}fOSb&$Cd`XH z{^!_C=@tDE&(0q4DKMczz qe$~vG^OIR#jBz7J$6sp(8-|oO%p84@IUGQbFnGH9xvXe7D%F2O(yu7@Ef`TF#C@Co^gMo^QimIxrnwpwA7-(o{XliO|X=!PL zfsT%juCA`0o}RwGz5y5*8X6iI85tWJo0yoGnwpxKnVFlLTUc0FT3T9JSy@|K+kkCcvmzTGP*6~CaBxUSNN8wiSXfv@L_}m{WK>jCbaZq~OiWx{Tzq_dLPA1fVq$V~a!N`{ zYHDg)T3SX%MrLMaR#sMac6M%VZeCtqetv#oVPR2GQAtTjX=!O$Sy@FzMP+4WRaI3@ zO-*fWZGC-xLqkJTQ&V$ub4yE0TU%RudwXYRXIEEOPft&8Z*PBp|AYw>CQX_&dGh3` zQ>RX!K7GcF8M9{1nmv2=+_`h-&!4|w!GcAL7A;=9cQ>uk5sDH4e!pN zM?2c%!f)$Moqn;JbAR{#-LH2<-aWd<6M=_Uy)Vz z>Gb1s+(~DB#NsS6_)g4`cRj>@b~4MGr%TsH2#HlrdJFVdQ&MBb@08(^UA^-pY literal 0 HcmV?d00001 diff --git a/docs/geminidb/umn/en-us_image_0000001815204812.png b/docs/geminidb/umn/en-us_image_0000001815204812.png new file mode 100644 index 0000000000000000000000000000000000000000..c808e11c36ee8c29d51723f5e042624ff604d4a6 GIT binary patch literal 540 zcmV+%0^|LOP)Px#1ZP1_K>z@;j|==^1poj532;bRa{vGi!vFvd!vV){sAK>D0kKI$K~z{r?U*f( zgFq05?_VPjD=-Me3Je0V0#k7UQHwxe5SJ8DgQ!4Y+GGW3G4Jib()8}yD<3`DFh^>(8%vI`2H9R$a7k}RT83e6>6Dh^NVK%Xu#>E~H zAJQ}WMtG#I?8itk^-{*|sBjahGq;h6+nmee`{#Cy7DK&7(99@~^_3acQ5S1)S}hh} z+xIyt#)~Pc?Fu#(H7s~xhVrs-T_OuTSj}-8@A&{L#UwGJ+NtSoQE?rn1s3YTekl5o{#D=nn4P_A<$``Sh{i$+19-9Q&J~POH eT+U*z2k;4>cV8xgT$6|Z0000Px#1ZP1_K>z@;j|==^1poj532;bRa{vGi!vFvd!vV){sAK>D0nAB6K~z{r?UuVv z!$1&4`BGYFp(P!3AVHB&FfCM(pnw7d6`^!G-XMX*8)F)>=mf82;K-d@j%uN0ROR7cswb zr6d%}$VXmVk&WUA-09valecB$w-Hz?j({Pn1?jE5XAz&JIeDJEvtInD@GuovDULuP zD;D*hvP{*0L)3fBeM~D@DUL5!B;(Wi@n@Dr4<~Vw`@%~XN^yLhQ0=HwF%|H`-=sa2 z;&zT+OQd`lZDot%HaY0OXRGy4id&EFOT>H_W8DS#69;}eP>Kt6Ko8EpvJ7^>pE$Z5 zpcFSw%9kbSFw0;ET2sc-L960?z$BJZ+`{VhA5y-|y>i1*oTct@n--4 literal 0 HcmV?d00001 diff --git a/docs/geminidb/umn/en-us_image_0000001815204972.png b/docs/geminidb/umn/en-us_image_0000001815204972.png new file mode 100644 index 0000000000000000000000000000000000000000..515f02edfd506071f8fb7ddf073a4ff63bb01018 GIT binary patch literal 389 zcmV;00eb$4P)X1^@s6+90*i00001b5ch_0Itp) z=>Px#1ZP1_K>z@;j|==^1poj532;bRa{vGi!vFvd!vV){sAK>D0UAj}K~zXf?bI)G zgFq05@qTLr0&ylH;zUdZ;zSGrfvAl@U@8y@%n3vV22pVW^JaH)lcu?C%fECg`plf* znEZf+$rB#fAH-dUGS5-kcfTPwA9pRXU4$s&l^}f`{E4u6_!U+-))p`NasgAzPcR+7 zg&XHLdz}0QGV8Z)nud!o=g<|J_9Hx3;obj?PkGQI)K33!KM z1DFf(#t^{Y?mCzYaGNEB7}WlFDa_sBG!jK4IaJ`Ub{sm?`7)UMj1MPhg5pF$#XR@R zQpfo)cX#JKN*xmzV|OqpN{cr)`g8LOU+9K?;C+R3PvcMvmd?=%bGzbWn_(~gaMDU4 j{BQl%SRT+nE(Dwb&|hZuh`dvY00000NkvXXu0mjfMADt_ literal 0 HcmV?d00001 diff --git a/docs/geminidb/umn/en-us_image_0000001815204976.png b/docs/geminidb/umn/en-us_image_0000001815204976.png new file mode 100644 index 0000000000000000000000000000000000000000..247a08a4ad0285f5e1425f3ad89bc0b741ff0d25 GIT binary patch literal 214 zcmeAS@N?(olHy`uVBq!ia0vp^fNn{1`ISV`@iy0XB4ude`@%$AjK*4NJ7sn6_|GN{Sxeh4su7M@LiSB}ePy2F!)-rgy`njxg HN@xNAtJ+Ak literal 0 HcmV?d00001 diff --git a/docs/geminidb/umn/en-us_image_0000001815205036.png b/docs/geminidb/umn/en-us_image_0000001815205036.png new file mode 100644 index 0000000000000000000000000000000000000000..90d9996a01b76dac5dc524985eb8507365d40486 GIT binary patch literal 293 zcmeAS@N?(olHy`uVBq!ia0vp^B0wz2!3HGny7cS=QjEnx?oJHr&dIz4a#+$GeH|GX zHuiJ>Nn{1`ISV`@iy0XB4ude`@%$AjK*3#}E{-7<{%0?(7HU-xV0-ZSnv3?q1KI(- zY^(JX6eQNLF&|A(i1@eoaG(1g1BJHF=Plx<{dBwWx8af(+p#;|Ara5aP7D8?}al%X1vJuF#90Wye?4UrLKwG zhsb{nGNMxciys~EbW96ZUOIi*t>q`|W28c5o`)*bd5?>!&Pvi-%C mvHd5X1^)`Z2&osmA6P?<{C?Q@bA39{7Yv@RelF{r5}E+%5N|*L literal 0 HcmV?d00001 diff --git a/docs/geminidb/umn/en-us_image_0000001815205124.png b/docs/geminidb/umn/en-us_image_0000001815205124.png new file mode 100644 index 0000000000000000000000000000000000000000..1909444d23d92a3a6566bca91ce065d14dbda919 GIT binary patch literal 1004 zcmeAS@N?(olHy`uVBq!ia0vp^Vj#@H3?x5i&EaHVU}gyL32_B-i2;l_022maMg=TL zfE5PVkN`UjaKHd37;wP=HyH51052HufdM}l2!Meg7zlxZFc^q{fvBjc7#N6yfrNyF zBp676fwZ)=3>e7D%F2O(yu7@Ef`TF#C@Co^gMo^QimIxrnwpwA7-(o{XliO|X=!PL zfsT%juCA`0o}RwGz5y5*8X6iI85tWJo0yoGnwpxKnVFlLTUc0FT3T9JSy@|K+kkCcvmzTGP*6~CaBxUSNN8wiSXfv@L_}m{WK>jCbaZq~OiWx{Tzq_dLPA1fVq$V~a!N`{ zYHDg)T3SX%MrLMaR#sMac6M%VZeCtqetv#oVPR2GQAtTjX=!O$Sy@FzMP+4WRaI3@ zO-*fWZGC-xLqkJTQ&V$ub4yE0TU%RudwXYRXIEEOPft&8Z*PBp|AYw>CQX_&dGh3` zQ>RX!K7GcF8M9{1nmv2=+_`h-&!4|w!GcAL7A;=9cQ>uk5sDH4e!pN zM?2c%!f)$Moqn;JbAR{#-LH2<-aWd<6M=_Uy)Vz z>Gb1s+(~DB#NsS6_)g4`cRj>@b~4MGr%TsH2#HlrdJFVdQ&MBb@08(^UA^-pY literal 0 HcmV?d00001 diff --git a/docs/geminidb/umn/en-us_image_0000001815205188.png b/docs/geminidb/umn/en-us_image_0000001815205188.png new file mode 100644 index 0000000000000000000000000000000000000000..515f02edfd506071f8fb7ddf073a4ff63bb01018 GIT binary patch literal 389 zcmV;00eb$4P)X1^@s6+90*i00001b5ch_0Itp) z=>Px#1ZP1_K>z@;j|==^1poj532;bRa{vGi!vFvd!vV){sAK>D0UAj}K~zXf?bI)G zgFq05@qTLr0&ylH;zUdZ;zSGrfvAl@U@8y@%n3vV22pVW^JaH)lcu?C%fECg`plf* znEZf+$rB#fAH-dUGS5-kcfTPwA9pRXU4$s&l^}f`{E4u6_!U+-))p`NasgAzPcR+7 zg&XHLdz}0QGV8Z)nud!o=g<|J_9Hx3;obj?PkGQI)K33!KM z1DFf(#t^{Y?mCzYaGNEB7}WlFDa_sBG!jK4IaJ`Ub{sm?`7)UMj1MPhg5pF$#XR@R zQpfo)cX#JKN*xmzV|OqpN{cr)`g8LOU+9K?;C+R3PvcMvmd?=%bGzbWn_(~gaMDU4 j{BQl%SRT+nE(Dwb&|hZuh`dvY00000NkvXXu0mjfMADt_ literal 0 HcmV?d00001 diff --git a/docs/geminidb/umn/en-us_image_0000001861844977.png b/docs/geminidb/umn/en-us_image_0000001861844977.png new file mode 100644 index 0000000000000000000000000000000000000000..1909444d23d92a3a6566bca91ce065d14dbda919 GIT binary patch literal 1004 zcmeAS@N?(olHy`uVBq!ia0vp^Vj#@H3?x5i&EaHVU}gyL32_B-i2;l_022maMg=TL zfE5PVkN`UjaKHd37;wP=HyH51052HufdM}l2!Meg7zlxZFc^q{fvBjc7#N6yfrNyF zBp676fwZ)=3>e7D%F2O(yu7@Ef`TF#C@Co^gMo^QimIxrnwpwA7-(o{XliO|X=!PL zfsT%juCA`0o}RwGz5y5*8X6iI85tWJo0yoGnwpxKnVFlLTUc0FT3T9JSy@|K+kkCcvmzTGP*6~CaBxUSNN8wiSXfv@L_}m{WK>jCbaZq~OiWx{Tzq_dLPA1fVq$V~a!N`{ zYHDg)T3SX%MrLMaR#sMac6M%VZeCtqetv#oVPR2GQAtTjX=!O$Sy@FzMP+4WRaI3@ zO-*fWZGC-xLqkJTQ&V$ub4yE0TU%RudwXYRXIEEOPft&8Z*PBp|AYw>CQX_&dGh3` zQ>RX!K7GcF8M9{1nmv2=+_`h-&!4|w!GcAL7A;=9cQ>uk5sDH4e!pN zM?2c%!f)$Moqn;JbAR{#-LH2<-aWd<6M=_Uy)Vz z>Gb1s+(~DB#NsS6_)g4`cRj>@b~4MGr%TsH2#HlrdJFVdQ&MBb@08(^UA^-pY literal 0 HcmV?d00001 diff --git a/docs/geminidb/umn/en-us_image_0000001861924673.png b/docs/geminidb/umn/en-us_image_0000001861924673.png new file mode 100644 index 0000000000000000000000000000000000000000..1909444d23d92a3a6566bca91ce065d14dbda919 GIT binary patch literal 1004 zcmeAS@N?(olHy`uVBq!ia0vp^Vj#@H3?x5i&EaHVU}gyL32_B-i2;l_022maMg=TL zfE5PVkN`UjaKHd37;wP=HyH51052HufdM}l2!Meg7zlxZFc^q{fvBjc7#N6yfrNyF zBp676fwZ)=3>e7D%F2O(yu7@Ef`TF#C@Co^gMo^QimIxrnwpwA7-(o{XliO|X=!PL zfsT%juCA`0o}RwGz5y5*8X6iI85tWJo0yoGnwpxKnVFlLTUc0FT3T9JSy@|K+kkCcvmzTGP*6~CaBxUSNN8wiSXfv@L_}m{WK>jCbaZq~OiWx{Tzq_dLPA1fVq$V~a!N`{ zYHDg)T3SX%MrLMaR#sMac6M%VZeCtqetv#oVPR2GQAtTjX=!O$Sy@FzMP+4WRaI3@ zO-*fWZGC-xLqkJTQ&V$ub4yE0TU%RudwXYRXIEEOPft&8Z*PBp|AYw>CQX_&dGh3` zQ>RX!K7GcF8M9{1nmv2=+_`h-&!4|w!GcAL7A;=9cQ>uk5sDH4e!pN zM?2c%!f)$Moqn;JbAR{#-LH2<-aWd<6M=_Uy)Vz z>Gb1s+(~DB#NsS6_)g4`cRj>@b~4MGr%TsH2#HlrdJFVdQ&MBb@08(^UA^-pY literal 0 HcmV?d00001 diff --git a/docs/geminidb/umn/en-us_image_0000001861924833.png b/docs/geminidb/umn/en-us_image_0000001861924833.png new file mode 100644 index 0000000000000000000000000000000000000000..1267615e3e449ae0f815dd16f3aabb9bbb6d5d74 GIT binary patch literal 295 zcmeAS@N?(olHy`uVBq!ia0vp^B0$W?!3HGtkJx+wQjEnx?oJHr&dIz4a#+$GeH|GX zHuiJ>Nn{1`ISV`@i-8&rgD~Uq{1quc!9AWXjv*HQOD`I79Wsz;OVoenIcJVdgZf9l zpq6*62QPYBaa;-%XjXW&D0Y#c-S4d%g)VQoxF;av(){+8ZvwNbUQJ(R@Ii6Hnq;4{ z@V$aetDGBMUo5Xlo6%Lh^RIkHf*@OD+w4_#GanSTx;&|RxPmoV{==RlJ7l`LA6sAG z>$$o>guCZUg7T|I!^fxmt_UYz^WS)JZD(#!jEux)2et3TJlR*|lY13@yVV*zW4S5) n^=O3li6@>F$!moF=ssZWS}C#bj1zMU&>sw*u6{1-oD!MX1^@s6+90*i00001b5ch_0Itp) z=>Px#1ZP1_K>z@;j|==^1poj532;bRa{vGi!vFvd!vV){sAK>D0UAj}K~zXf?bI)G zgFq05@qTLr0&ylH;zUdZ;zSGrfvAl@U@8y@%n3vV22pVW^JaH)lcu?C%fECg`plf* znEZf+$rB#fAH-dUGS5-kcfTPwA9pRXU4$s&l^}f`{E4u6_!U+-))p`NasgAzPcR+7 zg&XHLdz}0QGV8Z)nud!o=g<|J_9Hx3;obj?PkGQI)K33!KM z1DFf(#t^{Y?mCzYaGNEB7}WlFDa_sBG!jK4IaJ`Ub{sm?`7)UMj1MPhg5pF$#XR@R zQpfo)cX#JKN*xmzV|OqpN{cr)`g8LOU+9K?;C+R3PvcMvmd?=%bGzbWn_(~gaMDU4 j{BQl%SRT+nE(Dwb&|hZuh`dvY00000NkvXXu0mjfMADt_ literal 0 HcmV?d00001 diff --git a/docs/geminidb/umn/nosql_01_0001.html b/docs/geminidb/umn/nosql_01_0001.html new file mode 100644 index 00000000..0bb7462f --- /dev/null +++ b/docs/geminidb/umn/nosql_01_0001.html @@ -0,0 +1,11 @@ + + +

System Architecture

+

GeminiDB is a distributed database with decoupled compute and storage architecture. The compute clusters consist of multiple homogeneous nodes, and data is stored in a distributed, shared storage pool. Compute and storage resources are decoupled from each other so they can be flexibly scaled in or out without having to migrate any data.

+
+
+
+
Parent topic: Introduction
+
+
+ diff --git a/docs/geminidb/umn/nosql_01_0002.html b/docs/geminidb/umn/nosql_01_0002.html new file mode 100644 index 00000000..bfc8959f --- /dev/null +++ b/docs/geminidb/umn/nosql_01_0002.html @@ -0,0 +1,31 @@ + + +

Highlights

+

High Reliability

Data backup

+

Data can be backed up automatically or manually. In an automated backup, all of the data in a given DB instance is backed up by the system. In a manual backup, the user backs up the data. These backups can be used to restore a DB instance in just a few clicks.

+

Backups are stored in Object Storage Service (OBS) buckets, which provides disaster recovery capabilities and save space. When you create a DB instance, the automated backup policy is enabled by default. After the creation is complete, an automated full backup is triggered instantly. The backup retention period is 7 days by default. You can set the backup retention period and modify the backup policy. In addition, you can initiate backup at any time according to your service requirements. Manual backups are saved until you manually delete them.

+
+

High Security

Network isolation

+

GeminiDB uses Virtual Private Clouds (VPCs) and network security groups to keep DB instances isolated. VPCs allow you to define which IP addresses are allowed to access a given database. Running a DB instance in a VPC improves security. To further enhance database security, you can configure subnets and security groups to control access to DB instances.

+

Access control

+

VPC security groups can be configured with rules to control traffic to and from DB instances.

+

Encryption

+

GeminiDB uses Secure Sockets Layer (SSL) to encrypt transmitted data. You can download the root CA certificate from the management console and upload it for authentication when connecting to a database.

+

Security

+

GeminiDB supports multi-layer network protection. The security system consists of VPCs, subnets, security groups, Anti-DDoS, and SSL, which collectively can defend against a wide range of attacks and keep your data secure.

+
  • VPCs isolate resources and control access.
  • SSL connections ensure data security and integrity.
  • Security group rules control traffic to and from specific IP addresses and ports, protecting connections between GeminiDB and other services.
+

Performance monitoring

+

GeminiDB monitors instance performance, reducing 60% of O&M activities. It provides real-time monitoring information about CPU utilization, disk usage, IOPS, and number of active connections, allowing you to check instance status at any time.

+
+

Convenience

Ready to use out of the box

+

You can create a DB instance on the management console and access the database over a private network to reduce latency and avoid the cost of using a public network.

+
+

Scalability

As a distributed database service with decoupled compute and storage architecture, GeminiDB supports minute-level compute node expansion and second-level storage expansion.

+
+
+
+
+
Parent topic: Introduction
+
+
+ diff --git a/docs/geminidb/umn/nosql_01_0003.html b/docs/geminidb/umn/nosql_01_0003.html new file mode 100644 index 00000000..e24fd80d --- /dev/null +++ b/docs/geminidb/umn/nosql_01_0003.html @@ -0,0 +1,13 @@ + + +

Regions and AZs

+

Concepts

A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.

+
  • A region is a physical data center. Each region is completely independent, improving fault tolerance and stability. After a resource is created, its region cannot be changed.
  • An AZ is a physical location using independent power supplies and networks. Faults in an AZ do not affect other AZs. A region can contain multiple AZs, which are physically isolated but interconnected through internal networks. This ensures the independence of AZs and provides low-cost and low-latency network connections.
+
+
+
+
+
Parent topic: Introduction
+
+
+ diff --git a/docs/geminidb/umn/nosql_01_0004.html b/docs/geminidb/umn/nosql_01_0004.html new file mode 100644 index 00000000..f930e8a0 --- /dev/null +++ b/docs/geminidb/umn/nosql_01_0004.html @@ -0,0 +1,21 @@ + + +

DB Instance

+
+ + diff --git a/docs/geminidb/umn/nosql_01_0006.html b/docs/geminidb/umn/nosql_01_0006.html new file mode 100644 index 00000000..4ae232d8 --- /dev/null +++ b/docs/geminidb/umn/nosql_01_0006.html @@ -0,0 +1,90 @@ + + +

DB Instance Specifications

+

The DB instance specifications depend on the selected DB engine.

+
+

GeminiDB Cassandra Instance Specifications

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 GeminiDB Cassandra cluster instance specifications

Flavor

+

vCPUs

+

Memory (GB)

+

Max. Storage Space (GB)

+

geminidb.cassandra.xlarge.8

+

4

+

32

+

24,000

+

geminidb.cassandra.2xlarge.8

+

8

+

64

+

48,000

+

geminidb.cassandra.4xlarge.8

+

16

+

128

+

96,000

+

geminidb.cassandra.6xlarge.8

+

24

+

192

+

144,000

+

geminidb.cassandra.8xlarge.8

+

32

+

256

+

192,000

+

geminidb.cassandra.12xlarge.8

+

48

+

384

+

288,000

+

geminidb.cassandra.15xlarge.8

+

60

+

480

+

384,000

+
+
+
+
+
+
+
Parent topic: DB Instance
+
+
+ diff --git a/docs/geminidb/umn/nosql_01_0007.html b/docs/geminidb/umn/nosql_01_0007.html new file mode 100644 index 00000000..51911e5b --- /dev/null +++ b/docs/geminidb/umn/nosql_01_0007.html @@ -0,0 +1,30 @@ + + +

Compatible APIs and Versions

+

This section lists the GeminiDB-compatible APIs and versions.

+ +
+ + + + + + + + + +
Table 1 Compatible APIs and versions

Compatible API

+

DB Instance Type

+

Version

+

Cassandra

+

Cluster

+

3.11

+
+
+
+
+
+
Parent topic: DB Instance
+
+
+ diff --git a/docs/geminidb/umn/nosql_01_0008.html b/docs/geminidb/umn/nosql_01_0008.html new file mode 100644 index 00000000..c135debd --- /dev/null +++ b/docs/geminidb/umn/nosql_01_0008.html @@ -0,0 +1,92 @@ + + +

DB Instance Status

+

DB Instance Status

You can determine whether a DB instance is healthy based on its status displayed on the management console.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 DB instance statuses

Status

+

Description

+

Available

+

DB instance is available.

+

Abnormal

+

DB instance is faulty.

+

Creating

+

DB instance is being created.

+

Creation failed

+

DB instance creation fails.

+

Restarting

+

DB instance is being restarted.

+

Resetting password

+

Administrator password is being reset.

+

Adding node

+

Nodes are being added to a DB instance.

+

Deleting node

+

Nodes are being deleted from a DB instance.

+

Scaling up

+

The storage space of the DB instance is being expanded.

+

Changing instance class

+

The CPU or memory of a DB instance is being changed.

+

Uploading backup

+

The backup file is being uploaded.

+

Backing up

+

Backup is being created.

+

Checking restoration

+

The backup of the current DB instance is being restored to a new DB instance.

+

Switching SSL

+

SSL is being enabled or disabled.

+
+
+
+
+
+
+
Parent topic: DB Instance
+
+
+ diff --git a/docs/geminidb/umn/nosql_01_0009.html b/docs/geminidb/umn/nosql_01_0009.html new file mode 100644 index 00000000..279fd116 --- /dev/null +++ b/docs/geminidb/umn/nosql_01_0009.html @@ -0,0 +1,51 @@ + + +

Related Services

+

Table 1 shows the relationship between GeminiDB and other services.

+ +
+ + + + + + + + + + + + + + + + + + + + + + +
Table 1 Relationship between GeminiDB and other services

Service

+

Description

+

ECS

+

Elastic Cloud Server (ECS) provides GeminiDB with elastic computing resources and a running environment for DB instances.

+

VPC

+

GeminiDB uses Virtual Private Clouds (VPCs) and network security groups to keep DB instances isolated. VPCs allow you to define which IP addresses are allowed to access a given database. Running a DB instance in a VPC improves security.

+

EIP

+

The Elastic IP (EIP) service provides independent public IP addresses and bandwidth for Internet access.

+

OBS

+

Backups are stored in Object Storage Service (OBS) to allow for disaster recovery and save space.

+

TMS

+

Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags globally and other cloud services manage their own tags.

+

Cloud Eye

+

Cloud Eye serves as an open monitoring platform, monitoring GeminiDB resources for you. It reports alarms and issues warnings promptly to ensure that services are running properly.

+
+
+
+
+
+
Parent topic: Introduction
+
+
+ diff --git a/docs/geminidb/umn/nosql_01_0010.html b/docs/geminidb/umn/nosql_01_0010.html new file mode 100644 index 00000000..58c20d35 --- /dev/null +++ b/docs/geminidb/umn/nosql_01_0010.html @@ -0,0 +1,22 @@ + + +

Typical Application Scenarios

+

IoT

GeminiDB is compatible with Cassandra APIs. It is designed for write-intensive scenarios, specifically applied in manufacturing, logistics, health care, real estate, energy production, and agriculture. It can process data sent by different types of sensors for further analysis.

+

Advantages:

+
  • High Write Performance: GeminiDB provides higher write performance than other NoSQL services.
  • High Scalability: Compute nodes can be scaled in or out to flexibly cope with traffic surges or large writes loads at any time.
+
+

Internet

E-commerce and entertainment websites that include product catalogs, recommendations, and personalization engines use GeminiDB when they require fast reading and writing of data and high scalability. GeminiDB stores visitor activities, making it easy for analysis tools to access data fast and to generate recommendations.

+

Advantages:

+
  • High Write Performance: GeminiDB provides higher write performance than other NoSQL services.
  • Big Data Analysis: GeminiDB can work with Spark to provide recommendations to your customers in real-time.
+
+

Finance

With Spark′s big data analysis capabilities, GeminiDB helps companies in the finance sector build risk control systems and mitigate fraud.

+

Advantages:

+

Big Data Analysis: Spark and other big data processing technologies enable real-time fraud detection and prevention.

+
+
+
+
+
Parent topic: Introduction
+
+
+ diff --git a/docs/geminidb/umn/nosql_01_0110.html b/docs/geminidb/umn/nosql_01_0110.html new file mode 100644 index 00000000..b90bcf38 --- /dev/null +++ b/docs/geminidb/umn/nosql_01_0110.html @@ -0,0 +1,13 @@ + + +

Overview

+

A DB instance is the minimum management unit and an independently running database. A DB instance can contain multiple user-created databases, and you can access it using the same tools and applications that you use with a stand-alone DB instance.

+

The cloud database supports multiple instance types to meet different compute and storage requirements. Each instance type provides various flavors with different vCPU and memory configurations for you to select.

+ +
+
+
+
Parent topic: DB Instance
+
+
+ diff --git a/docs/geminidb/umn/nosql_01_101.html b/docs/geminidb/umn/nosql_01_101.html new file mode 100644 index 00000000..095dfbc9 --- /dev/null +++ b/docs/geminidb/umn/nosql_01_101.html @@ -0,0 +1,13 @@ + + +

User Permissions

+

GeminiDB provides two types of user permissions by default: user management and resource management.

+
  • User management refers to the management of users, user groups, and user group permissions.
  • Resource management refers to the control operations that can be performed by users on cloud service resources.
+

For details about GeminiDB user permissions, see Permissions.

+
+
+
+
Parent topic: Introduction
+
+
+ diff --git a/docs/geminidb/umn/nosql_02_0001.html b/docs/geminidb/umn/nosql_02_0001.html new file mode 100644 index 00000000..0cffb645 --- /dev/null +++ b/docs/geminidb/umn/nosql_02_0001.html @@ -0,0 +1,15 @@ + + +

Getting Started with GeminiDB Cassandra

+
+ + diff --git a/docs/geminidb/umn/nosql_02_0002.html b/docs/geminidb/umn/nosql_02_0002.html new file mode 100644 index 00000000..f4d0a982 --- /dev/null +++ b/docs/geminidb/umn/nosql_02_0002.html @@ -0,0 +1,174 @@ + + +

Creating a GeminiDB Cassandra Instance

+

This section describes how to create a DB instance that is compatible with Cassandra APIs.

+

Procedure

  1. Log in to the GaussDB NoSQL console.
  2. On the Instance Management page, click Create DB Instance.
  3. On the displayed page, select your DB instance specifications, and click Create Now.

    +

    + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Basic information

    Parameter

    +

    Description

    +

    Region

    +

    The region where the tenant is located.

    +
    NOTICE:

    Select the region nearest where you will be accessing the DB from so latency can be kept to a minimum and response time will be faster. Also, products deployed in different regions cannot communicate with each other through a private network and you cannot change the region of an instance after creating the instance.

    +
    +

    DB Instance Name

    +

    The new name can be the same as an existing instance name. It must start with a letter and consist of 4 to 64 characters. Only letters (case-sensitive), digits, hyphens (-), and underscores (_) are allowed.

    +

    +

    +

    After the DB instance is created, you can change the DB instance name. For details, see section Changing a DB Instance Name.

    +

    Compatible API

    +

    Cassandra

    +

    DB Instance Type

    +

    Cluster

    +

    DB Engine Version

    +

    3.11

    +

    AZ

    +

    An AZ is a part of a region with its own independent power supplies and networks. AZs are physically isolated but can communicate through an internal network connection.

    +
    +
    + +
    + + + + + + + + + + + + + +
    Table 2 Specifications and storage

    Parameter

    +

    Description

    +

    Instance Specifications

    +

    The CPU and memory of a DB instance.

    +

    Different performance specifications support different numbers of connections and maximum IOPSs. Select CPU and memory specifications based on your service requirements.

    +

    After a DB instance is created, you can change its CPU and memory. For details, see Changing a DB Instance Class.

    +

    Nodes

    +

    The number of nodes ranges from 3 to 200. Select the number of nodes based on the site requirements.

    +

    After a DB instance is created, you can add nodes. For details, see Adding Nodes.

    +

    Storage Space

    +

    Storage space depends on the instance specifications. The minimum storage space is 100 GB, and the storage space you set must be an integer. You can select a minimum of 1 GB each time you scale up storage space.

    +

    After a DB instance is created, you can scale up its storage space. For details, see Scaling Up Storage Space.

    +
    +
    + +
    + + + + + + + + + + + + + +
    Table 3 Network

    Parameter

    +

    Description

    +

    VPC

    +

    The virtual network where your DB instances are located. A VPC isolates networks for different services. You can select an existing VPC or create a VPC.

    +

    If there are no VPCs available, the system allocates resources to you by default.

    +

    For details on how to create a subnet, see the "Creating a VPC" section in the Virtual Private Cloud User Guide.

    +
    NOTE:

    After the GeminiDB Cassandra instance is created, the VPC where the instance resides cannot be changed.

    + +
    +

    Subnet

    +

    A subnet provides dedicated network resources that are logically isolated from other networks for network security.

    +

    Security Group

    +

    A security group controls access between GeminiDB instances and other services. When you select a security group, you must ensure that it allows the client to access DB instances.

    +

    If there are no security groups available, the system allocates resources to you by default.

    +
    +
    + +
    + + + + + + + + + + + + + + + + +
    Table 4 Database configuration

    Parameter

    +

    Description

    +

    Administrator

    +

    The default administrator account is rwuser.

    +

    Administrator Password

    +

    Set a password for the administrator. The password:

    +
    • Must be 8 to 32 characters long.
    • Must contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!@#%^*-_=+?
    • For security reasons, you must select a strong password. The system will verify the password strength.
    +

    Keep this password secure. If you lose it, the system cannot retrieve it.

    +

    Confirm Password

    +

    Enter the administrator password again.

    +

    Parameter Template

    +

    A parameter template contains engine configuration values that can be applied to one or more instances.

    +

    After a DB instance is created, you can modify parameters to better meet your service requirements. For details, see Modifying a Parameter Template.

    +
    +
    + +
    + + + + + + + +
    Table 5 Tags

    Parameter

    +

    Description

    +

    Tags

    +

    The setting is optional. Adding tags helps you better identify and manage your DB instances. Each DB instance can have up to 20 tags.

    +

    A tag is composed of a key-value pair.

    +
    • Key: Mandatory if the DB instance is going to be tagged

      Each tag key must be unique for each DB instance. The key can include up to 36 characters, including digits, letters, underscores (_), and hyphens (-).

      +
    • Value: Optional if the DB instance is going to be tagged

      The value can contain up to 43 characters, including digits, letters, underscores (_), periods (.), and hyphens (-).

      +
    +

    After a DB instance is created, you can view its tag details on the Tags tab. In addition, you can add, modify, and delete tags for existing DB instances. For details, see Managing Tags.

    +
    +
    +

  4. On the displayed page, confirm the DB instance details.

    • If you need to modify the specifications, click Previous to return to the previous page.
    • If you do not need to modify the specifications, click Submit to start creating the instance.
    +

  5. On the Instance Management page, view and manage your DB instances.

    • Creating a DB instance takes about 5 to 9 minutes. During the process, the instance status displayed in the DB instance list is Creating.
    • After the creation is complete, the status changes to Available.

      You can click in the upper right corner of the page to refresh the DB instance statuses.

      +
    • During creation, an automated backup policy is enabled by default. A full backup is automatically triggered after a DB instance is created.
    +

+
+
+ + diff --git a/docs/geminidb/umn/nosql_02_0004.html b/docs/geminidb/umn/nosql_02_0004.html new file mode 100644 index 00000000..b8087185 --- /dev/null +++ b/docs/geminidb/umn/nosql_02_0004.html @@ -0,0 +1,19 @@ + + +

Configuring Security Group Rules

+

Scenarios

The default security group rule allows all outgoing data packets. ECSs and GeminiDB 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 GeminiDB instances that in it.

+

The following describes how to set security groups.

+
+

Precautions

  • If the ECS and DB instance are in the same security group, they can communicate with each other by default. No security group rule needs to be configured.
  • If the ECS and DB instance are in different security groups, you need to configure security group rules for the ECS and DB instance separately.
    • To allow access to the GeminiDB Cassandra instance, you need to configure an inbound rule for the security group that the instance nodes belong to.
    • By default, the security group allows all outbound data packets, so you do not need to configure a security rule for the ECS. If not all access from the ECS is allowed, you need to configure an outbound rule for the ECS.
    +
+
  • By default, you can create up to 500 security group rules. However, too many rules increase network latency for initial access, so it is recommended that you add no more than 50 rules for each security group.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Network, click Virtual Private Cloud.
  4. In the navigation pane on the left, choose Access Control > Security Groups.
  5. On the Security Groups page, click the security group name.
  6. On the Inbound Rules tab, click Add Rule. In the displayed Add Inbound Rule dialog box, set required parameters to add inbound rules. On the Outbound Rules tab, click Add Rule. In the displayed Add Outbound Rule dialog box, set required parameters to add outbound rules.
  7. In the displayed dialog box, set required parameters.
  8. Click OK.
+
+
+ + diff --git a/docs/geminidb/umn/nosql_02_0005.html b/docs/geminidb/umn/nosql_02_0005.html new file mode 100644 index 00000000..68d57109 --- /dev/null +++ b/docs/geminidb/umn/nosql_02_0005.html @@ -0,0 +1,50 @@ + + +

Connecting to a GeminiDB Cassandra Instance Over Private Networks

+

Scenarios

This section uses the Linux operating system as an example to describe how to connect an ECS to a GeminiDB Cassandra instance over private networks.

+
+

Constraints

  • The DB instances must be in the same VPC subnet as the ECS.
  • The ECS must be allowed in a security group that has access to the DB instances.
    • If the security group that the target DB instance belongs to is the default security group, you do not need to configure security group rules.
    • If the security group that the target DB instance belongs to is not the default security group, check whether the security group rules allow the ECS to connect to the DB instance. For details, see section Configuring Security Group Rules.

      If the security group rules allow the access from the ECS, the ECS can connect to the DB instance.

      +

      If the security group rule does not allow the access from the ECS, you need to add an inbound rule to the security group.

      +
    +
  • The default port of the GeminiDB Cassandra instance is 8635.
+
+

Prerequisites

  • Create an ECS running Linux. For details, see "Creating ECSs" in ECS User Guide.
  • Obtain the Cassandra client installation package from the Cassandra official website.
  • Before using this tool, install the Python dependency package cassandra-driver 3.11.0 or later.
+
+

Using the Cassandra Client Tool to Connect to a DB Instance

  1. Log in to the ECS. For details, see the section "Logging In to an ECS" in the Elastic Cloud Server User Guide.
  2. Upload the Cassandra client installation package to ECS.
  3. Obtain the client tool cqlsh.
  4. Connect to the DB instance in the directory where the cqlsh tool is located.

    ./cqlsh <DB_HOST> <DB_PORT> -u <DB_USER>

    +

    Example:

    +

    ./cqlsh 192.168.1.8 8635 -u rwuser

    +
    • <DB_HOST> indicates the private IP address of the node to be connected. Obtain the value from the Private IP Address column in the node list on the Basic Information page.
    • <DB_PORT> indicates the port number. The default value is 8635 and cannot be changed.
    • <DB_USER> indicates the database account name. The default value is rwuser.
    +
    +

  5. Check the connection result. If the following information is displayed, the connection is successful.

    rwuser@cqlsh>
    +

+
+

Follow-up Operations

After logging in to the GeminiDB Cassandra instance, you can perform the following operations:

+
  • Run the HELP command to view all supported commands.
+
  • HELP <COMMAND>: This command queries the usage of a command. Example: HELP DESC
  • Keyspace syntax
    • Create a keyspace. Example:

      CREATE KEYSPACE IF NOT EXISTS nosql WITH replication = {'class': 'SimpleStrategy', 'replication_factor': '3'};

      +

      Set the keyspace name to nosql, replication to SimpleStrategy, and number of replicas to 3.

      +
    • DESC <keyspace_name>: This command verifies the creation result.
    • use <keyspace_name>: This command switches to the keyspace you created.
    • DROP KEYSPACE <keyspace_name>: This command deletes the keyspace you created.
    +
  • Table syntax
    • Create a table. Example:

      CREATE TABLE nosql_table(user_id int, age int, user_name text, PRIMARY KEY(user_id));

      +

      The table name is nosql_table, and the following three columns are defined: user_id, age, and user_name. user_id is of the int type and indicates the user ID. age is of the int type and indicates the age of a user. user_name is of the text type and indicates the user name. The primary key is user_id.

      +
    • DESC <table_name>: This command verifies the creation result.
    • Insert data into the table. Example:

      INSERT INTO nosql_table (user_id, age, user_name) VALUES (1, 10, 'user1');

      +

      INSERT INTO nosql_table (user_id, age, user_name) VALUES (2, 20, 'user2');

      +

      INSERT INTO nosql_table (user_id, age, user_name) VALUES (3, 30, 'user3');

      +
    • SELECT * FROM <table_name>: This command queries table data.
    • Add a column to the table. Example

      ALTER TABLE nosql_table ADD gender text;

      +
    • Insert data to the added column. Example:

      UPDATE nosql.nosql_table SET prename = 'user_prename1' WHERE user_id = 1;

      +

      UPDATE nosql.nosql_table SET prename = 'user_prename2' WHERE user_id = 2;

      +

      UPDATE nosql.nosql_table SET prename = 'user_prename3' WHERE user_id = 3;

      +
    • Delete data in a keyspace. Example:

      Delete the age data of the user whose ID is 1.

      +

      DELETE age FROM nosql.nosql_table WHERE user_id=1;

      +

      Delete the entire record of the user whose ID is 2.

      +

      DELETE FROM nosql.nosql_table WHERE user_id=2;

      +
    • Clear all records in the table. Example:

      TRUNCATE nosql.nosql_table;

      +
    • Delete the entire table. Example:

      DROP TABLE nosql.nosql_table;

      +
    +
+
+
+ + diff --git a/docs/geminidb/umn/nosql_02_0006.html b/docs/geminidb/umn/nosql_02_0006.html new file mode 100644 index 00000000..72259833 --- /dev/null +++ b/docs/geminidb/umn/nosql_02_0006.html @@ -0,0 +1,19 @@ + + +

Connecting to a GeminiDB Cassandra Instance Over Private Networks

+
+ + diff --git a/docs/geminidb/umn/nosql_02_0007.html b/docs/geminidb/umn/nosql_02_0007.html new file mode 100644 index 00000000..d2b3c6c6 --- /dev/null +++ b/docs/geminidb/umn/nosql_02_0007.html @@ -0,0 +1,21 @@ + + +

Connecting to a GeminiDB Cassandra Instance Over Public Networks

+
+ + diff --git a/docs/geminidb/umn/nosql_02_0008.html b/docs/geminidb/umn/nosql_02_0008.html new file mode 100644 index 00000000..c893f239 --- /dev/null +++ b/docs/geminidb/umn/nosql_02_0008.html @@ -0,0 +1,20 @@ + + +

Binding an EIP

+

Scenarios

The Elastic IP service provides independent public IP addresses and bandwidth for Internet access. After you create a GeminiDB Cassandra instance, you can bind an EIP to it to allow external access. If later you want to prohibit external access, you can also unbind the EIP from the DB instance.

+
+

Precautions

  • Before accessing a database, you need to apply for an EIP on the VPC console. Then, add an inbound rule to allow the IP addresses or IP address ranges of ECSs. For details, see section Configuring Security Group Rules.
  • To change the EIP that has been bound to a node, you need to unbind it from the node first.
+
+

Binding an EIP

  1. On the Instance Management page, click the target GeminiDB Cassandra instance.
  2. On the Basic Information page, in the Node Information area, locate the target node and click Bind EIP in the Operation column.
  3. In the displayed dialog box, all available unbound EIPs are listed. Select the required EIP and click OK. If no available EIPs are displayed, click View EIP and create an EIP on the VPC console.
  4. In the EIP column, view the EIP that is successfully bound.

    To unbind the EIP from the DB instance, see Unbinding an EIP.

    +

+
+

Unbinding an EIP

  1. On the Instance Management page, click the target GeminiDB Cassandra instance.
  2. On the Basic Information page, in the Node Information area, locate the target node and click Unbind EIP in the Operation column.
  3. In the displayed dialog box, click Yes.

    To bind an EIP to the DB instance again, see Binding an EIP.

    +

+
+
+ + diff --git a/docs/geminidb/umn/nosql_02_0009.html b/docs/geminidb/umn/nosql_02_0009.html new file mode 100644 index 00000000..eec1eed6 --- /dev/null +++ b/docs/geminidb/umn/nosql_02_0009.html @@ -0,0 +1,46 @@ + + +

Connecting to a GeminiDB Cassandra Instance Over Public Networks

+

Scenarios

You can use an ECS or local device to connect to a GeminiDB instance over a public network.

+

This section describes how to use a Linux ECS to connect to a GeminiDB Cassandra instance over a public network.

+
+

Prerequisites

  • Bind an EIP to the GeminiDB Cassandra instance node and set security group rules.
  • Create an ECS running Linux. For details, see "Creating ECSs" in ECS User Guide.
  • Obtain the Cassandra client installation package from the Cassandra official website.
  • Before using this tool, install the Python dependency package cassandra-driver 3.11.0 or later.
+
+

Connecting to a DB Instance Through a Cassandra Client

  1. Log in to the ECS. For details, see the section "Logging In to an ECS" in the Elastic Cloud Server User Guide.
  2. Upload the Cassandra client installation package to ECS.
  3. Obtain the client tool cqlsh.
  4. Connect to the DB instance in the directory where the cqlsh tool is located.

    ./cqlsh <DB_HOST> <DB_PORT> -u <DB_USER>

    +

    Example:

    +

    ./cqlsh 192.168.1.8 8635 -u rwuser

    +
    • <DB_HOST> indicates the EIP of the node to be connected. Obtain the value from the EIP column in the node list on the Basic Information page.
    • <DB_PORT> indicates the port number. The default value is 8635 and cannot be changed.
    • <DB_USER> indicates the database account name. The default value is rwuser.
    +
    +

  5. Check the connection result. If the following information is displayed, the connection is successful.

    rwuser@cqlsh>
    +

+
+

Follow-up Operations

After logging in to the GeminiDB Cassandra instance, you can perform the following operations:

+
  • Run the HELP command to view all supported commands.
+
  • HELP <COMMAND>: This command queries the usage of a command. Example: HELP DESC
  • Keyspace syntax
    • Create a keyspace. Example:

      CREATE KEYSPACE IF NOT EXISTS nosql WITH replication = {'class': 'SimpleStrategy', 'replication_factor': '3'};

      +

      Set the keyspace name to nosql, replication to SimpleStrategy, and number of replicas to 3.

      +
    • DESC <keyspace_name>: This command verifies the creation result.
    • use <keyspace_name>: This command switches to the keyspace you created.
    • DROP KEYSPACE <keyspace_name>: This command deletes the keyspace you created.
    +
  • Table syntax
    • Create a table. Example:

      CREATE TABLE nosql_table(user_id int, age int, user_name text, PRIMARY KEY(user_id));

      +

      The table name is nosql_table, and the following three columns are defined: user_id, age, and user_name. user_id is of the int type and indicates the user ID. age is of the int type and indicates the age of a user. user_name is of the text type and indicates the user name. The primary key is user_id.

      +
    • DESC <table_name>: This command verifies the creation result.
    • Insert data into the table. Example:

      INSERT INTO nosql_table (user_id, age, user_name) VALUES (1, 10, 'user1');

      +

      INSERT INTO nosql_table (user_id, age, user_name) VALUES (2, 20, 'user2');

      +

      INSERT INTO nosql_table (user_id, age, user_name) VALUES (3, 30, 'user3');

      +
    • SELECT * FROM <table_name>: This command queries table data.
    • Add a column to the table. Example

      ALTER TABLE nosql_table ADD gender text;

      +
    • Insert data to the added column. Example:

      UPDATE nosql.nosql_table SET prename = 'user_prename1' WHERE user_id = 1;

      +

      UPDATE nosql.nosql_table SET prename = 'user_prename2' WHERE user_id = 2;

      +

      UPDATE nosql.nosql_table SET prename = 'user_prename3' WHERE user_id = 3;

      +
    • Delete data in a keyspace. Example:

      Delete the age data of the user whose ID is 1.

      +

      DELETE age FROM nosql.nosql_table WHERE user_id=1;

      +

      Delete the entire record of the user whose ID is 2.

      +

      DELETE FROM nosql.nosql_table WHERE user_id=2;

      +
    • Clear all records in the table. Example:

      TRUNCATE nosql.nosql_table;

      +
    • Delete the entire table. Example:

      DROP TABLE nosql.nosql_table;

      +
    +
+
+
+ + diff --git a/docs/geminidb/umn/nosql_02_0010.html b/docs/geminidb/umn/nosql_02_0010.html new file mode 100644 index 00000000..21fef7a5 --- /dev/null +++ b/docs/geminidb/umn/nosql_02_0010.html @@ -0,0 +1,174 @@ + + +

Creating a GeminiDB Cassandra Instance

+

This section describes how to create a DB instance that is compatible with Cassandra APIs.

+

Procedure

  1. Log in to the GeminiDB console.
  2. On the Instance Management page, click Create DB Instance.
  3. On the displayed page, select your DB instance specifications and click Create Now.

    +

    + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Basic information

    Parameter

    +

    Description

    +

    Region

    +

    The region where the tenant is located.

    +
    NOTICE:

    Select the region nearest where you will be accessing the DB from so latency can be kept to a minimum and response time will be faster. Also, products deployed in different regions cannot communicate with each other through a private network and you cannot change the region of an instance after creating the instance.

    +
    +

    DB Instance Name

    +

    The new name can be the same as an existing instance name. It must start with a letter and consist of 4 to 64 characters. Only letters (case-sensitive), digits, hyphens (-), and underscores (_) are allowed.

    +

    +

    +

    After the DB instance is created, you can change the DB instance name. For details, see section Changing a DB Instance Name.

    +

    Compatible API

    +

    Cassandra

    +

    DB Instance Type

    +

    Cluster

    +

    DB Engine Version

    +

    3.11

    +

    AZ

    +

    An AZ is a part of a region with its own independent power supplies and networks. AZs are physically isolated but can communicate through an internal network connection.

    +
    +
    + +
    + + + + + + + + + + + + + +
    Table 2 Specifications and storage

    Parameter

    +

    Description

    +

    Instance Specifications

    +

    The CPU and memory of a DB instance.

    +

    Different performance specifications support different numbers of connections and maximum IOPSs. Select CPU and memory specifications based on your service requirements.

    +

    After a DB instance is created, you can change its CPU and memory. For details, see Changing a DB Instance Class.

    +

    Nodes

    +

    The number of nodes ranges from 3 to 200. Select the number of nodes based on the site requirements.

    +

    After a DB instance is created, you can add nodes. For details, see Adding Nodes.

    +

    Storage Space

    +

    Storage space depends on the instance specifications. The minimum storage space is 100 GB, and the storage space you set must be an integer. You can select a minimum of 1 GB each time you scale up storage space.

    +

    After a DB instance is created, you can scale up its storage space. For details, see Scaling Up Storage Space.

    +
    +
    + +
    + + + + + + + + + + + + + +
    Table 3 Network

    Parameter

    +

    Description

    +

    VPC

    +

    The virtual network where your DB instances are located. A VPC isolates networks for different services. You can select an existing VPC or create a VPC.

    +

    If there are no VPCs available, the system allocates resources to you by default.

    +

    For details on how to create a subnet, see the "Creating a VPC" section in the Virtual Private Cloud User Guide.

    +
    NOTE:

    After the GeminiDB Cassandra instance is created, the VPC where the instance resides cannot be changed.

    + +
    +

    Subnet

    +

    A subnet provides dedicated network resources that are logically isolated from other networks for network security.

    +

    Security Group

    +

    A security group controls access between GeminiDB instances and other services. When you select a security group, you must ensure that it allows the client to access DB instances.

    +

    If there are no security groups available, the system allocates resources to you by default.

    +
    +
    + +
    + + + + + + + + + + + + + + + + +
    Table 4 Database configuration

    Parameter

    +

    Description

    +

    Administrator

    +

    The default administrator account is rwuser.

    +

    Administrator Password

    +

    Set a password for the administrator. The password:

    +
    • Must be 8 to 32 characters long.
    • Must contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!@#%^*-_=+?
    • For security reasons, you must select a strong password. The system will verify the password strength.
    +

    Keep this password secure. If you lose it, the system cannot retrieve it.

    +

    Confirm Password

    +

    Enter the administrator password again.

    +

    Parameter Template

    +

    A parameter template contains engine configuration values that can be applied to one or more instances.

    +

    After a DB instance is created, you can modify parameters to better meet your service requirements. For details, see Modifying a Parameter Template.

    +
    +
    + +
    + + + + + + + +
    Table 5 Tags

    Parameter

    +

    Description

    +

    Tags

    +

    The setting is optional. Adding tags helps you better identify and manage your DB instances. Each DB instance can have up to 20 tags.

    +

    A tag is composed of a key-value pair.

    +
    • Key: Mandatory if the DB instance is going to be tagged

      Each tag key must be unique for each DB instance. The key can include up to 36 characters, including digits, letters, underscores (_), and hyphens (-).

      +
    • Value: Optional if the DB instance is going to be tagged

      The value can contain up to 43 characters, including digits, letters, underscores (_), periods (.), and hyphens (-).

      +
    +

    After a DB instance is created, you can view its tag details on the Tags tab. In addition, you can add, modify, and delete tags for existing DB instances.

    +
    +
    +

  4. On the displayed page, confirm the DB instance details.

    • If you need to modify the specifications, click Previous to return to the previous page.
    • If you do not need to modify the specifications, click Submit to start creating the instance.
    +

  5. On the Instance Management page, view and manage your DB instances.

    • Creating a DB instance takes about 5 to 9 minutes. During the process, the instance status displayed in the DB instance list is Creating.
    • After the creation is complete, the status changes to Available.

      You can click in the upper right corner of the page to refresh the DB instance statuses.

      +
    • During creation, an automated backup policy is enabled by default. A full backup is automatically triggered after a DB instance is created.
    +

+
+
+ + diff --git a/docs/geminidb/umn/nosql_02_0011.html b/docs/geminidb/umn/nosql_02_0011.html new file mode 100644 index 00000000..498da5ef --- /dev/null +++ b/docs/geminidb/umn/nosql_02_0011.html @@ -0,0 +1,17 @@ + + +

Configuring Security Group Rules

+

Scenarios

The default security group rule allows all outgoing data packets. ECSs and GeminiDB Cassandra 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 GeminiDB Cassandra instances that in it.

+

This section describes how to create a security group to enable specific IP addresses and ports to access GeminiDB Cassandra instances.

+
+

Precautions

  • By default, you can create up to 500 security group rules. However, too many rules increase network latency for initial access, so it is recommended that you add no more than 50 rules for each security group.
  • To access a GeminiDB Cassandra instance from resources outside the security group, you need to configure an inbound rule to allow access to the GeminiDB Cassandra instance.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Network, click Virtual Private Cloud.
  4. In the navigation pane on the left, choose Access Control > Security Groups.
  5. On the Security Groups page, click the security group name.
  6. On the Inbound Rules tab, click Add Rule. In the displayed Add Inbound Rule dialog box, set required parameters to add inbound rules. On the Outbound Rules tab, click Add Rule. In the displayed Add Outbound Rule dialog box, set required parameters to add outbound rules.
  7. In the displayed dialog box, set required parameters.
  8. Click OK.
+
+
+ + diff --git a/docs/geminidb/umn/nosql_03_0002.html b/docs/geminidb/umn/nosql_03_0002.html new file mode 100644 index 00000000..193a045d --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0002.html @@ -0,0 +1,31 @@ + + +

DB Instance Management

+
+ + diff --git a/docs/geminidb/umn/nosql_03_0003.html b/docs/geminidb/umn/nosql_03_0003.html new file mode 100644 index 00000000..2160119d --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0003.html @@ -0,0 +1,17 @@ + + +

Restarting a DB Instance

+

Scenarios

You may need to occasionally restart a DB instance to perform routine maintenance.

+
+

Precautions

  • If the instance status is Available, Abnormal, or Checking restoration, you can restart the instance.
  • Restarting a DB instance interrupts services, so exercise caution when performing this operation.
  • If you restart a DB instance, all nodes in the instance are also restarted.
+
+

Procedure

  1. Log in to the GeminiDB console.
  2. On the Instance Management page, locate the DB instance you wish to restart and choose More > Restart in the Operation column.

    Alternatively, click the DB instance you wish to restart, and on the displayed Basic Information page, click Restart in the upper right corner of the page.

    +

  3. In the displayed dialog box, click Yes.
+
+
+
+
+
Parent topic: DB Instance Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_03_0004.html b/docs/geminidb/umn/nosql_03_0004.html new file mode 100644 index 00000000..32eb7c86 --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0004.html @@ -0,0 +1,17 @@ + + +

Deleting Nodes

+

Scenarios

You can delete nodes that are no longer used to release resources.

+
+

Precautions

Deleted nodes cannot be recovered. Exercise caution when performing this operation.

+
+

Procedure

  1. Log in to the GaussDB NoSQL console.
  2. On the Instance Management page, click the instance whose nodes you wish to delete.
  3. In the Node Information area on the Basic Information page, locate the node you wish to delete and click Delete in the Operation column.
  4. In the displayed dialog box, click Yes.

    • The status of the instance in the instance list is Deleting node.
    • After the deletion, the instance status becomes Available.
    +

+
+
+
+
+
Parent topic: DB Instance Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_03_0005.html b/docs/geminidb/umn/nosql_03_0005.html new file mode 100644 index 00000000..a21c8dac --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0005.html @@ -0,0 +1,17 @@ + + +

Deleting DB Instances

+

Scenarios

This section describes how to delete a DB instance no longer used to release resources.

+
+

Precautions

  • If you delete a DB instance, all the data in it and all automated backups are automatically deleted as well and cannot be restored, so exercise caution when performing this operation.
  • If you delete an instance, all nodes in the instance are also deleted.
+
+

Procedure

  1. Log in to the GaussDB NoSQL console.
  2. On the Instance Management page, locate the DB instance you wish to delete and choose More > Delete in the Operation column.
  3. On the displayed page, click Yes.

    Deleted DB instances are not displayed in the instance list.

    +

+
+
+
+
+
Parent topic: DB Instance Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_03_0006.html b/docs/geminidb/umn/nosql_03_0006.html new file mode 100644 index 00000000..56b2672d --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0006.html @@ -0,0 +1,19 @@ + + +

Backups and Restorations

+
+ + diff --git a/docs/geminidb/umn/nosql_03_0007.html b/docs/geminidb/umn/nosql_03_0007.html new file mode 100644 index 00000000..664eac2d --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0007.html @@ -0,0 +1,36 @@ + + +

Managing Automated Backups

+

GeminiDB Cassandra creates automated backups to ensure data reliability. If a database or table is maliciously or accidentally deleted, backups can help you ensure you do not lose your data.

+

Automated Backup Policy

Automated backups are generated according to a backup policy and saved as packages in OBS buckets to ensure data confidentiality and durability. You are advised to regularly back up your database, in case it becomes faulty or damaged. However, backing up data might affect the database read and write performance so it is recommended that you enable automated backups during off-peak hours.

+
When you create a DB instance, an automated backup policy is enabled by default.
  • Retention Period: Automated backup files are saved for seven days by default. The backup retention period can range from 1 to 35 days.
    • If the retention period is less than seven days, the system automatically backs up data every day.
    • The system checks existing automated backup files and deletes the files that exceed the backup retention period you set.
    • Time Window: An hour within 24 hours, such as 01:00-02:00 or 12:00-13:00. The backup time is in GMT format. If the DST or standard time is switched, the backup time segment changes with the time zone.
    +
    +
  • Backup Cycle: By default, each day of the week is selected.
    • All: Each day of the week is selected. The system automatically backs up data every day.
    • Select a cycle: You can select one or more days in a week. The system automatically backs up data at the specified time.
    +

    A full backup starts within one hour of the time you specify. The amount of time required for the backup depends on the amount of data to be backed up. The more data has to be backed up, the longer it will take.

    +
    +
  • After a DB instance is created, you can modify the automated backup policy as needed. You can change the time window after the DB instance is created. The system backs up data based on the automated backup policy you have set.
  • If the automated backup policy is disabled, any automated backups in progress stop immediately.
+
+
+

Modifying an Automated Backup Policy

  1. Log in to the GaussDB NoSQL console.
  2. On the Instance Management page, click the DB instance you wish to modify the policy for.
  3. On the Backups & Restorations page, click Modify Backup Policy. In the displayed dialog box, set the backup policy. Then, click Yes to save the configuration.

    For details about how to set a backup policy, see Automated Backup Policy.

    +

  4. Check or manage the generated backups on the Backup Management page or on the Backups & Restorations page.
+
+

Disabling Automated Backup Policy

  1. Log in to the GaussDB NoSQL console.
  2. On the Instance Management page, click the DB instance you wish to modify the policy for.
  3. On the Backups & Restorations page, click Modify Backup Policy.
  4. In the displayed dialog box, click to disable the backup policy and click Yes.

    When disabling the automated backup policy, you can decide whether to delete the automated backups by selecting Delete automated backups.
    • If you select it, all backup files within the retention period will be deleted. No automated backups are displayed in the backup list until you enable the automated backup policy again.
    • If you do not select it, all backup files within the retention period will be retained, but you can still manually delete them later if needed. For details, see section Deleting an Automated Backup.
    +
    +

    If the automated backup policy is disabled, any automated backups in progress stop immediately.

    +

+
+

Deleting an Automated Backup

If the automated backup policy is disabled, you can delete stored automated backups to free up storage space.

+

If the automated backup policy is enabled, the system will delete automated backups as they expire. You cannot delete them manually.

+

The deletion operation is irreversible, so exercise caution when performing this operation.

+
+
  • Method 1
    1. On the Instance Management page, click the DB instance you wish to delete backups for.
    2. On the Backups & Restorations page, locate the backup you wish to delete and click Delete.
    3. In the Delete Backup dialog box, confirm the backup information and click Yes.
    +
  • Method 2
    1. On the Backup Management page, locate the target backup and click Delete.
    2. In the Delete Backup dialog box, confirm the backup information and click Yes.
    +
+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/geminidb/umn/nosql_03_0008.html b/docs/geminidb/umn/nosql_03_0008.html new file mode 100644 index 00000000..10d59307 --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0008.html @@ -0,0 +1,56 @@ + + +

Managing Manual Backups

+

To ensure data reliability, GeminiDB Cassandra API allows you to manually back up DB instances whose status is Available. If a database or table is deleted, maliciously or accidentally, backups can help recover your data.

+
  • By default, you can create up to 50 backups.
  • Manual backups are full backups.
+
+

Creating a Manual Backup

  1. Log in to the GeminiDB console.
  2. Create a manual backup.

    Method 1

    +

    On the Instance Management page, locate the DB instance you wish to back up and click Create Backup or More > Create Backup in the Operation column.

    +
    Method 2
    1. On the Instance Management page, click the DB instance you wish to back up.
    2. On the Backups & Restorations page, click Create Backup.
    +
    +

    Method 3

    +

    In the navigation pane on the left, choose Backup Management. On the displayed page, click Create Backup.

    +

  3. In the displayed dialog box, enter the backup name and description, and click OK.

    +

    + + + + + + + + + + + + + +
    Table 1 Parameter description

    Parameter

    +

    Description

    +

    DB Instance Name

    +

    The default value is the name of the DB instance to be backed up and cannot be modified.

    +

    Backup Name

    +

    The backup name must be 4 to 64 characters in length and start with a letter. Backup names are case-insensitive and can only contain letters, digits, hyphens (-), and underscores (_).

    +

    Description

    +

    The description contains a maximum of 256 characters and cannot include line breaks or the following special characters: >!<"&'=

    +
    +
    +

  4. View the backup status after the task has been executed.

    • During the creation of a manual backup, you can query the backup status on the Backup Management page or the Backups & Restorations page. The backup status is Backing up.
    • If a manual backup was successfully created, the backup status is Completed.
    +

+
+

Deleting a Manual Backup

If you do not need the manual backup, you can delete it on the Backup Management page or the Backups & Restorations page.

+

Deleted backups are not displayed in the backup list.

+

The deletion operation is irreversible, so exercise caution when performing this operation.

+
+
Method 1
  1. On the Instance Management page, click the DB instance whose backup you wish to delete.
  2. On the Backups & Restorations page, locate the backup you wish to delete and click Delete.
  3. In the Delete Backup dialog box, confirm the backup details and click Yes.
+
+

Method 2

+
  1. On the Backup Management page, locate the target backup and click Delete.
  2. In the Delete Backup dialog box, confirm the backup details and click Yes.
+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/geminidb/umn/nosql_03_0009.html b/docs/geminidb/umn/nosql_03_0009.html new file mode 100644 index 00000000..012cc824 --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0009.html @@ -0,0 +1,23 @@ + + +

Restoring Data to a New DB Instance

+

Scenarios

GeminiDB Cassandra API allows you to restore the existing backup to a new DB instance.

+
+

Procedure

  1. Log in to the GeminiDB console.
  2. Restore a DB instance from the backup.

    Method 1

    +
    1. On the Instance Management page, click the target DB instance.
    2. On the Backups & Restorations page, locate the target backup and click Restore.
    +

    Method 2

    +

    On the Backup Management page, locate the target backup and click Restore.

    +

  3. In the displayed dialog box, confirm the current instance details and restoration method and click OK.

    • The default API type and DB engine version are the same as those of the original instance and cannot be changed.
    • GeminiDB automatically calculates the minimum storage space required for restoration based on the size of the selected backup file. The storage space depends on the instance specifications, and must be a multiple of 10 GB.
    • You need to set a new administrator password.
    +
    • To modify other parameters, see the description of creating DB instances of other DB engines in the Getting Started.
    +

  4. View the restoration results.

    A new DB instance is created using the backup data. The status of the DB instance changes from Creating to Available.

    +

    After the restoration, the system will perform a full backup.

    +

    The new DB instance is independent from the original one.

    +

+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/geminidb/umn/nosql_03_0010.html b/docs/geminidb/umn/nosql_03_0010.html new file mode 100644 index 00000000..64251f75 --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0010.html @@ -0,0 +1,20 @@ + + +

Monitoring and Alarm Reporting

+

+
+ + diff --git a/docs/geminidb/umn/nosql_03_0011.html b/docs/geminidb/umn/nosql_03_0011.html new file mode 100644 index 00000000..bb156677 --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0011.html @@ -0,0 +1,604 @@ + + +

GeminiDB Cassandra Metrics

+

Description

This section describes GeminiDB Cassandra metrics reported to Cloud Eye as well as their namespaces and dimensions. You can use APIs provided by Cloud Eye to query the metrics of the monitored object and alarms generated for GeminiDB Cassandra API.

+
+

Namespace

SYS.NoSQL

+
+

Metrics

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Metrics

Metric

+

Name

+

Description

+

Value Range

+

Monitored Object

+

Monitoring Interval (Raw Data)

+

nosql005_disk_usage

+

Storage Space Usage

+

Storage space usage of the monitored object

+

Unit: Percent

+

0-100%

+

Measured object: ECS

+

Monitored object: GeminiDB instance

+

1 minute

+

nosql006_disk_total_size

+

Total Storage Space

+

Total storage space of the monitored object

+

Unit: GB

+

≥ 0 GB

+

Measured object: ECS

+

Monitored object: GeminiDB instance

+

1 minute

+

nosql007_disk_used_size

+

Used Storage Space

+

Used storage space of the monitored object

+

Unit: GB

+

≥ 0 GB

+

Measured object: ECS

+

Monitored object: GeminiDB instance

+

1 minute

+

cassandra001_cpu_usage

+

CPU Usage

+

CPU usage of an instance

+

Unit: Percent

+

0-100%

+

Measured object: ECS

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra002_mem_usage

+

Memory Usage

+

Memory usage of the instance

+

Unit: Percent

+

0-100%

+

Measured object: ECS

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra003_bytes_out

+

Network Output Throughput

+

Outgoing traffic in bytes per second

+

Unit: byte/s

+

≥ 0 Bytes/s

+

Measured object: ECS

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra004_bytes_in

+

Network Input Throughput

+

Incoming traffic in bytes per second

+

Unit: byte/s

+

≥ 0 Bytes/s

+

Measured object: ECS

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra014_connections

+

Active Node Connections

+

Total number of connections attempting to connect to Cassandra instance nodes

+

Unit: count

+

≥ 0 Counts

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra015_read_latency

+

Average Read Latency

+

Average amount of time consumed by read requests

+

Unit: ms

+

≥ 0 ms

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra016_write_latency

+

Average Write Latency

+

Average amount of time consumed by write requests

+

Unit: ms

+

≥ 0 ms

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra037_pending_write

+

Suspended Write Tasks

+

Number of write tasks in waiting status

+

Unit: count

+

≥ 0 Counts

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra038_pending_read

+

Suspended Read Tasks

+

Number of read tasks in waiting status

+

Unit: count

+

≥ 0 Counts

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra044_range_slice_latency

+

Scan Duration

+

Average amount of time consumed by scan operations

+

Unit: ms

+

≥ 0 ms

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra049_dropped_mutation

+

Dropped Writes

+

Average number of dropped writes

+

Unit: Count

+

≥ 0 Counts

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra052_dropped_read

+

Dropped Reads

+

Average number of dropped reads

+

Unit: Count

+

≥ 0 Counts

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra092_load_info

+

Data Volume on a Node

+

Data volume on a node

+

Unit: byte

+

≥ 0 Bytes

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra093_write_count_latency

+

Accumulated Write Requests

+

Total number of write requests initiated by a node

+

Unit: count

+

≥ 0 Counts

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra094_write_1min_rate

+

Average Write Rate in the Last Minute

+

Average write rate in the last minute

+

Unit: Count

+

≥ 0 Counts

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra095_write_p75_latency

+

P75 Write Latency

+

P75 write latency

+

Unit: ms

+

≥ 0 ms

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra096_write_p95_latency

+

P95 Write Latency

+

P95 write latency

+

Unit: ms

+

≥ 0 ms

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra097_write_p99_latency

+

P99 Write Latency

+

P99 write latency

+

Unit: ms

+

≥ 0 ms

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra098_read_count_latency

+

Accumulated Read Requests

+

Total number of read requests initiated by a node

+

Unit: count

+

≥ 0 Counts

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra099_read_1min_rate

+

Average Read Rate in the Last Minute

+

Average read rate in the last minute

+

Unit: Count

+

≥ 0 Counts

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra100_read_p75_latency

+

P75 Read Latency

+

P75 read latency

+

Unit: ms

+

≥ 0 ms

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra101_read_p95_latency

+

P95 Read Latency

+

P95 read latency

+

Unit: ms

+

≥ 0 ms

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra102_read_p99_latency

+

P99 Read Latency

+

P99 read latency

+

Unit: ms

+

≥ 0 ms

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra103_range_slice_count_latency

+

Accumulated Range Read Requests

+

Accumulated range read requests

+

Unit: Count

+

≥ 0 Counts

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra104_range_slice_1min_rate

+

Average Range Read Rate in the Last Minute

+

Average range read rate in the last minute

+

Unit: Count

+

≥ 0 Counts

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra105_range_slice_p75_latency

+

P75 Range Read Latency

+

P75 range read latency

+

Unit: ms

+

≥ 0 ms

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra106_range_slice_p95_latency

+

P95 Range Read Latency

+

P95 range read latency

+

Unit: ms

+

≥ 0 ms

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra107_range_slice_p99_latency

+

P99 Range Read Latency

+

P99 range read latency

+

Unit: ms

+

≥ 0 ms

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra163_write_p999_latency

+

P999 Write Latency

+

P999 write latency

+

Unit: ms

+

≥ 0 ms

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra164_read_p999_latency

+

P999 Read Latency

+

P999 read latency

+

Unit: ms

+

≥ 0 ms

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra165_large_partition_num

+

Large Keys

+

Number of large keys on the current node

+

Unit: count

+

≥ 0 Counts

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra166_write_max_latency

+

Maximum Write Latency

+

Maximum write latency

+

Unit: ms

+

≥ 0 ms

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra167_read_max_latency

+

Maximum Read Latency

+

Maximum read latency

+

Unit: ms

+

≥ 0 ms

+

Monitored object: database

+

Monitored object: GeminiDB Cassandra instance node

+

1 minute

+

cassandra168_imbalance_table_num

+

Tables with Uneven Data Distribution

+

Number of tables in which data is not evenly distributed.

+

Unit: Count

+

≥ 0 Counts

+

Monitored object: database

+

Monitored object: node of the Kunpeng-based GeminiDB Cassandra instance

+

1 minute

+
+
+
+

Dimensions

+
+ + + + + + + +

Key

+

Value

+

cassandra_cluster_id.cassandra_node_id

+

Cluster ID or node ID of the GeminiDB Cassandra instance

+
+
+
+
+
+
+
Parent topic: Monitoring and Alarm Reporting
+
+
+ diff --git a/docs/geminidb/umn/nosql_03_0012.html b/docs/geminidb/umn/nosql_03_0012.html new file mode 100644 index 00000000..d47bb57f --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0012.html @@ -0,0 +1,17 @@ + + +

Setting Alarm Rules

+

Scenarios

You can set alarm rules to customize the monitored objects and notification policies and to stay aware of the database operating status.

+

The alarm rules include alarm rule name, instance, metric, threshold, monitoring interval and whether to send notification. This section describes how to set alarm rules.

+

For more information about GeminiDB alarm rules, see Cloud Eye User Guide.

+
+
+

Procedure

  1. Log in to the management console.
  2. After the alarm rule is set, the system automatically notifies you when an alarm is triggered.
+
+
+
+
+
Parent topic: Monitoring and Alarm Reporting
+
+
+ diff --git a/docs/geminidb/umn/nosql_03_0013.html b/docs/geminidb/umn/nosql_03_0013.html new file mode 100644 index 00000000..cc608836 --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0013.html @@ -0,0 +1,22 @@ + + +

Viewing Metrics

+

Scenarios

Cloud Eye monitors GeminiDB running statuses. You can obtain the monitoring metrics of GeminiDB on the management console.

+

Monitored data requires a period of time for transmission and display. The status of the monitored object displayed on the Cloud Eye page is the status obtained 5 to 10 minutes before. You can view the monitored data of a newly created DB instance 5 to 10 minutes later.

+
+

Prerequisites

  • The DB instance is running properly.

    Cloud Eye does not display the metrics of a faulty or deleted DB instance. You can view the monitoring information only after the instance is restarted or recovered.

    +
+
  • The DB instance has been properly running for at least 10 minutes.

    The monitoring data and graphics are available for a new DB instance after the instance runs for at least 10 minutes.

    +
+
+

Procedure

  1. Log in to the GaussDB NoSQL console.
  2. On the Instance Management page, click the target DB instance.
  3. In the Node Information area on the Basic Information page, click View Metric in the Operation column.
  4. In the monitoring area, you can select a duration to view the monitoring data.

    You can view the monitoring data of the service in the last 1, 3, or 12 hours.

    +

    To view the monitoring curve in a longer time range, click to enlarge the graph.

    +

+
+
+
+
+
Parent topic: Monitoring and Alarm Reporting
+
+
+ diff --git a/docs/geminidb/umn/nosql_03_0014.html b/docs/geminidb/umn/nosql_03_0014.html new file mode 100644 index 00000000..1d65a41a --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0014.html @@ -0,0 +1,51 @@ + + +

Managing Tags

+

Scenarios

Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags globally and other cloud services manage their own tags.

+

Adding tags to GeminiDB instances helps you better identify and manage them. An instance can be tagged during or after it is created.

+

After an instance is tagged, you can search for the tag key or value to quickly query the instance details.

+
+

Precautions

  • You are advised to set predefined tags on the TMS console.
  • A tag consists of a key and value. You can add only one value for each key. For details about the naming rules of tag keys and tag values, see Table 1.
  • Up to 20 tags can be added for each instance.
+ +
+ + + + + + + + + + + + + +
Table 1 Naming rules

Parameter

+

Requirement

+

Example Value

+

Tag key

+
  • The key cannot be left blank.
  • Each tag key is unique for each instance.
  • A tag key consists of a maximum of 36 characters.
  • The key can only consist of digits, letters, underscores (_), hyphens (-), and at signs (@).
+

Organization

+

Tag value

+
  • This tag value can be left blank.
  • The value consists of up to 43 characters.
  • The value can only consist of digits, letters, underscores (_), hyphens (-), and at signs (@).
+

nosql_01

+
+
+
+

Adding a Tag

  1. Log in to the GaussDB NoSQL console.
  2. On the Instance Management page, click the instance you wish to add tags for to go to the Basic Information page.
  3. In the navigation pane on the left, click Tags.
  4. On the Tags page, click Add Tag. In the displayed dialog box, enter a tag key and value, and click OK.
  5. View and manage tags on the Tags page.
+
+

Editing a Tag

  1. Log in to the GaussDB NoSQL console.
  2. On the Instance Management page, click the instance you wish to add tags for to go to the Basic Information page.
  3. In the navigation pane on the left, click Tags.
  4. On the Tags page, locate the tag to be edited and click Edit in the Operation column. In the displayed dialog box, change the tag value and click OK.

    Only the tag value can be edited when editing a tag.

    +

  5. View and manage tags on the Tags page.
+
+

Deleting a Tag

  1. Log in to the GaussDB NoSQL console.
  2. On the Instance Management page, click the instance you wish to delete tags for to go to the Basic Information page.
  3. In the navigation pane on the left, click Tags.
  4. On the Tags page, locate the tag to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.
  5. After a tag has been deleted, it will not be displayed on the Tags page.
+
+

Searching an Instance by Tag

  1. Log in to the GaussDB NoSQL console.
  2. On the Instance Management page, click Search by Tag in the upper right corner of the instance list.
  3. Enter the key or value of the tag to be queried and click Search to query the instance associated with the tag.
+
+
+
+
+
Parent topic: DB Instance Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_03_0015.html b/docs/geminidb/umn/nosql_03_0015.html new file mode 100644 index 00000000..3f4694ae --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0015.html @@ -0,0 +1,50 @@ + + +

Using COPY to Import and Export Data

+

Scenarios

The COPY command is one of cqlsh commands. It includes COPY TO and COPY FROM. They are used to copy data to and from Cassandra.

+

You can run the COPY TO command to export data from an existing Cassandra instance and then run the COPY FROM command to import the data to an RDBMS instance or a new Cassandra instance. Currently, you can copy data to or from the CSV and JSON files.

+
+

Precautions

You are advised to import and export data during off-peak hours to avoid the impact on your services.

+
+

Prerequisites

You have connected to a DB instance. For details, see Connecting to a GeminiDB Cassandra Instance Over Private Networks.

+
+

Method

  • Start cqlsh, and then run the COPY command.

    ./cqlsh <DB_HOST> -u <user_name>

    +

    COPY cycling.cyclist_name TO '/home/cas/copydata';

    +
    • <DB_HOST> indicates the IP address and port of the native Cassandra database. Change it based on the site requirements.
    • -e: Executes a specified statement in the background, then exits.
    • cycling.cyclist_name: indicates the database name and table name. Change it based on the site requirements.
    +
    +
  • If there is large amount of data, add the -e parameter in the command to perform operations in the background.

    ./cqlsh <DB_HOST> -u <user_name> -e "COPY cycling.cyclist_name TO '/home/cas/copydata'";

    +
    • <DB_HOST> indicates the IP address and port of the native Cassandra database. Change it based on the site requirements.
    • -e: Executes a specified statement in the background, then exits.
    • cycling.cyclist_name: indicates the database name and table name. Change it based on the site requirements.
    +
    +
+
+

COPY TO

  • Command format:

    COPY <table name> [(<column>, ...)] TO <file name> WITH <copy option> [AND <copy option> ...]

    +
  • Example:

    nohup ./cqlsh <DB_HOST> --request-timeout=3600 --debug -e "COPY nihao.sz_user TO '/home/cas/copydata' with WHERECONDITION='update_timestamp=1' NUMPROCESSES=12 AND RATEFILE='rate.txt' AND RESULTFILE='export_result' AND dataformats='json';" >export.log 2>&1 &

    +
+

Parameter description:

+

The common parameters are as follows: NUMPROCESSES, RATEFILE, PAGESIZE, BEGINTOKEN, ENDTOKEN, MAXATTEMPTS, and MAXOUTPUTSIZE.

+

The newly added parameters are as follows: RESULTFILE, DATAFORMATS, and WHERECONDITION.

+

For details about other COPY TO parameters, see the Cassandra official documentation.

+
  • file name: specifies the directory or file the data is copied to. The data is exported to a file by default.
    • If you specify an existing directory to export the file, the system exports data to different files in the directory based on the specified range. If no data is exported for a given range, no file is generated.

      ./cqlsh <DB_HOST> -e "COPY cycling.cyclist_name TO '/home/cas/copydata'"

      +
    • When you specify a file name, data is exported to the file. If the file does not exist, the system automatically creates a file as you named it.

      ./cqlsh <DB_HOST> -e "COPY cycling.cyclist_name TO '/home/cas/copydata/cycling.cyclist_name'"

      +
    +
  • NUMPROCESSES is the number of exported threads. The range is divided by the number of threads. The more threads are exported, the smaller the ranges are. If the number of threads is too large, the server may be overloaded and the export may fail. You should select a suitable number of threads for export.

    The default number of threads is calculated as follows: <Number of vCPUs>-1

    +
  • RATEFILE is the rate file. After the file path is specified, the instantaneous rate of the export process is displayed for evaluating the export performance.
  • PAGESIZE is the number of rows queried in a single page. The default value is 1000. Do not set this parameter to a small value, or the export performance will suffer.
  • BEGINTOKEN and ENDTOKEN are the range to be exported. By default, all data is exported.
  • MAXATTEMPTS is the number of retries for each query. If the maximum number of retries of a query is reached, the export fails.
  • MAXOUTPUTSIZE is the maximum number of rows in an exported file. If the number of exported rows is greater than the value, another file is generated. By default, the number of rows is not limited.

    ./cqlsh <DB_HOST> -e "COPY cycling.cyclist_name TO '/home/cas/copydata/cycling.cyclist_name' with MAXOUTPUTSIZE=1"

    +
  • RESULTFILE is the path of the result file. If this parameter is not set, the result file is generated in the current directory by default. If there is already a result file in the directory, the file will be renamed. The exported results show the following information: whether the export is successful, total number of exported rows and rate, number of exported ranges, number of successful or failed ranges, and number of exported rows in each range.
  • DATAFORMATS is the data format to be exported. The value can be csv or json. The default value is csv. If the value is in set to json, data will be exported in JSON format.
  • WHERECONDITION is the query criteria to be exported. The query criteria can be exported. For non-primary-key columns, the export performance can be improved if the query is based on indexes.
    • Supported operators: >=, <=, >, <, and =
    • If the value contains special characters, for example, ",><=', add double quotation marks to the value.
    +
+
+

COPY FROM

  • Command format:

    COPY <table name> [(<column>, ...)] FROM <file name> WITH <copy option> [AND <copy option> ...]

    +
  • Example:

    nohup ./cqlsh <DB_HOST> --request-timeout=3600 --debug -e "COPY nihao.sz_user FROM '/home/cas/copydata' with NUMPROCESSES=12 AND RATEFILE='rate.txt' AND dataformats='json';" >import.log 2>&1 &

    +
+

Parameter description:

+

The common parameters are as follows: NUMPROCESSES, MAXROWS, INGESTRATE, ERRFILE, MAXBATCHSIZE, MINBATCHSIZE, CHUNKSIZE, MAXPARSEERRORS, MAXINSERTERRORS, SKIPROWS, and SKIPCOLS.

+

The newly added parameter is DATAFORMATS.

+

For details about other COPY FROM parameters, see the Cassandra official documentation.

+
  • file name is the path the file will be imported to. The value can be a directory, a file, or a list of file names separated by commas (,). If the value is set to a specified directory, all files in the directory are imported.
  • NUMPROCESSES is the number of imported threads.
  • MAXROWS is the maximum number of rows to be imported. By default, the number of rows is not limited.
  • INGESTRATE is the maximum number of rows to be imported per second. The default value is 100000.
  • ERRFILE: The columns that fail to be imported are stored in this file.
  • MAXBATCHSIZE is the maximum number of rows to be imported in each batch. The default value is 20.
  • MINBATCHSIZE is the minimum number of rows to be imported in each batch. The default value is 2.
  • CHUNKSIZE is the number of rows that the main thread transfers to a child thread each time. The default value is 1000.
  • MAXPARSEERRORS: indicates the maximum number of rows whose syntax parsing errors can be ignored. By default, the number of rows is not limited.
  • MAXINSERTERRORS: indicates the maximum number of rows that can be ignored when the rows fail to be inserted. The default value is 1000.
  • SKIPROWS is the number of rows that are skipped during the import. The default value is 0, meaning that no row is skipped.
  • SKIPCOLS is the names of the columns that are ignored during the import. The column names are separated by commas (,). The value is not ignored by default.
  • DATAFORMATS is the data format to be imported. The value can be csv or json. The default value is csv. If the data is in JSON format, set this value to json.
+
+
+ + diff --git a/docs/geminidb/umn/nosql_03_0016.html b/docs/geminidb/umn/nosql_03_0016.html new file mode 100644 index 00000000..7d013dcb --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0016.html @@ -0,0 +1,20 @@ + + +

Resetting the Administrator Password

+

Scenarios

For security reasons, change administrator passwords periodically.

+
+

Precautions

If the instance status is Available, Backing up, Checking restoration, Scaling up or certain nodes become abnormal, you can reset the administrator password.

+
+

Method 1

  1. Log in to the GeminiDB console.
  2. On the Instance Management page, locate the DB instance you wish to reset the password for and choose More > Reset Password in the Operation column.
  3. Enter and confirm the new administrator password and click OK.

    The password must be 8 to 32 characters in length and contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!@#%^*-_=+?

    +

+
+

Method 2

  1. Log in to the GeminiDB console.
  2. On the Instance Management page, click the DB instance you wish to reset the password for. The Basic Information page is displayed.
  3. In the DB Information area, click Reset Password in the Administrator field.
  4. Enter and confirm the new administrator password and click OK.

    The password must be 8 to 32 characters in length and contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!@#%^*-_=+?

    +

+
+
+
+
+
Parent topic: DB Instance Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_03_0017.html b/docs/geminidb/umn/nosql_03_0017.html new file mode 100644 index 00000000..eaf2e2f5 --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0017.html @@ -0,0 +1,199 @@ + + +

Key Operations Recorded by CTS

+

With CTS, you can record operations associated with GeminiDB for later query, audit, and backtrack operations.

+

Table 1 lists the key operations that can be recorded by CTS.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 GeminiDB Cassandra key operations

Operation

+

Resource

+

Trace Name

+

Creating a DB instance

+

instance

+

NoSQLCreateInstance

+

Deleting a DB instance

+

instance

+

NoSQLDeleteInstance

+

Adding nodes

+

instance

+

NoSQLEnlargeInstance

+

Deleting nodes

+

instance

+

NoSQLReduceInstance

+

Restarting a DB instance

+

instance

+

NoSQLRestartInstance

+

Restoring data to new DB instances

+

instance

+

NoSQLRestoreNewInstance

+

Scaling up storage space

+

instance

+

NoSQLExtendInstanceVolume

+

Resetting a password

+

instance

+

NoSQLResetPassword

+

Changing DB instance names

+

instance

+

NoSQLRenameInstance

+

Changing a DB instance class

+

instance

+

NoSQLResizeInstance

+

Binding an EIP

+

instance

+

NoSQLBindEIP

+

Unbinding an EIP

+

instance

+

NoSQLUnBindEIP

+

Creating a backup

+

backup

+

NoSQLCreateBackup

+

Deleting a backup

+

backup

+

NoSQLDeleteBackup

+

Setting a backup policy

+

backup

+

NoSQLSetBackupPolicy

+

Adding an instance tag

+

tag

+

NoSQLAddTags

+

Modifying an instance tag

+

tag

+

NoSQLModifyInstanceTag

+

Deleting an instance tag

+

tag

+

NoSQLDeleteInstanceTag

+

Creating a parameter template

+

parameterGroup

+

NoSQLCreateConfigurations

+

Modifying a parameter template

+

parameterGroup

+

NoSQLUpdateConfigurations

+

Modifying instance parameters

+

parameterGroup

+

NoSQLUpdateInstanceConfigurations

+

Replicating a parameter template

+

parameterGroup

+

NoSQLCopyConfigurations

+

Resetting a parameter template

+

parameterGroup

+

NoSQLResetConfigurations

+

Applying a parameter template

+

parameterGroup

+

NoSQLApplyConfigurations

+

Deleting a parameter template

+

parameterGroup

+

NoSQLDeleteConfigurations

+
+
+
+
+
+
Parent topic: Auditing
+
+
+ diff --git a/docs/geminidb/umn/nosql_03_0018.html b/docs/geminidb/umn/nosql_03_0018.html new file mode 100644 index 00000000..71663a49 --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0018.html @@ -0,0 +1,19 @@ + + +

Querying Traces

+

After CTS is enabled, CTS starts recording operations on cloud resources. The CTS console stores the last seven days of operation records.

+

This section describes how to query operation records for the last 7 days on the CTS console.

+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Management & Deployment, click Cloud Trace Service.
  4. Choose Trace List in the navigation pane on the left.
  5. Specify the filters used for querying traces. The following four filters are available:

    • Trace Source, Resource Type, Search By, and Operator

      Select the filter from the drop-down list.

      +

      When you select Trace name for Search By, you also need to select a specific trace name.

      +

      When you select Resource ID for Search By, you also need to select or enter a specific resource ID.

      +

      When you select Resource name for Search By, you also need to select or enter a specific resource name.

      +
    • Operator: Select a specific operator (a user rather than tenant).
    • Trace Status: Available options include All trace statuses, normal, warning, and incident. You can only select one of them.
    • Start time and end time: You can specify the time period for query traces.
    +

  6. Click to the left of the record to be queried to extend its details.
  7. Locate a trace and click View Trace in the Operation column.
+
+
+
+
+
Parent topic: Auditing
+
+
+ diff --git a/docs/geminidb/umn/nosql_03_0019.html b/docs/geminidb/umn/nosql_03_0019.html new file mode 100644 index 00000000..7e750441 --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0019.html @@ -0,0 +1,18 @@ + + +

Auditing

+

+
+ + diff --git a/docs/geminidb/umn/nosql_03_0025.html b/docs/geminidb/umn/nosql_03_0025.html new file mode 100644 index 00000000..daa3e3b0 --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0025.html @@ -0,0 +1,20 @@ + + +

Changing a DB Instance Name

+

Scenarios

This section describes how to change a GeminiDB Cassandra instance name to identify different DB instances.

+
+

Method 1

  1. Log in to the GeminiDB console.
  2. On the Instance Management page, click to the right of the instance whose name you wish to change.

    • To submit the change, click OK.

      The new name can be the same as an existing instance name. It must start with a letter and consist of 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.

      +
    • To cancel the change, click Cancel.
    +

  3. View the results on the Instance Management page.
+
+

Method 2

  1. Log in to the GeminiDB console.
  2. On the Instance Management page, click the instance whose name you wish to change.
  3. In the Instance Information area on the Basic Information page, click in the DB Instance Name field to change the instance name.

    • To submit the change, click .

      The new name can be the same as an existing instance name. It must start with a letter and consist of 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.

      +
    • To cancel the change, click .
    +

  4. View the results on the Instance Management page.
+
+
+
+
+
Parent topic: DB Instance Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_03_0026.html b/docs/geminidb/umn/nosql_03_0026.html new file mode 100644 index 00000000..37a330ff --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0026.html @@ -0,0 +1,24 @@ + + +

Changing a DB Instance Class

+

Scenarios

This section describes how to change the CPU or memory of your instance to suit your service requirements.

+
+

Precautions

  • Instances can be scaled up or down.
  • Services will be interrupted for 5 to 10 minutes when you change DB instance CPU or memory, so you are advised to perform these operations during off-peak hours.
  • You are not advised to perform DDL operations when changing the CPU and memory.

    A data definition language (DDL) is a syntax for defining data structures and database objects. Common examples of DDL statements include CREATE, ALTER, and DROP. DDL is used to create, modify, and delete database objects, such as tables, indexes, views, functions, stored procedures, and triggers.

    +
    +
+
+

Procedure

  1. Log in to the GaussDB NoSQL console.
  2. On the Instance Management page, click the DB instance you wish to change the CPU and memory for.
  3. In the in DB Information area on the Basic Information page, click Change next to the Instance Class field.
  4. On the displayed page, select the desired vCPUs and memory and click Next.
  5. On the displayed page, confirm the instance class.

    • If you need to modify your settings, click Previous to go back to the page where you specify details.
    • If you do not need to modify your settings, click Submit to change the instance class.
    +

  6. View the DB instance class change result.

    Go to the Basic Information page and in the DB Information area you can see the new instance class.

    +

+
+

Method 2

  1. Log in to the GaussDB NoSQL console.
  2. On the Instance Management page, locate the instance you want to change the class for and choose More > Change Instance Class in the Operation column.
  3. On the displayed page, select the desired vCPUs and memory and click Next.
  4. On the displayed page, confirm the instance class.

    • If you need to modify your settings, click Previous to go back to the page where you specify details.
    • If you do not need to modify your settings, click Submit to change the instance class.
    +

  5. View the DB instance class change result.

    Go to the Basic Information page and in the DB Information area you can see the new instance class.

    +

+
+
+
+
+
Parent topic: DB Instance Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_03_0027.html b/docs/geminidb/umn/nosql_03_0027.html new file mode 100644 index 00000000..dd384624 --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0027.html @@ -0,0 +1,15 @@ + + +

Log Management

+
+ + diff --git a/docs/geminidb/umn/nosql_03_0028.html b/docs/geminidb/umn/nosql_03_0028.html new file mode 100644 index 00000000..f9e02919 --- /dev/null +++ b/docs/geminidb/umn/nosql_03_0028.html @@ -0,0 +1,16 @@ + + +

Slow Query Logs

+

Scenarios

GeminiDB allows you to view slow query logs of databases. The unit of the execution time is ms. With slow query logs, you can identify and optimize slowly executed statements.

+
+

Viewing Log Details

  1. Log in to the GaussDB NoSQL console.
  2. On the Instance Management page, click the target DB instance.
  3. In the navigation pane on the left, click Slow Query Logs.
  4. On the Slow Query Logs page, set search criteria and click Search to view log information.

    • If you select All nodes, the slow query logs of all nodes in the DB instance are displayed.
    • Slow query logs of a node in different time periods
    • Slow query statements of the following level +
    +

+
+
+
+
+
Parent topic: Log Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_04_change_history.html b/docs/geminidb/umn/nosql_04_change_history.html new file mode 100644 index 00000000..1269496a --- /dev/null +++ b/docs/geminidb/umn/nosql_04_change_history.html @@ -0,0 +1,51 @@ + + +

Change History

+
+
+ + + + + + + + + + + + + + + + + + + + + + +

Released On

+

Description

+

2024-04-30

+

This issue is the sixth official release.

+

GaussDB NoSQL is changed to GeminiDB.

+

2020-07-31

+

This issue is the fifth official release, which incorporates the following change:

+

In Managing Tags, a tag key can contain the at sign (@). A tag value can contain the at sign (@), but cannot contain periods (.).

+

2020-02-10

+

This issue is the fourth official release, which incorporates the following change:

+

Instance specifications 24 vCPUs | 192 GB, and 48 vCPUs | 384 GB in Table 1

+

2020-11-30

+

This issue is the third official release, which incorporates the following changes:

+

GeminiDB Cassandra Metrics

+

Setting Alarm Rules

+

Viewing Metrics

+

2020-08-30

+

This issue is the second official release.

+

2020-06-30

+

This issue is the first official release.

+
+
+
+ diff --git a/docs/geminidb/umn/nosql_05_0001.html b/docs/geminidb/umn/nosql_05_0001.html new file mode 100644 index 00000000..252a562b --- /dev/null +++ b/docs/geminidb/umn/nosql_05_0001.html @@ -0,0 +1,35 @@ + + +

Parameter Template Management

+
+ + diff --git a/docs/geminidb/umn/nosql_05_0002.html b/docs/geminidb/umn/nosql_05_0002.html new file mode 100644 index 00000000..e31c6fb4 --- /dev/null +++ b/docs/geminidb/umn/nosql_05_0002.html @@ -0,0 +1,15 @@ + + +

Creating a Parameter Template

+

You can use database parameter templates to manage the DB engine configuration. A database parameter template acts as a container for engine configuration values that can be applied to one or more DB instances.

+

Each user can create up to 100 parameter templates. All types of instances in the same project can share the quota.

+

Procedure

  1. Log in to the GaussDB NoSQL console.
  2. In the navigation pane on the left, choose Parameter Template Management.
  3. On the Parameter Template Management page, click Create Parameter Template.
  4. Select a compatible DB engine version, name the parameter group, add the parameter group description, and click OK to create a parameter group template.

    • Compatible API: Select the API type that is compatible with your DB engine parameter template.
    • DB Engine Version: Select a DB engine version, for example, 3.11.
    • Parameter Template Name: The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
    • Description: The description can contain a maximum of 256 characters except the carriage return character and the following special characters: > ! < " & ' =
    +

  5. On the Parameter Template Management page, view the created parameter template.
+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_05_0003.html b/docs/geminidb/umn/nosql_05_0003.html new file mode 100644 index 00000000..8f80e7da --- /dev/null +++ b/docs/geminidb/umn/nosql_05_0003.html @@ -0,0 +1,28 @@ + + +

Modifying a Parameter Template

+

This section describes how to modify parameters in the parameter template that you have created to meet your service requirements and achieve optimal performance.

+

Note that parameter values in default parameter templates cannot be changed.

+

Though parameter values in a default template cannot be changed, you can view details about a default parameter template. If a custom parameter template is set incorrectly, the database startup may fail. You can re-configure the custom parameter template according to the configurations of the default parameter template.

+
+

Modifying Parameters in Custom Parameter Template

  1. Log in to the GeminiDB console.
  2. In the navigation pane on the left, choose Parameter Template Management.
  3. In the navigation pane on the left, choose Parameter Template Management. On the Custom Templates tab, click the parameter template you wish to modify.
  4. Change parameter values as required.

    • To save the modifications, click Save.
    • To cancel the modifications, click Cancel.
    • To preview the modifications, click Preview.
    +

  5. After parameters are modified, click Change History to view parameter modification details.

    For details about how to view parameter modification details, see Viewing Parameter Change History.
    • The modifications take effect only after you apply the parameter template to DB instances. For details, see Applying a Parameter Template.
    • The change history page displays only the modifications of the last seven days.
    +
    +
    +

+
+

Modifying Parameters of a Specified DB Instance

  1. Log in to the GeminiDB console.
  2. In the navigation pane on the left, choose Instance Management. On the displayed page, click the target DB instance.
  3. In the navigation pane on the left, choose Parameters. On the displayed page, modify parameters as required.

    • To save the modifications, click Save.
    • To cancel the modifications, click Cancel.
    • To preview the modifications, click Preview.
    +

  4. After parameters are modified, click Change History to view parameter modification details.

    For how to view parameter modification details, see Viewing Parameter Change History.

    After you modify instance parameters, the modifications immediately take effect for the instance.

    +
    Check the value in the Effective upon Restart column.
    • If the value is Yes and the DB instance status on the Instance Management page is Pending restart, you must restart the DB instance for the modifications to take effect.
    • If the value is No, the modifications take effect immediately.
    +
    +
    +
    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_05_0004.html b/docs/geminidb/umn/nosql_05_0004.html new file mode 100644 index 00000000..80e03d0b --- /dev/null +++ b/docs/geminidb/umn/nosql_05_0004.html @@ -0,0 +1,22 @@ + + +

Exporting a Parameter Template

+

Scenarios

  • You can export a parameter template of a DB instance for future use. To learn how to apply the exported parameter template to a DB instance, refer to section Applying a Parameter Template.
  • You can export the parameter template details (parameter names, values, and descriptions) of a DB instance to a CSV file for review and analysis.
+
+

Procedure

  1. Log in to the GaussDB NoSQL console.
  2. In the navigation pane on the left, choose Instance Management. On the displayed page, click the target DB instance.
  3. In the navigation pane on the left, choose Parameters. On the Parameters tab, above the parameter list, click Export.

    • Parameter Template: You can export the parameters of the DB instance to a template for future use.
      In the displayed dialog box, configure required details and click OK.
      • The template name can be up to 64 characters long. It can contain only uppercase letters, lowercase letters, numbers, hyphens (-), underscores (_), and periods (.).
      • The template description consists of a maximum of 256 characters and cannot include line breaks or the following special characters: >!<"&'=
      +
      +
      +

      After the parameter template is exported, a new template is generated in the list on the Parameter Template Management page.

      +
    • File: You can export the parameter template information (parameter names, values, and descriptions) of a DB instance to a CSV file for viewing and analysis.
      In the displayed dialog box, enter the file name and click OK.

      The file name must start with a letter and consist of 4 to 81 characters. It can contain only letters, numbers, hyphens (-), and underscores (_).

      +
      +
      +
    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_05_0005.html b/docs/geminidb/umn/nosql_05_0005.html new file mode 100644 index 00000000..f83e6975 --- /dev/null +++ b/docs/geminidb/umn/nosql_05_0005.html @@ -0,0 +1,18 @@ + + +

Comparing Parameter Templates

+

Scenarios

This section guides you on how to compare two parameter templates of the same node type and DB engine version to know their current settings.

+
+

Comparing Parameter Templates

  1. Log in to the GaussDB NoSQL console.
  2. In the navigation pane on the left, click Parameter Template Management.
  3. In the parameter template list, locate the parameter template that you created and click Compare in the Operation column.
  4. In the displayed dialog box, select a parameter template that shares the same DB engine with the template 1 and click OK.

    • If their settings are different, the parameter names and values of both parameter templates are displayed.
    • If their settings are the same, no data is displayed.
    +

+
+

Comparing Parameter Templates of a Specified Instance

  1. Log in to the GaussDB NoSQL console.
  2. In the navigation pane on the left, choose Instance Management.
  3. On the Instance Management page, click the target DB instance.
  4. In the navigation pane on the left, choose Parameters. On the Parameters tab, click Compare above the parameter list.
  5. In the displayed dialog box, select a parameter template to be compared and click OK.

    • If their settings are different, the parameter names and values of both parameter templates are displayed.
    • If their settings are the same, no data is displayed.
    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_05_0006.html b/docs/geminidb/umn/nosql_05_0006.html new file mode 100644 index 00000000..72373618 --- /dev/null +++ b/docs/geminidb/umn/nosql_05_0006.html @@ -0,0 +1,18 @@ + + +

Replicating a Parameter Template

+

Scenarios

You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values from that template in a new parameter template, you can replicate that parameter template. You can also export the parameter template to generate a new parameter template for future use.

+

Default parameter templates cannot be replicated, but you can create parameter templates based on the default templates provided.

+
+

Procedure

  1. Log in to the GaussDB NoSQL console.
  2. In the navigation pane on the left, click Parameter Template Management.
  3. On the Parameter Template Management page, click the Custom Templates tab. Locate the target parameter template and click Replicate in the Operation column.

    Alternatively, click the target DB instance on the Instance Management page. On the Parameters page, click Export to generate a new parameter template for future use.

    +

  4. In the displayed dialog box, enter the parameter template name and description and click OK.

    • The template name can be up to 64 characters long. It can contain only uppercase letters, lowercase letters, numbers, hyphens (-), underscores (_), and periods (.).
    • The description contains a maximum of 256 characters and cannot include line breaks or the following special characters: >!<"&'=
    +

    After the parameter template is replicated, a new template is generated in the list on the Parameter Template Management page.

    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_05_0007.html b/docs/geminidb/umn/nosql_05_0007.html new file mode 100644 index 00000000..b32519dc --- /dev/null +++ b/docs/geminidb/umn/nosql_05_0007.html @@ -0,0 +1,14 @@ + + +

Resetting a Parameter Template

+

Scenarios

You can reset all parameters in a custom parameter template to their default settings.

+
+

Procedure

  1. Log in to the GaussDB NoSQL console.
  2. In the navigation pane on the left, click Parameter Template Management.
  3. On the Parameter Template Management page, click the Custom Templates tab. Locate the target parameter template and choose More > Reset in the Operation column.
  4. Click Yes to reset the parameter template.
+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_05_0008.html b/docs/geminidb/umn/nosql_05_0008.html new file mode 100644 index 00000000..5352ecb4 --- /dev/null +++ b/docs/geminidb/umn/nosql_05_0008.html @@ -0,0 +1,17 @@ + + +

Applying a Parameter Template

+

Scenarios

Modifications to parameters in a custom parameter template take effect for DB instances only after you have applied the template to the target DB instances.

+
+

Procedure

  1. Log in to the GaussDB NoSQL console.
  2. In the navigation pane on the left, click Parameter Template Management.
  3. On the Parameter Template Management page, apply a default template or a custom template to a target DB instance:

    • To apply a default template, click Default Templates, locate the target parameter template, and in the Operation column, click Apply.
    • To apply a custom template, click Custom Templates, locate the target parameter template, and in the Operation column, choose More > Apply.
    +

    A parameter template can be applied to one or more DB instances.

    +

  4. In the displayed dialog box, select one or more DB instances to which the parameter template will be applied and click OK.

    After a parameter template is applied, you can view its application records.

    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_05_0009.html b/docs/geminidb/umn/nosql_05_0009.html new file mode 100644 index 00000000..36676a9a --- /dev/null +++ b/docs/geminidb/umn/nosql_05_0009.html @@ -0,0 +1,15 @@ + + +

Viewing Application Records of a Parameter Template

+

Scenarios

You can view the application records of a parameter template.

+
+

Procedure

  1. Log in to the GaussDB NoSQL console.
  2. In the navigation pane on the left, click Parameter Template Management.
  3. On the Parameter Template Management page, locate the target parameter template and choose More > View Application Record in the Operation column.

    You can view the name or ID of the DB instance that the parameter template applies to, as well as the application status, application time, and the causes of any failures that have occurred.

    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_05_0010.html b/docs/geminidb/umn/nosql_05_0010.html new file mode 100644 index 00000000..111230f1 --- /dev/null +++ b/docs/geminidb/umn/nosql_05_0010.html @@ -0,0 +1,15 @@ + + +

Modifying a Parameter Template Description

+

Scenarios

You can modify the description of a custom parameter template if needed.

+
+

Procedure

  1. Log in to the GaussDB NoSQL console.
  2. In the navigation pane on the left, click Parameter Template Management.
  3. On the Parameter Template Management page, click the Custom Templates tab. Locate the target parameter template and click in the Description column.
  4. Enter a new description. You can click to submit or to cancel the modification.

    • After you submit the modification, you can view the new description in the Description column on the Parameter Template Management page.
    • The description can include up to 256 characters but cannot contain the following special characters: >!<"&'=
    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_05_0011.html b/docs/geminidb/umn/nosql_05_0011.html new file mode 100644 index 00000000..fc1e4db7 --- /dev/null +++ b/docs/geminidb/umn/nosql_05_0011.html @@ -0,0 +1,16 @@ + + +

Deleting a Parameter Template

+

Scenarios

You can delete a custom parameter template that is no longer in use.

+
  • Deleted templates cannot be recovered, so exercise caution when performing this operation.
  • Default parameter templates cannot be deleted.
+
+
+

Procedure

  1. Log in to the GaussDB NoSQL console.
  2. In the navigation pane on the left, click Parameter Template Management.
  3. On the Parameter Template Management page, click Custom Templates. Locate the parameter template you wish to delete and choose More > Delete in the Operation column.
  4. Click Yes to delete the parameter template.
+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_05_0012.html b/docs/geminidb/umn/nosql_05_0012.html new file mode 100644 index 00000000..4c4b5ac5 --- /dev/null +++ b/docs/geminidb/umn/nosql_05_0012.html @@ -0,0 +1,19 @@ + + +

Viewing Parameter Change History

+

Scenarios

You can view the change history of a parameter template.

+

In a newly exported or created parameter template, change history is left blank.

+
+
+

Viewing Change History of a Custom Parameter Template

  1. Log in to the GaussDB NoSQL console.
  2. In the navigation pane on the left, choose Parameter Template Management. On the Custom Templates page, click the parameter template you wish to view.
  3. In the navigation pane on the left, choose Change History. Then, view the parameter name, original parameter value, new parameter value, modification status, and modification time.

    You can apply the parameter template to DB instances as required by referring to section Applying a Parameter Template.

    +

+
+

Viewing Change History of DB Instance Parameters

  1. Log in to the GaussDB NoSQL console.
  2. On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
  3. In the navigation pane on the left, click Parameters. On the Change History tab, view the parameter name, original parameter value, new parameter value, modification status, and modification time.
+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_06_0001.html b/docs/geminidb/umn/nosql_06_0001.html new file mode 100644 index 00000000..c4b09f58 --- /dev/null +++ b/docs/geminidb/umn/nosql_06_0001.html @@ -0,0 +1,39 @@ + + +

Instance Connection Methods

+

You can connect to a GeminiDB Cassandra DB instance over a private or public network.

+ +
+ + + + + + + + + + + + + +
Table 1 Connection methods

Method

+

Scenario

+

Description

+

Private network

+

A private IP address is provided by default.

+

If your applications are deployed on an ECS that is in the same region and VPC as your DB instance, connect to the DB instance using a private IP address.

+

High security and performance

+

Public network

+

If you cannot access a DB instance using a private IP address, bind an EIP to an ECS and connect the ECS to the instance using the EIP.

+

+
  • Low security
  • For faster transmission and improved security, migrate your applications to an ECS that is in the same subnet as your instance and use a private IP address to access the instance.
+
+
+
+ + diff --git a/docs/geminidb/umn/nosql_cassandra_0001.html b/docs/geminidb/umn/nosql_cassandra_0001.html new file mode 100644 index 00000000..81574acb --- /dev/null +++ b/docs/geminidb/umn/nosql_cassandra_0001.html @@ -0,0 +1,23 @@ + + +

Working with GeminiDB Cassandra API

+
+ + diff --git a/docs/geminidb/umn/nosql_increase_nodes.html b/docs/geminidb/umn/nosql_increase_nodes.html new file mode 100644 index 00000000..260ad2d0 --- /dev/null +++ b/docs/geminidb/umn/nosql_increase_nodes.html @@ -0,0 +1,19 @@ + + +

Adding Nodes

+

Scenarios

This section describes how to add nodes to a DB instance to suit your service requirements. You can also delete a node as required. For details, see Deleting Nodes.

+
+

Precautions

  • Adding nodes may lead to the decrease of operations per second (OPS). You are advised to perform this operation during off-peak hours.
  • You can only add nodes when the instance status is Available or Checking restoration.
  • A DB instance cannot be deleted when one or more nodes are being added.
+
+

Procedure

  1. Log in to the GaussDB NoSQL console.
  2. On the Instance Management page, click the DB instance you wish to add nodes for.
  3. In the Node Information area on the Basic Information page, click Add Node.
  4. Specify Add Nodes and click Next.

    • By default, the specifications of new nodes are the same as the DB instance and cannot be modified.
    • Up to 200 nodes can be added to a GeminiDB Cassandra instance.
    +

  5. On the displayed page, confirm the node configuration details.

    • If you need to modify your settings, click Previous to go back to the page where you specify details.
    • If you do not need to modify your settings, click Submit to add the nodes.
    +

  6. View the result of adding nodes.

    • The status of the DB instance in the instance list is Adding node.
    • After the nodes are added, the DB instance status becomes Available.
    • Click the DB instance name. In the Node Information area on the Basic Information page, view the information about the new nodes.
    +

+
+
+
+
+
Parent topic: DB Instance Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_increase_storage.html b/docs/geminidb/umn/nosql_increase_storage.html new file mode 100644 index 00000000..de266133 --- /dev/null +++ b/docs/geminidb/umn/nosql_increase_storage.html @@ -0,0 +1,20 @@ + + +

Scaling Up Storage Space

+

Scenarios

This section describes how to scale up the storage space of a DB instance to suit your service requirements.

+

During the scale-up process, the DB instance will not restart, and your services will not be interrupted.

+
+

Precautions

Storage space can only be scaled up. It cannot be scaled down.

+
+

Procedure

  1. Log in to the GeminiDB console.
  2. On the Instance Management page, click the DB instance you wish to scale up.
  3. In the Storage Space area on the Basic Information page, click Scale.
  4. On the displayed page, specify the new storage capacity and click Next.

    Select at least 1 GB each time you scale up the storage, and the storage size must be an integer.

    +

  5. On the displayed page, confirm the storage space.

    • If you need to modify your settings, click Previous to go back to the page where you specify details.
    • If you do not need to modify your settings, click Submit to scale up the storage space.
    +

  6. Check the scale-up result.

    • The status of the DB instance in the instance list is Scaling up.
    • After the scale up is completed, the DB instance status becomes Available.
    • In the Storage Space area on the Basic Information page, check whether the scale up was successful.
    +

+
+
+
+
+
Parent topic: DB Instance Management
+
+
+ diff --git a/docs/geminidb/umn/nosql_introduction.html b/docs/geminidb/umn/nosql_introduction.html new file mode 100644 index 00000000..205ccbc9 --- /dev/null +++ b/docs/geminidb/umn/nosql_introduction.html @@ -0,0 +1,14 @@ + + +

What Is GeminiDB?

+

GeminiDB is a distributed, multi-model NoSQL database service with decoupled compute and storage architecture. This high availability database is secure and scalable, can be deployed, backed up, or restored quickly, and includes monitoring and alarm management. GeminiDB Cassandra API is compatible with mainstream NoSQL APIs of Cassandra and provides high-performance read/write at low costs, making it well suited to IoT, meteorology, Internet, and gaming applications.

+

GeminiDB Cassandra API

GeminiDB Cassandra API is a cloud-native NoSQL database compatible with Cassandra. It supports Cassandra Query Language (CQL), which gives you SQL-like syntax. It is secure, reliable, scalable, and easy to manage and can provide high read/write performance.

+
  • A multi-layer security system, including a VPC, subnet, security group, and SSL, ensures database security and user privacy. You can deploy nodes across three AZs and create backups or restore data with ease. The distributed architecture provides superlative fault tolerance (N-1 reliability).
  • GeminiDB Cassandra API gives you 3 times the performance of the open source version. Data can be written to this high availability database 24/7, and with automated load balancing and elastic scaling, you always have all the performance you need.
  • The distributed architecture, with decoupled compute and storage, means that compute nodes can be expanded in minutes, and storage capacity can be scaled up in seconds without affecting your services.
  • On the visualized instance management console, you can create or delete instances in just a few clicks. Backup and restoration, configuring alarms or adding nodes is just as easy.
+
+
+
+
+
Parent topic: Introduction
+
+
+ diff --git a/docs/geminidb/umn/nosql_login.html b/docs/geminidb/umn/nosql_login.html new file mode 100644 index 00000000..030ac4c3 --- /dev/null +++ b/docs/geminidb/umn/nosql_login.html @@ -0,0 +1,10 @@ + + +

Logging In to the GeminiDB Console

+

Prerequisites

You have registered a cloud account for logging in to the GeminiDB management console.

+

If you do not have a cloud account, register an account at the official website. After the registration, your account has permissions to access GeminiDB, as well as all other cloud services.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. In the service list, choose Database > GeminiDB.
+
+
+ diff --git a/docs/geminidb/umn/nosql_user_guide.html b/docs/geminidb/umn/nosql_user_guide.html new file mode 100644 index 00000000..10d61d75 --- /dev/null +++ b/docs/geminidb/umn/nosql_user_guide.html @@ -0,0 +1,25 @@ + + +

Introduction

+
+ + diff --git a/docs/geminidb/umn/public_sys-resources/caution_3.0-en-us.png b/docs/geminidb/umn/public_sys-resources/caution_3.0-en-us.png new file mode 100644 index 0000000000000000000000000000000000000000..60f60762138fe7d98fa081415cf26a4943897779 GIT binary patch literal 2752 zcmV;x3P1IUP)pPa!Eu%RCwC$n`u~-F-BFk{0Y@>jH&Wt02T)4n7aXBssVicB` zOX`JaF2{q_2~&#?rkP8$id|Xfs23G(+0lTGT0tnFxgZFMIx;xG$R>Lr2ng2sFhB=q zSd{Td_5QEx{V+WDJooe7@Bg{)|8u`XpV~`~ZvvYTAfN{@5<(zAAd&!qNCE^R2@oI< zNq|5k0e^NPrRGdyW8`F%MH7XH|3P8=s2${2dg49z003YAM?%tm1!4=85P2aZJs3WS zG6CT8kCv0C(eT;v!9vu9jP&3oZEw^8HmnQ6+clMCL4mv(zK?)Ob8&M#`$%sr@v0v& z@zoUHs-n619H>uFER~Aj==ntk06q~XtAWrX`-(7l=)GLjQP?!@q z{@ZTZw0`amLgo~4vvd&0Pxryp)QHy>ob2%4P9)V*SX4zr!(BuoQ>IK9!d&k>z1cqI z{8L;})njUE#LIJj>h%6Q^ZVF{wB;i;Qi+5h9}NJn%x@raKm6;fW+Fl#T`67idLh|4 zu~b$4-1hhHTVfMtV@>p)0G=3ns@?Zq+;oGKv z*YE#+n>`1!`TpdYF4yhs&w)&meoVo}#+v$ur`WVKNyq<%YnFsZMC$eXSc!Bf$)AMeNOrxm z98up?0IbZ4d1uoLyuSG}0{xcY?H+G%68SDpqp0{6ZmtR(?ChBNKk$ZxK&chd%Fub9B!C3$z*oSdfKP$^R+Au*=jW--Q5@}8T8wOFz(A> z+jPJi0CSN!@M}8~J+m~H+qJd0$mL8L?}^W38D?fiTvJtZ_QG{CGOx1j!^2co2eNIY zE_th}e&*28WCEs4)4Ngh`F*TJs&5jrEg}J*$>Ry|NTs@Q5S4XS*jiLGYupV!l}OmJ zCkyWg!}|T(8zmGK-@ggmTpXX4Lzd^H6d8Ibpk8+o_km$bMW>TS}&FY)P96F+{d%+84 z0FbR#^Wj0eUL$0WrHtk7-A3#N4!~oiv))WDwoq|!rza!b-MC#_%g6i5bZq+f?}v+A z&dvOM*6oz`?o(Suoq{*R_pvM}5O;^mT)Ww?Z7fftAwAED0FP9BCXZ)ZL<03qVuSdN zP8xtRONCq}V{LHL13e@F7rC5Q7nL%1)>HuEPG%TvZ9T=8(JF40lp-DCMCkm>9oo4$ zp2gbI0)X_(**fDB#*QLr-bCyM4&cnWE2QR3>%BzUvd0>L#Q|n|$1Tk60kC$33wat1 zyP`b|;`hpR?G6;%TDEA7?qPdG5~XG3DCEwFEmXV^*atUP1r?Q*Z6tf#C@HG~z|7R7 z%W^bSHmKdEz8|Y+XCNKoj5;@$;5Eqx+bjkplCo$bd!u65ur3Iht+xK#S>J1CGr+PQ z0C$JWZS8>kO3xnquB&Tk(E(-;v|eN5zDOk!LKaKgc6D>}Jxa^U*&dP9D~M#(l4Wdd zEW5NF>oE`jQ&SV}G+O8_@4Ge+!`aD+oB8?teVaq?BU0GA1xO_l=1nQrAx&+WdOB8S#d?X;+5%{W zL%$q0tP5gqR7{WS^|&#ETLM_$tqfODr{F@Wvh7$L9&xbkIv%IZL`G<~%z?=et2Z8l(~lTRu|vXblrbH{CQq;M*jC6P7 zAFJjO7P_e26);09x-VYJYSS8{M>uNB=$!_=`UBu*VJQICR{ab{qy@7TIM~}!cc+es zuSRv+yK8E024LzW_fF?DH>qIv7JK9}8Okgb+deq(_=yx1KZZPwhLE7)i2By(j4ulc zZ0X+G=!}W_*0i+)j$M5C6#K-`Q^PI#NC$_uZf2|)Q-QCDmtJxjn1b~m%uQ)q7k*!v<@zee~^S^yy8n;SIv9h!z@F~L` zuV;E)#MIP`TP3BWq~-E)te=ie;#EKP>`x<4qruHp!K;f(yPS8hZ8~d0reR}ajZ`A( z(HeW)kgTXvuy(`eEDH)`tWfsw@ySLcm z71)pX#Is~7?MOOfjY2*gfad0Vq-SPfE=p#UyBs4UBW!G}*%&$+h}RorbCI@}bUZGD z(D`DX7<2A;EnO+wSMkI5S3ZiysJKOPz zXHjNr`1+U~!-i@z2TQevhO_F+9anqo4qDp6*s z{^#^#iMhy}=wm-XjcU;ayd~S zjKa+^{((2(%#||Kxw$%iyNf&$A}5<97d+PwF{vJcqF5t}K17 zWA47SPe$ba7&NE7d;EGLztWTQN_%qi?{fFvpbejgc;mTn%wk=QtX`o_PVsJpPg-Jv~RCwC$oO@7HS02Ydnp$REOA{(Mow8*Mm>A3h9MeO=6 zYU>mmT}9emv9DQm*RJeXc5T5Q!v0 zB$5b`NFqdtL=w?OklwC|&JB*_kR*g*P1STeQY~6uB+{*;B2i1mw!HxCh>m7?uX_kB zZW668hPGS7cBvYGjjLu-T2{ta(MHkoqDQ**khXqXE?M&}B*qkwZb{|!wVV0PLl1U( zh|@k2Pt@e8KI2W7%cc| zO7%;oh!GEaKI?~$MKHY5t{0Ps=^60OI`;KR@k?HRh+XkChOueL!}QpzFXL=(zz|LUxf|B{Fmxd{EXn6tyV1mZmG!*PMf2b20p#%- z`o8%ZVfQ~su(20?SHHrs3D0@S-1|flxSZIlFT0HsqCq!dAXirJ4@lTnmkYTz0`t-t zoL%_-P1mIvW2W1<$B}7tG*?~Z^s+@a=y&VTO-%?Gh7Jy#@{?>}D?H+5hs1sBQ0R>W z$rPxPB0JS9by>2#BO!*;vNGmn#B$c!n|>2>7?JiN4?lg9=9Ul^WTvn;zkmZNJ#I@f zXfLYayW|WUHCNr9F<}t$c#W4#+=3U8s&%wF9keEQnyx}+}N<*(D-{;R$ zaL&lM{`n*i9mMK`CvfP6+g4qiUbYCAy$P8{NBGDGJ>#mRNP+|zE_)NFmo4(hwYIv@ zj4}Jw)#_@YXz^U^wkl+5Ed$yU@(x$pVxcJ-ZmXBjPZHcyBPNTQ@jT3znFTMzB|S?h0gxfpz6m)AA4I1f{{Z$&2y zk3ciVjBaWI{dcTHs?p)HH*sm#raQmUz>fucJ<0Wt1$&7Yo{Gv8hdf^6w-o?Tw&YWcsTM+dBoLi8 zm#bgrQM3K5ud%~av^tvIiFi|^-&R4OlHQ{uGz@8In6F1rD1F94&As{c8*2bi=#8{A z)KIlQhtnC$?tCJxvO0({nRs+qm1oR!Z=IKnF2v^f{N$t{)~t1Vv2?ngNK$nuGEKO< zzf@ihKvc#!1ci#0h8lzrHSz1+9!LmL<7})$rq&Yk)GWTA^F~0u-~E0TNjvu-Q)}t} z)&}+s8s@*>B2&1%Q%tPac=st8NJG2{;%siGF;7#NJH;& zhtmrs6i)v0ou4BeO^#u2egO+IQwUR3_$5wT3!n{#&@*Jsx3K<;Tq+W^T~4H!KR$~@ zu5|Zlat{Mw&iD(0QiW8dAv|#;hS6ylMyC;;I1(Y)o!@mEZ@FnQU-ZJ$IBKhr$d&Y3 z@~n?c&GxedN!C@{=B92P%iuKA4P5P zF?T5M7UQl=?_?r5^a9HdpCWnaAVwy9ACNdxCO+iz-A9L25o0p3%IfG+5=G4$jjDT3 z_rX_P#9mZ`W{jEERu|5u25kR1=sC=`>*|qQT57FGWQv;}!j;wgsVgZ&P^ySbnS#<_ z@{wsQcZWQgM(3rkuisR2@ddhKm zm>y`QU}}cvFx#%9zncRR0f}5m+=3T>`k`rb(CYH78vp)0Ee*BEwGqTVll7BY1|4qD zR@y0eaw?7*EAlWsiJLyTGjpW6UP@ltw4HQIDv2=#er2YNQnNeHL|TgfF7e2O?@1my zh~&SD2{!g(;QB4N?2Xi&J%utn0;xtv zkRbctK7@An=2gu(9Ra)bZS!9G@?)aLPe-neAnxr2otkuaibwkB-UtAuk5dGci8mbQ zpHD?%2tDKXzEY@Rj-@xHWo6{`Gk44bDS}ZNOehT|CG6gP2Ggpt~a%lW$PyZ(R zi8N$tEzX8o&aMocNSD04oR)@K6nZ1(%xk%iRHX^nOsp#j+)(^s?wgdX$fl*dQ#vN{kQBLN_&` z(}>jJm$ns&TBh$jOxAo08KVLl?;k50S@-!F7S4`i=H$SR@bCXNvu5pPHYX!BHAMhH=PbZLgf2GrXYPBlYfJrz}; z)`4zn0@|b`lo3(5nj87CARk+Pp-;mw(B7`!W7{6u*6MHG>-993S9MlnGP}b>T0X$Q z*4=p=+dA4SslE}Gg;&WhtYpG)6U!Ea29!H%?ahd^54+^o0V28#9s2{xQ^UKnb$1>s zUY^}9i2&9v4QJu(xOPbdVAh?wt?d92zi^J^&vgoySb1+qmmi0B}` Z`Y-il7nw201!5QImN;7^FeRDuvlieQm$nqSgH2#ST^0cx)=Dn zcnY!FJo_HPt-fVW+YdiB+UT#;6V;vF(d}+cR@IeV(d8~pF{?8>qtl(5 z-l&f3hz@sXMqTY}N84?I)T&mtqU9C|*g%8DFx{Fx6Im5iuF|X}%dCt_S87;LjI4+X zS7=Dl>numvWx_9&xPzYqFMxz!h@dKJnV+WiNj6zrg25Bat1rHX34YcM&(@mM25EsKp^s$!A zn#VD|u6s{$op5YkSDD^r^tisfo6%**9APOOq(ypevUm*eg627JCCoz;t2Wm=9wHzA zIZpn)d?D?0K6~e%(5n+Y{``IW_383vZ~ype`|Z!iyVvi|9^OBm{E(}2>Xh(M9J1dY2CIYT07X)PL*D{uoU3SWSe zM5)Z@cZj(9E!*Rn@%yj8UtL_@?zGcisVAyCyQACPnyjiTyQ0fonqpRGc1EW=HN8j060m^=i($GodnU3fs$8X6OO{y~m9EsVpcq*Z6|T^b zqSslDvde-aqopiG$tAYJ8Zb!15?a()3^veUF{}|ZIT4x8)aYX^Swx02G;(1<(UEpq zsD~82sYp46Jp6zr)7XK2NT3kbfI%9Tw8DeMU;_=7#;04Wd;7XW>CRXi!yzvnE_|I|r wZ*w5M>1_7SKcT}DJ@4vn|M>OS_UPly>%-H_{r>p;)5Xs}-+pgDf7s~DJ6{D>Q~&?~ literal 0 HcmV?d00001 diff --git a/docs/geminidb/umn/public_sys-resources/icon-arrowdn.gif b/docs/geminidb/umn/public_sys-resources/icon-arrowdn.gif new file mode 100644 index 0000000000000000000000000000000000000000..379428032932289326e52c2772bd90ba3d88b906 GIT binary patch literal 1887 zcmZ?wbhEHbCgqow z*eU^C3h_d20o>TUVm+{T^pf*)^(zt!^bPe4Kwg3=^!3HBG&dKny0|1L72#g21{a4^ z7NqJ2r55Lx7A2Jm>Ih`8X1|p zSh~8p7&*iAy5uL9=BDPA!1Sgd^t#~G3rY&P1wfl!Qj0RnQd8WD@^clyUbf1_?G{Iz z=0WwQ;C71>PQCg-$LND17Ac}(Lcr7mV#1RxkONQnsd>QEUIa|mjQ{`r{qy_R&mZ5v zef{$J)5j0*-@SeF`qj%9&!0Vg^7zri2lwyYy>t84%^TORUA=Po(!~qs&z(JU`qar2 z$B!L7a`@1}1N-;w-Lrew&K=vgZQZhY)5ZeMTG_VdAT{+S(zE> zX{jm6Nr?&Zaj`McQIQehVWA3>*p!%p5Wn0u7E$th{n6D>ft^YU5&dnB%c=(a~-RV>2EO25SIA CZ-yWM literal 0 HcmV?d00001 diff --git a/docs/geminidb/umn/public_sys-resources/icon-arrowrt.gif b/docs/geminidb/umn/public_sys-resources/icon-arrowrt.gif new file mode 100644 index 0000000000000000000000000000000000000000..6aaaa11c23e919c4798d7dcd2b1ae98dd35dd316 GIT binary patch literal 1890 zcmZ?wbhEHb7yetOgf{ zR2HP_2c;J0mlh?b0+lO+tSYc_E=o--$uA1Y&(DE{Vn9ZINq%ugeu08>u$h8JcxGNo zetEGbSiP^Wm1kaYNn&1ds;7&s63_&_%*+%k11Cod14Ab>6ALqQLqk^=3j-5FHzP|& zBUd9gQwvj9m|mCsATTyHM;rzL?XHK6w zdE)r7qel)OI(T6JzP)>P@7lRz`?jrHHgDRvVg0(bYgVsXxnlXUrArnsTDV~Tyt#8` z&zd=7`n0K2CQq6;p}()Ur@O1OqrI)QrMaoGp}wxRrn;)KqP(oMq`0WCAU`iRCp#-M zBRwrOB{?ZEAwDiPCORrIB0MZKBseHAz~9f;$J@)(!`;o*#o5Wx!QRf+#@fo#!raW% z#MsEtKwnQ+M_Wr%LtRZ(MOjHvL0(Q)Mp{ZzLR?H#L|8~rfS-?-hntI&gPo0)g_((w zfkE*n3y@@B&;b#k`jUY|nSq%>!ec`MLnAA%oR7zc2TpB#@>)|YCO&lN;uMU!b7Eqm H1A{dHTIz>f literal 0 HcmV?d00001 diff --git a/docs/geminidb/umn/public_sys-resources/icon-caution.gif b/docs/geminidb/umn/public_sys-resources/icon-caution.gif new file mode 100644 index 0000000000000000000000000000000000000000..079c79b263f4b48089f3b3256154c73e7699593f GIT binary patch literal 1086 zcmW+#YfRQ<6hA3LZMyP?V}KhnEtF{Q4vGxS52AozEVM85nq$#%tv8gRF!3GhgM?_) zd5Luv3SKrXFTGCpn$y>EMGZQ&sWI^~+e%qWysRPK%BSD+f4-fabAGq;|Cf|4nO{(o zMH%#n$oXf^sdM5SJ4e1UbEeM389O82RCB6M#VI=_KP%=$orn{5LVlIau{svV?3jS$ z$Q-F7am0>L02|Q2!ZN1G^Z2J`V#a3VX;G<~iYc3tSAnLeiI}hnc~O{UH5OwwCTPT} zks65+8-W$70S3`f30dfY7}$UY7M95y@-?2QvMPChphYF3!YbtLLIs*E%B)Oq4^fy^ z5+zoGJ>&tI*hU=i4-s$()c}KNsKh9AfEd_-1{V3`d>b_$i;xcz{y>Y0S(uP3>_P>a zLM((Fku(B;E{r2+xJ8u612VCVIG_oJ;Sj0;2GQ7rEa(6+umMf}M1C4=)Odu8AxQWG zEh;Aearj(=d;4Z^LLYN*6+asU?Nbl3^Q%D|{s@6Xj}(aZHwkoj-~bw*1FnSd;0aX! zUW<-TPD&b;6s;@zw7K~4mF9cDuK&BQ;b_N-Cj%R=CnEjde9%~1kk}vYY^@mTTNm%F z?mbrf*~d#iX;?ITDf(MHQdK;&p(ek&e9qe?*&A0E)mG(1s`J*pn^#ttId4vCXjV$j zj464u)2F9Q$V#0!dHk4(FDB#D&wP^f0*q1)G?4!%Xe>;ROD~Oee-}xfJUd+aa_0AK zFP$vgR2te>+%}b$hVw&Ni`yT>F5LNRM@_utk68Piwi5??BLBpCcb8mx|3c*1x!xZJ zKU!7(#h8s(^x)5*w=Z0K{=a9#qeoHU|0&%MiU0rr literal 0 HcmV?d00001 diff --git a/docs/geminidb/umn/public_sys-resources/icon-danger.gif b/docs/geminidb/umn/public_sys-resources/icon-danger.gif new file mode 100644 index 0000000000000000000000000000000000000000..079c79b263f4b48089f3b3256154c73e7699593f GIT binary patch literal 1086 zcmW+#YfRQ<6hA3LZMyP?V}KhnEtF{Q4vGxS52AozEVM85nq$#%tv8gRF!3GhgM?_) zd5Luv3SKrXFTGCpn$y>EMGZQ&sWI^~+e%qWysRPK%BSD+f4-fabAGq;|Cf|4nO{(o zMH%#n$oXf^sdM5SJ4e1UbEeM389O82RCB6M#VI=_KP%=$orn{5LVlIau{svV?3jS$ z$Q-F7am0>L02|Q2!ZN1G^Z2J`V#a3VX;G<~iYc3tSAnLeiI}hnc~O{UH5OwwCTPT} zks65+8-W$70S3`f30dfY7}$UY7M95y@-?2QvMPChphYF3!YbtLLIs*E%B)Oq4^fy^ z5+zoGJ>&tI*hU=i4-s$()c}KNsKh9AfEd_-1{V3`d>b_$i;xcz{y>Y0S(uP3>_P>a zLM((Fku(B;E{r2+xJ8u612VCVIG_oJ;Sj0;2GQ7rEa(6+umMf}M1C4=)Odu8AxQWG zEh;Aearj(=d;4Z^LLYN*6+asU?Nbl3^Q%D|{s@6Xj}(aZHwkoj-~bw*1FnSd;0aX! zUW<-TPD&b;6s;@zw7K~4mF9cDuK&BQ;b_N-Cj%R=CnEjde9%~1kk}vYY^@mTTNm%F z?mbrf*~d#iX;?ITDf(MHQdK;&p(ek&e9qe?*&A0E)mG(1s`J*pn^#ttId4vCXjV$j zj464u)2F9Q$V#0!dHk4(FDB#D&wP^f0*q1)G?4!%Xe>;ROD~Oee-}xfJUd+aa_0AK zFP$vgR2te>+%}b$hVw&Ni`yT>F5LNRM@_utk68Piwi5??BLBpCcb8mx|3c*1x!xZJ zKU!7(#h8s(^x)5*w=Z0K{=a9#qeoHU|0&%MiU0rr literal 0 HcmV?d00001 diff --git a/docs/geminidb/umn/public_sys-resources/icon-huawei.gif b/docs/geminidb/umn/public_sys-resources/icon-huawei.gif new file mode 100644 index 0000000000000000000000000000000000000000..a31d60f895af919d33855217ca02daf4093136d7 GIT binary patch literal 2767 zcmV;=3NZCYNk%w1VaEV40Oo%H*MEWRpQG)+!RUX6`tR@RDKg4%aM+KK_}}3B+S#H2 z0rt<*_Nl4!k%7|y4fwgY^uNNg00pZ61NzIz@q2NyEiLIHE%S?g^NEbfKt%9!YU?yQ z^qh&+U}WbD8{q&E?Mq9<013DN2H5})@N8$u01CkX3Fs9f^{bWHKuGLFOZ1kS)=*aD z01@p=RQ9r(>pemK^YiUeQPU6`>94W!hk53YleQ2Q>_SB7aCr2fj@; z@a|n&?qX^0W?<$J9`9pa@`8Bj9VzWnT-qQk!yqQl01W6ECF?mp=LHtlFgo|Iv-PHs z+HiFBprpVM7yReuz5od5zrUyu5$;)5@{gDATVup9HOgRO=U{2(0u;*t3-Hg-^OuGE z;N9vkH}7a--=Co1Fg#jPP{_r^k&B8kCM0%mZLFxL@$v9KH8SJk;?~sDy0^BTnwV%{ zUQ9zlgnfM9U}wHiP~xwz{`dCrZ*%7e7{X9d^{Afom69VE761SLA^8LW004ggEC2ui z0LK6@000O7fPaF6goTEOh>41ejE#|lU+C8$A-c{-jb1$W_sAqMbtN`+RZ#DGFR(dnrcRE3N%f+!F;*y7(oOv#1FPiAwy#YP$z^Q7U<_8BLs** zMSr>_(L`oBgxA?;z>x3<218xJ;14v)$l4!yG&Wrk_I1$$0*;vB$B=#`at4uppizkb zkVG1Zq>_oSkp_`a7SaZiZXiMjk!m2q29j+I!X%PpB5B5wO%5V}2qJRl1%NsHfxr&G z=|x^!dAKu_41Dql0y7LOA)N(0dcZ^rABfh-m_;ITB$a5UdB~$fR(S{-NTzYfmPE#Z z$dyBCddM0`(jjJQ3^=Hu0tmpW@WUTds1O^W zCv4aPqTVsWsFRSgiX^m^Dgr8zYZ&qdl5-rgEs}5?A_tOhoSJHxtD4)WAg_+-CV)r$ z0l^3=PP3O0e*huI221P;!@n>Lqi=>hZs_9&J75vyw2nR*>5$YWnFy(5hH1$EwSHt- z2&Y^c@+FZL3&QBRsy<8z0uiv;-+usJMIdJZ34w1G1pu?}1~|L$M-&7rk*ppEBV3oW z3{UE?w2~S^sl>(pGc6ETQUgwH}48uSiAJo0SA(QX~FrGzYvq#TC0!EGVmk{K=`YG64w z*^4Iq2N`U_YT26(@Ww;iA6V3a3V*n8!U;+!QN-&o;K;WJKrdVR4kI*6wC0H)Z8+gt z8&Y|wjA~4X(?lBohtwStGUbrnULHxSg=BE{y8s3-FXI^_2KJ7l* zPUi?^WVSHxgDj2s;6@ith~r!?-DM$hAerqT7$efv{s0FgQSEnvBN74j@P$DTKnvHC zONlTuy0+nk2Y*mO7rMX%Cg?#AOZY{0)h5f{2_S7&W;+3~xxv`varUz{DmpF%e^`f&wJ41t9(5fhwzv1mBc| z0U*EuBM2j%FvtTFnh*k5Fk|UZh`TZf2my8Qf){uKMUtgzel#qE{5o z`T+owlz=pEZ~#HrKnm`Pm2OzzgBhrem4EOJodD;_ahfxf-U+}Ak|4_v=x&*|EE67c z`G;K+;#whFp8pE*u^;}yhknQwAj5S;KNQlDsB)$xqbbb@AmI*w_<|O)xy2+vAOLDp z8yCVE${l#|oS_`S5dZ^$BP4;HUf`rVX&Fy4%@bn4W7;49dBA^~$q>dQOL?8kgXdnQvsYOnDfj24t0FVQ&GJsH);SXF0X(+eq z0|aFCq_QkQ2uwgnL@)|$U)!lnaS7A<-BO9Aav~Zq1~shtZ;*=2X&Qw1zoAY~flO_x zQ=i%a0w5p*o16;-5U|cJ{sE(En`{^}sx}@hzy~=vDN0qkRui}|sdcU4U8UAnL&&wT ze-NTA73oVe_41G0LefE{2Z>hMA+geI=u@QtfIkQT2`1nUZwBxt8^}v-apD4J9dHDm z*r2j$RqI-*fP_WBP>(V+WFp;)q}Cd-rO7KqPBT@AJ}!>D^n`Dbmde!NE;eOIpur!e zT2+HIfiCh&!V$`4~D_J+6+9nP?X4+~QQR3Nd6O>yUni+~O!R{(#Yf%|x3 zV=w6V57*_SoPYe_5lO*{ETyMCXS!kI{qmTJC@5?}tYs@Z`Gp%cnIOCjX8WdC#YjMN znOSg%0i?hn3uwZe>0DG@D8{!L9NVviU!0?6(AlZm;xWpa)Zb-c0Yf<`I615cvC$3@R|NPo+jf8PRu)%BB zhMd<%u5!4#ylXATHvtr$a54bk<~ZL%26n#lMX-S98Gr)LaZUq?L;OQXHv|E!0Ok|h zR|}ywHv~IJbrC%JsW+&2(zpJHJ2XAlm3#yMI(PL)OS76>Px~OC`E{mNAnK0zLI%qI z)ZlJG?RXaiuD@;tv`>NzH;90J?Vk56!rvj>leB^Xjy?$j0N@7pwE`ImPx(Jo;pSvu Vyd?-=a{xfJ@}LjB=qC{f06U7uGEOJ7jGVWt0R$WZ8s=je-u*DOe&kq9}!i z4KyN^y7WUtlMt&*F%bljtRbDEJamX6>@vOi{twMwE+=kqtJr%yLc-a1j}Z>-)`f9GBO%WDhy=L0>5=eLzUZCI?G``P_| zXl3c^-NL}=_M!Zh=FG7pU)shB58htr9~}O0uVbq2_rt-Fxv_(zmmdB7)lfOReyZ>D zrqum6#Z#+~moGM-oS4Ziby(A(@4L&ZrWcR4wV&_mTide#$G4kXKF-|cGp}2pJe$2t GE&l)<3Z_>8 literal 0 HcmV?d00001 diff --git a/docs/geminidb/umn/public_sys-resources/icon-notice.gif b/docs/geminidb/umn/public_sys-resources/icon-notice.gif new file mode 100644 index 0000000000000000000000000000000000000000..409070650a49518feb1624c624d814c3bfa63d2e GIT binary patch literal 962 zcmb7D&r8&C5S<{wSd_qn6)U)w5LOaRh!N}_*49lD)S!dZp@M<3gPIX|@UR9-fz+X3 zAaT9)OY{xZtO-;RC85Vab;JEUNIMS5f^r$7-e%-XK`j{0+N$CsgpRd6B1wp z8dw-cH^rU^H4`&7qgabf)l^K`l!66{q9$U(CKRO5%W5pfY)s&YQ6n`HBR0ZTum%`N zgC%I8hQ+`JG_WvCAt-W$sIn@BKCDG1qQWW^a=`*c7G+i@s0S(ZDv1&+K_2`7O-#cM z=m!ZX1Z#kSG+3e)Jg^wpfCd(Yb5TZ)U=a!DwsG z)Z`|1ejMK4ap%CHj;%+>T6=D++5I=uBbQ$fZ48cf{hV1}9&Njl-I}i7e0#6Hdug@s zsr-57_=gLr&9Ros$k}}M>tJ77=hEJ}iPaZ%8|P+gUbS|Oj}5I{|5nZZc)C1$e*Rj` d`09hYXJ4M@PhCx)dHK8WZo1*|*q+^V@*ncduk8Q; literal 0 HcmV?d00001 diff --git a/docs/geminidb/umn/public_sys-resources/icon-tip.gif b/docs/geminidb/umn/public_sys-resources/icon-tip.gif new file mode 100644 index 0000000000000000000000000000000000000000..c47bae05c9fd17c02a851d96cfac67bf194498d8 GIT binary patch literal 879 zcmchWKWmj?48@OdDOZPr)a61!OE4yGD)salg#|^Ix$qIEF#uk)V>D{95e^!2r`i+9t# zTMu5YtUcd+@#gp0tDE;9ug>oLIzL$6dOx4-t#2PKExu1KulwoYeD?Os#mVO%AMWih HO|EMGZQ&sWI^~+e%qWysRPK%BSD+f4-fabAGq;|Cf|4nO{(o zMH%#n$oXf^sdM5SJ4e1UbEeM389O82RCB6M#VI=_KP%=$orn{5LVlIau{svV?3jS$ z$Q-F7am0>L02|Q2!ZN1G^Z2J`V#a3VX;G<~iYc3tSAnLeiI}hnc~O{UH5OwwCTPT} zks65+8-W$70S3`f30dfY7}$UY7M95y@-?2QvMPChphYF3!YbtLLIs*E%B)Oq4^fy^ z5+zoGJ>&tI*hU=i4-s$()c}KNsKh9AfEd_-1{V3`d>b_$i;xcz{y>Y0S(uP3>_P>a zLM((Fku(B;E{r2+xJ8u612VCVIG_oJ;Sj0;2GQ7rEa(6+umMf}M1C4=)Odu8AxQWG zEh;Aearj(=d;4Z^LLYN*6+asU?Nbl3^Q%D|{s@6Xj}(aZHwkoj-~bw*1FnSd;0aX! zUW<-TPD&b;6s;@zw7K~4mF9cDuK&BQ;b_N-Cj%R=CnEjde9%~1kk}vYY^@mTTNm%F z?mbrf*~d#iX;?ITDf(MHQdK;&p(ek&e9qe?*&A0E)mG(1s`J*pn^#ttId4vCXjV$j zj464u)2F9Q$V#0!dHk4(FDB#D&wP^f0*q1)G?4!%Xe>;ROD~Oee-}xfJUd+aa_0AK zFP$vgR2te>+%}b$hVw&Ni`yT>F5LNRM@_utk68Piwi5??BLBpCcb8mx|3c*1x!xZJ zKU!7(#h8s(^x)5*w=Z0K{=a9#qeoHU|0&%MiU0rr literal 0 HcmV?d00001 diff --git a/docs/geminidb/umn/public_sys-resources/note_3.0-en-us.png b/docs/geminidb/umn/public_sys-resources/note_3.0-en-us.png new file mode 100644 index 0000000000000000000000000000000000000000..57a0e1f53377b28fd80ceb393b035f8d9b8b392a GIT binary patch literal 1080 zcmV-81jqY{P)pI>PbXFRA}Dqnq7z+RTRg6r`*v5D@IBmL~4s5$SN3-f`YICkrqS^ z3O*?4J{4psT?>Nv;P$DA4|YKmeJd1v=!+{-P(e)MT23E4 zfpM5g?!;YNyXOywggfWv-aG#}pA%7499KRz`7Lmw98Q!I<#3`LPLvbnaH1TQ5UMEG zlVk_b1{y%CK&5Na8Kh~iV1CQyHSIUD=$Ui|Y1(mW{t2nlnW!hpqTT3)%#9tQ2@Hwc z4!jG@4brq%Pm%+`OlEvYXy4{GY5awd{We?gCpulWuT{Z9`oN)jk~9ZtI#ba@Tm#IC$eXI#i?GB7 z@C|Siuxi7{ffK+jzyrW_z5t&id2Xi{7fGOZ7RUNhF z=`q(YYu4B2zr}fA1-My6UW~A&C(H`Z0J{sqLLYb>ST?)$UTJH~j4 z)U5D`kx~@HyTBjADBwh`9UcOHGnaO3gx+o=^sFTdqcDs&7cD!S1Y1R9DJQENmMBXi zUX68u7SqPL=oS0?tDydiCJNY=lMCxo@cxg;Iw&H0tZv&cB5#jSkGc8v45{4-xAi@+ zH#c^6Llb3aTk2cp0#8`%*2*ZSb3DivIwje71|rV*JnwHI2e{V0 z?L}VtT_k|}D>qFKHz^_)cUMxtxkDBWXzz2D1oirfKkqs5Z>m~O`i+$JJR1>-NN>fsG-Q5hHbmeou}1??2@ zp;^{uvz{qy3k557pH|h^|K(Paf~;?wS^K(J)S`9Ki+p;|vZBS3*BostG+QG&8PgN& z=@C2h$ubuxBJTs&=XH#%UFPZrh=oAMNN{DPG_uReuDWcPESRPGOKD;{Otwcu3X@*QY`k0+@}-e yxT4{IZgHXpLI!Q!9RCwC$n{8}UWfaGMW8J;IUE8&LY1fUhGLTVa3!QBW+ZA*L=y*M3rfr5il?z?dJZieJ#47>M$@*mD4$1ecadv1qsU1#wR$;qu4Bmh4yS`Hi)ReG=4*#e zajgEV5YlLPaKTMvrW)|6L6Y@JtlU|tX}9u@d<^;|8a!TJ`kRn8mKIZX-z)%<^+`jn z738I}>P{CwooQ#@mc8ItdHsQ6rsk%O$iLY)*x7Zcj%}lwEK@`-=;otzSyX+&p9{kzQYbgSF@Q=2Qy+?#VW0=Vy|cYT&lQ@%;A2YQ{hH z9%ov+34{hBa~SnWOw39F;7p5`9$z4G?cJ)An*I*rb~&khdI=d8h1SkK)If-j5C2TB z8p4%r<<^31tR|Tw4Xs1QHMjMk20}yD8f4p%dXd_$me9Z-SWPlj8%nUOe;>LpUUAI& z1+$nxI~Q3>q`9q!{1-nPlEMa4o@e_SGSdvCrzn))J%_ut?ipfIn4e4CD=Pq4zT@D? zqk$|@wV{L*qfBG7mtFghv-Lntl$pcnz~kwNI)BUSUuvgmQEXp5=UThz?DmmjlsW$V z@)3#dyh6UbBYa%QD%n4gom-Glu20@0My{Xs3VRpaU9=0QxbJP-J)Pz^`?kOW30Tn z@ufYqb@gL4$<)8N0%S?kG%v#(IqvH7UvcW1v+a@N8!}9Baks0-uUUYP1beE1+)Q)S zUobczB2ql)J>S90pM1~e2X4k70q-59;@Rj(Ixc6Ok_Z$V@dbE+GNTrV;HlFQ=lRMeN%CX^J*|inqrfX$fdWuECU& zYE~#M%8xCgqI||*N`--7Xw)BgEZ#bB0-qYhW>q--LhLmBU*r0E*5+4PP+l2n2}rtV z_qXh+#jl32SrvAyo2R)OD=o_BoyYIMW>x6y_Tety7r)3^eF8`TK$3KP{`eA2F}YpN zxa|~0YP$+*PB&3e-M~W&UFbFHknL5q%yVT?GB=Ox3?p^VEh7*N@$03nevU0%RA*Qe zy8Bd~e78Ejsl=~x+vYF$e)B!#In3BC3Kw>)rNi4F>6}lnndnzTghB(1f9&nZP({}9 z<_Y#X?@5R5*rUdbm zZ9zPQB)-@t_#f`t1VTsxAtZr72uUD>BoIOp2q6gsLP&yt3mvdY+y=oIIs7M?<}pwN SX0_=60000pR4oO5oRCwC$oPSW0cb>;zfj~mSuLKN~5E4Ot2?$cVg1bfW*MgmP zwXW?r{^)GC>z&@*cI;fk*-bA_)*65J|u{1o1b~sY9&bgB!&FtPHC|>aqwkEf8t)sIV8a zy`l<$fv1-750WZjrUfER4&AbBw(qRs>9xxN*j}-pMOzA)VQ&y-TOiWJv9nVR=-IGB zL`2wi-rWtmJCwYrnwtLq8d^@54N{_E#qc2?d98FYUt9|#UM6CV$k!5{lNa$(kHW9K zOnWgQF}`S;)25`yKPRE0?;CL9SWtgolNa zrBRX}cY`9==aUXcrj$ru%8RMoU&9MOUrS=-S8j{+s~_?FOYc$kFAFFdtPOe${ncT1 z{rLzf8V%)-DtvDE-wqmRZ8xCPYAJtA<5`q3{Ob`bjZO9Fv|84D-@EVUj$Eg)=@6=E z@#L*7W|qCq*W!xRyz%}azq+NTrIL{{k5{wx9=$&5QFz+d73A@UdA>TE#nbrfC(X3B z8(6fZ$fI-Rsms(id`VH^EXwBij$f6Q%6pGy`z7a}PPWn1d>+=6lPmX*Un}gz{Ox!v z`WEl|IDGSOT%3|O*G+D{rZj7N?NbLjt(LV5jh=HqnA?U z8mrYxV|c!gMHxe<(a3REu1^wRwhaLAc*#s3m+W-80O+~e%iEuijH}D~<%`(7rkqDg z=TTZb2dmA-!DFZR&9(3NZQo)rQeiLlD~pmzCp{Of?FN2YE1pz;Th3*$^KYlnx3rR& zpyJ_&X0!Fj%Xs-G%lKj0eA3fW0mv9`|G!E9Ya~lJ`Po^X-Lx2KsErPD79Hj+q@gxm z{Mlkoes-3_qjQ5Er(oy{Vq#*j+H8D$A>2z=-J3vbyTSAQk0(04Sglr))oM!O z`@CekFQuSwX(c8)8igX37UN~i63tz8`Qdaso8^aiGyN2A&2A@2H4T81Uv&6wZ?)Oj zTifJC_?WSn~TqB!^hRw*Ad4e7J~3dFR=6G>_8NdnsMLm)G}au^{sd3m-1x^#e`g zF3xz6x-4W*PjVBduE|UGaf6#U1-aQM6tVOT40?@sz!ZhmW+Or>@p4-Zv4VXye+OW7 zc`+d&A#@sz?CP00DZSLHz!o=IttMHmrqgKTxg*zuw$4$Jkz99N$7-|j*1@mnmSvB7 zO=WExR-28GkWk(!3-#*~r7p`oB}P+1qz`Ts(`7QTajn||ZQHTiBYWfRy#Q?8q@~Mb zVxKK9=<$~3C;^C&N<0(TEz8Di8z5P&W>aZ0G0`z}8jaMCZ=XmZMWeykeJP-en=p}N zQr=uQi}bWqx=f~kF79@>Z|%3c-P>cc{E{db1WhEfM8nqKxzqiJbY}y$o33o;>9xz* zUQson-E%k07oQ_VqoK9kz%l!D08Tq~beT*pkf^ z4(PF1`pDEKqI8;gLeoonS}MI}GariryW_5*SlZ-;)XNs|tUjBo*UTssvHYZ9)NlJ) z_By_sKLd-UZ%SNTyvWApvWyA2xbs6QE?m4wVctygq*taq{STT*zcFP3uVFUm(>{fsnY2byQucdN-4PVNGGwlltbpW(qxPn=t@v%0g@(xlo8u|zNX$;Tj zL~B0)v5_*bKys%(iq>`m{r&x%z8c|~$V_b_07FC0fQu6zCMG;gOl!LV)wFmvmglg* zQ8R8V_1h;>NK8;+wORT1?%)IOmvT)cCaCB#nI=Te-qC2U(nDqS8QysRkk_a3)aCm} zq?bP(MW@xWs-)NJe1QW+nJCD~rsrxeyN)(b$ZgNE*Rg8RgYE+A=jS;+kQlUu{`Kmaq-Zo)ZC1bW*X)SP zB&*dleDyW$_FJ1<>AK4LvN>#CQ_ki!<><89`&-$rmo4DrXSKYw{l~;e&UndGvBREY zdBhz%GStSin-=p=&;OneA1vbs!`1gR{w#YP5zt^s>sevrzAfWX_)uEYBrfUeBv}`^qrW~HGWfKsmsDE zOQ*BGS9P4Wl`RF-yksh zy60FsZNNwVNWragKrk^ve!4rg7mMBdVO@#NOI{X#h4i#kMn*=saPcD79Zs)o<((?G z^^%CiJRf_Q&GJKDpRI*9vNO}^G#dG@zTAL%%&<4GWyKs~qN8as7&HHba-?wT_zK+{<0Kls4ZZI zwt3@|Ua`~d_}Me*beT*+rNNJ9iBKqFak*TiXf(`~bowmtSfv`EtT@NZqPks+{a z5!JMKPh8~>&n-znE|bw}==6Ccb0>biz(smmDwnVHu}ZPEji zzW45)-n*6<0^#-C^K4pKLR_4Zk&zJ&pEynB{*O3#>=aGS=dlkuD9FiX!}lillwCC0 z-?hEgU&dQ|syVhNu(h$+M6CR&JD%9FMMGhZ|GG+tIg8TOds)AHF)ylW?m2UG5RP)x z8t}<_w^)soA(EXPo(HDmU3a@1zaW|JX{#K%Oq;}A@|fXl@p%B-Ez8C%ib2W{N|$?g zkBuLwVmzkfoqdk=b-RuZv4S>9rqBJ{sq>hQNv?~2V>^dfL1TD6U)yB#J4cCkVw)_#|7FHwSFj&?I903+@}Q+?E}XNC3Nz=CN(ZZjK1= zEPb1Cd{SB4f1Go_kMMN4^{(v-b4ID$mhCyd8&;L{vU{JFmp>h)qCi-YZ!0DoBh||m zu>a`Eo9X_gaoZQ>jE+kpfEdXop55erJD^6gL|Bn;DJE=@t~lNAw+sx9aIkUClqxYW z=nj}aF^#ZTB`nJSYa&gTT1nApc>bmLzAo-6E0000