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.

Sign up for GitHub

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

Jump to bottom

RT segment size does NOT follow "realtime.segment.flush.desired.size" parameter #10060

Closed
sajjad-moradi opened this issue Jan 5, 2023 · 1 comment
Closed

RT segment size does NOT follow "realtime.segment.flush.desired.size" parameter #10060

sajjad-moradi opened this issue Jan 5, 2023 · 1 comment

Comments

@sajjad-moradi
Copy link
Contributor

Segments of realtime tables which have "flush.desired.size" configured do not honor the specified value (reported here). Here are actual sizes for some segments for which the desired size is 500M.
image
@sajjad-moradi
Copy link
Contributor Author

This is a false alarm. The segment size reported here are for "tar.gz" version of the segments, not the original ones. I just double checked one of our tables and un-tarred a segment; the tar.gz was ~250MB while the untar segment size was ~1GB which is what the desired segment size param is for this table.

@sajjad-moradi sajjad-moradi removed the bug label Jan 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sajjad-moradi