Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/8417#issuecomment-142113658
@zsxwing I got the race condition already, but thank for adding that table,
makes it very very obvious. Regarding solution, I think I agree with
@harishreedharan at a high level. It is better to ensure that the existing
assumption on RecurringTimer is better met. There are number of uses of
RecurringTimer and its best if that gives more guarantees, rather than higher
layers work around its limitations. So could you make sure the it is guaranteed
that RecurringTimer will call the function one more time after stop is called?
---
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]
