Back to bug 1019742
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Martin Gencur | 2013-10-16 11:01:00 UTC | Blocks | 1010419 | |
| mark yarborough | 2013-10-16 13:07:27 UTC | Target Release | --- | 6.2.0 |
| CC | myarboro | |||
| Tristan Tarrant | 2013-10-17 11:45:12 UTC | Status | NEW | ASSIGNED |
| Target Milestone | --- | ER3 | ||
| Martin Gencur | 2013-10-17 14:56:23 UTC | Blocks | 1010419 | 1017190 |
| Martin Gencur | 2013-10-23 08:26:48 UTC | CC | gsheldon | |
| Doc Text | If a node is losing ownership of an entry during a state transfer, when the node performs a write and commits, the change is propagated only to the new owners, and the entry is not written locally. However, when it executes read for this key afterwards | |||
| Doc Text | , it gets the old value as this is directly retrieved from the data container. This bug was observed in transactional mode, but may not be limited to it. | |||
| Status | ASSIGNED | POST | ||
| Radim Vansa | 2013-11-04 10:01:33 UTC | Doc Text | If a node is losing ownership of an entry during a state transfer, when the node performs a write and commits, the change is propagated only to the new owners, and the entry is not written locally. However, when it executes read for this key afterwards, it gets the old value as this is directly retrieved from the data container. This bug was observed in transactional mode, but may not be limited to it. | During the cluster rebalance process (after some node joining/leaving the cluster) a read operation may retrieve data that have already been overwritten. The bug was observed in transactional mode but may not be limited to. |
| Tristan Tarrant | 2013-11-19 16:44:35 UTC | Doc Text | During the cluster rebalance process (after some node joining/leaving the cluster) a read operation may retrieve data that have already been overwritten. The bug was observed in transactional mode but may not be limited to. | During the cluster rebalance process, after a node joins or leaves the cluster, a read operation may retrieve data that has already been overwritten. The bug was observed in transactional mode but may not be limited to it. |
| Doc Type | Bug Fix | Known Issue | ||
| Doc Text | During the cluster rebalance process, after a node joins or leaves the cluster, a read operation may retrieve data that has already been overwritten. The bug was observed in transactional mode but may not be limited to it. | During the cluster rebalance process, after a node joins or leaves the cluster, a read operation may retrieve data that has already been overwritten. The behaviour was observed in transactional mode but may not be limited to it. | ||
| Doc Text | During the cluster rebalance process, after a node joins or leaves the cluster, a read operation may retrieve data that has already been overwritten. The behaviour was observed in transactional mode but may not be limited to it. | During the cluster rebalance process, after a node joins or leaves the cluster, a read operation may retrieve data that has already been overwritten. The behavior was observed in transactional mode but may not be limited to it. | ||
| Status | POST | ON_QA | ||
| Target Milestone | ER3 | ER4 | ||
| Radim Vansa | 2013-11-22 11:27:17 UTC | Status | ON_QA | VERIFIED |
| PnT Account Manager | 2018-09-12 22:21:24 UTC | CC | gsheldon |
Back to bug 1019742