- Release Notes
- Get Started
- Clusters
- Cloud Settings
- Table Type
- Query Data Lakes
- Integration
- Query Acceleration
- Data Loading
- Concepts
- Batch load data from Amazon S3
- Batch load data from Azure cloud storage
- Load data from a local file system
- Load data from Confluent Cloud
- Load data from Amazon MSK
- Load data from Amazon Kinesis
- Data Unloading
- Data Backup
- Security
- Console Access Control
- Data Access Control
- Application keys
- Service accounts
- Use SSL connection
- Alarm
- Usage and Billing
- Organizations and Accounts
- Reference
- Amazon Web Services (AWS)
- Microsoft Azure
- SQL Reference
- Keywords
- ALL statements
- User Account Management
- Cluster Management
- ADMIN CANCEL REPAIR
- ADMIN CHECK TABLET
- ADMIN REPAIR
- ADMIN SET CONFIG
- ADMIN SET REPLICA STATUS
- ADMIN SHOW CONFIG
- ADMIN SHOW REPLICA DISTRIBUTION
- ADMIN SHOW REPLICA STATUS
- ALTER RESOURCE GROUP
- ALTER SYSTEM
- CANCEL DECOMMISSION
- CREATE FILE
- CREATE RESOURCE GROUP
- DROP FILE
- DROP RESOURCE GROUP
- EXPLAIN
- INSTALL PLUGIN
- SET
- SHOW BACKENDS
- SHOW BROKER
- SHOW COMPUTE NODES
- SHOW FRONTENDS
- SHOW FULL COLUMNS
- SHOW INDEX
- SHOW PLUGINS
- SHOW PROCESSLIST
- SHOW RESOURCE GROUP
- SHOW TABLE STATUS
- SHOW FILE
- SHOW VARIABLES
- UNINSTALL PLUGIN
- DDL
- ALTER DATABASE
- ALTER MATERIALIZED VIEW
- ALTER TABLE
- ALTER VIEW
- ANALYZE TABLE
- BACKUP
- CANCEL ALTER TABLE
- CANCEL BACKUP
- CANCEL RESTORE
- CREATE ANALYZE
- CREATE DATABASE
- CREATE EXTERNAL CATALOG
- CREATE INDEX
- CREATE MATERIALIZED VIEW
- CREATE REPOSITORY
- CREATE TABLE AS SELECT
- CREATE TABLE LIKE
- CREATE TABLE
- CREATE VIEW
- CREATE FUNCTION
- DROP ANALYZE
- DROP STATS
- DROP CATALOG
- DROP DATABASE
- DROP INDEX
- DROP MATERIALIZED VIEW
- DROP REPOSITORY
- DROP TABLE
- DROP VIEW
- DROP FUNCTION
- KILL ANALYZE
- RECOVER
- REFRESH EXTERNAL TABLE
- RESTORE
- SET CATALOG
- SHOW ANALYZE JOB
- SHOW ANALYZE STATUS
- SHOW META
- SHOW FUNCTION
- TRUNCATE TABLE
- USE
- DML
- ALTER LOAD
- ALTER ROUTINE LOAD
- BROKER LOAD
- CANCEL LOAD
- CANCEL EXPORT
- CANCEL REFRESH MATERIALIZED VIEW
- CREATE ROUTINE LOAD
- DELETE
- EXPORT
- GROUP BY
- INSERT
- PAUSE ROUTINE LOAD
- RESUME ROUTINE LOAD
- REFRESH MATERIALIZED VIEW
- SELECT
- SHOW ALTER
- SHOW ALTER MATERIALIZED VIEW
- SHOW BACKUP
- SHOW CATALOGS
- SHOW CREATE CATALOG
- SHOW CREATE MATERIALIZED VIEW
- SHOW CREATE TABLE
- SHOW CREATE VIEW
- SHOW DATA
- SHOW DATABASES
- SHOW DELETE
- SHOW DYNAMIC PARTITION TABLES
- SHOW EXPORT
- SHOW LOAD
- SHOW MATERIALIZED VIEW
- SHOW PARTITIONS
- SHOW REPOSITORIES
- SHOW RESTORE
- SHOW ROUTINE LOAD
- SHOW ROUTINE LOAD TASK
- SHOW SNAPSHOT
- SHOW TABLES
- SHOW TABLET
- SHOW TRANSACTION
- STOP ROUTINE LOAD
- STREAM LOAD
- SUBMIT TASK
- UPDATE
- Auxiliary Commands
- Data Types
- Keywords
- SQL Functions
- Function list
- Java UDFs
- Window functions
- Lambda expression
- Date Functions
- add_months
- adddate
- convert_tz
- current_date
- current_time
- current_timestamp
- date
- date_add
- date_diff
- date_format
- date_slice
- date_sub, subdate
- date_trunc
- datediff
- day
- dayofweek_iso
- dayname
- dayofmonth
- dayofweek
- dayofyear
- days_add
- days_diff
- days_sub
- from_days
- from_unixtime
- hour
- hours_add
- hours_diff
- hours_sub
- jodatime_format
- last_day
- makedate
- microseconds_add
- microseconds_sub
- minute
- minutes_add
- minutes_diff
- minutes_sub
- month
- monthname
- months_add
- months_diff
- months_sub
- next_day
- now
- previous_day
- quarter
- second
- seconds_add
- seconds_diff
- seconds_sub
- str_to_date
- str_to_jodatime
- str2date
- time_slice
- time_to_sec
- timediff
- timestamp
- timestampadd
- timestampdiff
- to_date
- to_days
- to_iso8601
- to_tera_date
- to_tera_timestamp
- unix_timestamp
- utc_timestamp
- week
- week_iso
- weekofyear
- weeks_add
- weeks_diff
- weeks_sub
- year
- years_add
- years_diff
- years_sub
- Aggregate Functions
- any_value
- approx_count_distinct
- array_agg
- avg
- bitmap
- bitmap_agg
- count
- count_if
- corr
- covar_pop
- covar_samp
- group_concat
- grouping
- grouping_id
- hll_empty
- hll_hash
- hll_raw_agg
- hll_union
- hll_union_agg
- max
- max_by
- min
- min_by
- multi_distinct_sum
- multi_distinct_count
- percentile_approx
- percentile_cont
- percentile_disc
- retention
- stddev
- stddev_samp
- sum
- variance, variance_pop, var_pop
- var_samp
- window_funnel
- Geographic Functions
- String Functions
- append_trailing_char_if_absent
- ascii
- char
- char_length
- character_length
- concat
- concat_ws
- ends_with
- find_in_set
- group_concat
- hex
- hex_decode_binary
- hex_decode_string
- instr
- lcase
- left
- length
- locate
- lower
- lpad
- ltrim
- money_format
- null_or_empty
- parse_url
- repeat
- replace
- reverse
- right
- rpad
- rtrim
- space
- split
- split_part
- substring_index
- starts_with
- strleft
- strright
- str_to_map
- substring
- trim
- ucase
- unhex
- upper
- url_decode
- url_encode
- Pattern Matching Functions
- JSON Functions
- Overview of JSON functions and operators
- JSON operators
- JSON constructor functions
- JSON query and processing functions
- Bit Functions
- Bitmap Functions
- Array Functions
- all_match
- any_match
- array_agg
- array_append
- array_avg
- array_concat
- array_contains
- array_contains_all
- array_cum_sum
- array_difference
- array_distinct
- array_filter
- array_generate
- array_intersect
- array_join
- array_length
- array_map
- array_max
- array_min
- array_position
- array_remove
- array_slice
- array_sort
- array_sortby
- array_sum
- arrays_overlap
- array_to_bitmap
- cardinality
- element_at
- reverse
- unnest
- Map Functions
- Binary Functions
- cast function
- hash function
- Cryptographic Functions
- Math Functions
- Pattern Matching Functions
- Percentile Functions
- Scalar Functions
- Struct Functions
- Table Functions
- Utility Functions
- AUTO_INCREMENT
- Generated columns
- System variables
- System limits
- Information Schema
- Overview
- be_bvars
- be_cloud_native_compactions
- be_compactions
- character_sets
- collations
- column_privileges
- columns
- engines
- events
- global_variables
- key_column_usage
- load_tracking_logs
- loads
- materialized_views
- partitions
- pipe_files
- pipes
- referential_constraints
- routines
- schema_privileges
- schemata
- session_variables
- statistics
- table_constraints
- table_privileges
- tables
- tables_config
- task_runs
- tasks
- triggers
- user_privileges
- views
- System Metadatabase
- API
- Overview
- Actions
- Clusters
- Create and Manage Clusters
- Query Clusters
- Identity and Access Management
- Organization and Account
- Usage and Billing
- Clusters
- Terraform Provider
- Run scripts
Suspend and resume a CelerData cluster
CelerData allows suspending a cluster to avoid unnecessary costs during idle time. Once your cluster is suspended, CelerData does not charge you with CCUs for your suspended cluster any more. Also, you no longer need to pay your cloud provider for the virtual machines on which your cluster runs.
You can resume your suspended cluster if you need it again.
Suspend a cluster
CelerData provides three suspend methods:
- Manual suspend
- Scheduled suspend
- Auto suspend on idle
Note that when CelerData suspends a cluster, it suspends all of the cluster's warehouses (including the default warehouse) together with the cluster.
Manual suspend
Sign in to the CelerData Cloud BYOC console.
On the Clusters page, click the cluster that you want to suspend.
On the cluster details page, click Manage and choose Suspend cluster.
In the message that appears, click Confirm.
CelerData immediately starts suspending the cluster. This may take a few minutes, during which the cluster stays in the Suspending state. During that period of time, you cannot perform operations such as scaling the cluster, adding warehouses to the cluster, or releasing the cluster. When suspending the cluster is complete, the cluster enters the Suspended state.
NOTE
You can only suspend clusters that are in the Running state. If a cluster is not in the Running state, the Suspend cluster menu item is not displayed.
Scheduled suspend
Sign in to the CelerData Cloud BYOC console.
On the Clusters page, click the cluster that you want to periodically suspend.
On the cluster details page, click the Resource Scheduling tab. Then, click Create scheduling policy in the Scheduling policy section.
In the Create scheduling policy dialog box, specify the name, description, and time zone of the scheduling policy, select the days on which you want the cluster to be off, select the hour at which you want CelerData to automatically suspend the cluster, and then click Submit.
In the Scheduling policy section of the cluster details page, find the scheduling policy you just created, and turn on its switch in the Enabled column to make it take effect.
The cluster will be suspended at the selected hour on every selected day according to the scheduling policy that you created.
Auto suspend on idle
When the Auto Suspend feature is enabled, CelerData monitors the activity levels of the nodes in the cluster. If the nodes stay idle for a specified amount of time, CelerData automatically suspends the cluster.
With the Auto Suspend feature, resources are allocated only when needed. This delivers efficient resource utilization and further reduces costs.
Follow these steps to configure the Auto Suspend feature:
Sign in to the CelerData Cloud BYOC console.
On the Clusters page, click the cluster that you want to suspend when it stays idle.
On the cluster details page, click the Resource Scheduling tab. Then, click Edit in the Auto suspend on idle section.
In the Edit auto suspend on idle dialog box, turn on the switch next to Idle suspend, select the maximum amount of time during which the cluster can stay idle, and then click Submit.
If you want to disable this feature, turn off the switch and click Submit in the dialog box.
Resume a cluster
CelerData provides two resume methods:
- Manual resume
- Scheduled resume
Note that when CelerData resumes a cluster, it resumes only the default warehouse together with the cluster. For the other warehouses created after the cluster deployment, you need to resume them one by one if you need them to run. For more information, see Suspend and resume a warehouse.
Manual resume
Sign in to the CelerData Cloud BYOC console.
On the Clusters page, click the cluster that you want to resume.
On the cluster details page, click Manage and choose Resume cluster.
If the cluster is a classic cluster, CelerData immediately starts resuming the cluster.
If the cluster is an elastic cluster deployed on AWS Cloud, CelerData displays a message stating that only the default warehouse will be resumed and asking you whether you want to resume the cluster. CelerData starts resuming the cluster only after you click Confirm in the message.
Resuming the cluster takes a few minutes, during which the cluster stays in the Resuming state. During that period of time, you cannot perform operations such as scaling the cluster or adding warehouses to the cluster. When resuming the cluster is complete, the cluster enters the Running state.
NOTE
You can only resume clusters that are in the Suspended state. If a cluster is not in the Suspended state, the Resume menu item is not displayed.
Scheduled resume
Sign in to the CelerData Cloud BYOC console.
On the Clusters page, click the cluster that you want to periodically resume.
On the cluster details page, click the Resource Scheduling tab. Then, click Create scheduling policy in the Scheduling policy section.
In the Create scheduling policy dialog box, specify the name, description, and time zone of the scheduling policy, select the days on which you want the cluster to be on, select the hour at which you want CelerData to automatically resume the cluster, and then click Submit.
In the Scheduling policy section of the cluster details page, find the scheduling policy you just created, and turn on its switch in the Enabled column to make it take effect.
The cluster will be resumed at the selected hour on every selected day according to the scheduling policy that you created.
What's more
You can configure a single scheduling policy that controls both scheduled resume and scheduled suspend.
You can also delete a scheduling policy. To achieve this, open the cluster details page, navigate to the Resource Scheduling tab, find the scheduling policy you want to delete, click Delete in its Action column, and then click Delete in the message that appears.