Status stays in processing

mnordhoff · March 28, 2018, 3:06pm

That sounds like most likely this issue...

github.com/letsencrypt/boulder

SA.GetValidAuthorizations fetches too much

opened 12:21AM - 20 Mar 18 UTC

closed 06:04PM - 27 Mar 18 UTC

jsha

area/sa kind/performance kind/bug

In SA.GetValidAuthorizations, we query for all authorizations that match a given… identifier, then fetch challenges for them, and then throw away all but the most recent of the authorizations for each identifier, as indicated by the Expires field. The number of authorizations can be quite large in certain circumstances, meaning we fetch a lot of challenges that we subsequently throw away. This can result in query timeouts. We should only fetch challenges for the authorizations we intend to return. Since we already have an index on the Expires field, we could just add an `ORDER BY expires DESC` to the query, which would ensure that we iterate through in order by optimality and throw away the authorizations we don't care about.

If so, the fix might be deployed tomorrow or April 5?