Skip to content

Handle backend timeout gracefully #25

@giftig

Description

@giftig

Not currently logging anything when it takes a long time to talk to redis; the request times out and spray tells the client it wasn't able to respond in a timely manner, but nothing is logged to help narrow down the problem. It'll be useful to log before and after hitting the db so that timings are visible, and to handle timeouts by logging the issue and possibly serving a JSON response to match the rest of the API rather than falling back on spray's text/plain one (maybe. Status code is probably good enough; passing back JSON won't add much information).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions