Back to bug 1025258
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Martin Gencur | 2013-11-01 13:00:22 UTC | Blocks | 1017190 | |
| Misha H. Ali | 2013-11-04 09:27:46 UTC | CC | mhusnain | |
| Radim Vansa | 2013-11-04 10:32:10 UTC | Doc Text | With L1 enabled, after cluster rebalance (after node join/leave) L1 may stay outdated on some node - reads from this node will not reflect further writes to the entry until the entry times out from the L1. | |
| Red Hat Bugzilla | 2013-11-05 05:09:11 UTC | CC | gsheldon | |
| Doc Text | With L1 enabled, after cluster rebalance (after node join/leave) L1 may stay outdated on some node - reads from this node will not reflect further writes to the entry until the entry times out from the L1. | With L1 enabled, after cluster rebalance (after node join/leave) L1 may stay outdated on a node - reads from this node will not reflect further writes to the entry until the entry times out from the L1. | ||
| Doc Type | Bug Fix | Known Issue | ||
| Doc Type | Known Issue | Bug Fix | ||
| Tristan Tarrant | 2013-11-19 13:45:08 UTC | Doc Text | With L1 enabled, after cluster rebalance (after node join/leave) L1 may stay outdated on a node - reads from this node will not reflect further writes to the entry until the entry times out from the L1. | With L1 enabled, after a cluster rebalance following a node joining or leaving, L1 may stay outdated on a node - reads from this node will not reflect further writes to the entry until the entry times out from the L1. |
| Doc Type | Bug Fix | Known Issue | ||
| Status | NEW | ON_QA | ||
| Target Release | --- | 6.2.0 | ||
| Target Milestone | --- | ER4 | ||
| Radim Vansa | 2013-11-21 09:19:42 UTC | Status | ON_QA | VERIFIED |
| PnT Account Manager | 2018-09-12 22:21:33 UTC | CC | gsheldon | |
| PnT Account Manager | 2018-09-12 22:31:38 UTC | CC | mhusnain |
Back to bug 1025258