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
Kathryn Hancox (kathancox) commented:
After talking to David, going to push this back until a docs issue comes through relating to a more significant change around backup priority for v23.1. The change in v22.1 is minor.
In v22.1, we changed to send with a different priority, but this would only trigger if full resource exhaustion was happening.
The change in 23.1, is much more significant, which is that the requests now actively leave spare resources available, to ensure they are there for foreground traffic. (That mode was available in 22.2 as well but defaulted off.)
From Aditya: is that the KV requests sent by backups are allotted fixed slices of on-CPU time to read the required keys/values. Once the request has exhausted its on-CPU time it paginates and will have to be resumed at a later time once it can be allocated a new on-CPU time slice. This pagination allows for other processes such as foreground traffic to continue almost unaffected since there is a cap on how much CPU a backup will be allowed to hog.
Matt Sherman (shermanCRL) commented:
In v22.1, and later patch releases of v21.2, backups will operate with a different priority than previous versions:
Let’s document what users should expect here, and link to the broader context of admission control. cc @stevendanna @dt
Jira Issue: DOC-3528
The text was updated successfully, but these errors were encountered: