Github user mridulm commented on the issue:
https://github.com/apache/spark/pull/17276
@jinxing64
If the intent behind these metrics is to help with SPARK-19659, it would be
good to either add it as part of SPARK-19659 or subsequently (once the feature
is merged).
This ensures that the metrics added are actually relevant to the existing
spark core, and not a future expected evolution of the code - for example, the
review of SPARK-19659 might significantly change its design/implementation :
making some of these either irrelevant or require other more informative
metrics to be introduced.
I am unclear about the intention btw - do you expect shuffle reads to be
informed by metrics from the mapper side ? I probably got that wrong.
---
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]
