Github user suyanNone commented on the pull request:
https://github.com/apache/spark/pull/8237#issuecomment-132054268
@tdas, yean, I agree with it will be confused in semantics, and for a batch
streaming system, it will not blocked the next batch as long as it will
finished quickly, even not larger than batch time. Ah...I still have a little
uncomfortable for launching empty tasks to executor, as we run spark on yarn,
the resource is based soft isolation, so it will occurs resource competition,
some times, even for empty task, the process time will larger than batch time.
---
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]
