Skip to content

Commit 5d7510d

Browse files
feat(rdb): stuck state
1 parent a33edaf commit 5d7510d

File tree

2 files changed

+38
-1
lines changed

2 files changed

+38
-1
lines changed

menu/navigation.json

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2538,6 +2538,24 @@
25382538
"label": "API/CLI",
25392539
"slug": "api-cli"
25402540
},
2541+
{
2542+
"items": [
2543+
{
2544+
"label": "Dealing with Database Instance unavailability",
2545+
"slug": "database-instance-unavailable"
2546+
},
2547+
{
2548+
"label": "Dealing with Database Instance connectivity issues",
2549+
"slug": "database-instance-connectivity-issues"
2550+
},
2551+
{
2552+
"label": "Dealing with Database Instance performance issues",
2553+
"slug": "database-instance-performance-issues"
2554+
}
2555+
],
2556+
"label": "Troubleshooting",
2557+
"slug": "troubleshooting"
2558+
},
25412559
{
25422560
"items": [
25432561
{

pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-unavailable.mdx

Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ categories:
1414
- postgresql-and-mysql
1515
---
1616

17+
## My Database Instance is unavailable
18+
1719
## Problem
1820

1921
My Database Instance is unavailable.
@@ -31,4 +33,21 @@ You can monitor your Database Instance activity to be able to quickly identify a
3133

3234
- 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
3335
- 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.
53+

0 commit comments

Comments
 (0)