You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
other databases should not be affected as they use a connection pool since Sqlite by design is a single writer and if WAL is enabled multiple readers.
When using AppSec component you may sometimes see a context.deadline exceeded error due to the database writer being held by a community blocklist update. By default the header request has a default 200ms timeout to be responsive as possible, but since the writer is held it cannot get a response fast enough.
Check Releases to make sure your agent is on the latest version.
Details
I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.
@LaurenceJJones: There are no 'kind' label on this issue. You need a 'kind' label to start the triage process.
/kind feature
/kind enhancement
/kind refactoring
/kind bug
/kind packaging
Details
I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.
LaurenceJJones
changed the title
[AppSec] Head request is blocked due to other writes on DB
[AppSec] Head request is delayed due to other writes on DB
Oct 15, 2024
Confirmed database types issue:
other databases should not be affected as they use a connection pool since Sqlite by design is a single writer and if WAL is enabled multiple readers.
When using AppSec component you may sometimes see a context.deadline exceeded error due to the database writer being held by a community blocklist update. By default the header request has a default 200ms timeout to be responsive as possible, but since the writer is held it cannot get a response fast enough.
CrowdSec Logs:
LAPI Response timer:
The text was updated successfully, but these errors were encountered: