[GitHub] spark pull request: [SPARK-2228] change hard coded EVENT_QUEUE_CAP...

2014-08-25 Thread andrewor14
Github user andrewor14 commented on the pull request: https://github.com/apache/spark/pull/1257#issuecomment-53314914 @bxshi This is fixed in #1679. Would you mind closing this PR? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

[GitHub] spark pull request: [SPARK-2228] change hard coded EVENT_QUEUE_CAP...

2014-08-25 Thread bxshi
Github user bxshi closed the pull request at: https://github.com/apache/spark/pull/1257 --- 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

[GitHub] spark pull request: [SPARK-2228] change hard coded EVENT_QUEUE_CAP...

2014-08-25 Thread bxshi
Github user bxshi commented on the pull request: https://github.com/apache/spark/pull/1257#issuecomment-53315109 Sure, np. Baoxu Shi(Dash) Computer Science and Engineering Department University of Notre Dame On Aug 25, 2014, at 3:26 PM,

[GitHub] spark pull request: [SPARK-2228] change hard coded EVENT_QUEUE_CAP...

2014-08-02 Thread pwendell
Github user pwendell commented on the pull request: https://github.com/apache/spark/pull/1257#issuecomment-50971654 Okay we fixed the underlying issue in #1579 - would you mind closing this for now? --- If your project is set up for it, you can reply to this email and have your

[GitHub] spark pull request: [SPARK-2228] change hard coded EVENT_QUEUE_CAP...

2014-06-29 Thread rxin
Github user rxin commented on the pull request: https://github.com/apache/spark/pull/1257#issuecomment-47448132 @pwendell why 1 then? Like why not 1000, or 1M? --- 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

[GitHub] spark pull request: [SPARK-2228] change hard coded EVENT_QUEUE_CAP...

2014-06-28 Thread pwendell
Github user pwendell commented on the pull request: https://github.com/apache/spark/pull/1257#issuecomment-47434691 I commented on the JIRA, but I don't think this should be configurable. If someone overflows this buffer it means there program is not in steady state (the buffer is