140
140
# blocks storage.
141
141
[store_gateway : <store_gateway_config>]
142
142
143
- # The purger_config configures the purger which takes care of delete requests.
144
- [purger : <purger_config>]
145
-
146
143
tenant_federation :
147
144
# If enabled on all Cortex services, queries can be federated across multiple
148
145
# tenants. The tenant IDs involved need to be specified separated by a `|`
@@ -604,8 +601,8 @@ instance_limits:
604
601
The `ingester_config` configures the Cortex ingester.
605
602
606
603
` ` ` yaml
607
- # Configures the Write-Ahead Log (WAL) for the Cortex chunks storage. This
608
- # config is ignored when running the Cortex blocks storage .
604
+ # Configures the Write-Ahead Log (WAL) for the removed Cortex chunks storage.
605
+ # This config is now always ignored .
609
606
walconfig:
610
607
# Enable writing of ingested data into WAL.
611
608
# CLI flag: -ingester.wal-enabled
@@ -2832,9 +2829,9 @@ chunk_tables_provisioning:
2832
2829
The `storage_config` configures where Cortex stores the data (chunks storage engine).
2833
2830
2834
2831
` ` ` yaml
2835
- # The storage engine to use: chunks (deprecated) or blocks .
2832
+ # The storage engine to use: blocks is the only supported option today .
2836
2833
# CLI flag: -store.engine
2837
- [engine: <string> | default = "chunks "]
2834
+ [engine: <string> | default = "blocks "]
2838
2835
2839
2836
aws:
2840
2837
dynamodb:
@@ -3375,93 +3372,6 @@ index_queries_cache_config:
3375
3372
# The CLI flags prefix for this block config is: store.index-cache-read
3376
3373
[fifocache : <fifo_cache_config>]
3377
3374
3378
- delete_store :
3379
- # Store for keeping delete request
3380
- # CLI flag: -deletes.store
3381
- [store : <string> | default = ""]
3382
-
3383
- # Name of the table which stores delete requests
3384
- # CLI flag: -deletes.requests-table-name
3385
- [requests_table_name : <string> | default = "delete_requests"]
3386
-
3387
- table_provisioning :
3388
- # Enables on demand throughput provisioning for the storage provider (if
3389
- # supported). Applies only to tables which are not autoscaled. Supported by
3390
- # DynamoDB
3391
- # CLI flag: -deletes.table.enable-ondemand-throughput-mode
3392
- [enable_ondemand_throughput_mode : <boolean> | default = false]
3393
-
3394
- # Table default write throughput. Supported by DynamoDB
3395
- # CLI flag: -deletes.table.write-throughput
3396
- [provisioned_write_throughput : <int> | default = 1]
3397
-
3398
- # Table default read throughput. Supported by DynamoDB
3399
- # CLI flag: -deletes.table.read-throughput
3400
- [provisioned_read_throughput : <int> | default = 300]
3401
-
3402
- write_scale :
3403
- # Should we enable autoscale for the table.
3404
- # CLI flag: -deletes.table.write-throughput.scale.enabled
3405
- [enabled : <boolean> | default = false]
3406
-
3407
- # AWS AutoScaling role ARN
3408
- # CLI flag: -deletes.table.write-throughput.scale.role-arn
3409
- [role_arn : <string> | default = ""]
3410
-
3411
- # DynamoDB minimum provision capacity.
3412
- # CLI flag: -deletes.table.write-throughput.scale.min-capacity
3413
- [min_capacity : <int> | default = 3000]
3414
-
3415
- # DynamoDB maximum provision capacity.
3416
- # CLI flag: -deletes.table.write-throughput.scale.max-capacity
3417
- [max_capacity : <int> | default = 6000]
3418
-
3419
- # DynamoDB minimum seconds between each autoscale up.
3420
- # CLI flag: -deletes.table.write-throughput.scale.out-cooldown
3421
- [out_cooldown : <int> | default = 1800]
3422
-
3423
- # DynamoDB minimum seconds between each autoscale down.
3424
- # CLI flag: -deletes.table.write-throughput.scale.in-cooldown
3425
- [in_cooldown : <int> | default = 1800]
3426
-
3427
- # DynamoDB target ratio of consumed capacity to provisioned capacity.
3428
- # CLI flag: -deletes.table.write-throughput.scale.target-value
3429
- [target : <float> | default = 80]
3430
-
3431
- read_scale :
3432
- # Should we enable autoscale for the table.
3433
- # CLI flag: -deletes.table.read-throughput.scale.enabled
3434
- [enabled : <boolean> | default = false]
3435
-
3436
- # AWS AutoScaling role ARN
3437
- # CLI flag: -deletes.table.read-throughput.scale.role-arn
3438
- [role_arn : <string> | default = ""]
3439
-
3440
- # DynamoDB minimum provision capacity.
3441
- # CLI flag: -deletes.table.read-throughput.scale.min-capacity
3442
- [min_capacity : <int> | default = 3000]
3443
-
3444
- # DynamoDB maximum provision capacity.
3445
- # CLI flag: -deletes.table.read-throughput.scale.max-capacity
3446
- [max_capacity : <int> | default = 6000]
3447
-
3448
- # DynamoDB minimum seconds between each autoscale up.
3449
- # CLI flag: -deletes.table.read-throughput.scale.out-cooldown
3450
- [out_cooldown : <int> | default = 1800]
3451
-
3452
- # DynamoDB minimum seconds between each autoscale down.
3453
- # CLI flag: -deletes.table.read-throughput.scale.in-cooldown
3454
- [in_cooldown : <int> | default = 1800]
3455
-
3456
- # DynamoDB target ratio of consumed capacity to provisioned capacity.
3457
- # CLI flag: -deletes.table.read-throughput.scale.target-value
3458
- [target : <float> | default = 80]
3459
-
3460
- # Tag (of the form key=value) to be added to the tables. Supported by
3461
- # DynamoDB
3462
- # CLI flag: -deletes.table.tags
3463
- [tags : <map of string to string> | default = ]
3464
-
3465
3375
grpc_store :
3466
3376
# Hostname or IP of the gRPC store instance.
3467
3377
# CLI flag: -grpc-store.server-address
@@ -3473,16 +3383,17 @@ grpc_store:
3473
3383
The `flusher_config` configures the WAL flusher target, used to manually run one-time flushes when scaling down ingesters.
3474
3384
3475
3385
` ` ` yaml
3476
- # Directory to read WAL from (chunks storage engine only).
3386
+ # Has no effect: directory to read WAL from (chunks storage engine only).
3477
3387
# CLI flag: -flusher.wal-dir
3478
3388
[wal_dir: <string> | default = "wal"]
3479
3389
3480
- # Number of concurrent goroutines flushing to storage (chunks storage engine
3481
- # only).
3390
+ # Has no effect: number of concurrent goroutines flushing to storage (chunks
3391
+ # storage engine only).
3482
3392
# CLI flag: -flusher.concurrent-flushes
3483
3393
[concurrent_flushes: <int> | default = 50]
3484
3394
3485
- # Timeout for individual flush operations (chunks storage engine only).
3395
+ # Has no effect: timeout for individual flush operations (chunks storage engine
3396
+ # only).
3486
3397
# CLI flag: -flusher.flush-op-timeout
3487
3398
[flush_op_timeout: <duration> | default = 2m]
3488
3399
@@ -5492,31 +5403,6 @@ sharding_ring:
5492
5403
[sharding_strategy: <string> | default = "default"]
5493
5404
` ` `
5494
5405
5495
- # ## `purger_config`
5496
-
5497
- The `purger_config` configures the purger which takes care of delete requests.
5498
-
5499
- ` ` ` yaml
5500
- # Enable purger to allow deletion of series. Be aware that Delete series feature
5501
- # is still experimental
5502
- # CLI flag: -purger.enable
5503
- [enable: <boolean> | default = false]
5504
-
5505
- # Number of workers executing delete plans in parallel
5506
- # CLI flag: -purger.num-workers
5507
- [num_workers: <int> | default = 2]
5508
-
5509
- # Name of the object store to use for storing delete plans
5510
- # CLI flag: -purger.object-store-type
5511
- [object_store_type: <string> | default = ""]
5512
-
5513
- # Allow cancellation of delete request until duration after they are created.
5514
- # Data would be deleted only after delete requests have been older than this
5515
- # duration. Ideally this should be set to at least 24h.
5516
- # CLI flag: -purger.delete-request-cancel-period
5517
- [delete_request_cancel_period: <duration> | default = 24h]
5518
- ` ` `
5519
-
5520
5406
# ## `s3_sse_config`
5521
5407
5522
5408
The `s3_sse_config` configures the S3 server-side encryption. The supported CLI flags `<prefix>` used to reference this config block are :
0 commit comments