spark-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From andrewor14 <...@git.apache.org>
Subject [GitHub] spark pull request: [SPARK-14065]Increase probability of using cac...
Date Tue, 03 May 2016 23:53:39 GMT
Github user andrewor14 commented on the pull request:

    https://github.com/apache/spark/pull/11886#issuecomment-216701518
  
    The high level fix makes sense. I think the right approach here would be to have a read
write lock, where all reads are concurrent but the writes block everything. However, that's
probably overkill here so I'm OK with the code as is.
    
    Are there any potential sources of regressions? Now we hold a lock while serializing,
which could take a while.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


Mime
View raw message