[COMPASS-7337] Unable to decompress log file while Compass is still running Created: 11/Oct/23 Updated: 27/Oct/23 Resolved: 18/Oct/23 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Logging |
| Affects Version/s: | None |
| Fix Version/s: | No version |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Jeffrey Yemin | Assignee: | Unassigned |
| Resolution: | Works as Designed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
OS: OSX |
||
| Documentation Changes: | Not Needed |
| Description |
Problem Statement/RationaleWhat is going wrong? What action would you like the Engineering team to take? The "current" Compass log file is not readable until Compass is shut down. Please be sure to attach relevant logs with any sensitive data redacted. Steps to ReproduceHow could an engineer replicate the issue you’re reporting?
Expected ResultsWhat do you expect to happen? The log file can be uncompressed while Compass is still running Actual ResultsWhat do you observe is happening? I get an error:
After shutting down Compass, I can uncompress the file. Additional NotesAny additional information that may be useful to include. |
| Comments |
| Comment by Le Roux Bodenstein [ 12/Oct/23 ] | |
|
anna.henningsen@mongodb.com recently explained this to me: https://mongodb.slack.com/archives/G2L10JAV7/p1695118200772879?thread_ts=1695025789.325329&cid=G2L10JAV7 > Sorry to disappoint, but no, they’re truncated, not corrupt. > That the gzip CLI on macOS can’t unzip them is the tool’s fault (and I wouldn’t be surprised if there was actually some way of overriding this behavior, I think it’s just extra integrity checks that get in the way), not Compass’s. GNU gzip and Node.js can handle these files just fine. > This is kind of an inherent problem with using compression on files that are still being written at the time where they were copied/uploaded/etc.; we do cleanly close the files when Compass exits, but that’s not something that users wait for a lot of the time. >> Can we be sure these files contain every line? >> how compression would flush all output yet still do compression The way we usually uncompress these:
|