This message was deleted.
# general
s
This message was deleted.
a
Hi Daniel, you want to select for high IOPS especially for bookkeeper. Besides that testing/benchmarking your specific workload is recommended. You might also want to consider the cost factor (see here https://www.vantage.sh/blog/ebs-vs-nvme-pricing-performance)
d
Thank you Alexander! I will check this out.
👍 1
Alexander, could you please clarify the following: • The same recommendation stands for kubernetes deployments right? • Going back to the docs, I see that it seems to recommend i3 instances for bookies and brokers. And t2 for zookeeper. Would a t2 or other general purpose compute should suffice for other pods (zookeeper, toolset, recovery, pulsar-manager, proxy, prometheus, grafana)?
a
Hi Daniel, yeah k8s deployments should be the same. I think using the t2 instances for the non broker and bookie pods is fine
👌 1
d
Brilliant! Thanks, Alexander.
What are my options when I am shifting away from EBS? Tiered storage? Replication? I am worried that instance memory is ephemeral that I can lose data even if there are hardware faults in AWS. I am very new to bookkeepers and I am still learning to manage then and my nightmares are mostly about bookies facing an error like data loss or corruption that they cannot recover from 😅
a
Both tiered storage and replication would be an option, replication would be your choice for quick disaster recovery while tiered storage aims to be a solution for cheap long term storage of data you might need again but infrequently
👍 1
d
Thanks Alexander! This helps 😄