Skip to content

Incident detail

Lightweight updates can cause undesired effects

Active incidentMinor2 affected services36 regions: af-south-1, ap-east-1, ap-east-2, ap-northeast-1, ap-northeast-2, ap-south-1, ap-southeast-1, ap-southeast-2, ap-southeast-3, ap-southeast-5, asia-northeast1, asia-southeast1, australia-southeast1, australiaeast, eastus2, eu-central-1, eu-north-1, eu-west-1, eu-west-2, europe-west3, europe-west4, europe-west6, germanywestcentral, il-central-1, japaneast, mx-central-1, northamerica-northeast1, sa-east-1, uaenorth, us-central1, us-east-1, us-east-2, us-east1, us-west-2, us-west1, westus3

Timeline window

Started

Get alerted the next time ClickHouse Cloud breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    We’ve discovered an issue where enabling lightweight updates on an existing table via setting `enable_block_number_column = 1` could cause incorrect results. To achieve desired results, create a new table and set `enable_block_offset_column = 1`  on the table first before inserting any data into it.

Keep exploring

More from ClickHouse Cloud

Neighboring incidents on ClickHouse Cloud's timeline and the rest of their record on OutageDeck.