Bug 1333932
| Summary: | Enable etcd watch cache for origin types | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Dan McPherson <dmcphers> |
| Component: | Master | Assignee: | Jordan Liggitt <jliggitt> |
| Status: | CLOSED ERRATA | QA Contact: | weiwei jiang <wjiang> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.2.0 | CC: | adellape, aos-bugs, jokerman, mmccomas, wsun |
| Target Milestone: | --- | ||
| Target Release: | 3.2.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
The etcd watch cache was enabled in a previous release for Kubernetes resource types. This bug fix enables the etcd watch cache for all OpenShift resource types, as well.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-06-27 15:06:52 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: | |||
|
Description
Dan McPherson
2016-05-06 17:26:53 UTC
Checked with atomic-openshift-3.2.1.1-1.git.0.96f9555.el7.x86_64 and saw some related info in the log like this: Jun 07 22:51:28 openshift-106.lab.eng.nay.redhat.com atomic-openshift-master[67697]: I0607 22:51:28.415467 67697 configgetter.go:127] using watch cache storage (capac ity=1000) for policies Jun 07 22:51:28 openshift-106.lab.eng.nay.redhat.com atomic-openshift-master[67697]: I0607 22:51:28.416160 67697 configgetter.go:127] using watch cache storage (capac ity=1000) for policybindings Jun 07 22:51:28 openshift-106.lab.eng.nay.redhat.com atomic-openshift-master[67697]: I0607 22:51:28.416560 67697 configgetter.go:127] using watch cache storage (capac ity=1000) for clusterpolicies .... And for regression part, no issues found related with this fix till now. So move to verified. 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-2016:1343 |