How to change the size of object storage chunk?

[btdan]

Hello.
I want to change the size of chunk which is stored in object storage.
For example, there are 6 chunks for every minute in object storage, and I want to store one chunk for each minute. just as shown below:

I have modified the configuration as follow:

    ingester:
      wal:
        enabled: true
        dir: /tmp/wal
      lifecycler:
        ring:
          replication_factor: 1
          kvstore:
            consul:
              consistent_reads: false
              host: consul:8500
              http_client_timeout: 20s
              watch_burst_size: 1
              watch_rate_limit: 1
            store: consul
        final_sleep: 0s
      chunk_idle_period: 12h
      max_chunk_age: 12h
      chunk_retain_period: 1m
      max_transfer_retries: 0
      chunk_target_size: 12582912
      chunk_encoding: snappy

However, it does not work at all. And that is to say, the size of each chunk is still 1.8MB
Can anyone be kind to tell me how to solve this problem?
Thanks very much.

[liguozhong]

‘chunk_block_size’

hi, there are 2 configurations that need to be modified at the same time, you can refer to my configuration and set one of the configurations to 0, so that you can simplify this configuration.

ingester:
  chunk_block_size: 262140
  chunk_target_size: 0
  max_chunk_age: 1h

If this helps you that would be great.

[stale]

Hi! This issue has been automatically marked as stale because it has not had any
activity in the past 30 days.

We use a stalebot among other tools to help manage the state of issues in this project.
A stalebot can be very useful in closing issues in a number of cases; the most common
is closing issues or PRs where the original reporter has not responded.

Stalebots are also emotionless and cruel and can close issues which are still very relevant.

If this issue is important to you, please add a comment to keep it open. More importantly, please add a thumbs-up to the original issue entry.

We regularly sort for closed issues which have a stale label sorted by thumbs up.

We may also:

• Mark issues as revivable if we think it's a valid issue but isn't something we are likely
  to prioritize in the future (the issue will still remain closed).
• Add a keepalive label to silence the stalebot if the issue is very common/popular/important.

We are doing our best to respond, organize, and prioritize all issues but it can be a challenging task,
our sincere apologies if you find yourself at the mercy of the stalebot.