To GoodData homepage

Replies posted by David Kubecka

6 Replies

T
tibiNew Participant
asked in Data sources

GD.CN running the same, long running query in multiple parallel sessions

@Carson We would like to support multi column PK for center-of-star fact tables in the future. Dimensions (which are referenced from other datasets) would still require single column PK as that’s considered best practice for performance reasons.Let me know whether this (multi column PK in fact tables) would better match your model.

5
D
GoodData Employee
2 years ago
ashok
ashokKnown Participant
asked in GoodData.UI

Analyze Tab : Connection failed, try again later…

So this looks like a different problem than what @jacek anticipated:"detail":"{'ERROR',{user_fault,\"no source table covering objects: objects=[attribute/audiences.audience_id/headquarters]\"}}"This means that you are missing Data mapping between attribute “audiences.audience_id/headquarters” and the underlying physical tables. Ideally your mapping should look like this in LDM modeler:I assume that in your case the Source Columns are blank. You can either filled them manually or better generate them from scratch using Scan feature of LDM modeler with the “Generate datasets” option turned on like this:Let us know if that helped.

6
D
GoodData Employee
2 years ago
N
NickKKnown Participant
posted in Dashboards and Reports

GoodData.CN Internal Server Error

@Yuriy Balakhonov@Vasiliy Ostrovsky@NickK We have made some progress on this issue and would like to test whether it helps in your particular case. For that we would need the dump of your metadata, namely logical (LDM) and physical (PDM) models.PDM can be obtained at/api/layout/dataSources/{data_source_id}/physicalModeland LDM at/api/layout/workspaces/{workspaceId}/logicalModelAlso can you describe the usage pattern (concurrency) at the time you hit those issues?Thanks

24
Martin Burian
Community Manager
1 year ago
N
NickKKnown Participant
posted in Dashboards and Reports

GoodData.CN Internal Server Error

@Yuriy Balakhonov The log exceptions are indeed related to timeout but unfortunately they do not point in any way to the root cause which most probably lies in the overloaded DB (hypothesis). That’s why it’s important for us if you would be able to check postgres database traffic. Especially contents of “pg_stat_activity” table might be of interest.Regarding configuration: currently it’s not possible to configure timeouts for this particular service.

24
Martin Burian
Community Manager
1 year ago
N
NickKKnown Participant
posted in Dashboards and Reports

GoodData.CN Internal Server Error

@Vasiliy Ostrovsky Can you please attach log events with relevant errors to your issue? Also what is the content of “pg_stat_activity” table when this issue happens?

24
Martin Burian
Community Manager
1 year ago
N
NickKKnown Participant
posted in Dashboards and Reports

GoodData.CN Internal Server Error

@NickK May I ask you to still check postgres database if this kind of issue ever happens again? Especially contents of “pg_stat_activity” table. Thanks

24
Martin Burian
Community Manager
1 year ago
Welcome to the GoodData Community!Cookie settings