-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[pkg/stanza] Data loss before increasing fingerprint to config size in specified state #20745
Labels
Comments
maokitty
added
bug
Something isn't working
needs triage
New item requiring triage
labels
Apr 7, 2023
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
maokitty
changed the title
Data loss before fingerprint increase to config size in specified condition
Data loss before increasing fingerprint to config size in specified state
Apr 7, 2023
djaglowski
changed the title
Data loss before increasing fingerprint to config size in specified state
[pkg/stanza] Data loss before increasing fingerprint to config size in specified state
Apr 7, 2023
Hi @djaglowski , I'm afraid we still need to do something
|
@maokitty, thanks for pointing these issues out. Would you mind opening a new issue for each of them? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component(s)
pkg/stanza, receiver/filelog
What happened?
Description
If two files have the same fingerprint and the fingerprint size is smaller than config, even if they have different bytes in the future, data of one file will be lost.
Steps to Reproduce
Expected Result
no error
Actual Result
Collector version
v.0.73.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
Some idea:
If the fingerprint size is less than the config size, and the old and new fingerprints are from different files, the new file should be read from the beginning.
The text was updated successfully, but these errors were encountered: