Questions tagged with Amazon Elastic Block Store

Content language: English

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

EC2 instance fails to start after changing instance type from t2 to t3

I tried to update an EC2 instance from t2 to t3. Since the AZ I was running the instance in did not support t3 instances. I stopped the instance, created an image, and then tried to create an instance from that image in us-east-1c. The instance is running RockyOS v. 8.5. The instance did not start. Using the serial console, it appears as though the EBS volume was not detected. I verified that the ENA and NMVE drivers were installed. I tried a series of experiments, where I created new instances from the original AMI and I was able to create t2 instances, stopped them, created images, and then created new t3 instances without issue. The main difference of course is that the production instance has a lot more data on it, has been updated via dnf update, etc. I suppose I could just create a brand new t3 instance and migrate the data over, but I would like to understand why I wasn't able to convert the instance from t2 to t3. Some more information: The reason that the experiments worked, was because the original AMI was based on RockyOS v. 8.4. This version allows me to migrate between t2 and t3 versions without any issues. The production instance was updated at some point to version 8.5 and for some reason this version does not boot on t3 (nitro) instance types. I repeated my experiment, and launched the original AMI in a t2, did an upgrade, then after changing the instance type to t3, the instance does not boot. While this doesn't provide a solution to the problem, at least not it is reproducible. So, what is it about Rocky OS v. 8.5 that prevents the migration to a nitro instance? The modinfo ena and modinfo nvme both show the drivers are present
2
answers
0
votes
222
views
asked a year ago

EBS Volumes on RAID0 to gain perfomance

Hi, I have to setup a Domino Server, that uses a "translog" path. On the Domino Server documentation, it is suggested to dedicate a specific disk with his own controller to this path directory. I am not sure what method to use, either to use a normal GP3 disk, and add more IOPs if I see they are needed, or using ESB (algo GP3) on Raid0. Problem that I see with Raid0 is that I do not known how easy is to increase volumes on a RAID0 Configuration. On a normal (single) ESB volume, starting with a "small" size of the volume (ie, 100Gb), and then, increase it, is easy, is a trivial thing, and I can add also more IOPs / trhoughput on a very easy way, so I guess I can get the same (or very similar) perfomance that I will get with RAID0. I am aware that will RAID0 I will be able to "double" the perfomance, because I will get accumulatted IOPs values, so the maximum of IOPs obtained on RAID0 will be always greater, but not sure if I will need to increase the IOPS to a ratio that can not be obtained also on a single GP3 Disk. Moreover, my concern on RAID0 is about how easy will be to increase volume on it.. Can I increase a ESB volume that is being part of a RAID0 the same way that a normal EBS volume ? Do I need to have both ESB volumes at the same size ? Is the administrative additional task on a RAID0 woth the less (ie, complexity added for increasing volumes, for snapshoots, backups/recoverys, etc) ? In summary... When is bettert to have a single EBS volume with the number of IOPS you need, or a RAID0 config ?
2
answers
0
votes
109
views
AndresG
asked a year ago

Multiple EBS volumes to gain perfomance

Hi, I want to run "HCL Domino Server 12" on an EC2 instance, Domino is a server specialized on collaboration applications and includes a mail server, we can see it also as web servers that includes a Non-sql database behind as the engine for the email and the apps . During server setup, I can specify different paths for transactional logging, view indexes, mail&database applications, etc. I was thinking on create different filesystems for each route, and assign a different EBS volumen to each path/filesystem, but I do have several concerns / question on it: - EBS baseline: I am aware that t3 family EC2 instances have a baseline for CPU on 30%.... What about baselines for EBS ? Does t3 also have a baseline for EBS and credits towards the use of them ? I did not see clearly that info. - EBS and IOPs / Troughtput: I guess that if I have 3 EBS disk, and each of them have a performance base-level of 3000 IOPS and 125 MiB/s throughput. Does that means that using 3, I will have 9000 IOPS in total and 375 Mibs ? I am not sure if I have a previous bottleneck on the EC2 (ie, EC2 having a maximum on total for all the disk of 300 Mibs, so even I have multiple EBS volumes the maximum troughput is the one obtained by the EC2 machine) - Root Volumes: When you create and EC2 machine on a t3.large instance, how is by default created the Root Volume ? Is using an EBS gp2 or an EBS gp3 volume ? - NVMe SSD volumes: I saw EC2 images (ie, m5ad.large) that insted using "normal" EBS SSD volumes on the rrot, they provide you directly with 1x75 NVMe SSD volumes, and higher. I am confused there, since when I mounted additional SSD volumes on my linux systems, they always appeared also as a "NVMe" device. Are not normal gp2 / gp3 volumes NVMe based ? Can someone explained the difference and the value of this 1x75 VNMe SSD volumes offered by the m5ad.large image ?
1
answers
0
votes
68
views
AndresG
asked a year ago