[jira] [Updated] (SPARK-5225) Support coalesed Input Metrics from different sources

2019-05-20 Thread Hyukjin Kwon (JIRA)


 [ 
https://issues.apache.org/jira/browse/SPARK-5225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hyukjin Kwon updated SPARK-5225:

Labels: bulk-closed  (was: )

> Support coalesed Input Metrics from different sources
> -
>
> Key: SPARK-5225
> URL: https://issues.apache.org/jira/browse/SPARK-5225
> Project: Spark
>  Issue Type: Improvement
>  Components: Spark Core
>Reporter: Kostas Sakellis
>Priority: Major
>  Labels: bulk-closed
>
> Currently, If task reads data from more than one block and it is from 
> different read methods we ignore the second read method bytes. For example:
> {noformat}
>   CoalescedRDD
>| 
>  Task1 
>  /  |  \   
>  hadoop  hadoop  cached
> {noformat}
> if Task1 starts reading from the hadoop blocks first, then the input metrics 
> for Task1 will only contain input metrics from the hadoop blocks and ignre 
> the input metrics from cached blocks. We need to change the way we collect 
> input metrics so that it is not a single value but rather a collection of 
> input metrics for a task. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org



[jira] [Updated] (SPARK-5225) Support coalesed Input Metrics from different sources

2015-05-15 Thread Sean Owen (JIRA)

 [ 
https://issues.apache.org/jira/browse/SPARK-5225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Owen updated SPARK-5225:
-
Issue Type: Improvement  (was: Bug)

 Support coalesed Input Metrics from different sources
 -

 Key: SPARK-5225
 URL: https://issues.apache.org/jira/browse/SPARK-5225
 Project: Spark
  Issue Type: Improvement
  Components: Spark Core
Reporter: Kostas Sakellis

 Currently, If task reads data from more than one block and it is from 
 different read methods we ignore the second read method bytes. For example:
 {noformat}
   CoalescedRDD
| 
  Task1 
  /  |  \   
  hadoop  hadoop  cached
 {noformat}
 if Task1 starts reading from the hadoop blocks first, then the input metrics 
 for Task1 will only contain input metrics from the hadoop blocks and ignre 
 the input metrics from cached blocks. We need to change the way we collect 
 input metrics so that it is not a single value but rather a collection of 
 input metrics for a task. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org



[jira] [Updated] (SPARK-5225) Support coalesed Input Metrics from different sources

2015-02-08 Thread Sean Owen (JIRA)

 [ 
https://issues.apache.org/jira/browse/SPARK-5225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Owen updated SPARK-5225:
-
Component/s: Spark Core

 Support coalesed Input Metrics from different sources
 -

 Key: SPARK-5225
 URL: https://issues.apache.org/jira/browse/SPARK-5225
 Project: Spark
  Issue Type: Bug
  Components: Spark Core
Reporter: Kostas Sakellis

 Currently, If task reads data from more than one block and it is from 
 different read methods we ignore the second read method bytes. For example:
 {noformat}
   CoalescedRDD
| 
  Task1 
  /  |  \   
  hadoop  hadoop  cached
 {noformat}
 if Task1 starts reading from the hadoop blocks first, then the input metrics 
 for Task1 will only contain input metrics from the hadoop blocks and ignre 
 the input metrics from cached blocks. We need to change the way we collect 
 input metrics so that it is not a single value but rather a collection of 
 input metrics for a task. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org



[jira] [Updated] (SPARK-5225) Support coalesed Input Metrics from different sources

2015-01-13 Thread Kostas Sakellis (JIRA)

 [ 
https://issues.apache.org/jira/browse/SPARK-5225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kostas Sakellis updated SPARK-5225:
---
Description: 
Currently, If task reads data from more than one block and it is from different 
read methods we ignore the second read method bytes. For example:
{noformat}
  CoalescedRDD
   | 
 Task1 
 /  |  \   
 hadoop  hadoop  cached
{noformat}
if Task1 starts reading from the hadoop blocks first, then the input metrics 
for Task1 will only contain input metrics from the hadoop blocks and ignre the 
input metrics from cached blocks. We need to change the way we collect input 
metrics so that it is not a single value but rather a collection of input 
metrics for a task. 

  was:
Currently, If task reads data from more than one block and it is from different 
read methods we ignore the second read method bytes. For example:
 CoalescedRDD
| 
Task1 
  / |\
/   |  \   
  hadoop   hadoop  cached

if Task1 starts reading from the hadoop blocks first, then the input metrics 
for Task1 will only contain input metrics from the hadoop blocks and ignre the 
input metrics from cached blocks. We need to change the way we collect input 
metrics so that it is not a single value but rather a collection of input 
metrics for a task. 


 Support coalesed Input Metrics from different sources
 -

 Key: SPARK-5225
 URL: https://issues.apache.org/jira/browse/SPARK-5225
 Project: Spark
  Issue Type: Bug
Reporter: Kostas Sakellis

 Currently, If task reads data from more than one block and it is from 
 different read methods we ignore the second read method bytes. For example:
 {noformat}
   CoalescedRDD
| 
  Task1 
  /  |  \   
  hadoop  hadoop  cached
 {noformat}
 if Task1 starts reading from the hadoop blocks first, then the input metrics 
 for Task1 will only contain input metrics from the hadoop blocks and ignre 
 the input metrics from cached blocks. We need to change the way we collect 
 input metrics so that it is not a single value but rather a collection of 
 input metrics for a task. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org