Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/7276#discussion_r34626645
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/ReceiverTracker.scala
---
@@ -227,6 +255,8 @@ class ReceiverTracker(ssc: StreamingContext,
skipReceiverLaunch: Boolean = false
case DeregisterReceiver(streamId, message, error) =>
deregisterReceiver(streamId, message, error)
context.reply(true)
+ case ScheduleReceiver(streamId) =>
--- End diff --
Good point. How about this.
The scheduler returns the following.
- if there are >= 3, zero-weight options, return all of them
- else return 3 best options.
Before submitting the job, run the scheduler and use those options to
launch the job. When the RegisterReceiver is called, you again run the
scheduler to get updated options and verify whether the host where the task was
actually launched is still in the best options. That should reduce the
likelihood of the above condition happening by a lot.
How does that sound?
---
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]
