@earth-app/collegedb
    Preparing search index...

    Interface ShardState

    Known facts about one shard binding.

    1.4.0

    interface ShardState {
        drain?: "active" | "draining" | "retired";
        id?: string;
        tags?: Record<string, string>;
        writable?: boolean;
    }
    Index
    drain?: "active" | "draining" | "retired"

    Where the shard is in being emptied. Only active takes new keys. draining and retired differ in intent: retired says its data should already be moved, and pruneEpochs is what proves it. Both stay readable and stay in older epochs, so existing keys keep resolving.

    'active'
    
    id?: string

    Stable physical database id (for D1, the database UUID). Session bookmarks are keyed by it, so a topology change cannot apply one database's bookmark to another.

    tags?: Record<string, string>

    Labels the eligible predicate can read, such as a jurisdiction or a schema version

    writable?: boolean

    Whether the shard accepts new keys. false keeps it out of new allocations; its existing keys stay readable and writable.

    true