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
Originally posted by tu5har February 24, 2024
PG: 15
Citus: 12.1
Hi All,
We have a large table distributed on a date column(event_date) with a shard count 128.
It has data for more than 400 days and the total size has reached almost 4TB.
We checked the shard sizes, seems the data is not uniform across all the shards. Some shards are fat having more than 100GB of data while many have very less data. Data size for each day is almost the same around, So the expectation is all shards should have almost similar sizes; and not be so skewed. This impacts the query latency when it hits a fat shard.
Can someone let us know how to redistribute data among the shards uniformly?
Below is a snapshot of shard sizes
Discussed in #7535
Originally posted by tu5har February 24, 2024
PG: 15
Citus: 12.1
Hi All,
We have a large table distributed on a date column(event_date) with a shard count 128.
It has data for more than 400 days and the total size has reached almost 4TB.
We checked the shard sizes, seems the data is not uniform across all the shards. Some shards are fat having more than 100GB of data while many have very less data. Data size for each day is almost the same around, So the expectation is all shards should have almost similar sizes; and not be so skewed. This impacts the query latency when it hits a fat shard.
Can someone let us know how to redistribute data among the shards uniformly?
Below is a snapshot of shard sizes
The text was updated successfully, but these errors were encountered: