You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently in the CDK we only support EBS based instances with the exception of i3 instances. This limit the testing to use only EBS based cluster. With launch of Disk based vector search, we have create our own custom solutions to setup the cluster. But this repo provides a very easy way to create the cluster, hence having a capability to use SSD based instances via this CDK will be very useful.
Agree, having disk based instances would benefit such use-cases.
I can add this to our sprint, but in the meantime if you can squeeze in a PR I can review it and merge quickly.
Is your feature request related to a problem?
Currently in the CDK we only support EBS based instances with the exception of i3 instances. This limit the testing to use only EBS based cluster. With launch of Disk based vector search, we have create our own custom solutions to setup the cluster. But this repo provides a very easy way to create the cluster, hence having a capability to use SSD based instances via this CDK will be very useful.
What solution would you like?
Ideally, we support instance with SSD. Only by adding the nodes here: https://github.com/opensearch-project/opensearch-cluster-cdk/blob/main/lib/opensearch-config/node-config.ts#L63 won't help, we also need to mount the SSD to the correct data folder where opensearch stores the index.
Ref: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/making-instance-stores-available-on-your-instances.html
What alternatives have you considered?
Alternative is to create the setup from scratch manually.
Do you have any additional context?
NA
The text was updated successfully, but these errors were encountered: