Help Center > > User Guide> FusionInsight Manager Operation Guide> Alarm Reference (Applicable to MRS 3.x)> ALM-27007 Database Enters the Read-Only Mode

ALM-27007 Database Enters the Read-Only Mode

Updated at: Mar 25, 2021 GMT+08:00

Description

The system checks the disk space usage of the data directory on the active DBServer node every 30 seconds. The alarm is generated when the disk space usage exceeds 90%.

The alarm is cleared when the disk space usage is lower than 80%.

Attribute

Alarm ID

Alarm Severity

Auto Clear

27007

Critical

Yes

Parameters

Name

Meaning

ClusterName

Specifies the cluster for which the alarm is generated.

ServiceName

Specifies the service for which the alarm is generated.

RoleName

Specifies the role for which the alarm is generated.

Trigger Condition

Specifies the threshold triggering the alarm. If the actual indicator value exceeds this threshold, the alarm is generated.

Impact on the System

The database enters the read-only mode, causing service data loss.

Possible Causes

The disk configuration cannot meet service requirements. The disk usage reaches the upper limit.

Procedure

Check whether the disk space usage reaches the upper limit.

  1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > DBService.
  2. On the Dashboard page, view the Disk Space Usage of the Data Directory chart and check whether the disk space usage of the data directory exceeds 90%.

    • If yes, go to 3.
    • If no, go to 13.

  3. Log in to the active management node of the DBServer as user omm and run the following commands to check whether the database enters the read-only mode:

    source $DBSERVER_HOME/.dbservice_profile

    gsql -U omm -W password -d postgres -p 20051

    show default_transaction_read_only;

    In the preceding commands, password indicates the password of user omm of the GaussDB database. The default password is dbserverAdmin@123. You can run the \q command to exit the database.

    Check whether the value of default_transaction_read_only is on.

    POSTGRES=# show default_transaction_read_only; 
     default_transaction_read_only 
    ------------------------------- 
     on
    (1 row)
    • If yes, go to 4.
    • If no, go to 13.

  4. Run the following commands to open the dbservice.properties file:

    source $DBSERVER_HOME/.dbservice_profile

    vi ${DBSERVICE_SOFTWARE_DIR}/tools/dbservice.properties

  5. Change the value of gaussdb_readonly_auto to OFF.
  6. Run the following command to open the dbservice.properties file:

    vi ${DBSERVICE_DATA_DIR}/postgresql.conf

  7. Delete default_transaction_read_only = on.
  8. Run the following command for the configuration to take effect:

    gs_ctl reload -D ${DBSERVICE_DATA_DIR}

  9. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms. On the right of the alarm "Database Enters the Read-Only Mode", click Clear in the Operation column. In the dialog box that is displayed, click OK to manually clear the alarm.
  10. Log in to the active management node of the DBServer as user omm and run the following commands to view the files whose size exceeds 500 MB in the data directory and check whether there are large files incorrectly written into the directory:

    source $DBSERVER_HOME/.dbservice_profile

    find "$DBSERVICE_DATA_DIR"/../ -type f -size +500M

    • If yes, go to 11.
    • If no, go to 13.

  11. Handle the files that are incorrectly written into the directory based on the actual scenario.
  12. Log in to FusionInsight Manager and choose Cluster > Name of the desired cluster > Services > DBService. On the Dashboard page, view the Disk Space Usage of the Data Directory chart and check whether the disk space usage is lower than 80%.

    • If yes, no further action is required.
    • If no, go to 13.

    Collect fault information.

  13. On FusionInsight Manager, choose O&M > Log > Download.
  14. Expand the Service drop-down list, and select DBService for the target cluster.
  15. Specify the host for collecting logs by setting the Host parameter which is optional. By default, all hosts are selected.
  16. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
  17. Contact the O&M personnel and send the collected logs.

Alarm Clearing

After the fault is rectified, the system automatically clears this alarm.

Related Information

None

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel