[jira] [Updated] (YARN-1773) ShuffleHeader should have a format that can inform about errors

2016-06-14 Thread Varun Saxena (JIRA)

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

Varun Saxena updated YARN-1773:
---
Assignee: (was: Varun Saxena)

> ShuffleHeader should have a format that can inform about errors
> ---
>
> Key: YARN-1773
> URL: https://issues.apache.org/jira/browse/YARN-1773
> Project: Hadoop YARN
>  Issue Type: Bug
>Affects Versions: 2.3.0, 2.4.0
>Reporter: Bikas Saha
>Priority: Critical
>
> Currently, the ShuffleHeader (which is a Writable) simply tries to read the 
> successful header (mapid, reduceid etc). If there is an error then the input 
> will have an error message instead of (mapid, reducedid etc). Thus parsing 
> the ShuffleHeader fails and since we dont know where the error message ends, 
> we cannot consume the remaining input stream which may have good data from 
> the remaining map outputs. Being able to encode the error in the 
> ShuffleHeader will let us parse out the error correctly and move on to the 
> remaining data.
> The shuffle handler response should say which maps are in error and which are 
> fine, what the error was for the erroneous maps. These will help report 
> diagnostics for easier upstream reporting.



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

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



[jira] [Updated] (YARN-1773) ShuffleHeader should have a format that can inform about errors

2015-05-01 Thread Jian He (JIRA)

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

Jian He updated YARN-1773:
--
Target Version/s:   (was: 2.6.0)

 ShuffleHeader should have a format that can inform about errors
 ---

 Key: YARN-1773
 URL: https://issues.apache.org/jira/browse/YARN-1773
 Project: Hadoop YARN
  Issue Type: Bug
Affects Versions: 2.3.0, 2.4.0
Reporter: Bikas Saha
Assignee: Varun Saxena
Priority: Critical

 Currently, the ShuffleHeader (which is a Writable) simply tries to read the 
 successful header (mapid, reduceid etc). If there is an error then the input 
 will have an error message instead of (mapid, reducedid etc). Thus parsing 
 the ShuffleHeader fails and since we dont know where the error message ends, 
 we cannot consume the remaining input stream which may have good data from 
 the remaining map outputs. Being able to encode the error in the 
 ShuffleHeader will let us parse out the error correctly and move on to the 
 remaining data.
 The shuffle handler response should say which maps are in error and which are 
 fine, what the error was for the erroneous maps. These will help report 
 diagnostics for easier upstream reporting.



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


[jira] [Updated] (YARN-1773) ShuffleHeader should have a format that can inform about errors

2014-07-02 Thread Karthik Kambatla (JIRA)

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

Karthik Kambatla updated YARN-1773:
---

Target Version/s: 2.6.0  (was: 2.5.0)

 ShuffleHeader should have a format that can inform about errors
 ---

 Key: YARN-1773
 URL: https://issues.apache.org/jira/browse/YARN-1773
 Project: Hadoop YARN
  Issue Type: Bug
Affects Versions: 2.3.0, 2.4.0
Reporter: Bikas Saha
Priority: Critical

 Currently, the ShuffleHeader (which is a Writable) simply tries to read the 
 successful header (mapid, reduceid etc). If there is an error then the input 
 will have an error message instead of (mapid, reducedid etc). Thus parsing 
 the ShuffleHeader fails and since we dont know where the error message ends, 
 we cannot consume the remaining input stream which may have good data from 
 the remaining map outputs. Being able to encode the error in the 
 ShuffleHeader will let us parse out the error correctly and move on to the 
 remaining data.
 The shuffle handler response should say which maps are in error and which are 
 fine, what the error was for the erroneous maps. These will help report 
 diagnostics for easier upstream reporting.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (YARN-1773) ShuffleHeader should have a format that can inform about errors

2014-06-23 Thread Gopal V (JIRA)

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

Gopal V updated YARN-1773:
--

 Target Version/s: 2.5.0  (was: 2.4.0)
Affects Version/s: 2.4.0

 ShuffleHeader should have a format that can inform about errors
 ---

 Key: YARN-1773
 URL: https://issues.apache.org/jira/browse/YARN-1773
 Project: Hadoop YARN
  Issue Type: Bug
Affects Versions: 2.3.0, 2.4.0
Reporter: Bikas Saha
Priority: Critical

 Currently, the ShuffleHeader (which is a Writable) simply tries to read the 
 successful header (mapid, reduceid etc). If there is an error then the input 
 will have an error message instead of (mapid, reducedid etc). Thus parsing 
 the ShuffleHeader fails and since we dont know where the error message ends, 
 we cannot consume the remaining input stream which may have good data from 
 the remaining map outputs. Being able to encode the error in the 
 ShuffleHeader will let us parse out the error correctly and move on to the 
 remaining data.
 The shuffle handler response should say which maps are in error and which are 
 fine, what the error was for the erroneous maps. These will help report 
 diagnostics for easier upstream reporting.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (YARN-1773) ShuffleHeader should have a format that can inform about errors

2014-04-11 Thread Bikas Saha (JIRA)

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

Bikas Saha updated YARN-1773:
-

Description: 
Currently, the ShuffleHeader (which is a Writable) simply tries to read the 
successful header (mapid, reduceid etc). If there is an error then the input 
will have an error message instead of (mapid, reducedid etc). Thus parsing the 
ShuffleHeader fails and since we dont know where the error message ends, we 
cannot consume the remaining input stream which may have good data from the 
remaining map outputs. Being able to encode the error in the ShuffleHeader will 
let us parse out the error correctly and move on to the remaining data.
The shuffle handler response should say which maps are in error and which are 
fine, what the error was for the erroneous maps. These will help report 
diagnostics for easier upstream reporting.

  was:Currently, the ShuffleHeader (which is a Writable) simply tries to read 
the successful header (mapid, reduceid etc). If there is an error then the 
input will have an error message instead of (mapid, reducedid etc). Thus 
parsing the ShuffleHeader fails and since we dont know where the error message 
ends, we cannot consume the remaining input stream which may have good data 
from the remaining map outputs. Being able to encode the error in the 
ShuffleHeader will let us parse out the error correctly and move on to the 
remaining data.


 ShuffleHeader should have a format that can inform about errors
 ---

 Key: YARN-1773
 URL: https://issues.apache.org/jira/browse/YARN-1773
 Project: Hadoop YARN
  Issue Type: Bug
Affects Versions: 2.3.0
Reporter: Bikas Saha
Priority: Critical

 Currently, the ShuffleHeader (which is a Writable) simply tries to read the 
 successful header (mapid, reduceid etc). If there is an error then the input 
 will have an error message instead of (mapid, reducedid etc). Thus parsing 
 the ShuffleHeader fails and since we dont know where the error message ends, 
 we cannot consume the remaining input stream which may have good data from 
 the remaining map outputs. Being able to encode the error in the 
 ShuffleHeader will let us parse out the error correctly and move on to the 
 remaining data.
 The shuffle handler response should say which maps are in error and which are 
 fine, what the error was for the erroneous maps. These will help report 
 diagnostics for easier upstream reporting.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (YARN-1773) ShuffleHeader should have a format that can inform about errors

2014-02-28 Thread Karthik Kambatla (JIRA)

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

Karthik Kambatla updated YARN-1773:
---

Priority: Critical  (was: Major)
Target Version/s: 2.4.0

 ShuffleHeader should have a format that can inform about errors
 ---

 Key: YARN-1773
 URL: https://issues.apache.org/jira/browse/YARN-1773
 Project: Hadoop YARN
  Issue Type: Bug
Affects Versions: 2.3.0
Reporter: Bikas Saha
Priority: Critical

 Currently, the ShuffleHeader (which is a Writable) simply tries to read the 
 successful header (mapid, reduceid etc). If there is an error then the input 
 will have an error message instead of (mapid, reducedid etc). Thus parsing 
 the ShuffleHeader fails and since we dont know where the error message ends, 
 we cannot consume the remaining input stream which may have good data from 
 the remaining map outputs. Being able to encode the error in the 
 ShuffleHeader will let us parse out the error correctly and move on to the 
 remaining data.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)