Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide CLI access to storage configuration #19505

Closed
stuartcarnie opened this issue Sep 4, 2020 · 0 comments · Fixed by #19506
Closed

Provide CLI access to storage configuration #19505

stuartcarnie opened this issue Sep 4, 2020 · 0 comments · Fixed by #19506
Assignees
Labels
area/2.x OSS 2.0 related issues and PRs

Comments

@stuartcarnie
Copy link
Contributor

stuartcarnie commented Sep 4, 2020

What

It is important that influxd provide access to various TSM and TSI parameters in order to tune its operation.

The following switches should be made available, and correspond to their equivalent 1.x parameters (after dropping the storage- prefix):

--storage-cache-max-memory-size Size                            The maximum size a shard's cache can reach before it starts rejecting writes. (default 1.0 GiB)
--storage-cache-snapshot-memory-size Size                       The size at which the engine will snapshot the cache and write it to a TSM file, freeing up memory. (default 25 MiB)
--storage-cache-snapshot-write-cold-duration Duration           The length of time at which the engine will snapshot the cache and write it to a new TSM file if the shard hasn't received writes or deletes. (default 10m0s)
--storage-compact-full-write-cold-duration Duration             The duration at which the engine will compact all TSM files in a shard if it hasn't received a write or delete. (default 4h0m0s)
--storage-compact-throughput-burst Size                         The rate limit in bytes per second that we will allow TSM compactions to write to disk. (default 48 MiB)
--storage-max-concurrent-compactions int                        The maximum number of concurrent full and level compactions that can run at one time.  A value of 0 results in 50% of runtime.GOMAXPROCS(0) used at runtime.  Any number greater than 0 limits compactions to that value.  This setting does not apply to cache snapshotting.
--storage-max-index-log-file-size Size                          The threshold, in bytes, when an index write-ahead log file will compact into an index file. Lower sizes will cause log files to be compacted more quickly and result in lower heap usage at the expense of write throughput. (default 1.0 MiB)
--storage-series-file-max-concurrent-snapshot-compactions int   The maximum number of concurrent snapshot compactions that can be running at one time across all series partitions in a database.
--storage-series-id-set-cache-size int                          The size of the internal cache used in the TSI index to store previously calculated series results.
--storage-tsm-use-madv-willneed                                 Controls whether we hint to the kernel that we intend to page in mmap'd sections of TSM files.
--storage-validate-keys                                         Validates incoming writes to ensure keys only have valid unicode characters.
--storage-wal-fsync-delay Duration                              The amount of time that a write will wait before fsyncing. A duration greater than 0 can be used to batch up multiple fsync calls. This is useful for slower disks or when WAL write contention is seen. (default 0s)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/2.x OSS 2.0 related issues and PRs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant