Github user ilganeli commented on the pull request:

    https://github.com/apache/spark/pull/7160#issuecomment-118187601
  
    All - thanks for the clarification and weigh in. I don't have any pipelines 
set up that would exercise this with the level of rigor necessary. I think it's 
fine to close it for now. Thanks.
    
    
    
    Thank you,
    Ilya Ganelin
    
    
    
    -----Original Message-----
    From: jkbradley [[email protected]<mailto:[email protected]>]
    Sent: Thursday, July 02, 2015 06:09 PM Eastern Standard Time
    To: apache/spark
    Cc: Ganelin, Ilya
    Subject: Re: [spark] [SPARK-8733][MLLIB] ML RDD.unpersist calls should use 
blocking = false (#7160)
    
    
    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<https://github.com/mengxr> I'm OK with closing the JIRA if it does 
not seem worth the trouble of testing. @ilganeli<https://github.com/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.
    
    —
    Reply to this email directly or view it on 
GitHub<https://github.com/apache/spark/pull/7160#issuecomment-118181016>.
    ________________________________________________________
    
    The information contained in this e-mail is confidential and/or proprietary 
to Capital One and/or its affiliates and may only be used solely in performance 
of work or services for Capital One. The information transmitted herewith is 
intended only for use by the individual or entity to which it is addressed. If 
the reader of this message is not the intended recipient, you are hereby 
notified that any review, retransmission, dissemination, distribution, copying 
or other use of, or taking of any action in reliance upon this information is 
strictly prohibited. If you have received this communication in error, please 
contact the sender and delete the material from your computer.



---
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]

Reply via email to