[CONTROLLER-1153] Clustering : ShardTransaction ReadData should be process synchronously Created: 12/Feb/15 Updated: 12/Feb/15 Resolved: 12/Feb/15 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | Post-Helium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Moiz Raja | Assignee: | Moiz Raja |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 2705 |
| Description |
|
ShardTransaction should process ReadData the same way it processes DataExists. There is no good reason or value to making it async in the ShardTransaction actor. Also this allows all operations on a transaction to be executed in proper order (i.e) a write cannot happen before a read and so on. Logging needs to be enhanced to log exceptions when a read fails. |
| Comments |
| Comment by Tom Pantelis [ 12/Feb/15 ] |