Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/16936
I agreed with @srowen. Streaming should not need to know the details about
the mode, and when someone changes other modules, they won't know these codes
inside streaming. I would like to see a
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16936
Let us call @zsxwing for some suggestions.
---
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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16936
Hm it just seems like the wrong approach, to externally estimate whether in
theory it won't schedule. It is certainly a problem if streaming doesn't work
though users would already realize it. The
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16936
@srowen
> Does it really not work if not enough receivers can schedule?
That's not what I want to express. What I mean is the stream output can not
operate.
---
If your project is
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16936
(There is no detail in the JIRA that you point to.) I think we already
discussed this in part? this duplicates some logic about how cluster resource
management works. Does it really not work if not
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16936
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72928/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16936
Merged build finished. Test PASSed.
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16936
**[Test build #72928 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72928/testReport)**
for PR 16936 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16936
**[Test build #72928 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72928/testReport)**
for PR 16936 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16936
**[Test build #72926 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72926/testReport)**
for PR 16936 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16936
Merged build finished. Test FAILed.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16936
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72926/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16936
**[Test build #72926 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72926/testReport)**
for PR 16936 at commit
13 matches
Mail list logo
