From 47b87f14a103f927c48a8b0540cd8ec0554c474e Mon Sep 17 00:00:00 2001 From: Zach Tilev Date: Fri, 5 Aug 2022 15:45:07 +0300 Subject: [PATCH 1/5] First draft of Connection to database timed out --- .../050-connection-to-db-timed-out.mdx | 45 +++++++++++++++++++ 1 file changed, 45 insertions(+) create mode 100644 content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx diff --git a/content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx b/content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx new file mode 100644 index 0000000000..e4045fe206 --- /dev/null +++ b/content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx @@ -0,0 +1,45 @@ +--- +title: 'Connection to database timed out' +metaTitle: 'Connection to database timed out' +metaDescription: 'When viewing models in the Data Browser or running queries in the Query Console, you might see errors reporting that the connection to your database times out.' +--- + + + + + +## **Problem** + +The error _Connection your database timed out_ appears when you use the **Data Browser** or the **Query Console**. + +## **Cause** + +When using the **Data Browser** or the **Query Console**, the default timeout for requests sent to the database is `15ms`. If a response is not avaialble within this limit, the error appears. + +Several reasons related to the Data Proxy or database configuration might cause this issue. + +### **Causes related to Data Proxy** + +* The time added to a request as a result of it going through the Data Proxy pushed the timeout beyond the limit +* The database and Data Proxy are in different geolocations + +### **Causes related to the response size, database, and network latency** + +* The time it took the database to process the query pushed it over the timeout limit +* The payload response is large and could not be processed within the timeout limit +* The depth of the query is large (it includes mutliple relational fields) + +## **Solution** + +While you can do little to impact potential Data Proxy or network latency, you can start with one of the following solutions. + +* Retry your operation in the **Data Browser** or query in the **Query Console** and see if it completes successfully. +* Configure your Data Proxy to be in a closer or the same location as the database. + + + **Note**

+ You can only do so by creating a new environment in which you can specify a different Data Proxy location. + + + +If you experience this issue consistently, [contact Support](/data-platform/contact-support). \ No newline at end of file From ed6cd8eb9acc5da1fe71e58a2a060a89f1043322 Mon Sep 17 00:00:00 2001 From: Zach Tilev <103522279+zachtil@users.noreply.github.com> Date: Mon, 15 Aug 2022 11:18:08 +0300 Subject: [PATCH 2/5] Update content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx Co-authored-by: Tana M Berry --- .../12-troubleshooting/050-connection-to-db-timed-out.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx b/content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx index e4045fe206..488eb23df0 100644 --- a/content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx +++ b/content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx @@ -1,7 +1,7 @@ --- title: 'Connection to database timed out' metaTitle: 'Connection to database timed out' -metaDescription: 'When viewing models in the Data Browser or running queries in the Query Console, you might see errors reporting that the connection to your database times out.' +metaDescription: 'When viewing models in the Data Browser or running queries in the Query Console, you might see errors that the connection to your database timed out.' --- From 41ab0b7637e80a56450623f764b738ee51595b5d Mon Sep 17 00:00:00 2001 From: Zach Tilev <103522279+zachtil@users.noreply.github.com> Date: Mon, 15 Aug 2022 11:18:23 +0300 Subject: [PATCH 3/5] Update content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx Co-authored-by: Tana M Berry --- .../12-troubleshooting/050-connection-to-db-timed-out.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx b/content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx index 488eb23df0..c9deef9361 100644 --- a/content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx +++ b/content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx @@ -20,7 +20,7 @@ Several reasons related to the Data Proxy or database configuration might cause ### **Causes related to Data Proxy** -* The time added to a request as a result of it going through the Data Proxy pushed the timeout beyond the limit +* The time added to a request because it is routed through the Data Proxy pushed the timeout beyond the limit * The database and Data Proxy are in different geolocations ### **Causes related to the response size, database, and network latency** From 7b60278910ff9ff888b2600169c07cf73020a77c Mon Sep 17 00:00:00 2001 From: Zach Tilev <103522279+zachtil@users.noreply.github.com> Date: Mon, 15 Aug 2022 11:18:36 +0300 Subject: [PATCH 4/5] Update content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx Co-authored-by: Tana M Berry --- .../12-troubleshooting/050-connection-to-db-timed-out.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx b/content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx index c9deef9361..bd0bb8f785 100644 --- a/content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx +++ b/content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx @@ -34,7 +34,7 @@ Several reasons related to the Data Proxy or database configuration might cause While you can do little to impact potential Data Proxy or network latency, you can start with one of the following solutions. * Retry your operation in the **Data Browser** or query in the **Query Console** and see if it completes successfully. -* Configure your Data Proxy to be in a closer or the same location as the database. +* Configure your Data Proxy to be closer to or in the same location as the database. **Note**

From e10dc7119c88d4e90f04314f4142b671d993655d Mon Sep 17 00:00:00 2001 From: Zach Tilev <103522279+zachtil@users.noreply.github.com> Date: Mon, 15 Aug 2022 11:18:45 +0300 Subject: [PATCH 5/5] Update content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx Co-authored-by: Tana M Berry --- .../12-troubleshooting/050-connection-to-db-timed-out.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx b/content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx index bd0bb8f785..bc10bb3b53 100644 --- a/content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx +++ b/content/800-data-platform/12-troubleshooting/050-connection-to-db-timed-out.mdx @@ -38,7 +38,7 @@ While you can do little to impact potential Data Proxy or network latency, you c **Note**

- You can only do so by creating a new environment in which you can specify a different Data Proxy location. + You can do so only by creating a new environment in which you can specify a different Data Proxy location.