I notice that recently the forge just doesn't respond when it's being hormonal, instead of getting the "Not set up" error, which seemed to be its fave problem before.
I suspect the DB problem was due to not releasing concurrent threads whenever there was a failure, which could be because of max threads in use, so if it got too busy it died. It may be that fixing that lets it hit a monthly bandwidth limit or something like that.
I know this site uses Drupal instead of TikiWiki, and probably a different database, but maybe Sol can comment on the database failure modes he's seen?
I notice that recently the forge just doesn't respond when it's being hormonal, instead of getting the "Not set up" error, which seemed to be its fave problem before.
I suspect the DB problem was due to not releasing concurrent threads whenever there was a failure, which could be because of max threads in use, so if it got too busy it died. It may be that fixing that lets it hit a monthly bandwidth limit or something like that.
I know this site uses Drupal instead of TikiWiki, and probably a different database, but maybe Sol can comment on the database failure modes he's seen?