Back to bug 1401969
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Nag Pavan Chilakam | 2016-12-07 10:40:53 UTC | CC | nchilaka | |
| RamaKasturi | 2017-04-10 12:05:38 UTC | Blocks | 1411323 | |
| Sahina Bose | 2017-04-18 05:59:24 UTC | Priority | unspecified | high |
| CC | ravishankar, sabose | |||
| Blocks | 1433896 | |||
| Flags | needinfo?(ravishankar) | |||
| SATHEESARAN | 2017-06-16 07:53:15 UTC | CC | sasundar | |
| Hardware | Unspecified | x86_64 | ||
| QA Contact | ksandha | sasundar | ||
| OS | Unspecified | Linux | ||
| SATHEESARAN | 2017-06-16 08:05:47 UTC | Depends On | 1439657 | |
| Atin Mukherjee | 2017-06-27 11:50:14 UTC | CC | amukherj | |
| Atin Mukherjee | 2017-06-27 11:58:59 UTC | Whiteboard | 3.3.0-devel-freeze-exception | |
| Ravishankar N | 2017-06-28 06:16:04 UTC | Assignee | ravishankar | ksubrahm |
| Flags | needinfo?(ravishankar) | |||
| Rahul Hinduja | 2017-06-28 07:21:12 UTC | CC | rhinduja | |
| Blocks | 1417147 | |||
| Alok | 2017-06-28 09:46:59 UTC | CC | asrivast | |
| Rejy M Cyriac | 2017-06-28 09:47:33 UTC | Target Release | --- | RHGS 3.3.0 |
| CC | rcyriac | |||
| Laura Bailey | 2017-06-29 05:46:42 UTC | Flags | needinfo?(sasundar) | |
| Atin Mukherjee | 2017-07-06 12:55:11 UTC | Status | NEW | ASSIGNED |
| Rejy M Cyriac | 2017-07-14 09:51:45 UTC | Keywords | ZStream | |
| Target Release | RHGS 3.3.0 | --- | ||
| Rejy M Cyriac | 2017-07-14 09:54:13 UTC | Blocks | 1417147 | |
| SATHEESARAN | 2017-07-14 11:05:06 UTC | Flags | needinfo?(sasundar) | |
| Atin Mukherjee | 2017-07-27 11:48:22 UTC | Blocks | 1475687 | |
| Rejy M Cyriac | 2017-08-04 19:11:25 UTC | Whiteboard | 3.3.0-devel-freeze-exception | |
| Karthik U S | 2017-08-16 11:52:39 UTC | Depends On | 1482064 | |
| Karthik U S | 2017-08-30 05:12:24 UTC | Status | ASSIGNED | POST |
| Atin Mukherjee | 2017-09-01 07:25:05 UTC | Keywords | ZStream | |
| Blocks | 1475687 | |||
| Sunil Kumar Acharya | 2017-11-03 08:56:01 UTC | CC | sheggodu | |
| Blocks | 1503134 | |||
| Red Hat Bugzilla Rules Engine | 2017-11-13 15:35:37 UTC | Target Release | --- | RHGS 3.4.0 |
| Karthik U S | 2017-11-22 13:02:36 UTC | Depends On | 1516313 | |
| Atin Mukherjee | 2017-11-27 13:23:05 UTC | Status | POST | MODIFIED |
| Karthik U S | 2017-12-15 12:30:53 UTC | Status | MODIFIED | POST |
| Sunil Kumar Acharya | 2018-01-15 10:00:16 UTC | Status | POST | MODIFIED |
| Atin Mukherjee | 2018-01-17 10:34:36 UTC | Status | MODIFIED | ON_QA |
| Fixed In Version | glusterfs-3.12.2-2 | |||
| PnT Account Manager | 2018-02-08 00:13:59 UTC | CC | asrivast | |
| Bipin Kunal | 2018-03-12 09:40:48 UTC | CC | bkunal | |
| Karthik U S | 2018-03-27 09:53:51 UTC | Doc Text | In an arbiter configuration, if bricks were going down in a particular order while parallel IOs are going on, leading to arbiter becoming source for data heal and data unavailability. Since arbiter does not contain any data, it could not be a source for data heal. This bug fixes the issue, by not marking the arbiter brick as source even if the bricks are going down in any order. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Ravishankar N | 2018-04-11 15:12:34 UTC | Depends On | 1566131 | |
| Rejy M Cyriac | 2018-07-03 06:16:00 UTC | Blocks | 1411323 | |
| Srijita Mukherjee | 2018-08-27 06:38:40 UTC | CC | ksubrahm, srmukher | |
| Doc Text | In an arbiter configuration, if bricks were going down in a particular order while parallel IOs are going on, leading to arbiter becoming source for data heal and data unavailability. Since arbiter does not contain any data, it could not be a source for data heal. This bug fixes the issue, by not marking the arbiter brick as source even if the bricks are going down in any order. | Previously, when bricks went down in a particular order while parallel IOs are going on, arbiter became the source for data heal and data unavailability. With this fix, arbiter brick will not be considered as the source as it does not contain any data. | ||
| Flags | needinfo?(ksubrahm) | |||
| Karthik U S | 2018-08-27 09:42:17 UTC | Doc Text | Previously, when bricks went down in a particular order while parallel IOs are going on, arbiter became the source for data heal and data unavailability. With this fix, arbiter brick will not be considered as the source as it does not contain any data. | Previously, when bricks went down in a particular order while parallel IOs are going on, arbiter became the source for data heal. This will lead to data unavailability since the arbiter brick won't contain any data. With this fix, arbiter brick will not be marked as the source for data heal. |
| Flags | needinfo?(ksubrahm) | |||
| SATHEESARAN | 2018-08-27 09:52:38 UTC | Status | ON_QA | VERIFIED |
| Srijita Mukherjee | 2018-09-03 15:38:28 UTC | Doc Text | Previously, when bricks went down in a particular order while parallel IOs are going on, arbiter became the source for data heal. This will lead to data unavailability since the arbiter brick won't contain any data. With this fix, arbiter brick will not be marked as the source for data heal. | Previously, when bricks went down in a particular order while parallel I/O was in progress, the arbiter brick became the source for data heal. This led to data being unavailable, since arbiter bricks store only metadata. With this fix, arbiter bricks are not considered data sources in this situation. |
| Flags | needinfo?(ksubrahm) | |||
| Karthik U S | 2018-09-03 16:02:47 UTC | Doc Text | Previously, when bricks went down in a particular order while parallel I/O was in progress, the arbiter brick became the source for data heal. This led to data being unavailable, since arbiter bricks store only metadata. With this fix, arbiter bricks are not considered data sources in this situation. | Previously, when bricks went down in a particular order while parallel I/O was in progress, the arbiter brick became the source for data heal. This led to data being unavailable, since arbiter bricks store only metadata. With this fix, arbiter brick won't be marked as source for data in these situations. |
| Flags | needinfo?(ksubrahm) | |||
| Srijita Mukherjee | 2018-09-03 16:08:48 UTC | Doc Text | Previously, when bricks went down in a particular order while parallel I/O was in progress, the arbiter brick became the source for data heal. This led to data being unavailable, since arbiter bricks store only metadata. With this fix, arbiter brick won't be marked as source for data in these situations. | Previously, when bricks went down in a particular order while parallel I/O was in progress, the arbiter brick became the source for data heal. This led to data being unavailable, since arbiter bricks store only metadata. With this fix, arbiter bricks are not considered data sources in this situation. |
| Flags | needinfo?(ksubrahm) | |||
| Karthik U S | 2018-09-03 16:16:38 UTC | Flags | needinfo?(ksubrahm) | |
| Srijita Mukherjee | 2018-09-03 17:14:25 UTC | Doc Text | Previously, when bricks went down in a particular order while parallel I/O was in progress, the arbiter brick became the source for data heal. This led to data being unavailable, since arbiter bricks store only metadata. With this fix, arbiter bricks are not considered data sources in this situation. | Previously, when bricks went down in a particular order while parallel I/O was in progress, the arbiter brick became the source for data heal. This led to data being unavailable, since arbiter bricks store only metadata. With this fix, arbiter brick will not be marked as source. |
| errata-xmlrpc | 2018-09-04 06:29:55 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2018-09-04 02:29:55 UTC | |||
| errata-xmlrpc | 2018-09-04 06:32:05 UTC | Link ID | Red Hat Product Errata RHSA-2018:2607 | |
| Anees Patel | 2018-10-31 08:41:21 UTC | CC | anepatel |
Back to bug 1401969