# test name 
name: "gc_unsafe_destroy_range"
creator: "zhenjing"
# type is the type of the test, supported type: prepare / test
# we will run the prepare tests before all test tests
type: "test"
tags:
  - scan

environment:
  # machine resources
  resources:
    limits:
      cpu: 1000m
      memory: 2Gi
    requests:
      cpu: 500m
      memory: 1Gi
  # image is a docker execution image for running test
  # default image: hub.pingcap.net/schrodinger/agent:latest
  # image: hub.pingcap.net/schrodinger/agent:latest

  # execution arguments
  args: ""

# manual for users
manual:
  # description is to introduce the test purpose and instructions for this case.
  description: |-
    When dropping table/index in TiDB, TiDB will use TiKV's UnsafeDestroyRange API to reclaim
    disk space. This case ensures normal data is never broken by UnsafeDestroyRange.
  # describe the purpose of the parameters and optional values
  parameters: |-
    db: the name of the created database
    concurrency: concurrency of sql.DB. default 200
    time: time limit (in minutes) to run the test. pass 0 to run forever. no less than 60. default: 60
    max-table-size: max size of each table. default: 10000
  # notes is to list all matters which need to be noted
  # eg: the special requirements of the test environment
  notes: |-
    If some jobs runs for longer time than gc_life_time, the case may fail.