Bug 975399
| Summary: | [RHS-C] When glusterd is restarted, Server Status is not changing to "UP" from "Non-Operational" immediately | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Prasanth <pprakash> |
| Component: | rhsc | Assignee: | Sahina Bose <sabose> |
| Status: | CLOSED WONTFIX | QA Contact: | RHS-C QE <rhsc-qe-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 2.1 | CC: | asriram, dpati, knarra, mmahoney, mmccune, rhs-bugs, sabose, ssampat |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
When gluster daemon service is restarted, the host status does not change to UP from Non-Operational immediately in the Red Hat Storage Console. There would be a 5 minute interval for auto-recovery operations which detect changes in Non-Operational hosts.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-12-28 06:57:35 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: | 1035040 | ||
|
Description
Prasanth
2013-06-18 11:27:46 UTC
GlusterMonotoringStrategy has been implemented to check gluster capabilities. When host state is Non-Operational, it is set back to UP via the AutoRecoveryManager. The interval of it can be configured via ConfigValues.AutoRecoverySchedule. Currently set to run every 5 mins. This can be changed to run for shorter duration. Please check by changing the ConfigValues.AutoRecoverySchedule (In reply to Sahina Bose from comment #4) > Please check by changing the ConfigValues.AutoRecoverySchedule Is it user configurable? If so, can you tell me where can I find and edit this configuration parameter to verify this bug? The config value is currently not exposed. Will be posting a patch to do that. You can change value meantime, by psql engine postgres -c "update vdc_options set option_value = '0/5 * * * * ?' where option_name = 'AutoRecoverySchedule';" Changing a database value is not an end-user solution. Please set to ON_QA once there is an configuration solution that would be used by an end-user. User can manually activate the host, if they know that the glusterd has already come-up. This is a framework limitation and for the time being, we can not enhance this to synch up immediately after the auto-recovery. It happens every 5 min (default) and the user would not see the update in that 5 min window. Hence need to move it out of Corbett. There is a limitation on the framework for 5 min auto recovery operation... ( kind of synch up )... Need to take it out of Corbett Please review the edited Doc Text and sign off. Doctext ok RHSC 2.1 is EOLed and we don't have any plan to fix this issue. If you think, this is an important bug to be addressed, pls. re-open it on the latest release. I will go ahead and "CLOSE" this bug for this release. |