Skip to content

Commit

Permalink
Update capacity-planning.adoc (hazelcast#1117)
Browse files Browse the repository at this point in the history
Added a few words to clarify the point that this calculation is only for
the HybridLog requirement, and that the startup sanity check also
includes the amount allocated at the data structure configuration level.
It also clarifies the point that memory capacity planning includes
hybridlog and the data itself - which should be obvious but isn't
explicitly stated.
  • Loading branch information
naadhira authored Jul 8, 2024
1 parent 2f2e40a commit 11297e6
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/modules/tiered-storage/pages/capacity-planning.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ NOTE: There is a HybridLog instance for every configured index on every partitio

This means that if you have Tiered Storage enabled for a single IMap, with no index configured, and the default partition count and page size, the minimum required memory is `(1 + 0) * 271 * 4MB = 1084MB`.

The Hazelcast cluster members validate, on startup, if the native memory configured for the member is greater than or equal to the minimum required memory as calculated above.
The Hazelcast cluster members validate, on startup, if the native memory configured for the member is greater than or equal to the minimum required memory. This includes the above calculation along with the amount of memory allocated for each data structure using Tiered Storage.
If not, the cluster fails to start.

In addition, around 20 MB of RAM is required for every one million entries stored on a member, including backups. To calculate the required RAM for members, divide the total expected number of entries (including backups) stored in the cluster by the member count.
Expand Down

0 comments on commit 11297e6

Please sign in to comment.