I run GridDB on GridDB Cloud (Free plan) with a single TimeSeries container that’s actively ingesting data. I need to add a secondary index on deviceid to speed up point/range lookups.
Environment:
- GridDB Cloud (Free)
- TimeSeries container
TSDB ts TIMESTAMP PRIMARY KEY(row key),deviceid STRING, other metrics- Continuous writes (~tens/sec) + concurrent reads
Existing DDL:
CREATE TABLE TSDB ( ts TIMESTAMP PRIMARY KEY, deviceid STRING, temperature DOUBLE, humidity DOUBLE, status STRING ) USING TIMESERIES; Planned change:
CREATE INDEX idx_tsdb_deviceid ON TSDB (deviceid); On a small test set, this finished quickly, but I need to schedule it safely for a much larger container in production.
Question: On GridDB Cloud, is CREATE INDEX on a TimeSeries container executed online (i.e., without blocking inserts/reads), or does it take locks that pause/slow writers or readers? If it’s not fully online, what is the documented impact and the recommended way to perform the index build safely under write load (e.g., maintenance window, batching, throttling, or Cloud-side tooling/monitoring)?
I’m looking for the official behavior/expectations so I can plan the change (impact, monitoring, and any best-practice sequence).