The state status is displayed incorrectly after the openGauss switch

One master and one backup

Version: openGauss 3

Before switching:

Toggle:

Execute on the standby machine:

[[email protected] ~]$ gs_ctl switchover -D /my/openGauss/data/dn/

[[email protected] ~]$ gs_om -t refreshconf

Check the status after switching, the display is wrong

Executing the gs_checkperf command also reports an errorERROR: cannot execute DROP SCHEMA in a read-only transaction

---

Other Answer 1:

This display is normal, the execution of the command reports an error, but the current database is in a read-only state, it should be that your disk space has reached the threshold, take a look at this

https://opengauss.org/en/docs/3.0.0/docs/Developerguide/%E7%A3%81%E7%9B%98%E7%A9%BA%E9%97%B4%E8%BE%BE%E5%88%B0%E9%98%88%E5%80%BC-%E6%95%B0%E6%8D%AE%E5%BA%93%E5%8F%AA%E8%AF%BB.html

Other Answer 2:

gs_checkperf

Background Information

openGauss provides the gs_checkperf tool to help check the openGauss level (host CPU usage, Gauss CPU usage, I/O usage, etc.), node level (CPU usage, memory usage, I/O usage),Periodically check the session/process level (CPU usage, memory usage, I/O usage), and SSD performance (write and read performance), so that users can understand the load of openGauss and take corresponding improvement measures.

Prerequisites

• openGauss is running normally and not in read-only mode.

• Businesses running on top of the database are running normally.

Other Answer 3:

Have you tried restarting the cluster?

Other Answer 4:

There are only a few commands for the active-standby switch. This problem should not occur. Check the log during the active-standby switchover. Is there any problem

Other Answer 5:

There is no problem with the configuration in /etc/hosts