Details
-
Task
-
Status: In Progress
-
Major
-
Resolution: Unresolved
-
4.5, 4.6, 5.0, Server 5.5/Vulcan, Alice, Mad Hatter, 6.6.0
-
DOC-2020-S12-Jun28, DOC-2020-S13-Jul12, DOC-2020-S17-Sep06, DOC-2020-S18-Sep20, DOC-2020-S19-Oct04, DOC-2020-S20-Oct18, DOC-2020-S22-Nov15, DOC-2020-S21-Nov01, DOC-2020-S23-Nov29, DOC-2020-S24-Dec13, DOC-2020-S25-Jan03, DOC-2021-Jan17-S1, DOC-2021-Jan31-S2, DOC-2021-Feb14-S3, DOC-2021-Feb28-S4, DOC-2021-Mar14-S5, DOC-2021-Mar28-S6, DOC-2021-Apr11-S7, DOC-2021-Apr25-S8
-
1
Description
In the Index sizing page https://docs.couchbase.com/server/current/install/sizing-general.html#sizing-index-service-nodes, we could add more details about the overhead memory requires. For example, secondary indexes could require 120 bytes overhead per item between the mainstore and backstore tree structure. This is especially important for MOI, as the indexes will be in memory.
- Possibly separate discussion for MOI vs. Standard/Plasma.
- Add snapshot sizing information needed for MOI disk snapshots.
- Overhead sizing for primary and secondary indexes. In addition to the item data itself, how much overhead is needed per item to maintain the index data structure?
- Considering mainstore and backstore when mentioning sizing.
- Possibly consider adding more information about other (often hard to predict additional sizing needed), such as queues formed due to slow indexing or when an index is first built. Additionally the additional space usage that might come from a delta chain.
- Possibly an honorable mention of the memory usage needed for the Index Service to maintain its basic self ... just to operate ... memory needed for network communications ... etc.
Docs Contrib
Please edit the page linked above to provide the required information. To be backported to 5.0.
Attachments
Gerrit Reviews
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description | In the Index sizing page https://docs.couchbase.com/server/current/install/sizing-general.html#sizing-index-service-nodes, we could add more details about the overhead memory requires. For example, secondary indexes could require 120 bytes overhead per item between the mainstore and backstore tree structure. This is especially important for MOI, as the indexes will be in memory. |
In the Index sizing page https://docs.couchbase.com/server/current/install/sizing-general.html#sizing-index-service-nodes, we could add more details about the overhead memory requires. For example, secondary indexes could require 120 bytes overhead per item between the mainstore and backstore tree structure. This is especially important for MOI, as the indexes will be in memory.
I would recommend that we sync with the indexing team to get a more overview of sizing requirements. |
| Description |
In the Index sizing page https://docs.couchbase.com/server/current/install/sizing-general.html#sizing-index-service-nodes, we could add more details about the overhead memory requires. For example, secondary indexes could require 120 bytes overhead per item between the mainstore and backstore tree structure. This is especially important for MOI, as the indexes will be in memory.
I would recommend that we sync with the indexing team to get a more overview of sizing requirements. |
In the Index sizing page https://docs.couchbase.com/server/current/install/sizing-general.html#sizing-index-service-nodes, we could add more details about the overhead memory requires. For example, secondary indexes could require 120 bytes overhead per item between the mainstore and backstore tree structure. This is especially important for MOI, as the indexes will be in memory.
|
| Link | This issue relates to CBSE-7994 [ CBSE-7994 ] |
| Description |
In the Index sizing page https://docs.couchbase.com/server/current/install/sizing-general.html#sizing-index-service-nodes, we could add more details about the overhead memory requires. For example, secondary indexes could require 120 bytes overhead per item between the mainstore and backstore tree structure. This is especially important for MOI, as the indexes will be in memory.
|
In the Index sizing page https://docs.couchbase.com/server/current/install/sizing-general.html#sizing-index-service-nodes, we could add more details about the overhead memory requires. For example, secondary indexes could require 120 bytes overhead per item between the mainstore and backstore tree structure. This is especially important for MOI, as the indexes will be in memory.
* Possibly separate discussion for MOI vs. Standard/Plasma. * Add snapshot sizing information needed for MOI disk snapshots. * Overhead sizing for primary and secondary indexes. In addition to the item data itself, how much overhead is needed per item to maintain the index data structure? * Considering mainstore and backstore when mentioning sizing. * Possibly considering add more information about other (often hard to predict additional sizing needed), such as queues formed due to slow indexing or when an index is first built. Additionally the additional space usage that might come from a delta chain. * Possibly an honorable mention of the memory usage needed for the Index Service to maintain its basic self ... just to operate ... memory needed for network communications ... etc. |
| Description |
In the Index sizing page https://docs.couchbase.com/server/current/install/sizing-general.html#sizing-index-service-nodes, we could add more details about the overhead memory requires. For example, secondary indexes could require 120 bytes overhead per item between the mainstore and backstore tree structure. This is especially important for MOI, as the indexes will be in memory.
* Possibly separate discussion for MOI vs. Standard/Plasma. * Add snapshot sizing information needed for MOI disk snapshots. * Overhead sizing for primary and secondary indexes. In addition to the item data itself, how much overhead is needed per item to maintain the index data structure? * Considering mainstore and backstore when mentioning sizing. * Possibly considering add more information about other (often hard to predict additional sizing needed), such as queues formed due to slow indexing or when an index is first built. Additionally the additional space usage that might come from a delta chain. * Possibly an honorable mention of the memory usage needed for the Index Service to maintain its basic self ... just to operate ... memory needed for network communications ... etc. |
In the Index sizing page https://docs.couchbase.com/server/current/install/sizing-general.html#sizing-index-service-nodes, we could add more details about the overhead memory requires. For example, secondary indexes could require 120 bytes overhead per item between the mainstore and backstore tree structure. This is especially important for MOI, as the indexes will be in memory.
* Possibly separate discussion for MOI vs. Standard/Plasma. * Add snapshot sizing information needed for MOI disk snapshots. * Overhead sizing for primary and secondary indexes. In addition to the item data itself, how much overhead is needed per item to maintain the index data structure? * Considering mainstore and backstore when mentioning sizing. * Possibly consider adding more information about other (often hard to predict additional sizing needed), such as queues formed due to slow indexing or when an index is first built. Additionally the additional space usage that might come from a delta chain. * Possibly an honorable mention of the memory usage needed for the Index Service to maintain its basic self ... just to operate ... memory needed for network communications ... etc. |
| Component/s | gsi [ 12316 ] |
| Assignee | Amarantha Kulkarni [ amarantha.kulkarni ] | Simon Dew [ simon.dew ] |
| Labels | needs-info |
| Fix Version/s | 5.x Doc Updates [ 15024 ] | |
| Fix Version/s | 6.x Doc Updates [ 15700 ] | |
| Fix Version/s | 6.5 Milestone 2 [ 16768 ] | |
| Fix Version/s | 4.6 [ 13441 ] | |
| Fix Version/s | 4.5 [ 13355 ] |
| Fix Version/s | Server 5.5/Vulcan [ 14903 ] |
| Story Points | 1 |
| Labels | needs-info | docs-contrib needs-info |
| Description |
In the Index sizing page https://docs.couchbase.com/server/current/install/sizing-general.html#sizing-index-service-nodes, we could add more details about the overhead memory requires. For example, secondary indexes could require 120 bytes overhead per item between the mainstore and backstore tree structure. This is especially important for MOI, as the indexes will be in memory.
* Possibly separate discussion for MOI vs. Standard/Plasma. * Add snapshot sizing information needed for MOI disk snapshots. * Overhead sizing for primary and secondary indexes. In addition to the item data itself, how much overhead is needed per item to maintain the index data structure? * Considering mainstore and backstore when mentioning sizing. * Possibly consider adding more information about other (often hard to predict additional sizing needed), such as queues formed due to slow indexing or when an index is first built. Additionally the additional space usage that might come from a delta chain. * Possibly an honorable mention of the memory usage needed for the Index Service to maintain its basic self ... just to operate ... memory needed for network communications ... etc. |
In the Index sizing page https://docs.couchbase.com/server/current/install/sizing-general.html#sizing-index-service-nodes, we could add more details about the overhead memory requires. For example, secondary indexes could require 120 bytes overhead per item between the mainstore and backstore tree structure. This is especially important for MOI, as the indexes will be in memory.
* Possibly separate discussion for MOI vs. Standard/Plasma. * Add snapshot sizing information needed for MOI disk snapshots. * Overhead sizing for primary and secondary indexes. In addition to the item data itself, how much overhead is needed per item to maintain the index data structure? * Considering mainstore and backstore when mentioning sizing. * Possibly consider adding more information about other (often hard to predict additional sizing needed), such as queues formed due to slow indexing or when an index is first built. Additionally the additional space usage that might come from a delta chain. * Possibly an honorable mention of the memory usage needed for the Index Service to maintain its basic self ... just to operate ... memory needed for network communications ... etc. h2. Docs Contrib Please edit the page linked above to provide the required information. To be backported as far as |
| Description |
In the Index sizing page https://docs.couchbase.com/server/current/install/sizing-general.html#sizing-index-service-nodes, we could add more details about the overhead memory requires. For example, secondary indexes could require 120 bytes overhead per item between the mainstore and backstore tree structure. This is especially important for MOI, as the indexes will be in memory.
* Possibly separate discussion for MOI vs. Standard/Plasma. * Add snapshot sizing information needed for MOI disk snapshots. * Overhead sizing for primary and secondary indexes. In addition to the item data itself, how much overhead is needed per item to maintain the index data structure? * Considering mainstore and backstore when mentioning sizing. * Possibly consider adding more information about other (often hard to predict additional sizing needed), such as queues formed due to slow indexing or when an index is first built. Additionally the additional space usage that might come from a delta chain. * Possibly an honorable mention of the memory usage needed for the Index Service to maintain its basic self ... just to operate ... memory needed for network communications ... etc. h2. Docs Contrib Please edit the page linked above to provide the required information. To be backported as far as |
In the Index sizing page https://docs.couchbase.com/server/current/install/sizing-general.html#sizing-index-service-nodes, we could add more details about the overhead memory requires. For example, secondary indexes could require 120 bytes overhead per item between the mainstore and backstore tree structure. This is especially important for MOI, as the indexes will be in memory.
* Possibly separate discussion for MOI vs. Standard/Plasma. * Add snapshot sizing information needed for MOI disk snapshots. * Overhead sizing for primary and secondary indexes. In addition to the item data itself, how much overhead is needed per item to maintain the index data structure? * Considering mainstore and backstore when mentioning sizing. * Possibly consider adding more information about other (often hard to predict additional sizing needed), such as queues formed due to slow indexing or when an index is first built. Additionally the additional space usage that might come from a delta chain. * Possibly an honorable mention of the memory usage needed for the Index Service to maintain its basic self ... just to operate ... memory needed for network communications ... etc. h2. Docs Contrib Please edit the page linked above to provide the required information. To be backported to 5.0. |
| Affects Version/s | Mad Hatter [ 15119 ] | |
| Affects Version/s | Alice [ 15118 ] | |
| Affects Version/s | Server 5.5/Vulcan [ 14903 ] | |
| Affects Version/s | 4.6 [ 13441 ] | |
| Affects Version/s | 4.5 [ 13355 ] |
| Fix Version/s | 6.6.0 [ 16812 ] | |
| Fix Version/s | 4.5 [ 13355 ] | |
| Fix Version/s | 4.6 [ 13441 ] | |
| Fix Version/s | Server 5.5/Vulcan [ 14903 ] |
| Affects Version/s | 6.6.0 [ 16812 ] |
| Affects Version/s | 5.0 [ 14700 ] |
| Due Date | 28/Jun/20 |
| Labels | docs-contrib needs-info | docs-contrib |
| Labels | docs-contrib | docs-contrib need |
| Labels | docs-contrib need | docs-contrib |
| Fix Version/s | 6.6.0 [ 16812 ] |
| Labels | docs-contrib | 6.6.1 docs-contrib |
| Labels | 6.6.1 docs-contrib | 6.6.1 docs-contrib needs-info |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Sprint |
|
|
| Sprint |
|
|
| Sprint |
|
|
| Sprint |
|
|
| Sprint |
|
|
| Sprint |
|
|
| Sprint |
|
|
| Sprint |
|
|
| Sprint |
|
|
| Sprint |
|
|
| Sprint |
|
|
| Sprint |
|
|
| Sprint |
|
|
| Sprint |
|
|
| Sprint |
|
|