|
Even more strong argument. We have an request which for example remove some records from DB. Let say it remove 10 first records and wait a confirmation from RDBS. Once DB server is busy, but it start the request and busy by rebuilding indexes. We got a timeout. It should not happen ussualy, but if server will repeat a request again and again the application remove not 10 but 30 records from DB and user will not know about because 503 exception.
We need a way to restrict nuber of retry for some kind of requests, isn't it?
|