You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2012/06/22 02:21:42 UTC
[jira] [Created] (MAPREDUCE-4362) If possible, we should get back
the feature of propagating task logs bag to JobClient
Vinod Kumar Vavilapalli created MAPREDUCE-4362:
--------------------------------------------------
Summary: If possible, we should get back the feature of propagating task logs bag to JobClient
Key: MAPREDUCE-4362
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4362
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: client, mrv2
Affects Versions: 2.0.1-alpha
Reporter: Vinod Kumar Vavilapalli
MAPREDUCE-3889 removed the code which was trying to pull from /tasklog. We should see if it is possible to get back the feature.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4362) If possible, we should get back
the feature of propagating task logs back to JobClient
Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli updated MAPREDUCE-4362:
-----------------------------------------------
Summary: If possible, we should get back the feature of propagating task logs back to JobClient (was: If possible, we should get back the feature of propagating task logs bag to JobClient)
> If possible, we should get back the feature of propagating task logs back to JobClient
> --------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4362
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4362
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client, mrv2
> Affects Versions: 2.0.1-alpha
> Reporter: Vinod Kumar Vavilapalli
>
> MAPREDUCE-3889 removed the code which was trying to pull from /tasklog. We should see if it is possible to get back the feature.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4362) If possible, we should get back
the feature of propagating task logs bag to JobClient
Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399019#comment-13399019 ]
Vinod Kumar Vavilapalli commented on MAPREDUCE-4362:
----------------------------------------------------
As I noted one MAPREDUCE-3889
bq. But the problem is that the client doesn't have a way of mapping TaskAttemptId to the ContainerIDs so that the log-urls can be constructed properly. So may be for the shorter term, we can disable the feature completely.
May be we should add an API to ClientProtocol to get this? Thoughts?
> If possible, we should get back the feature of propagating task logs bag to JobClient
> -------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4362
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4362
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client, mrv2
> Affects Versions: 2.0.1-alpha
> Reporter: Vinod Kumar Vavilapalli
>
> MAPREDUCE-3889 removed the code which was trying to pull from /tasklog. We should see if it is possible to get back the feature.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4362) If possible, we should get back
the feature of propagating task logs back to JobClient
Posted by "Siddharth Seth (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399487#comment-13399487 ]
Siddharth Seth commented on MAPREDUCE-4362:
-------------------------------------------
ClientProtocol already has a {{getLogFileParams(JobID jobID, TaskAttemptID taskAttemptID)}} - which is used by the MR CLI to fetch logs. This should be usable.
> If possible, we should get back the feature of propagating task logs back to JobClient
> --------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4362
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4362
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client, mrv2
> Affects Versions: 2.0.1-alpha
> Reporter: Vinod Kumar Vavilapalli
>
> MAPREDUCE-3889 removed the code which was trying to pull from /tasklog. We should see if it is possible to get back the feature.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4362) If possible, we should get back
the feature of propagating task logs back to JobClient
Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399504#comment-13399504 ]
Vinod Kumar Vavilapalli commented on MAPREDUCE-4362:
----------------------------------------------------
Good. Forgot that we added this for dumping logs via JHS. We can use it then.
> If possible, we should get back the feature of propagating task logs back to JobClient
> --------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4362
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4362
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client, mrv2
> Affects Versions: 2.0.1-alpha
> Reporter: Vinod Kumar Vavilapalli
>
> MAPREDUCE-3889 removed the code which was trying to pull from /tasklog. We should see if it is possible to get back the feature.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4362) If possible, we should get back
the feature of propagating task logs back to JobClient
Posted by "Robert Joseph Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399316#comment-13399316 ]
Robert Joseph Evans commented on MAPREDUCE-4362:
------------------------------------------------
I agree, it should not be that hard to abstract away how we grab the logs, I thought there was already something like that in yarn logs, so it should not be too difficult if we know the container id and application state to get the logs back.
> If possible, we should get back the feature of propagating task logs back to JobClient
> --------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4362
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4362
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client, mrv2
> Affects Versions: 2.0.1-alpha
> Reporter: Vinod Kumar Vavilapalli
>
> MAPREDUCE-3889 removed the code which was trying to pull from /tasklog. We should see if it is possible to get back the feature.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira