Github user harishreedharan commented on the pull request:
https://github.com/apache/spark/pull/6508#issuecomment-106965307
Offline discussion with @vanzin - why go to executor to get the info when
we could get it from the driver?
The reason I went with this approach was that `getBlockStatus` API in
`BlockManagerMaster` suggests that the driver may not have the state of blocks
on an executor(see:
https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/storage/BlockManagerMaster.scala#L157).
If that API can be reliably used it might be better to just use that than talk
to the executors. Anyone knows why that API may not return the block status of
all blocks?
---
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
