Bug 1477515
| Summary: | [3.5] Data loss of logs can occur if fluentd pod is terminated/restarted when Elasticsearch is unavailable | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ruben Romero Montes <rromerom> |
| Component: | Logging | Assignee: | Noriko Hosoi <nhosoi> |
| Status: | CLOSED ERRATA | QA Contact: | Xia Zhao <xiazhao> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 3.5.1 | CC: | aos-bugs, jcantril, nhosoi, pportant, pweil, rmeggins, rromerom, xiazhao |
| Target Milestone: | --- | ||
| Target Release: | 3.5.z | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | logging-fluentd-docker-3.5.0-31 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: Messages are read into fluentds memory buffer and are lost if the pod is restarted because fluentd considers them read but they have not been pushed to storage
Consequence: Any message not stored but already read by fluentd is lost
Fix: Replace the memory buffer with a file based buffer
Result: File buffered messages are pushed to storage once fluentd restarts
|
Story Points: | --- |
| Clone Of: | 1460749 | Environment: | |
| Last Closed: | 2017-10-25 13:04:36 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1460749, 1483114 | ||
| Bug Blocks: | 1477513 | ||
|
Comment 1
Noriko Hosoi
2017-09-19 21:20:01 UTC
Pull request for openshift-ansible. https://github.com/openshift/openshift-ansible/pull/5528 It's fixed, currently didn't meet data loss of logs any more when fluentd is restarted: Verification steps: 1. Deploy logging stacks on openshift 2. Creat one project to populate logs. 3. Stop fluentd pods, and note down the last project logs in kibana 4. Wait for a while, and restart fluentd pods. 5. Check the subsequent logs after step 3, no logs is missing. 6. Repeat step 3 to 5, make sure no log is missing. Image tested with: logging-fluentd 3.5.0-31 604adb699900 6 days ago 235.8 MB Test env: # openshift version openshift v3.5.5.31.27 kubernetes v1.5.2+43a9be4 etcd 3.1.0 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:3049 |