Details
Description
See: http://review.couchbase.org/#/c/58983/1
The code to calculate default memory allocations looks wrong, and FTS needs a part of that memory allocation...
Handwaving the (current) algorithm...
Memory is divided into 5 portions.
A) 3 portions of the 5 are defaulted to KV.
B) Another 3 more portions of the 5 are defaulted to Index (GSI).
So... 3 + 3 == 6, and 6 portions > 5 portions already, so something already feels odd here.
C) 1 more portion of the 5 is defaulted to FTS.
So 3 + 3 + 1 == 7, and 7 > 5, so it's even more fishy. This issue is to figure out the right default memory pro-portion'ing policy across services.
Attachments
Issue Links
- blocks
-
MB-30705 Do not permit the user to set an FTS quota of less than 512MB
- Resolved
- duplicates
-
MB-16530 Initial cluster setup numbers are confusing
- Closed
- is duplicated by
-
MB-18372 [Windows] Default Index RAM Quota not enough for even one sample (like travel-sample)
- Closed
-
MB-18136 Max value for 'KV RAM Quota' in the initial setting should be based on cluster RAM Available
- Closed
-
MB-18339 Default values for RAM do not work for server setup
- Closed
-
MB-18619 Setup wizard: better calculate RAM quotas to "fit" within available resources
- Closed
- relates to
-
MB-17944 Wizard Step 1 FTS Quota does not update full quota
- Resolved
-
MB-27399 Determine default memory allocation for Analytics
- Closed