Bug 1838153
| Summary: | The ZeroRedundancy is not honored during upgrade clo-first | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Anping Li <anli> |
| Component: | Logging | Assignee: | Jeff Cantrill <jcantril> |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 4.5 | CC: | aos-bugs, ewolinet, lvlcek |
| Target Milestone: | --- | ||
| Target Release: | 4.6.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-10-27 16:00:21 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: | |||
| Bug Blocks: | 1843738 | ||
|
Description
Anping Li
2020-05-20 14:33:17 UTC
I can reproduce it. Tt is strange, when nodeCount=2, redundancyPolicy: "ZeroRedundancy", No Replicas shards. Interestingly, After upgrade, the ES doesn't allocate replicas to the indices infra-write and app-write any more. + oc exec -c elasticsearch elasticsearch-cdm-xv9zo8gz-1-6fcc5d4998-lpb9g -- es_util --query=_cat/shards project.logflatx.b1c056f0-4405-45bd-8cea-76338862d9ed.2020.05.23 0 p STARTED 746 543kb 10.129.2.63 elasticsearch-cdm-xv9zo8gz-1 .security 0 p STARTED 5 30.8kb 10.129.2.63 elasticsearch-cdm-xv9zo8gz-1 project.logjsonx.9b993d19-0818-4232-8940-cf06a750e965.2020.05.23 0 p STARTED 746 485.3kb 10.129.2.63 elasticsearch-cdm-xv9zo8gz-1 app-write 1 p STARTED 182 414kb 10.129.2.63 elasticsearch-cdm-xv9zo8gz-1 app-write 4 p STARTED 166 269.1kb 10.129.2.63 elasticsearch-cdm-xv9zo8gz-1 app-write 2 p STARTED 171 317.8kb 10.129.2.63 elasticsearch-cdm-xv9zo8gz-1 app-write 3 p STARTED 165 331.2kb 10.129.2.63 elasticsearch-cdm-xv9zo8gz-1 app-write 0 p STARTED 176 259.9kb 10.129.2.63 elasticsearch-cdm-xv9zo8gz-1 .kibana.647a750f1787408bf50088234ec0edd5a6a9b2ac 0 p STARTED 4 64.2kb 10.129.2.63 elasticsearch-cdm-xv9zo8gz-1 .operations.2020.05.23 0 p STARTED 31341 30.9mb 10.129.2.63 elasticsearch-cdm-xv9zo8gz-1 .searchguard 0 p STARTED 5 84.6kb 10.129.2.63 elasticsearch-cdm-xv9zo8gz-1 infra-write 1 p STARTED 18268 24.3mb 10.129.2.63 elasticsearch-cdm-xv9zo8gz-1 infra-write 4 p STARTED 18078 24mb 10.129.2.63 elasticsearch-cdm-xv9zo8gz-1 infra-write 2 p STARTED 18233 24.7mb 10.129.2.63 elasticsearch-cdm-xv9zo8gz-1 infra-write 3 p STARTED 18091 24.4mb 10.129.2.63 elasticsearch-cdm-xv9zo8gz-1 infra-write 0 p STARTED 18252 24.6mb 10.129.2.63 elasticsearch-cdm-xv9zo8gz-1 .kibana 0 p STARTED 1 3.2kb 10.129.2.63 elasticsearch-cdm-xv9zo8gz-1 *** Bug 1843596 has been marked as a duplicate of this bug. *** @Lukas, Move to verify as the indices replicas rollback after upgrade. and no function error. 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 (OpenShift Container Platform 4.6 GA Images), 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-2020:4196 |