Back to bug 1326663
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla Rules Engine | 2016-04-13 10:10:21 UTC | Keywords | ZStream | |
| Nithya Balachandran | 2016-04-15 05:43:47 UTC | CC | nbalacha | |
| Susant Kumar Palai | 2016-04-15 06:19:43 UTC | CC | spalai | |
| Susant Kumar Palai | 2016-04-15 09:21:19 UTC | Blocks | 1327507 | |
| Susant Kumar Palai | 2016-04-15 09:22:45 UTC | Status | NEW | POST |
| Blocks | 1327507 | |||
| Assignee | rgowdapp | spalai | ||
| Rahul Hinduja | 2016-04-19 16:20:07 UTC | CC | rhinduja | |
| Blocks | 1311817 | |||
| QA Contact | annair | kramdoss | ||
| Alok | 2016-04-20 11:03:41 UTC | CC | asrivast | |
| Red Hat Bugzilla Rules Engine | 2016-04-22 07:46:48 UTC | Target Release | --- | RHGS 3.1.3 |
| Nithya Balachandran | 2016-04-26 09:01:10 UTC | Sub Component | dht | |
| Component | glusterfs | gluster-dht | ||
| Assignee | spalai | rhs-bugs | ||
| QA Contact | kramdoss | storage-qa-internal | ||
| Susant Kumar Palai | 2016-04-26 09:20:58 UTC | Assignee | rhs-bugs | spalai |
| QA Contact | storage-qa-internal | kramdoss | ||
| Raghavendra G | 2016-04-28 06:33:04 UTC | Status | POST | MODIFIED |
| CC | rgowdapp | |||
| errata-xmlrpc | 2016-05-02 06:02:59 UTC | Status | MODIFIED | ON_QA |
| Satish Mohan | 2016-05-02 06:07:23 UTC | Fixed In Version | glusterfs-3.7.9-3 | |
| Sweta Anandpara | 2016-05-03 06:50:54 UTC | CC | sanandpa | |
| Sweta Anandpara | 2016-05-03 10:21:45 UTC | Status | ON_QA | VERIFIED |
| Sweta Anandpara | 2016-05-03 10:23:11 UTC | QA Contact | kramdoss | sanandpa |
| Susant Kumar Palai | 2016-05-11 06:38:25 UTC | Doc Text | Cause: The crawler thread goes to sleep when the queue limit has reached and waits for a signal from the migration threads to wake up. But migration threads used to exit without notifying the crawler thread for a _REBALANCE_STOP_ event. Consequence: Rebalance process won't be stopped for a "STOP" command. Fix: Migration threads need to signal crawler thread before exiting. |
|
| Laura Bailey | 2016-06-06 02:14:27 UTC | Doc Text | Cause: The crawler thread goes to sleep when the queue limit has reached and waits for a signal from the migration threads to wake up. But migration threads used to exit without notifying the crawler thread for a _REBALANCE_STOP_ event. Consequence: Rebalance process won't be stopped for a "STOP" command. Fix: Migration threads need to signal crawler thread before exiting. | When the crawler thread for rebalance reaches its queue limit, it sleeps until it receives a signal from the migration threads. However, migration threads exited without notifying the crawler thread for a REBALANCE_STOP event. This meant that, when 'rebalance stop' was run when the crawler thread had reached its queue limit, the rebalance process did not actually stop. Migration threads now signal the crawler before they exit, and the 'rebalance stop' command works as expected. |
| Flags | needinfo?(spalai) | |||
| Susant Kumar Palai | 2016-06-06 06:40:12 UTC | Flags | needinfo?(spalai) | |
| errata-xmlrpc | 2016-06-23 00:52:41 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-06-23 05:17:23 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-06-23 01:17:23 UTC |
Back to bug 1326663