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

Chunk utilization is incorrect for transferred chunks #1412

Closed
rfratto opened this issue Dec 13, 2019 · 3 comments · Fixed by #1946
Closed

Chunk utilization is incorrect for transferred chunks #1412

rfratto opened this issue Dec 13, 2019 · 3 comments · Fixed by #1946
Labels
component/loki keepalive An issue or PR that will be kept alive and never marked as stale. type/bug Somehing is not working as expected

Comments

@rfratto
Copy link
Member

rfratto commented Dec 13, 2019

We first noticed that loki_ingester_chunk_utilization_sum was being reported as NaN. After some investigation, it seems clear that the only cause would be transferred chunks: they don't have an uncompressed size, block size, target size, or cut block size set. This will always result in a division by zero when calculating utilization.

To Reproduce
Steps to reproduce the behavior:

  1. Started Loki (v1.2.0). Make sure to launch in microservices mode.
  2. Restart the ingesters.
  3. Force a flush across the new ingesters.
  4. Observe the value for loki_ingester_chunk_utilization_sum.

Expected behavior
The value should not be NaN.

@rfratto
Copy link
Member Author

rfratto commented Dec 13, 2019

This should probably wait for #1411 to get merged first.

@rfratto
Copy link
Member Author

rfratto commented Dec 13, 2019

Another effect of this is that the first chunk per stream after a transfer be very underutilized and only be able to store up to 10 log lines before running out of space.

@stale
Copy link

stale bot commented Jan 12, 2020

This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale A stale issue or PR that will automatically be closed. label Jan 12, 2020
@rfratto rfratto added the keepalive An issue or PR that will be kept alive and never marked as stale. label Jan 12, 2020
@stale stale bot removed the stale A stale issue or PR that will automatically be closed. label Jan 12, 2020
@chaudum chaudum added the type/bug Somehing is not working as expected label Jun 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/loki keepalive An issue or PR that will be kept alive and never marked as stale. type/bug Somehing is not working as expected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants