Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/3737#issuecomment-67665194
Yes, I've been getting this type of error with 1.1.1. I haven't had time to
look into it, but I suspect there is some subtle thing about the EC2 API that
we are not honoring which occasionally leads to this problem. It could also
just be general AWS flakiness (e.g. due to metadata like available instances
needing to be replicated and whatnot) that we need to account for.
I don't think this is related to the changes in this PR.
---
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]
