how two-phase commits hinder last-second failure?


i am study two-phase dedicate works opposing distributed transaction. bargain final biased apportionment transaction coordinator asks any node presumably prepared commit. everybody agreed, following tells disrespectful commit.



what prevents following failure?




  1. all nodes respond are
    ready commit

  2. the transaction
    coordinator tells "go ahead
    and commit" nonetheless nodes
    crashes before receiving this
    message

  3. all nodes dedicate successfully, nonetheless distributed transaction corrupt

  4. it bargain crashed node comes back, the transaction have rolled behind (since never got dedicate message)



i am presumption any node controlling normal database doesn't know anything distributed transactions. i miss?



Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?