Bug 1372481
Summary: | [ceph-ansible] : rolling_update got hung in task 'compress the store as much as possible' | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Storage Console | Reporter: | Rachana Patel <racpatel> |
Component: | ceph-ansible | Assignee: | seb |
Status: | CLOSED ERRATA | QA Contact: | Rachana Patel <racpatel> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 2 | CC: | adeza, aschoen, ceph-eng-bugs, gmeno, hnallurv, kdreyer, nthomas, racpatel, rcyriac, rghatvis, sankarshan, seb, vsarmila |
Target Milestone: | --- | ||
Target Release: | 2 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | ceph-ansible-1.0.5-33.el7scon | Doc Type: | Bug Fix |
Doc Text: |
Issuing a command to compact its data store during a rolling upgrade renders the Ceph monitors unresponsive. To avoid this behaviour, skip the command to compact the data store during a rolling upgrade. As a result, the Ceph monitors are responsive.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-10-19 15:22:11 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: | 1357777 |
Description
Rachana Patel
2016-09-01 21:28:12 UTC
Can you give me the state of the cluster prior to run this? Are all the monitors started? Can you try to run the compress command manually on the monitor nodes? I do have one question here. AFAIK, all MON share same db then why do we need to compress on all MONs? We can compress on one MON node and it should work fine, right? Please correct me if I am wrong It's weird that we don't know the root cause of that, even if the compaction is not needed by the upgrade, I think it's a nice to have. I ran the playbook several times and the only case where the compact command hung was the monitor being stopped... I can remove the compact command from the playbook anyway. 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/RHSA-2016:2082 |