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
{{ message }}
Repository navigation
feature: Make shards to own shard object locally #4335
Now every shard writes its shard object into root shard. Making root shart more special than it should be. In addition data is getting hard to handle. In example if we want to track shard status, every shards now writes this via expensive network call, vs locally.
Proposed Solution
We create new dedicated "hidden" workspace system:shard
We add shard object into this on every shard (one object only per shard). And shard use this to store data, statuses, etc
We replicate this shard object into cache server same lc.
We pull this into root shard as representation only.
Consequence of this is one can't edit shard object spec anymore and just change its configuration. Which is fine. At some point we can establish two way sync from designated representation location (root shard root workspace), but for now if you want to change something - you change shard configuration/deployment and see it replicate.
Activity
[-]feature: Make shards to own shard object[/-][+]feature: Make shards to own shard object locally [/+]