"Deadlock" is the term used in concurrent processing. It can happen if the resources are distributed. I actually had the privilege of troubleshooting such an issue not too long ago: http://dba.stackexchange.com/q/73833
I wasn't talking about deadlocks - a deadlock is when no work ends up being done, whereas I was wondering about the situation where very little work ends up being done. Interesting link though!
Comments
Has anyone had an experience of "gridlock" in a distributed system? Where bottlenecks cascade due to failover, etc?
"Deadlock" is the term used in concurrent processing. It can happen if the resources are distributed. I actually had the privilege of troubleshooting such an issue not too long ago: http://dba.stackexchange.com/q/73833
I wasn't talking about deadlocks - a deadlock is when no work ends up being done, whereas I was wondering about the situation where very little work ends up being done. Interesting link though!
I think this post that recently hit the front page of Hacker News could be such an example: https://news.ycombinator.com/item?id=8255128