Back to bug 1100567
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Atin Mukherjee | 2014-05-23 06:17:13 UTC | Assignee | vbellur | amukherj |
| Atin Mukherjee | 2014-05-23 06:20:21 UTC | Status | NEW | ON_QA |
| Atin Mukherjee | 2014-05-23 06:36:07 UTC | Fixed In Version | glusterfs-3.6.0.3-1.el6rhs | |
| Doc Text | barrier timeout reconfiguration was not working through volume set command. Investigation revealed the following: Reconfiguration of barrier timeout through gluster volume set shows a success but it never changes the default timeout value which is 120 seconds. After digging into the code deeper, it was found that timeout is never modified in reconfigure() as the first check i.e. whether barrier is already enabled or disabled always fails since barrier option is not modified in this request. Fix --- Introduced notify() in barrier translator which will take care of the rpc request to enable/disable barrier. reconfigure() will simply set barrier enable/disable and timeout options blindly without any validation. | |||
| OS | Unspecified | All | ||
| SATHEESARAN | 2014-05-23 06:58:16 UTC | Target Milestone | --- | RHS 3.0 |
| QA Contact | sdharane | sasundar | ||
| krishnan parthasarathi | 2014-05-23 07:15:55 UTC | CC | kparthas | |
| Nagaprasad Sathyanarayana | 2014-05-23 08:23:07 UTC | Priority | unspecified | high |
| CC | nsathyan | |||
| Sudhir D | 2014-05-27 08:50:17 UTC | CC | sdharane | |
| SATHEESARAN | 2014-05-28 08:39:50 UTC | Status | ON_QA | VERIFIED |
| errata-xmlrpc | 2014-09-22 18:04:04 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2014-09-22 19:39:12 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2014-09-22 15:39:12 UTC | |||
| Rejy M Cyriac | 2015-05-13 16:57:38 UTC | Target Release | --- | RHGS 3.0.0 |
| Target Milestone | RHS 3.0.0 | --- | ||
| Rejy M Cyriac | 2016-09-17 14:38:22 UTC | Sub Component | core | |
| CC | rhs-bugs, storage-qa-internal | |||
| Component | glusterfs | core |
Back to bug 1100567