From 09841dde95eba49d0818911091b7e5b0b32eebd5 Mon Sep 17 00:00:00 2001 From: "Wang , Deng Ke" Date: Tue, 12 Sep 2023 08:34:38 +0000 Subject: [PATCH] nosql umn 20230210 version Reviewed-by: Drobnak, David Co-authored-by: Wang , Deng Ke Co-committed-by: Wang , Deng Ke --- docs/gaussdb_nosql/umn/ALL_META.TXT.json | 72 +++++-- docs/gaussdb_nosql/umn/CLASS.TXT.json | 84 +++++--- ...9.png => en-us_image_0000001092058816.png} | Bin ...8.png => en-us_image_0000001092187298.png} | Bin ...0.png => en-us_image_0000001092187390.png} | Bin ...7.png => en-us_image_0000001092346948.png} | Bin ...0.png => en-us_image_0000001092347040.png} | Bin ...2.png => en-us_image_0000001092506886.png} | Bin ...1.png => en-us_image_0000001138926357.png} | Bin ...7.png => en-us_image_0000001139129107.png} | Bin ...9.png => en-us_image_0000001139129187.png} | Bin ...3.png => en-us_image_0000001139129197.png} | Bin ...9.png => en-us_image_0000001139224537.png} | Bin ...1.png => en-us_image_0000001139224555.png} | Bin ...9.png => en-us_image_0000001139224635.png} | Bin .../umn/en-us_image_0108820738.png | Bin 0 -> 248 bytes .../umn/en-us_image_0160430768.png | Bin 0 -> 1004 bytes docs/gaussdb_nosql/umn/nosql_01_0006.html | 16 +- docs/gaussdb_nosql/umn/nosql_02_0002.html | 6 +- docs/gaussdb_nosql/umn/nosql_02_0004.html | 6 +- docs/gaussdb_nosql/umn/nosql_02_0005.html | 6 +- docs/gaussdb_nosql/umn/nosql_02_0009.html | 6 +- docs/gaussdb_nosql/umn/nosql_02_0010.html | 6 +- docs/gaussdb_nosql/umn/nosql_02_0011.html | 2 +- docs/gaussdb_nosql/umn/nosql_03_0004.html | 5 +- docs/gaussdb_nosql/umn/nosql_03_0007.html | 6 +- docs/gaussdb_nosql/umn/nosql_03_0008.html | 4 +- docs/gaussdb_nosql/umn/nosql_03_0009.html | 4 +- docs/gaussdb_nosql/umn/nosql_03_0013.html | 2 +- docs/gaussdb_nosql/umn/nosql_03_0014.html | 16 +- docs/gaussdb_nosql/umn/nosql_03_0015.html | 2 +- docs/gaussdb_nosql/umn/nosql_03_0017.html | 199 ++++++++++++++++++ docs/gaussdb_nosql/umn/nosql_03_0018.html | 19 ++ docs/gaussdb_nosql/umn/nosql_03_0019.html | 18 ++ docs/gaussdb_nosql/umn/nosql_03_0025.html | 6 +- .../umn/nosql_04_change_history.html | 44 ++-- docs/gaussdb_nosql/umn/nosql_05_0010.html | 2 +- docs/gaussdb_nosql/umn/nosql_06_0001.html | 8 +- .../umn/nosql_cassandra_0001.html | 2 + docs/gaussdb_nosql/umn/nosql_faq_0010.html | 11 + docs/gaussdb_nosql/umn/nosql_faq_0103.html | 2 + .../gaussdb_nosql/umn/nosql_introduction.html | 7 +- docs/gaussdb_nosql/umn/nosql_login.html | 2 +- 43 files changed, 444 insertions(+), 119 deletions(-) rename docs/gaussdb_nosql/umn/{en-us_image_0000001158064899.png => en-us_image_0000001092058816.png} (100%) rename docs/gaussdb_nosql/umn/{en-us_image_0000001111385068.png => en-us_image_0000001092187298.png} (100%) rename docs/gaussdb_nosql/umn/{en-us_image_0000001111544820.png => en-us_image_0000001092187390.png} (100%) rename docs/gaussdb_nosql/umn/{en-us_image_0000001158104877.png => en-us_image_0000001092346948.png} (100%) rename docs/gaussdb_nosql/umn/{en-us_image_0000001111544870.png => en-us_image_0000001092347040.png} (100%) rename docs/gaussdb_nosql/umn/{en-us_image_0000001111385042.png => en-us_image_0000001092506886.png} (100%) rename docs/gaussdb_nosql/umn/{en-us_image_0000001158104851.png => en-us_image_0000001138926357.png} (100%) rename docs/gaussdb_nosql/umn/{en-us_image_0000001158064897.png => en-us_image_0000001139129107.png} (100%) rename docs/gaussdb_nosql/umn/{en-us_image_0000001158104939.png => en-us_image_0000001139129187.png} (100%) rename docs/gaussdb_nosql/umn/{en-us_image_0000001158064793.png => en-us_image_0000001139129197.png} (100%) rename docs/gaussdb_nosql/umn/{en-us_image_0000001158064769.png => en-us_image_0000001139224537.png} (100%) rename docs/gaussdb_nosql/umn/{en-us_image_0000001158064901.png => en-us_image_0000001139224555.png} (100%) rename docs/gaussdb_nosql/umn/{en-us_image_0000001158104849.png => en-us_image_0000001139224635.png} (100%) create mode 100644 docs/gaussdb_nosql/umn/en-us_image_0108820738.png create mode 100644 docs/gaussdb_nosql/umn/en-us_image_0160430768.png create mode 100644 docs/gaussdb_nosql/umn/nosql_03_0017.html create mode 100644 docs/gaussdb_nosql/umn/nosql_03_0018.html create mode 100644 docs/gaussdb_nosql/umn/nosql_03_0019.html create mode 100644 docs/gaussdb_nosql/umn/nosql_faq_0010.html diff --git a/docs/gaussdb_nosql/umn/ALL_META.TXT.json b/docs/gaussdb_nosql/umn/ALL_META.TXT.json index ffee02d08..07cbf6d5f 100644 --- a/docs/gaussdb_nosql/umn/ALL_META.TXT.json +++ b/docs/gaussdb_nosql/umn/ALL_META.TXT.json @@ -153,7 +153,7 @@ "uri":"nosql_06_0001.html", "product_code":"nosql", "code":"16", - "des":"GaussDB(for Cassandra) supports databases connections over public and private networks.", + "des":"You can connect to a GaussDB(for Cassandra) DB instance over a private or public network.", "doc_type":"usermanual", "kw":"Instance Connection Methods,Getting Started with GaussDB(for Cassandra),User Guide", "title":"Instance Connection Methods", @@ -333,7 +333,7 @@ "uri":"nosql_03_0004.html", "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 DB ", + "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", "title":"Deleting Nodes", @@ -383,7 +383,7 @@ "uri":"nosql_03_0007.html", "product_code":"nosql", "code":"39", - "des":"GaussDB NoSQL 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 ", + "des":"GaussDB(for Cassandra) creates automated backups to ensure data reliability. If a database or table is maliciously or accidentally deleted, backups can help you ensure yo", "doc_type":"usermanual", "kw":"automated backups,Managing Automated Backups,Backups and Restorations,User Guide", "title":"Managing Automated Backups", @@ -393,7 +393,7 @@ "uri":"nosql_03_0008.html", "product_code":"nosql", "code":"40", - "des":"To ensure data reliability, GaussDB NoSQL allows you to manually back up DB instances whose status is Available. If a database or table is deleted, maliciously or acciden", + "des":"To ensure data reliability, GaussDB(for Cassandra) 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", "title":"Managing Manual Backups", @@ -403,7 +403,7 @@ "uri":"nosql_03_0009.html", "product_code":"nosql", "code":"41", - "des":"GaussDB NoSQL helps 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 & Restora", + "des":"GaussDB(for Cassandra) 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", "title":"Restoring Data to a New DB Instance", @@ -570,11 +570,41 @@ "githuburl":"" }, { - "uri":"nosql_03_0027.html", + "uri":"nosql_03_0019.html", "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", + "title":"Auditing", + "githuburl":"" + }, + { + "uri":"nosql_03_0017.html", + "product_code":"nosql", + "code":"59", + "des":"With CTS, you can record operations associated with GaussDB NoSQL for later query, audit, and backtrack operations.Table 1 lists the key operations that can be recorded b", + "doc_type":"usermanual", + "kw":"Key Operations Recorded by CTS,Auditing,User Guide", + "title":"Key Operations Recorded by CTS", + "githuburl":"" + }, + { + "uri":"nosql_03_0018.html", + "product_code":"nosql", + "code":"60", + "des":"After CTS is enabled, the tracker starts recording operations on cloud resources. Operation records for the last 7 days are stored on the CTS console.This section describ", + "doc_type":"usermanual", + "kw":"Querying Traces,Auditing,User Guide", + "title":"Querying Traces", + "githuburl":"" + }, + { + "uri":"nosql_03_0027.html", + "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", "title":"Log Management", "githuburl":"" @@ -582,7 +612,7 @@ { "uri":"nosql_03_0028.html", "product_code":"nosql", - "code":"59", + "code":"62", "des":"GaussDB NoSQL 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 s", "doc_type":"usermanual", "kw":"Slow Query Logs,Log Management,User Guide", @@ -592,7 +622,7 @@ { "uri":"nosql_faq_0001.html", "product_code":"nosql", - "code":"60", + "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":"FAQs", @@ -602,7 +632,7 @@ { "uri":"nosql_faq_0101.html", "product_code":"nosql", - "code":"61", + "code":"64", "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":"Product Consulting", @@ -612,7 +642,7 @@ { "uri":"nosql_faq_0002.html", "product_code":"nosql", - "code":"62", + "code":"65", "des":"DB instances' operating systems (OSs) are invisible to you. Your applications can only access a database through an IP address and port.The backup files stored in OBS and", "doc_type":"usermanual", "kw":"What Should I Pay Attention to When Using GaussDB NoSQL?,Product Consulting,User Guide", @@ -622,7 +652,7 @@ { "uri":"nosql_faq_0003.html", "product_code":"nosql", - "code":"63", + "code":"66", "des":"Formula for a GaussDB NoSQL instance availability:DB instance availability = (1 – Failure duration/Total service duration) × 100%.The failure duration refers to the total", "doc_type":"usermanual", "kw":"What Is Instance Availability?,Product Consulting,User Guide", @@ -632,7 +662,7 @@ { "uri":"nosql_faq_0103.html", "product_code":"nosql", - "code":"64", + "code":"67", "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":"Database Connection", @@ -642,17 +672,27 @@ { "uri":"nosql_faq_0006.html", "product_code":"nosql", - "code":"65", + "code":"68", "des":"To create an ECS, see Elastic Cloud Server User Guide.The ECS to be created must be in the same VPC with the GaussDB NoSQL instance to which it connects.Configure the sec", "doc_type":"usermanual", "kw":"How Can I Create and Connect to an ECS?,Database Connection,User Guide", "title":"How Can I Create and Connect to an ECS?", "githuburl":"" }, + { + "uri":"nosql_faq_0010.html", + "product_code":"nosql", + "code":"69", + "des":"After a GaussDB NoSQL instance is created, its VPC cannot be changed. To change the VPC of an instance, you can restore a full backup of the instance to a new instance in", + "doc_type":"usermanual", + "kw":"Can I Change the VPC of a GaussDB NoSQL Instance After It Is Created,Database Connection,User Guide", + "title":"Can I Change the VPC of a GaussDB NoSQL Instance After It Is Created", + "githuburl":"" + }, { "uri":"nosql_faq_0104.html", "product_code":"nosql", - "code":"66", + "code":"70", "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":"Backup and Restoration", @@ -662,7 +702,7 @@ { "uri":"nosql_faq_0007.html", "product_code":"nosql", - "code":"67", + "code":"71", "des":"You can define the retention period of an automated backup. There is no limit on the manual backup retention period. You can delete manual backups as needed.", "doc_type":"usermanual", "kw":"How Long Does an Instance Store Backup Data?,Backup and Restoration,User Guide", @@ -672,7 +712,7 @@ { "uri":"nosql_04_change_history.html", "product_code":"nosql", - "code":"68", + "code":"72", "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", diff --git a/docs/gaussdb_nosql/umn/CLASS.TXT.json b/docs/gaussdb_nosql/umn/CLASS.TXT.json index de190433a..281974e7d 100644 --- a/docs/gaussdb_nosql/umn/CLASS.TXT.json +++ b/docs/gaussdb_nosql/umn/CLASS.TXT.json @@ -135,7 +135,7 @@ "code":"15" }, { - "desc":"GaussDB(for Cassandra) supports databases connections over public and private networks.", + "desc":"You can connect to a GaussDB(for Cassandra) DB instance over a private or public network.", "product_code":"nosql", "title":"Instance Connection Methods", "uri":"nosql_06_0001.html", @@ -297,7 +297,7 @@ "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 DB ", + "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", @@ -342,7 +342,7 @@ "code":"38" }, { - "desc":"GaussDB NoSQL 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 ", + "desc":"GaussDB(for Cassandra) creates automated backups to ensure data reliability. If a database or table is maliciously or accidentally deleted, backups can help you ensure yo", "product_code":"nosql", "title":"Managing Automated Backups", "uri":"nosql_03_0007.html", @@ -351,7 +351,7 @@ "code":"39" }, { - "desc":"To ensure data reliability, GaussDB NoSQL allows you to manually back up DB instances whose status is Available. If a database or table is deleted, maliciously or acciden", + "desc":"To ensure data reliability, GaussDB(for Cassandra) 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", @@ -360,7 +360,7 @@ "code":"40" }, { - "desc":"GaussDB NoSQL helps 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 & Restora", + "desc":"GaussDB(for Cassandra) 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", @@ -512,6 +512,33 @@ "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 GaussDB NoSQL for later query, audit, and backtrack operations.Table 1 lists the key operations that can be recorded b", + "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, the tracker starts recording operations on cloud resources. Operation records for the last 7 days are stored on the CTS console.This section describ", + "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", @@ -519,7 +546,7 @@ "uri":"nosql_03_0027.html", "doc_type":"usermanual", "p_code":"26", - "code":"58" + "code":"61" }, { "desc":"GaussDB NoSQL 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 s", @@ -527,8 +554,8 @@ "title":"Slow Query Logs", "uri":"nosql_03_0028.html", "doc_type":"usermanual", - "p_code":"58", - "code":"59" + "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.", @@ -537,7 +564,7 @@ "uri":"nosql_faq_0001.html", "doc_type":"usermanual", "p_code":"", - "code":"60" + "code":"63" }, { "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.", @@ -545,8 +572,8 @@ "title":"Product Consulting", "uri":"nosql_faq_0101.html", "doc_type":"usermanual", - "p_code":"60", - "code":"61" + "p_code":"63", + "code":"64" }, { "desc":"DB instances' operating systems (OSs) are invisible to you. Your applications can only access a database through an IP address and port.The backup files stored in OBS and", @@ -554,8 +581,8 @@ "title":"What Should I Pay Attention to When Using GaussDB NoSQL?", "uri":"nosql_faq_0002.html", "doc_type":"usermanual", - "p_code":"61", - "code":"62" + "p_code":"64", + "code":"65" }, { "desc":"Formula for a GaussDB NoSQL instance availability:DB instance availability = (1 – Failure duration/Total service duration) × 100%.The failure duration refers to the total", @@ -563,8 +590,8 @@ "title":"What Is Instance Availability?", "uri":"nosql_faq_0003.html", "doc_type":"usermanual", - "p_code":"61", - "code":"63" + "p_code":"64", + "code":"66" }, { "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.", @@ -572,8 +599,8 @@ "title":"Database Connection", "uri":"nosql_faq_0103.html", "doc_type":"usermanual", - "p_code":"60", - "code":"64" + "p_code":"63", + "code":"67" }, { "desc":"To create an ECS, see Elastic Cloud Server User Guide.The ECS to be created must be in the same VPC with the GaussDB NoSQL instance to which it connects.Configure the sec", @@ -581,8 +608,17 @@ "title":"How Can I Create and Connect to an ECS?", "uri":"nosql_faq_0006.html", "doc_type":"usermanual", - "p_code":"64", - "code":"65" + "p_code":"67", + "code":"68" + }, + { + "desc":"After a GaussDB NoSQL instance is created, its VPC cannot be changed. To change the VPC of an instance, you can restore a full backup of the instance to a new instance in", + "product_code":"nosql", + "title":"Can I Change the VPC of a GaussDB NoSQL Instance After It Is Created", + "uri":"nosql_faq_0010.html", + "doc_type":"usermanual", + "p_code":"67", + "code":"69" }, { "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.", @@ -590,8 +626,8 @@ "title":"Backup and Restoration", "uri":"nosql_faq_0104.html", "doc_type":"usermanual", - "p_code":"60", - "code":"66" + "p_code":"63", + "code":"70" }, { "desc":"You can define the retention period of an automated backup. There is no limit on the manual backup retention period. You can delete manual backups as needed.", @@ -599,8 +635,8 @@ "title":"How Long Does an Instance Store Backup Data?", "uri":"nosql_faq_0007.html", "doc_type":"usermanual", - "p_code":"66", - "code":"67" + "p_code":"70", + "code":"71" }, { "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.", @@ -609,6 +645,6 @@ "uri":"nosql_04_change_history.html", "doc_type":"usermanual", "p_code":"", - "code":"68" + "code":"72" } ] \ No newline at end of file diff --git a/docs/gaussdb_nosql/umn/en-us_image_0000001158064899.png b/docs/gaussdb_nosql/umn/en-us_image_0000001092058816.png similarity index 100% rename from docs/gaussdb_nosql/umn/en-us_image_0000001158064899.png rename to docs/gaussdb_nosql/umn/en-us_image_0000001092058816.png diff --git a/docs/gaussdb_nosql/umn/en-us_image_0000001111385068.png b/docs/gaussdb_nosql/umn/en-us_image_0000001092187298.png similarity index 100% rename from docs/gaussdb_nosql/umn/en-us_image_0000001111385068.png rename to docs/gaussdb_nosql/umn/en-us_image_0000001092187298.png diff --git a/docs/gaussdb_nosql/umn/en-us_image_0000001111544820.png b/docs/gaussdb_nosql/umn/en-us_image_0000001092187390.png similarity index 100% rename from docs/gaussdb_nosql/umn/en-us_image_0000001111544820.png rename to docs/gaussdb_nosql/umn/en-us_image_0000001092187390.png diff --git a/docs/gaussdb_nosql/umn/en-us_image_0000001158104877.png b/docs/gaussdb_nosql/umn/en-us_image_0000001092346948.png similarity index 100% rename from docs/gaussdb_nosql/umn/en-us_image_0000001158104877.png rename to docs/gaussdb_nosql/umn/en-us_image_0000001092346948.png diff --git a/docs/gaussdb_nosql/umn/en-us_image_0000001111544870.png b/docs/gaussdb_nosql/umn/en-us_image_0000001092347040.png similarity index 100% rename from docs/gaussdb_nosql/umn/en-us_image_0000001111544870.png rename to docs/gaussdb_nosql/umn/en-us_image_0000001092347040.png diff --git a/docs/gaussdb_nosql/umn/en-us_image_0000001111385042.png b/docs/gaussdb_nosql/umn/en-us_image_0000001092506886.png similarity index 100% rename from docs/gaussdb_nosql/umn/en-us_image_0000001111385042.png rename to docs/gaussdb_nosql/umn/en-us_image_0000001092506886.png diff --git a/docs/gaussdb_nosql/umn/en-us_image_0000001158104851.png b/docs/gaussdb_nosql/umn/en-us_image_0000001138926357.png similarity index 100% rename from docs/gaussdb_nosql/umn/en-us_image_0000001158104851.png rename to docs/gaussdb_nosql/umn/en-us_image_0000001138926357.png diff --git a/docs/gaussdb_nosql/umn/en-us_image_0000001158064897.png b/docs/gaussdb_nosql/umn/en-us_image_0000001139129107.png similarity index 100% rename from docs/gaussdb_nosql/umn/en-us_image_0000001158064897.png rename to docs/gaussdb_nosql/umn/en-us_image_0000001139129107.png diff --git a/docs/gaussdb_nosql/umn/en-us_image_0000001158104939.png b/docs/gaussdb_nosql/umn/en-us_image_0000001139129187.png similarity index 100% rename from docs/gaussdb_nosql/umn/en-us_image_0000001158104939.png rename to docs/gaussdb_nosql/umn/en-us_image_0000001139129187.png diff --git a/docs/gaussdb_nosql/umn/en-us_image_0000001158064793.png b/docs/gaussdb_nosql/umn/en-us_image_0000001139129197.png similarity index 100% rename from docs/gaussdb_nosql/umn/en-us_image_0000001158064793.png rename to docs/gaussdb_nosql/umn/en-us_image_0000001139129197.png diff --git a/docs/gaussdb_nosql/umn/en-us_image_0000001158064769.png b/docs/gaussdb_nosql/umn/en-us_image_0000001139224537.png similarity index 100% rename from docs/gaussdb_nosql/umn/en-us_image_0000001158064769.png rename to docs/gaussdb_nosql/umn/en-us_image_0000001139224537.png diff --git a/docs/gaussdb_nosql/umn/en-us_image_0000001158064901.png b/docs/gaussdb_nosql/umn/en-us_image_0000001139224555.png similarity index 100% rename from docs/gaussdb_nosql/umn/en-us_image_0000001158064901.png rename to docs/gaussdb_nosql/umn/en-us_image_0000001139224555.png diff --git a/docs/gaussdb_nosql/umn/en-us_image_0000001158104849.png b/docs/gaussdb_nosql/umn/en-us_image_0000001139224635.png similarity index 100% rename from docs/gaussdb_nosql/umn/en-us_image_0000001158104849.png rename to docs/gaussdb_nosql/umn/en-us_image_0000001139224635.png diff --git a/docs/gaussdb_nosql/umn/en-us_image_0108820738.png b/docs/gaussdb_nosql/umn/en-us_image_0108820738.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$ZXze7D%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/gaussdb_nosql/umn/nosql_01_0006.html b/docs/gaussdb_nosql/umn/nosql_01_0006.html index b90b50e7a..b365da180 100644 --- a/docs/gaussdb_nosql/umn/nosql_01_0006.html +++ b/docs/gaussdb_nosql/umn/nosql_01_0006.html @@ -4,7 +4,7 @@

The DB instance specifications depend on the selected DB engine.

GaussDB(for Cassandra) Instance Specifications

-
@@ -154,7 +152,7 @@ @@ -163,7 +161,7 @@
Table 1 GaussDB(for Cassandra) instance specifications

Flavor

+
@@ -14,7 +14,7 @@ - @@ -23,7 +23,7 @@ - @@ -32,7 +32,7 @@ - @@ -41,7 +41,7 @@ - @@ -50,7 +50,7 @@ - @@ -59,7 +59,7 @@ - @@ -68,7 +68,7 @@ - diff --git a/docs/gaussdb_nosql/umn/nosql_02_0002.html b/docs/gaussdb_nosql/umn/nosql_02_0002.html index 8af564bff..9f9e665a0 100644 --- a/docs/gaussdb_nosql/umn/nosql_02_0002.html +++ b/docs/gaussdb_nosql/umn/nosql_02_0002.html @@ -42,8 +42,6 @@ @@ -154,7 +152,7 @@ @@ -163,7 +161,7 @@
Table 1 GaussDB(for Cassandra) cluster instance specifications

Flavor

vCPUs

geminidb.cassandra.xlarge.arm.8

+

geminidb.cassandra.xlarge.8

4

24,000

geminidb.cassandra.2xlarge.arm.8

+

geminidb.cassandra.2xlarge.8

8

48,000

geminidb.cassandra.4xlarge.arm.8

+

geminidb.cassandra.4xlarge.8

16

96,000

geminidb.cassandra.6xlarge.arm.8

+

geminidb.cassandra.6xlarge.8

24

144,000

geminidb.cassandra.8xlarge.arm.8

+

geminidb.cassandra.8xlarge.8

32

192,000

geminidb.cassandra.12xlarge.arm.8

+

geminidb.cassandra.12xlarge.8

48

288,000

geminidb.cassandra.15xlarge.arm.8

+

geminidb.cassandra.15xlarge.8

60

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.

-

Instances can be deployed in a single AZ or three AZs.

-
  • If you want to deploy an instance in a single AZ, select one AZ.
  • If you want to deploy an instance across AZs for disaster recovery, select three AZs. In this deployment mode, the nodes are evenly distributed in the three AZs.

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 (-).

    +
  • 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.

  • 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.
    -

  • 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.

      +

    • 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/gaussdb_nosql/umn/nosql_02_0004.html b/docs/gaussdb_nosql/umn/nosql_02_0004.html index d679dbbbb..0d0d3c336 100644 --- a/docs/gaussdb_nosql/umn/nosql_02_0004.html +++ b/docs/gaussdb_nosql/umn/nosql_02_0004.html @@ -1,14 +1,14 @@

      Configuring Security Group Rules

      -

      Scenarios

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

      +

      Scenarios

      The default security group rule allows all outgoing data packets. ECSs and GaussDB NoSQL 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 GaussDB NoSQL 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 GaussDB(for Cassandra) instance, you need to configure an inbound rule for the security group where the instance resides.
        • 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.
        +

        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 GaussDB(for 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.
        +

        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/gaussdb_nosql/umn/nosql_02_0005.html b/docs/gaussdb_nosql/umn/nosql_02_0005.html index d7cb57945..a84d483bd 100644 --- a/docs/gaussdb_nosql/umn/nosql_02_0005.html +++ b/docs/gaussdb_nosql/umn/nosql_02_0005.html @@ -8,11 +8,11 @@
    • The default port of the GaussDB(for 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.
    +

    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>

      +

      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

        +

        ./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>
        diff --git a/docs/gaussdb_nosql/umn/nosql_02_0009.html b/docs/gaussdb_nosql/umn/nosql_02_0009.html index 01e81bef0..e0dbc45cd 100644 --- a/docs/gaussdb_nosql/umn/nosql_02_0009.html +++ b/docs/gaussdb_nosql/umn/nosql_02_0009.html @@ -4,11 +4,11 @@

        Scenarios

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

        This section describes how to use a Linux ECS to connect to a GaussDB(for Cassandra) instance over a public network.

        -

        Prerequisites

        • Bind an EIP to the GaussDB(for 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.
        +

        Prerequisites

        • Bind an EIP to the GaussDB(for 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>

          +

          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

            +

            ./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>
            diff --git a/docs/gaussdb_nosql/umn/nosql_02_0010.html b/docs/gaussdb_nosql/umn/nosql_02_0010.html index 7978ba431..40db401ed 100644 --- a/docs/gaussdb_nosql/umn/nosql_02_0010.html +++ b/docs/gaussdb_nosql/umn/nosql_02_0010.html @@ -42,8 +42,6 @@

    • 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.

    -

    Instances can be deployed in a single AZ or three AZs.

    -
    • If you want to deploy an instance in a single AZ, select one AZ.
    • If you want to deploy an instance across AZs for disaster recovery, select three AZs. In this deployment mode, the nodes are evenly distributed in the three AZs.

    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 (-).

      +
    • 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.

  • 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.
    -

  • 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.

      +

    • 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/gaussdb_nosql/umn/nosql_02_0011.html b/docs/gaussdb_nosql/umn/nosql_02_0011.html index fc3219a9d..131c9fb9d 100644 --- a/docs/gaussdb_nosql/umn/nosql_02_0011.html +++ b/docs/gaussdb_nosql/umn/nosql_02_0011.html @@ -6,7 +6,7 @@

    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 GaussDB(for Cassandra) instance from resources outside the security group, you need to configure an inbound rule to allow access to the GaussDB(for 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.
    +

    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/gaussdb_nosql/umn/nosql_03_0004.html b/docs/gaussdb_nosql/umn/nosql_03_0004.html index d8806cf88..32eb7c860 100644 --- a/docs/gaussdb_nosql/umn/nosql_03_0004.html +++ b/docs/gaussdb_nosql/umn/nosql_03_0004.html @@ -3,10 +3,9 @@

    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.

    - +

    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 DB 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 DB instance in the instance list is Deleting node.
      • After the deletion, the DB instance status becomes Available.
      +

      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.

    diff --git a/docs/gaussdb_nosql/umn/nosql_03_0007.html b/docs/gaussdb_nosql/umn/nosql_03_0007.html index f2041d925..1451e6268 100644 --- a/docs/gaussdb_nosql/umn/nosql_03_0007.html +++ b/docs/gaussdb_nosql/umn/nosql_03_0007.html @@ -1,7 +1,7 @@

    Managing Automated Backups

    -

    GaussDB NoSQL 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.

    +

    GaussDB(for 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.
      @@ -11,10 +11,10 @@
    • 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.

      +

      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.
        +

        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.

        diff --git a/docs/gaussdb_nosql/umn/nosql_03_0008.html b/docs/gaussdb_nosql/umn/nosql_03_0008.html index fe27adab0..52701f222 100644 --- a/docs/gaussdb_nosql/umn/nosql_03_0008.html +++ b/docs/gaussdb_nosql/umn/nosql_03_0008.html @@ -1,11 +1,11 @@

        Managing Manual Backups

        -

        To ensure data reliability, GaussDB NoSQL 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.

        +

        To ensure data reliability, GaussDB(for Cassandra) 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 GaussDB NoSQL 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.

          +

          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

          diff --git a/docs/gaussdb_nosql/umn/nosql_03_0009.html b/docs/gaussdb_nosql/umn/nosql_03_0009.html index b98da2cdb..74f78e705 100644 --- a/docs/gaussdb_nosql/umn/nosql_03_0009.html +++ b/docs/gaussdb_nosql/umn/nosql_03_0009.html @@ -1,13 +1,13 @@

          Restoring Data to a New DB Instance

          -

          Scenarios

          GaussDB NoSQL helps you to restore the existing backup to a new DB instance.

          +

          Scenarios

          GaussDB(for Cassandra) allows you to restore the existing backup to a new DB instance.

          Procedure

          1. Log in to the GaussDB NoSQL 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.
            • GaussDB NoSQL 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.
            +

          4. 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.
            • GaussDB NoSQL 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.

          5. 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.

            diff --git a/docs/gaussdb_nosql/umn/nosql_03_0013.html b/docs/gaussdb_nosql/umn/nosql_03_0013.html index d372495ea..3d065b4b9 100644 --- a/docs/gaussdb_nosql/umn/nosql_03_0013.html +++ b/docs/gaussdb_nosql/umn/nosql_03_0013.html @@ -10,7 +10,7 @@

          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.

            +

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

          diff --git a/docs/gaussdb_nosql/umn/nosql_03_0014.html b/docs/gaussdb_nosql/umn/nosql_03_0014.html index a6d89d1ee..a7c7f78dc 100644 --- a/docs/gaussdb_nosql/umn/nosql_03_0014.html +++ b/docs/gaussdb_nosql/umn/nosql_03_0014.html @@ -2,10 +2,10 @@

          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 GaussDB NoSQL resources helps you better identify and manage them. A DB instance can be tagged during or after it is created.

          -

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

          +

          Adding tags to GaussDB NoSQL 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.
          • Each DB instance can have up to 20 tags.
          +

          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.
          @@ -17,14 +17,14 @@ - - @@ -33,12 +33,12 @@
          Table 1 Naming rules

          Parameter

          Tag key

          • The key cannot be left blank.
          • Each tag key must be unique for each DB instance.
          • A tag key consists of up to 36 characters.
          • The key can only consist of digits, letters, underscores (_), and hyphens (-).
          +
          • 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 (_), periods (.), and hyphens (-).
          +
          • 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 DB instance you wish to add tags for. The Basic Information page is displayed.
          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.
          +

          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 DB instance you wish to add tags for. The Basic Information page is displayed.
          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.

            +

            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 DB instance you wish to delete tags for. The Basic Information page is displayed.
            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.
            +

            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.
            diff --git a/docs/gaussdb_nosql/umn/nosql_03_0015.html b/docs/gaussdb_nosql/umn/nosql_03_0015.html index 2096e118b..5d808f163 100644 --- a/docs/gaussdb_nosql/umn/nosql_03_0015.html +++ b/docs/gaussdb_nosql/umn/nosql_03_0015.html @@ -4,7 +4,7 @@

            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.

            +

            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 GaussDB(for Cassandra) Instance Over Private Networks.

            diff --git a/docs/gaussdb_nosql/umn/nosql_03_0017.html b/docs/gaussdb_nosql/umn/nosql_03_0017.html new file mode 100644 index 000000000..eb06fc09a --- /dev/null +++ b/docs/gaussdb_nosql/umn/nosql_03_0017.html @@ -0,0 +1,199 @@ + + +

            Key Operations Recorded by CTS

            +

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

            +

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

            + +
            + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
            Table 1 GaussDB(for 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/gaussdb_nosql/umn/nosql_03_0018.html b/docs/gaussdb_nosql/umn/nosql_03_0018.html new file mode 100644 index 000000000..05dda8adf --- /dev/null +++ b/docs/gaussdb_nosql/umn/nosql_03_0018.html @@ -0,0 +1,19 @@ + + +

            Querying Traces

            +

            After CTS is enabled, the tracker starts recording operations on cloud resources. Operation records for the last 7 days are stored on the CTS console.

            +

            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/gaussdb_nosql/umn/nosql_03_0019.html b/docs/gaussdb_nosql/umn/nosql_03_0019.html new file mode 100644 index 000000000..463da4b87 --- /dev/null +++ b/docs/gaussdb_nosql/umn/nosql_03_0019.html @@ -0,0 +1,18 @@ + + +

            Auditing

            +

            +
            + + diff --git a/docs/gaussdb_nosql/umn/nosql_03_0025.html b/docs/gaussdb_nosql/umn/nosql_03_0025.html index fd123bc82..d6d139abc 100644 --- a/docs/gaussdb_nosql/umn/nosql_03_0025.html +++ b/docs/gaussdb_nosql/umn/nosql_03_0025.html @@ -3,12 +3,12 @@

            Changing a DB Instance Name

            Scenarios

            This section describes how to change a GaussDB(for Cassandra) instance name to identify different DB instances.

            -

            Method 1

            1. Log in to the GaussDB NoSQL 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 (case-sensitive), digits, hyphens (-), and underscores (_) are allowed.

                +

                Method 1

                1. Log in to the GaussDB NoSQL 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 (case-sensitive), 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 GaussDB NoSQL 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 (case-sensitive), digits, hyphens (-), and underscores (_) are allowed.

                    -
                  • To cancel the change, click .
                  +

                  Method 2

                  1. Log in to the GaussDB NoSQL 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 (case-sensitive), digits, hyphens (-), and underscores (_) are allowed.

                      +
                    • To cancel the change, click .

                  4. View the results on the Instance Management page.
                diff --git a/docs/gaussdb_nosql/umn/nosql_04_change_history.html b/docs/gaussdb_nosql/umn/nosql_04_change_history.html index 693ce22da..3dad86580 100644 --- a/docs/gaussdb_nosql/umn/nosql_04_change_history.html +++ b/docs/gaussdb_nosql/umn/nosql_04_change_history.html @@ -2,38 +2,40 @@

                Change History

                -

                Released On

                +
                - - - - - - - + + + + + + diff --git a/docs/gaussdb_nosql/umn/nosql_05_0010.html b/docs/gaussdb_nosql/umn/nosql_05_0010.html index e52f95f87..126d50a2b 100644 --- a/docs/gaussdb_nosql/umn/nosql_05_0010.html +++ b/docs/gaussdb_nosql/umn/nosql_05_0010.html @@ -3,7 +3,7 @@

                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: >!<"&'=
                  +

                  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: >!<"&'=

                diff --git a/docs/gaussdb_nosql/umn/nosql_06_0001.html b/docs/gaussdb_nosql/umn/nosql_06_0001.html index a3221463f..2fff44189 100644 --- a/docs/gaussdb_nosql/umn/nosql_06_0001.html +++ b/docs/gaussdb_nosql/umn/nosql_06_0001.html @@ -1,7 +1,7 @@

                Instance Connection Methods

                -

                GaussDB(for Cassandra) supports databases connections over public and private networks.

                +

                You can connect to a GaussDB(for Cassandra) DB instance over a private or public network.

                Released On

                Description

                +

                Description

                2020-11-30

                +

                2020-07-31

                Added the following content:

                -

                Added monitoring metrics in GaussDB(for Cassandra) Monitoring Metrics.

                -

                Supported setting alarm rules in Setting Alarm Rules.

                -

                Supported viewing monitoring metrics in Viewing Metrics.

                +

                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-08-30

                +

                2023-02-10

                Added the following content:

                -

                Supported binding and unbinding an EIP in Binding an EIP.

                -

                Added support for connecting to a DB instance through a public network in Connecting to a GaussDB(for Cassandra) Instance Over Public Networks.

                -

                Supported changing the administrator password in Resetting the Administrator Password.

                -

                Supported restart of a DB instance Restarting a DB Instance.

                -

                Supported node scale-out in Adding Nodes.

                -

                Supported storage capacity expansion in Scaling Up Storage Space.

                -

                Supported changing specifications in Changing a DB Instance Class.

                -

                Supported node scale-in in Deleting Nodes.

                -

                Added the parameter template in Parameter Template Management.

                -

                Supported the query of slow query logs in Slow Query Logs.

                +

                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-06-30

                +

                2020-11-30

                This issue is the first official release.

                +

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

                +

                GaussDB(for Cassandra) Monitoring 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.
                @@ -14,17 +14,17 @@ - - diff --git a/docs/gaussdb_nosql/umn/nosql_cassandra_0001.html b/docs/gaussdb_nosql/umn/nosql_cassandra_0001.html index 7dc2fad58..6b0305013 100644 --- a/docs/gaussdb_nosql/umn/nosql_cassandra_0001.html +++ b/docs/gaussdb_nosql/umn/nosql_cassandra_0001.html @@ -14,6 +14,8 @@
              • Monitoring and Alarm Reporting
                • +
              • Auditing
                +
              • Log Management
                • diff --git a/docs/gaussdb_nosql/umn/nosql_faq_0010.html b/docs/gaussdb_nosql/umn/nosql_faq_0010.html new file mode 100644 index 000000000..65fc79c5f --- /dev/null +++ b/docs/gaussdb_nosql/umn/nosql_faq_0010.html @@ -0,0 +1,11 @@ + + +

                Can I Change the VPC of a GaussDB NoSQL Instance After It Is Created

                +

                After a GaussDB NoSQL instance is created, its VPC cannot be changed. To change the VPC of an instance, you can restore a full backup of the instance to a new instance in another VPC.

                +
                +
                +
                +
                Parent topic: Database Connection
                +
                +
                + diff --git a/docs/gaussdb_nosql/umn/nosql_faq_0103.html b/docs/gaussdb_nosql/umn/nosql_faq_0103.html index 7347e653f..d4585f219 100644 --- a/docs/gaussdb_nosql/umn/nosql_faq_0103.html +++ b/docs/gaussdb_nosql/umn/nosql_faq_0103.html @@ -7,6 +7,8 @@
                diff --git a/docs/gaussdb_nosql/umn/nosql_introduction.html b/docs/gaussdb_nosql/umn/nosql_introduction.html index bd352a957..0c428f603 100644 --- a/docs/gaussdb_nosql/umn/nosql_introduction.html +++ b/docs/gaussdb_nosql/umn/nosql_introduction.html @@ -1,9 +1,10 @@

                What Is GaussDB NoSQL?

                -

                GaussDB NoSQL 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. GaussDB NoSQL is compatible with mainstream NoSQL APIs. It provides high-performance read/write at a low costs, making it well suited to IoT, meteorology, Internet, and gaming applications.

                -

                Currently, GaussDB NoSQL supports the GaussDB(for Cassandra) DB engine.

                -

                GaussDB(for Cassandra) is a cloud-native NoSQL database compatible with Cassandra. It supports SQL-like CQL syntax. GaussDB(for Cassandra) is secure, reliable, scalable, and easy to manage.

                +

                GaussDB NoSQL 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. GaussDB NoSQL includes GaussDB(for Cassandra) with Cassandra API compatibility. It provides high-performance read/write at low costs, making it well suited to IoT, meteorology, Internet, and gaming applications.

                +

                GaussDB(for Cassandra)

                GaussDB(for Cassandra) is a cloud-native NoSQL database compatible with Cassandra. It supports Cassandra Query Language (CQL), which gives you SQL-like syntax. GaussDB(for Cassandra) is secure, reliable, scalable, and easy to manage.

                +
                • 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).
                • GaussDB(for Cassandra) read and write performance is 3 times that 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.
                +
                diff --git a/docs/gaussdb_nosql/umn/nosql_login.html b/docs/gaussdb_nosql/umn/nosql_login.html index b9c8487a0..df366c5c1 100644 --- a/docs/gaussdb_nosql/umn/nosql_login.html +++ b/docs/gaussdb_nosql/umn/nosql_login.html @@ -4,7 +4,7 @@

                Prerequisites

                You have registered a cloud account for logging in to the GaussDB NoSQL 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 GaussDB NoSQL, 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 > GaussDB NoSQL.
                +

                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 > GaussDB NoSQL.
                Table 1 Connection methods

                Method

                Private network

                A private IP address is provided by default.

                -

                Your applications are deployed on an ECS that is in the same region and VPC as your instances.

                +

                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 through a private IP address, bind an EIP to the DB instance first and connect the ECS to the DB instance through the EIP.

                +

                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, you are advised to 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.
                +
                • 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.