rest - Is it appropriate to return HTTP 503 in response to a database deadlock? -


is appropriate server return 503 ("service unavailable") when requested operation resulted in database deadlock?

here reasoning:

seeing as:

  • it's easier ask clients repeat operation.
  • they need able handle 503 service unavailable anyway.
  • database deadlocks rather rare.

i'm leaning towards solution. think?

update: think returning 503 ("service unavailable") still acceptable if wish it, no longer think technically required. see https://stackoverflow.com/a/17960047/14731.

i think it's fine long entire transaction rolled or if request idempotent.


Comments

Popular posts from this blog

SPSS keyboard combination alters encoding -

Socket.connect doesn't throw exception in Android -

iphone - How do I keep MDScrollView from truncating my row headers and making my cells look bad? -