Live

Lightweight updates can cause undesired effects

0

ClickHouse Cloud reports that lightweight updates on an existing table can cause incorrect results when setting enableblocknumbercolumn = 1. ClickHouse Cloud is investigating. The provider gives this workaround: create a new table and set enableblockoffsetcolumn = 1 on the table before you insert data.

State

Investigating

Started

Ongoing for

22 min

Worst impact

Degraded

Timeline

1 update
23:3323:3823:4423:4923:55
DegradedUpdate postedTimes in UTC

Investigating

22 min 100%

Updates

Times in UTC

As posted by ClickHouse Cloud

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.

ClickHouse Cloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

16

Days with an incident

16

Median duration

50 min

This incident

56% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

29 h 46 min
median 50 min
90 days agoToday

Other ClickHouse Cloud incidents

All incidents

Follow ClickHouse Cloud

Your coding agent knows when ClickHouse Cloud is down, and tells you when a failure is theirs, not yours. You can also get ClickHouse Cloud incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "clickhouse" and tell me if ClickHouse Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=clickhouse
Slack
/feed subscribe https://outages.live/feed.xml?providers=clickhouse

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane