-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
added docs for storage-node #69
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
logicalVolume.compression ... we do not support this parameter currently, pls remove
cachingnode.s3DataPath ... cachingnode.s3bucketname ... not supported, please remove
storagenode.iobufSmallPoolCount ... auto-calculated, pls remove
storagenode.iobufLargePoolCount ... auto-calculated, pls remove
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"If you are using terraform to deploy the cluster. Please attach container-instance-sg security group to all the instances." please indicate aws-specific information in the readme as such, e.g. with an aws symbol and information box.
"We suggest allocating at least 8GB of huge pages." tremove this, instead: One unit of huge page memory is 2 MiB in size. The minimum amount of huge pages to be allocated is 2 GiB + 0.5% of the size of the nvme cache. For example, if the nvme cache is 1.9 TiB, you will need an additional of 9.5 GiB of huge page memory.
changes for k8s version of storage cluster |
No description provided.