Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
Security Level: Public
-
None
-
CBG Sprint 72, CBG Sprint 73, CBG Sprint 74
-
2
Description
We already have warning thresholds to nudge customers away from potential issues.
Those existing today are:
- xattrr size limits (90% of 1MB)
- channels per doc (50)
- access grants per doc (50)
We could also add a new warning about channel count per user, to give early warning about running into memory issues with extremely high numbers of channels per user.
The expected limits of channels per user are higher than the ~50 we expect to see on a single doc.
Warning at >1000 channels per user seems to be a reasonable balance, but open to suggestions.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link | This issue relates to CBSE-10029 [ CBSE-10029 ] |
| Link | This issue relates to CBSE-10005 [ CBSE-10005 ] |
| Description |
We already have warning thresholds to nudge customers away from potential issues.
Those existing today are: - xattrr size limits (90% of 1MB) - channels per doc (50) - access grants per doc (50) We could also add a new warning about channels per user to warn customers about running into memory issues with extremely high numbers of channels per user. The expected limits of channels per user are higher than the ~50 we expect to see on a single doc. Warning at >1000 channels per user seems to be a reasonable balance, but open to suggestions. |
We already have warning thresholds to nudge customers away from potential issues.
Those existing today are: - xattrr size limits (90% of 1MB) - channels per doc (50) - access grants per doc (50) We could also add a new warning about channel count per user, to give early warning about running into memory issues with extremely high numbers of channels per user. The expected limits of channels per user are higher than the ~50 we expect to see on a single doc. Warning at >1000 channels per user seems to be a reasonable balance, but open to suggestions. |
| Assignee | The One [ the one ] | Sarath Kumar Sivan [ sarath.kumarsivan ] |
| Sprint | CBG Sprint 72 [ 1550 ] |
| Rank | Ranked lower |
| Sprint | CBG Sprint 72 [ 1550 ] | CBG Sprint 72, CBG Sprint 73 [ 1550, 1586 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
Automated transition triggered when Sarath Kumar Sivan created pull request #4998 in GitHub -
| Status | In Progress [ 3 ] | In Review [ 10107 ] |
| Sprint | CBG Sprint 72, CBG Sprint 73 [ 1550, 1586 ] | CBG Sprint 72, CBG Sprint 73, CBG Sprint 74 [ 1550, 1586, 1604 ] |
Build sync_gateway-3.0.0-204 contains sync_gateway commit 619961a with commit message:
CBG-1390 Add warning threshold for excessively large number of channels per user (#4998)
| Resolution | Fixed [ 1 ] | |
| Status | In Review [ 10107 ] | Resolved [ 5 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
General approach seems fine, let's use 50000 as the number, and have a way for customers to disable the warning if they have sized for this use case, in the same way the items listed above are doing.