You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-unavailable.mdx
+20-1Lines changed: 20 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,8 @@ categories:
14
14
- postgresql-and-mysql
15
15
---
16
16
17
+
## My Database Instance is unavailable
18
+
17
19
## Problem
18
20
19
21
My Database Instance is unavailable.
@@ -31,4 +33,21 @@ You can monitor your Database Instance activity to be able to quickly identify a
31
33
32
34
- Check if the usage is regular. Database Instance can be impacted by high data loads or unexpected high traffic from an app or website, for example
33
35
- Check if there are slow queries in the Database Instance log. Huge or sub-optimized queries can fill up all the memory and trigger OOM kills
34
-
- Check the Database Instance logs for any unusual or suspicious activity
36
+
- Check the Database Instance logs for any unusual or suspicious activity
37
+
38
+
## My Database Instance is in stuck state
39
+
40
+
## Problem
41
+
42
+
My Database Instance is currently in a stuck state.
43
+
44
+
## Possible causes
45
+
46
+
- A maintenance operation on Scaleway's side is taking longer than usual and timed out, making the Database Instance go into a transitional state
47
+
48
+
## Solution
49
+
50
+
If the Database Instance is sent to a transitional state, the Scaleway Databases team receives an alert and will act on the issue as soon as possible.
51
+
52
+
If you observe the resolution is taking longer than usual, [create a support ticket](/account/how-to/open-a-support-ticket/#writing-an-effective-subject-and-description) to let us know.
0 commit comments