citusdata / citusdata/test-automation
Some node sizes are not started with enough disk space to run TPC-H testing
- Dominant language
- C
- Stars
- 15
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
m2.small works because the AMI for that size has a root device at `/dev/xvda`, which the CloudFormation populates. However, the AMI for m3.medium uses a root device of `/dev/sda`, which the CloudFormation does not populate, so the OS does not expose enough space for us to do TPC-H testing.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the CloudFormation configuration that provisions the m2.small and m3.medium nodes, then compare how each AMI root device is populated. Reproduce the node setup and run the TPC-H testing workflow. Done means both node sizes expose enough disk space for TPC-H testing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100