Re: Multiple node cluster problems
This archive was generated by
No, this is no longer an issue for me. My guess is that this was all on
the AWS end, and resolved shortly after Thanksgiving.
On Thu, Dec 12, 2013 at 12:46 PM, Mayank Ahuja <mahuja_at_qubole.com> wrote:
> Hi Justin,
> It was a bug in AWS us-east-1 region which was fixed after a couple of
> days. The user data attribute of instances launched using one API call was
> empty (on except the one with ami launch index = 0). As a result the
> instances launched had no 'alias' tag.
> It might be worth exploring if the dependence on user data attribute for
> tag setting can be removed. Have seen a couple of times in the past when
> fetch of user data attribute did not exceed (with few retries) due to may
> be API latency issues at AWS end.
> On Thu, Dec 12, 2013 at 10:30 PM, Justin Riley <jtriley_at_mit.edu> wrote:
>> *major* issue if this change is indeed permanent. What region are you
Daniel G Polhamus, PhD
Metrum Research Group, LLC
2 Tunxis Rd, Suite 112
Tariffville, CT 06081
(888) 308-7049 ext 403
Received on Thu Dec 12 2013 - 12:58:14 EST