[MCOL-543] AMI postConfigure creates additional instance with non-matching local EBS volume Created: 2017-02-05 Updated: 2019-07-10 Resolved: 2019-07-10 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | installation |
| Affects Version/s: | 1.0.7 |
| Fix Version/s: | Icebox |
| Type: | Bug | Priority: | Major |
| Reporter: | Daniel Lee (Inactive) | Assignee: | Unassigned |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Build tested: 1.0.7-1 AMI (binary), non-root user (mariadb-user) I created an instance with 1TB local disk and use it to setup a 2UM combo stack. 1TB cpimport failed because PM2 ran out of disk space. It turned out that the local disk for PM2 is only 100GB. PM1 /dev/xvdz1 is an EBS volume where my 1TB source is. PM2 |
| Comments |
| Comment by David Hill (Inactive) [ 2017-02-06 ] |
|
So the current way that ColumnStore does it is to create an instance based on the AMI which has the root size set to 100 gb. It's not based off the current size of the disk on pm1, which was increased when the AMI was launched. But it looks like there is a way to do this: 1. would need to read the current size of the local disk, then use it when launching new instances. Work-around for now is to use external EBS storage for DBROOT's |