>
> those ticket don't come with request/session info, we have no idea where
> and when did this problem occur. does that mean that web2py already handle
> the retry?
>
AFAIK, web2py does not retry db I/O commands. The tickets are created when
the request generates an uncaught exception (in your case, a driver error).
One way of preventing this would be writing your own driver error (and
retry) handler in your application logic.
I guess something like this
def action():
from adriver import DriverException
try:
rows = ...
except DriverException:
raise HTTP(500, "Seems like the cluster is busy now. Try in a few
moments")
return dict(...)
--
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
