https://www.gooddata.com/ logo
Join Slack
Powered by
Hi Team, having an issue where I'm getting 400 err...
# gooddata-cloud
c
Hi Team, having an issue where I'm getting 400 errors on viz. will thread details
Copy code
6012.4341aee….js:2 Tiger backend threw an error: 
{status: 400, detail: 'An error has occurred while calculating the result', resultId: '7a76778a19a6443198c61a78f338875badf45b57', reason: "No connection to 'REDACTED' available.", traceId: '77b45e61c07e22e74446f6956adc21bc'}
detail
: 
"An error has occurred while calculating the result"
reason
: 
"No connection to 'REDACTED' available."
resultId
: 
"7a76778a19a6443198c61a78f338875badf45b57"
status
: 
400
traceId
: 
"77b45e61c07e22e74446f6956adc21bc"
[[Prototype]]
: 
Object
I am seeing it connect in our snowflake instance and run queries
I am also seeing this query from GD over and over as opposed to any data queries
m
Hi, I’ve reviewed the logs, and it appears that the connection to your data source (whose name begins with "O") is being limited or throttled on your end. After clearing its cache from the organization settings, previously computed insights are now failing to recompute because the connection is being refused. With this said, could you check if any monitors have exceeded their credit limits, which would automatically suspend queries and cause connection issues? You should also be able to check the queued queries or warehouse queuing delays, which could indicate bottlenecks in your current compute configuration. Please also be aware of the following documentation where we have some tips for improving database performance: https://www.gooddata.com/docs/cloud/connect-data/performance/
c
hmm, I am not seeing anything queued or running at the moment
i just changed to a new warehouse and now getting this error {status: 400, detail: 'General error', traceId: 'a9f92a9fed2e3944d229d30da2888b8e'}
actually its working now with a new warehouse
yes its fixed now, i changed to a brand new warehouse. to clarify we have no limits or credit thresholds on that old warehouse
✅ 1
m
Just for reference purposes, the connection on the new warehouse was failing due to the following error: 
No active warehouse selected in the current session.  Select an active warehouse with the 'use warehouse' command
c
yep probably needed to initialize
👍 1
but its a very strange thing that the old one stopped working like that
have you seen that before?
m
Regarding the old warehouse, I was able to get it to load while on edit mode and can see a few issues with it, let me send you a screenshot via DM
c
thank you
m
As discussed internally, the issue appears to stem from the JDBC driver version currently used to connect to Snowflake. We're actively working on a fix and will provide an update as soon as possible. Thank you for your patience.
b
Hello @CaS, This is Branislav from the L2 Technical Support team. I was informed, that the new driver, recommended by Snowflake to resolve the issue(s), is currently being tested. Provided that there are no unexpected issues found, our developers will proceed with merging the change and then it will most probably be delivered as a hotfix. Unfortunately, there is no specific ETA at the moment, but our developers are working hard so that it will be delivered as soon as possible. I will inform you as soon as there are more details available. We are sorry for the inconvenience caused and would like to thank you for your patience and understanding.
Hello @CaS, I would like to inform you that the latest driver recommended by Snowflake was deployed and the issue should be fixed now. With that in mind, could you please verify and let us know if everything is working as expected?
c
We are still having the same issue as of this morning
b
Thank you for letting us know and sharing the information with us. I would like to let you know that our developers are looking into the issue further. They discovered a "connection leak" that resulted in depletion of available connection in the pool. The fix is ready and should be released / deployed either today or on Monday next week. With that in mind, please continue with the monitoring and I will check back with you on Wednesday if there is no update from your side until then.
c
Thank you
As of this morning the problem still existed
b
Hi @CaS, Thank you for letting us know. The fix for the connection leak was released on Monday evening and on top of that, we have also enabled the Optimization of Resource Utilization During Executions feature also known as Cancellation of Abandoned Queries. We have not spotted the errors occurring in our logs since the connection leak fix deployment. However, to be on the safe side, could you please verify if everything works as expected on your side as well? If that is the case, may we consider the issue as resolved?
Hi @CaS, I would like to follow up regarding your intermittent Snowflake connectivity issues. We have not seen any related error(s) since the fix for the connection leak was released and since we enabled the cancellation of abandoned queries last week. As we have not received any update from your side since then, I believe there were no further issues on your side as well. With that in mind, I believe that we might consider this case as resolved. Alternatively, please do not hesitate to reach out in case there are any further issues or you need additional assistance regarding the matter.
c
thank you, it seems to have been working
👍 1
We are seeing the same issue again @Branislav Slávik
j
Hello, there is currently an issue occurring on a part of the platform where your organization is hosted. Our engineers are working on a fix for this, and we will keep you posted on the status as more details emerge.
The issue has been resolved. You can follow our announcments here:
c
thank you
2 Views
Open in Slack
PreviousNext
Powered by