<div dir="ltr">Please disregard. Not sure what my issue is, but it doesn't seem to be the placement group.</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 4, 2016 at 8:06 PM, Lyn Gerner <span dir="ltr"><<a href="mailto:schedulerqueen@gmail.com" target="_blank">schedulerqueen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi All,<div><br></div><div>I have an existing cluster that has a master and a node001 up; they were launched with *no* placement group, over a week ago. Now it seems something has changed in the availability zone, becauseI'm trying to grow that cluster, and any new addnode attempt is accompanied by the creation of a placement group. The addnode subsequently gets an unhandled exception before ever reaching SSH-able status. (Crash report attached.)</div><div><br></div><div>Has anybody else seen and resolved this? I see the placement group-related code in cluster.py, but I'd certainly appreciate not having to reinvent the wheel, or any insights.</div><div><br></div><div>Thanks,</div><div>Lyn</div></div>
</blockquote></div><br></div>