When attempting to create an EBS shared volume for all nodes in a StarCluster, the StarCluster createvolume command launches an AWS EC2 instance as the volume creator. However, the default instance type that is used for this is t1.micro, which is no longer available in the AWS availability zone (us-east-1f in my case). Is it possible to specify a different default instance type to use? t2.small, for example?
StarCluster VolumeCreator AWS instance_type
55 Views Asked by ECHOOooo... ECHOOooo... At
1
There are 1 best solutions below
Related Questions in AMAZON-WEB-SERVICES
- kernel module does not print packet info
- Packet drops in multicast when multiple instance of listner are running
- Timing packets on a traffic server
- How to use Espresso Idling Resource for network calls
- Dummynet does not match on flows
- Sending a notification from OS X to iOS
- Swift ios viewDidLoad or viewDidAppear
- Update player list on all clients on new connection
- Issues regarding multiplayer networking: input
- nmap does not show all open ports
Related Questions in STARCLUSTER
- kernel module does not print packet info
- Packet drops in multicast when multiple instance of listner are running
- Timing packets on a traffic server
- How to use Espresso Idling Resource for network calls
- Dummynet does not match on flows
- Sending a notification from OS X to iOS
- Swift ios viewDidLoad or viewDidAppear
- Update player list on all clients on new connection
- Issues regarding multiplayer networking: input
- nmap does not show all open ports
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular # Hahtags
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
I was able to find a work-around. While t1.micro instances were not available in AWS zone us-east-1f, they are still available in us-east-1d. So, I created the shared EBS volume there (and, to speed up data transfers to and from this volume, I changed my StarCluster config file to request that cluster nodes be launched in that same zone (us-east-1d)).
Still, if anyone knows an answer to the original question, I would prefer to be able to create EBS volumes and launch a cluster in the availability zone of my choice, and that would require being able to specify an instance type to use for the VolumeCreator node that is launched to create the EBS volume when the "$ starcluster createvolume" command is used. IMO, this should be a config file setting or, at a minimum, an optional argument to pass to the createvolume command.