You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To reduce the size of a DB shard without downtime, graphman copying deployments out is a good option. But it needs a few optimizations to be usable en masse, including on index creation. This track two of those optimizations:
Create the indexes based on the index creation DDL of the source, not based on the default.
Create the BTree indexes after the copy is done, and only the GiST afterwards.
In general, we should defer creating BTree attribute indexes on all subgraphs until the subgraph is synced. What we really want is to kick off creating those indexes so that they are ready when the subgraph is synced, but not much before then, but as a first step it's ok to create them when the subgraph becomes synced.
All other indexes (not BTree or not an attribute index) should be created when the subgraph is first deployed as creating them later can be very very slow with bad consequences for the rest of the system.
For copies and grafts, we do not want to create the indexes that we create by default for new subgraphs. Instead, we should look at the source of the graft/copy, and recreate all the indexes that actually exist on the source
To reduce the size of a DB shard without downtime,
graphman copy
ing deployments out is a good option. But it needs a few optimizations to be usable en masse, including on index creation. This track two of those optimizations:@incrypto32 will mentor @itsjerryokolo on this task.
The text was updated successfully, but these errors were encountered: