3 ms·
Think of it this way: category (1) are transaction aborts that are dependent on the state of the data. If so, you can explicitly include conditional logic on th
by abadid 8y ago
Think of it this way: category (1) are transaction aborts that are dependent on the state of the data. If so, you can explicitly include conditional logic on that data state. The mechanism for accomplishing category (2) is described in the section entitled: "Removing system-induced aborts". I agree it is non-trivial, but we've done it multiple times in my lab.
- ThePhysicist 8y agoI'm trying to understand your proposed system (as a non CS person). Would this be an accurate (basic) description of it? - You keep a deterministic log of all data inputs / transactions that should take place (a write-ahead log of sorts) that all workers can refer to. - Each worker remembers the position in the log that it has processed so far. - If a worker crashes during a transaction it can simply pick up at the position it was at before (possibly after doing some local cleanup) and replay the transactions.
- abadid 8y agoWhat you said is one reasonable way to accomplish what is stated in the post. There are other alternatives (described in the links from the post), but your way would work fine.