Github user ksakellis commented on a diff in the pull request:
https://github.com/apache/spark/pull/4067#discussion_r23952709
--- Diff: core/src/main/scala/org/apache/spark/CacheManager.scala ---
@@ -47,9 +49,13 @@ private[spark] class CacheManager(blockManager:
BlockManager) extends Logging {
val inputMetrics = blockResult.inputMetrics
val existingMetrics = context.taskMetrics
.getInputMetricsForReadMethod(inputMetrics.readMethod)
- existingMetrics.addBytesRead(inputMetrics.bytesRead)
+ existingMetrics.incBytesRead(inputMetrics.bytesRead)
- new InterruptibleIterator(context,
blockResult.data.asInstanceOf[Iterator[T]])
+ val iter = blockResult.data.asInstanceOf[Iterator[T]]
+ new InterruptibleIterator(context,
AfterNextInterceptingIterator(iter, (next: T) => {
+ existingMetrics.incRecordsRead(1)
--- End diff --
I'd like to get to my first question about removing AtomicLong. Are we
absolutely sure that more than one thread in the executor will never touch
InputMetrics now and possibly in the future? I already made the changes to
adding the counting into InterruptableIterator but now I'd like clarity on
AtomicLong vs. Long.
---
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]
