Upgrading to Hasura 2.0 , Track all returns timeout error

[nadendlaprasad]

TrackAll from the schema crashing Hasura and returns timeout error most of the time

[AndresPrez]

Same for me. I found and ENV for migration timeout that is not found in the docs. Maybe you also have on for track all?

[nadendlaprasad]

@AndresPrez can you share the environment config details?

[AndresPrez]

@nadendlaprasad turns out the console Track All action worked for me but it took about 4 to 5 hours to track all tables (540 tables), views and relations. I did this locally using v2.5.0.cli-migrations-v3 docker container in a 16GM RAM 2.2Ghz 6-Core interal i7 Apple Pro.

I noticed there once was a CLI command to do the same and also track individual tables hasura-cli metadata track, but not anymore after hasura v2.x.

[nadendlaprasad]

@AndresPrez agreed. Post 2.x.x, Track all takes quite long time to process the request

[dsandip]

Update: this is being looked at by the team and there should be updates on this in the near future.

[motya770]

Would like to receive updates on the issue, important for our team

[vijayprasanna13]

Hey folks! We've traced this issue to the large number of introspection calls that we fire. We're working on a new UX for postgres that makes the landing page for viewing/tracking your tables much faster.
We'll keep you updated in the related issue

[vijayprasanna13]

Hey folks! We've added a new experimental version of the Data Tab to handle larger schemas. You can try it out starting from v2.33.0-beta.1 by enabling the feature flag. Please follow this #9846 for more updates and do share your early feedback with us!