Bug 1477513
| Summary: | [3.4] 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.4.1 | CC: | aos-bugs, nhosoi, pportant, pweil, rmeggins, rromerom, xiazhao |
| Target Milestone: | --- | ||
| Target Release: | 3.4.z | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | logging-fluentd-docker-3.4.1-27 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: Fluentd buffers the logs which are not immediately flushed to the storage such as Elaticsearch. The buffers are placed in memory, by default.
Consequence: If there are some issue and the fluentd is forced to quit, the buffered logs would have been lost when the fluentd is restarted.
Fix: Instead of placing the buffers in memory, they are configured on the permanent storage.
Result: Even if the fluentd is accidentally restarted, the buffered logs would not be lost.
|
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, 1477515, 1483114 | ||
| Bug Blocks: | |||
|
Comment 1
Noriko Hosoi
2017-09-19 21:20:11 UTC
Pull request for template. https://github.com/openshift/origin-aggregated-logging/pull/680 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.4.1-27 5772acf0562d 7 days ago 235.7 MB Test env: # openshift version openshift v3.4.1.44.22 kubernetes v1.4.0+776c994 etcd 3.1.0-rc.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 |