447 views
0 votes
0 votes
In wait and die scheme we don't have starvation, if we add timeout to it, does it change? I think if we add timeout, it can cause starvation the old transaction always timeout before runnin and a new transaction will be run. Is that so?

1 Answer

0 votes
0 votes

@Tara22

Both the wound-wait and the wait-die schemes avoid starvation ...

At any time, there is a transaction with the smallest timestamp. This transaction cannot be required to roll back in either scheme....

Since timestamps always increase, and since transactions are not assigned new timestamps when they are rolled back, a transaction that is rolled back will eventually have the smallest timestamp. Thus it will not be rolled back again....

 

1. https://gateoverflow.in/165484/Transaction 

 

2. https://gateoverflow.in/250908/Wait-die-and-wound-wait 

 

3. https://gateoverflow.in/273872/Wait-die-deadlock-prevention-strategy

 

 

Related questions

1 votes
1 votes
2 answers
1
shekhar chauhan asked Jun 5, 2016
979 views
Either L attribute or S attributed .What kind of SDT it is ?S ->E# Out('#')E - E+E Out('+')E ->TT - T#F Out('*)T - FF - (E)F - a Out ('a')For the sentence...
0 votes
0 votes
1 answer
2
Anup patel asked Dec 26, 2017
516 views
We have 2 Schedule S1 and S2 ... There are no Conflict Operation in S1 and S2. So can we say they are conflict equivalent ?
3 votes
3 votes
4 answers
4
agoh asked Dec 11, 2016
1,091 views
My doubt is as follows: If deadlock is there, processes will be busy waiting in wait loop. So, decision on which process enters C.S. is not made in finite time. Hence, is...