You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, redpanda fallocates 32M whenever necessary. We currently inject one raft message into every partition when a topic is created. If I create a topic with 1000 partitions, 32G of my disk is eaten.
The fallocate was chosen to be 32M, and large sizes are beneficial, but it may be useful to have this size be a configuration option.
Today, redpanda
fallocate
s 32M whenever necessary. We currently inject one raft message into every partition when a topic is created. If I create a topic with 1000 partitions, 32G of my disk is eaten.The fallocate was chosen to be 32M, and large sizes are beneficial, but it may be useful to have this size be a configuration option.
The fallocate size is already an option internally: https://github.com/vectorizedio/redpanda/blob/dev/src/v/storage/segment_appender.cc#L325
"""
so the disk_log_impl has the info, we really just need to expand the ctor here: https://github.com/vectorizedio/redpanda/blob/dev/src/v/storage/segment.h#L68-L74
"""
This can be a new field in the redpanda section of redpanda.yaml that is used if present, else defaults to 32M if not.
The text was updated successfully, but these errors were encountered: