Details
-
Bug
-
Resolution: Done
-
Critical
-
4.0.0.Final, 4.1.0.CR1
-
None
-
Workaround Exists
-
-
Medium
Description
There's an ordering issue going on under the following circumstances where A and B communicate asynchronously via replication queue:
- Start Node A
- Start Node B
- Begin Pushing Requests to A
- A and B are in Sync
- Restart B (While Pushing Requests to A)
- State Transfer from A to B
- A and B are NOT in Sync
There appears to be an ordering issue:
Master
2010-08-05 11:38:21,028 // Put Key: 342197608235468 (OrderCache)
2010-08-05 11:38:21,230 // Remove Key: 342197608235468 (OrderCache)
2010-08-05 11:38:23,784 // State Transfer Response (OrderCache)
Slave
2010-08-05 11:38:23,782 // State Transfer Request (OrderCache)
2010-08-05 11:38:34,529 // Remove Key: 342197608235468 (OrderCache) Request 693
2010-08-05 11:46:08,845 // Put Key: 342197608235468 (OrderCache) * Request 692*