Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/9603#issuecomment-159088257
Beyond that, the message is actually somewhat misleading. The "Stopping"
message occurs in `stop()`, which is responsible for stopping the
messageScheduler, eventProcessLoop and taskScheduler. When the "Starting"
message is logged, at least the eventProcessLoop and taskScheduler will already
have been started, so the argument from symmetry for "Starting" because there
is a "Stopping" doesn't hold even without considering that "Starting",
...logMessage, ...logMessage, ... isn't symmetrical to logMessage,
...logMessage, "Stopping" unless we can somehow run time both forwards and
backwards. There is also the problem that the "Starting" message is only sent
from the secondary constructors and not from the primary.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
