Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/3986#issuecomment-69473834
Hmm, sucks that boto still prints that error.
Getting errors on `i.update()` seems to be part of AWS's general flakiness
when propagating metadata info. The tag operations probably got servers that
knew about the new instances, but the update operation got one that didn't.
It would be better if we could avoid adding arbitrary waits everywhere just
to work around this problem with AWS. Is there something more direct we can do?
Though honestly, maybe just adding a second inside `wait_for_cluster_state()`
like you suggested is sufficient.
cc @JoshRosen @shivaram
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
