Help Center> GeminiDB> GeminiDB Mongo API> Service Overview> Usage Specifications> Reliability

Updated on 2023-04-17 GMT+08:00

View PDF

Reliability

Rules for setting write concern:
For mission-critical services, set write concern to {w:n},n>0. A larger value indicates better consistency but poorer performance.
- w:1 indicates that a confirmation message is returned after data is written to the primary node.
- w:1,journal:true indicates that the result is returned after data is written to the primary node and logs.
- w:majority indicates that the result is returned after data is written to more than half of the total nodes.
  
  If data is not written using w:majority, the data that is not synchronized to the standby node may be lost when a primary/standby switchover occurs.
If high reliability is required, deploy a replica set across three AZs.

Parent topic: Usage Specifications

Previous topic: Database Connection

Next topic: Database Performance

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.