Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/7160#issuecomment-118181016
Good points; I suppose unpersisting without blocking might cause other
slowdowns which could cause other timeouts to occur. This does seem like the
kind of change which might require running all of the MLlib tests in spark-perf
on a cluster to test for speed changes. Perhaps a better solution in the
meantime is simply to adjust timeout settings as needed.
@mengxr I'm OK with closing the JIRA if it does not seem worth the trouble
of testing. @ilganeli I doubt we have the bandwidth to test right now, but do
let us know if you'd like to keep this open & run tests.
---
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]
