github.com/muhammadn/cortex@v1.9.1-0.20220510110439-46bb7000d03d/docs/configuration/single-process-config-blocks-gossip-1.yaml (about)

     1  
     2  # Configuration for running Cortex in single-process mode.
     3  # This should not be used in production.  It is only for getting started
     4  # and development.
     5  
     6  # Disable the requirement that every request to Cortex has a
     7  # X-Scope-OrgID header. `fake` will be substituted in instead.
     8  auth_enabled: false
     9  
    10  server:
    11    http_listen_port: 9109
    12    grpc_listen_port: 9195
    13  
    14    # Configure the server to allow messages up to 100MB.
    15    grpc_server_max_recv_msg_size: 104857600
    16    grpc_server_max_send_msg_size: 104857600
    17    grpc_server_max_concurrent_streams: 1000
    18  
    19  distributor:
    20    shard_by_all_labels: true
    21    pool:
    22      health_check_ingesters: true
    23  
    24  ingester_client:
    25    grpc_client_config:
    26      # Configure the client to allow messages up to 100MB.
    27      max_recv_msg_size: 104857600
    28      max_send_msg_size: 104857600
    29      grpc_compression: gzip
    30  
    31  ingester:
    32    lifecycler:
    33      # The address to advertise for this ingester.  Will be autodiscovered by
    34      # looking up address on eth0 or en0; can be specified if this fails.
    35      address: 127.0.0.1
    36      # Defaults to hostname, but we run both ingesters in this demonstration on the same machine.
    37      id: "Ingester 1"
    38  
    39      # We don't want to join immediately, but wait a bit to see other ingesters and their tokens first.
    40      # It can take a while to have the full picture when using gossip
    41      join_after: 10s
    42  
    43      # To avoid generating same tokens by multiple ingesters, they can "observe" the ring for a while,
    44      # after putting their own tokens into it. This is only useful when using gossip, since multiple
    45      # ingesters joining at the same time can have conflicting tokens if they don't see each other yet.
    46      observe_period: 10s
    47      min_ready_duration: 0s
    48      final_sleep: 5s
    49      num_tokens: 512
    50  
    51      # Use an in memory ring store, so we don't need to launch a Consul.
    52      ring:
    53        kvstore:
    54          store: memberlist
    55  
    56        replication_factor: 1
    57  
    58  memberlist:
    59    bind_port: 7946
    60    join_members:
    61      - localhost:7947
    62    abort_if_cluster_join_fails: false
    63  
    64  storage:
    65    engine: blocks
    66  
    67  blocks_storage:
    68    tsdb:
    69      dir: /tmp/cortex/tsdb-ing1
    70  
    71    bucket_store:
    72      sync_dir: /tmp/cortex/tsdb-sync-querier1
    73  
    74    # This is where Cortex uploads generated blocks. Queriers will fetch blocks from here as well.
    75    # Cortex of course supports multiple options (S3, GCS, Azure), but for demonstration purposes
    76    # we only use shared directory.
    77    backend: filesystem # s3, gcs, azure, swift or filesystem are valid options
    78    filesystem:
    79      dir: /tmp/cortex/storage
    80  
    81  store_gateway:
    82    sharding_enabled: true
    83    sharding_ring:
    84      kvstore:
    85        store: memberlist
    86  
    87  frontend_worker:
    88    match_max_concurrent: true
    89  
    90  ruler:
    91    enable_api: true
    92    enable_sharding: true
    93    ring:
    94      num_tokens: 512
    95      kvstore:
    96        store: memberlist
    97  
    98  ruler_storage:
    99    backend: local
   100    local:
   101      directory: /tmp/cortex/rules