[jira] [Commented] (MAPREDUCE-4607) Race condition in ReduceTask completion can result in Task being incorrectly failed
[
https://issues.apache.org/jira/browse/MAPREDUCE-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445652#comment-13445652
]
chackaravarthy commented on MAPREDUCE-4607:
---
you can add as part of this patch.
> Race condition in ReduceTask completion can result in Task being incorrectly
> failed
> ---
>
> Key: MAPREDUCE-4607
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4607
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Affects Versions: 2.1.0-alpha
>Reporter: Bikas Saha
>Assignee: Bikas Saha
> Attachments: MAPREDUCE-4607.1.patch
>
>
> Problem reported by chackaravarthy in MAPREDUCE-4252
> This problem has been handled when speculative task launched for map task and
> other attempt got failed (not killed)
> Can the similar kind of scenario can happen in case of reduce task?
> Consider the following scenario for reduce task in case of speculation (one
> attempt got killed):
> 1. A task attempt is started.
> 2. A speculative task attempt for the same task is started.
> 3. The first task attempt completes and causes the task to transition to
> SUCCEEDED.
> 4. Then speculative task attempt will be killed because of the completion of
> first attempt.
> As a result, internal error will be thrown from this attempt
> (TaskImpl.MapRetroactiveKilledTransition) and hence task attempt failure
> leads to job failure.
> TaskImpl.MapRetroactiveKilledTransition
> if (!TaskType.MAP.equals(task.getType())) {
> LOG.error("Unexpected event for REDUCE task " + event.getType());
> task.internalError(event.getType());
> }
> So, do we need to have following code in MapRetroactiveKilledTransition also
> just like in MapRetroactiveFailureTransition.
> if (event instanceof TaskTAttemptEvent) {
> TaskTAttemptEvent castEvent = (TaskTAttemptEvent) event;
> if (task.getState() == TaskState.SUCCEEDED &&
> !castEvent.getTaskAttemptID().equals(task.successfulAttempt)) {
> // don't allow a different task attempt to override a previous
> // succeeded state
> return TaskState.SUCCEEDED;
> }
> }
> please check whether this is a valid case and give your suggestion.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4607) Race condition in ReduceTask completion can result in Task being incorrectly failed
[
https://issues.apache.org/jira/browse/MAPREDUCE-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444791#comment-13444791
]
chackaravarthy commented on MAPREDUCE-4607:
---
No problem :)
One suggestion from me that you can add test case also (TestTaskImpl.java)
As of now only one test case is there which addresses *map task + speculation +
attempt failed*
I feel it would be better if you can add few more test cases as part of this
patch.
{quote}
1. reduce task + speculation + attempt failed
2. reduce task + speculation + attempt killed
3. map task + speculation + attempt killed
{quote}
Thanks
> Race condition in ReduceTask completion can result in Task being incorrectly
> failed
> ---
>
> Key: MAPREDUCE-4607
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4607
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Affects Versions: 2.1.0-alpha
>Reporter: Bikas Saha
>Assignee: Bikas Saha
> Attachments: MAPREDUCE-4607.1.patch
>
>
> Problem reported by chackaravarthy in MAPREDUCE-4252
> This problem has been handled when speculative task launched for map task and
> other attempt got failed (not killed)
> Can the similar kind of scenario can happen in case of reduce task?
> Consider the following scenario for reduce task in case of speculation (one
> attempt got killed):
> 1. A task attempt is started.
> 2. A speculative task attempt for the same task is started.
> 3. The first task attempt completes and causes the task to transition to
> SUCCEEDED.
> 4. Then speculative task attempt will be killed because of the completion of
> first attempt.
> As a result, internal error will be thrown from this attempt
> (TaskImpl.MapRetroactiveKilledTransition) and hence task attempt failure
> leads to job failure.
> TaskImpl.MapRetroactiveKilledTransition
> if (!TaskType.MAP.equals(task.getType())) {
> LOG.error("Unexpected event for REDUCE task " + event.getType());
> task.internalError(event.getType());
> }
> So, do we need to have following code in MapRetroactiveKilledTransition also
> just like in MapRetroactiveFailureTransition.
> if (event instanceof TaskTAttemptEvent) {
> TaskTAttemptEvent castEvent = (TaskTAttemptEvent) event;
> if (task.getState() == TaskState.SUCCEEDED &&
> !castEvent.getTaskAttemptID().equals(task.successfulAttempt)) {
> // don't allow a different task attempt to override a previous
> // succeeded state
> return TaskState.SUCCEEDED;
> }
> }
> please check whether this is a valid case and give your suggestion.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4607) Race condition in ReduceTask completion can result in Task being incorrectly failed
[
https://issues.apache.org/jira/browse/MAPREDUCE-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444740#comment-13444740
]
chackaravarthy commented on MAPREDUCE-4607:
---
Bikas,
Thanks for creating separate JIRA.
I would like to work on this and will upload the patch soon.
Thanks
> Race condition in ReduceTask completion can result in Task being incorrectly
> failed
> ---
>
> Key: MAPREDUCE-4607
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4607
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Affects Versions: 2.1.0-alpha
>Reporter: Bikas Saha
>Assignee: Bikas Saha
>
> Problem reported by chackaravarthy in MAPREDUCE-4252
> This problem has been handled when speculative task launched for map task and
> other attempt got failed (not killed)
> Can the similar kind of scenario can happen in case of reduce task?
> Consider the following scenario for reduce task in case of speculation (one
> attempt got killed):
> 1. A task attempt is started.
> 2. A speculative task attempt for the same task is started.
> 3. The first task attempt completes and causes the task to transition to
> SUCCEEDED.
> 4. Then speculative task attempt will be killed because of the completion of
> first attempt.
> As a result, internal error will be thrown from this attempt
> (TaskImpl.MapRetroactiveKilledTransition) and hence task attempt failure
> leads to job failure.
> TaskImpl.MapRetroactiveKilledTransition
> if (!TaskType.MAP.equals(task.getType())) {
> LOG.error("Unexpected event for REDUCE task " + event.getType());
> task.internalError(event.getType());
> }
> So, do we need to have following code in MapRetroactiveKilledTransition also
> just like in MapRetroactiveFailureTransition.
> if (event instanceof TaskTAttemptEvent) {
> TaskTAttemptEvent castEvent = (TaskTAttemptEvent) event;
> if (task.getState() == TaskState.SUCCEEDED &&
> !castEvent.getTaskAttemptID().equals(task.successfulAttempt)) {
> // don't allow a different task attempt to override a previous
> // succeeded state
> return TaskState.SUCCEEDED;
> }
> }
> please check whether this is a valid case and give your suggestion.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4252) MR2 job never completes with 1 pending task
[
https://issues.apache.org/jira/browse/MAPREDUCE-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443920#comment-13443920
]
chackaravarthy commented on MAPREDUCE-4252:
---
Hi Tom,
This problem has been handled when speculative task launched for map task and
other attempt got failed (not killed)
Can the similar kind of scenario can happen in case of reduce task?
Consider the following scenario for reduce task in case of speculation (one
attempt got killed):
{quote}
1. A task attempt is started.
2. A speculative task attempt for the same task is started.
3. The first task attempt completes and causes the task to transition to
SUCCEEDED.
4. Then speculative task attempt will be killed because of the completion of
first attempt.
{quote}
As a result, internal error will be thrown from this attempt
(*TaskImpl.MapRetroactiveKilledTransition*) and hence task attempt failure
leads to job failure.
{code:title=TaskImpl.MapRetroactiveKilledTransition|borderStyle=solid}
if (!TaskType.MAP.equals(task.getType())) {
LOG.error("Unexpected event for REDUCE task " + event.getType());
task.internalError(event.getType());
}
{code}
So, do we need to have following code in MapRetroactiveKilledTransition also
just like in MapRetroactiveFailureTransition.
{noformat}
if (event instanceof TaskTAttemptEvent) {
TaskTAttemptEvent castEvent = (TaskTAttemptEvent) event;
if (task.getState() == TaskState.SUCCEEDED &&
!castEvent.getTaskAttemptID().equals(task.successfulAttempt)) {
// don't allow a different task attempt to override a previous
// succeeded state
return TaskState.SUCCEEDED;
}
}
{noformat}
please check whether this is a valid case and give your suggestion.
Thanks
> MR2 job never completes with 1 pending task
> ---
>
> Key: MAPREDUCE-4252
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4252
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
>Affects Versions: 0.23.1
>Reporter: Tom White
>Assignee: Tom White
> Fix For: 0.23.3, 2.1.0-alpha, 3.0.0
>
> Attachments: MAPREDUCE-4252.patch, MAPREDUCE-4252.patch,
> MAPREDUCE-4252.patch, MAPREDUCE-4252.patch, MapReduce.png
>
>
> This was found by ATM:
> bq. I ran a teragen with 1000 map tasks. Many task attempts failed, but after
> 999 of the tasks had completed, the job is now sitting forever with 1 task
> "pending".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4049) plugin for generic shuffle service
[
https://issues.apache.org/jira/browse/MAPREDUCE-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443859#comment-13443859
]
chackaravarthy commented on MAPREDUCE-4049:
---
Avner,
yeah sure, I will let you know when I start working on that. Thanks for your
interest.
And regarding
{quote}Due to hard-coded expressions in hadoop code, it currently can’t benefit
from 3rd party ShuffleProviders .
The current TaskAttemptImpl.java code explicitly call: serviceData.put
(ShuffleHandler.MAPREDUCE_SHUFFLE_SERVICEID, ...) and ignores any additional
AuxiliaryService. Hence, 3rd party AuxillaryServices can’t receive
APPLICATION_INIT events
I consider the above limitation is separate to the patch purpose, hence, I used
a workaround in my environment and excluded it from my patch.
*Please let me know if you would like me to handle this limitation.* I can
approach it either through this JIRA issue, or in a separate one. I believe
that this limitation should not delay this patch commit.
{quote}
I wish that you can handle this limitation also through this JIRA itself so
that both shuffle consuming and providing will be pluggable and other provider
implementation also can work. its just my wish :)
And one doubt,
*So, won't be there any new interface ShuffleProviderPlugin in mrv2 as it is
already pluggable by adding as part of auxiliary services?*
Thanks
> plugin for generic shuffle service
> --
>
> Key: MAPREDUCE-4049
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4049
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: performance, task, tasktracker
>Affects Versions: 1.0.3, 1.1.0, 2.0.0-alpha, 3.0.0
>Reporter: Avner BenHanoch
> Labels: merge, plugin, rdma, shuffle
> Attachments: HADOOP-1.x.y.patch, Hadoop Shuffle Consumer Plugin
> TLD.rtf, Hadoop Shuffle Provider Plugin TLD.rtf, mapred-site.xml,
> mapreduce-4049.patch
>
>
> Support generic shuffle service as set of two plugins: ShuffleProvider &
> ShuffleConsumer.
> This will satisfy the following needs:
> # Better shuffle and merge performance. For example: we are working on
> shuffle plugin that performs shuffle over RDMA in fast networks (10gE, 40gE,
> or Infiniband) instead of using the current HTTP shuffle. Based on the fast
> RDMA shuffle, the plugin can also utilize a suitable merge approach during
> the intermediate merges. Hence, getting much better performance.
> # Satisfy MAPREDUCE-3060 - generic shuffle service for avoiding hidden
> dependency of NodeManager with a specific version of mapreduce shuffle
> (currently targeted to 0.24.0).
> References:
> # Hadoop Acceleration through Network Levitated Merging, by Prof. Weikuan Yu
> from Auburn University with others,
> [http://pasl.eng.auburn.edu/pubs/sc11-netlev.pdf]
> # I am attaching 2 documents with suggested Top Level Design for both plugins
> (currently, based on 1.0 branch)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4049) plugin for generic shuffle service
[
https://issues.apache.org/jira/browse/MAPREDUCE-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443816#comment-13443816
]
chackaravarthy commented on MAPREDUCE-4049:
---
Avner,
yeah I got it now. thanks for clarifying.
And I have got one more doubt.
{quote}
Here we are making ShuffleProvider and ShuffleConsumer as pluggable
So, *getting map output* has been made as pluggable.
Is it possible to make *writing map output* also pluggable?
{quote}
Thanks
> plugin for generic shuffle service
> --
>
> Key: MAPREDUCE-4049
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4049
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: performance, task, tasktracker
>Affects Versions: 1.0.3, 1.1.0, 2.0.0-alpha, 3.0.0
>Reporter: Avner BenHanoch
> Labels: merge, plugin, rdma, shuffle
> Attachments: HADOOP-1.x.y.patch, Hadoop Shuffle Consumer Plugin
> TLD.rtf, Hadoop Shuffle Provider Plugin TLD.rtf, mapred-site.xml,
> mapreduce-4049.patch
>
>
> Support generic shuffle service as set of two plugins: ShuffleProvider &
> ShuffleConsumer.
> This will satisfy the following needs:
> # Better shuffle and merge performance. For example: we are working on
> shuffle plugin that performs shuffle over RDMA in fast networks (10gE, 40gE,
> or Infiniband) instead of using the current HTTP shuffle. Based on the fast
> RDMA shuffle, the plugin can also utilize a suitable merge approach during
> the intermediate merges. Hence, getting much better performance.
> # Satisfy MAPREDUCE-3060 - generic shuffle service for avoiding hidden
> dependency of NodeManager with a specific version of mapreduce shuffle
> (currently targeted to 0.24.0).
> References:
> # Hadoop Acceleration through Network Levitated Merging, by Prof. Weikuan Yu
> from Auburn University with others,
> [http://pasl.eng.auburn.edu/pubs/sc11-netlev.pdf]
> # I am attaching 2 documents with suggested Top Level Design for both plugins
> (currently, based on 1.0 branch)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4049) plugin for generic shuffle service
[
https://issues.apache.org/jira/browse/MAPREDUCE-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443798#comment-13443798
]
chackaravarthy commented on MAPREDUCE-4049:
---
Hi Avner,
{quote}A *ShuffleConsumerPlugin* works either with the builtin ShuffleHandler
or with 3rd party ShuffleProviders which are loaded as AuxiliaryServices.{quote}
Guess you have wrongly mentioned as *ShuffleConsumerPlugin* instead of
*ShuffleProviderPlugin*
correct me if I am wrong
Thanks
> plugin for generic shuffle service
> --
>
> Key: MAPREDUCE-4049
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4049
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: performance, task, tasktracker
>Affects Versions: 1.0.3, 1.1.0, 2.0.0-alpha, 3.0.0
>Reporter: Avner BenHanoch
> Labels: merge, plugin, rdma, shuffle
> Attachments: HADOOP-1.x.y.patch, Hadoop Shuffle Consumer Plugin
> TLD.rtf, Hadoop Shuffle Provider Plugin TLD.rtf, mapred-site.xml,
> mapreduce-4049.patch
>
>
> Support generic shuffle service as set of two plugins: ShuffleProvider &
> ShuffleConsumer.
> This will satisfy the following needs:
> # Better shuffle and merge performance. For example: we are working on
> shuffle plugin that performs shuffle over RDMA in fast networks (10gE, 40gE,
> or Infiniband) instead of using the current HTTP shuffle. Based on the fast
> RDMA shuffle, the plugin can also utilize a suitable merge approach during
> the intermediate merges. Hence, getting much better performance.
> # Satisfy MAPREDUCE-3060 - generic shuffle service for avoiding hidden
> dependency of NodeManager with a specific version of mapreduce shuffle
> (currently targeted to 0.24.0).
> References:
> # Hadoop Acceleration through Network Levitated Merging, by Prof. Weikuan Yu
> from Auburn University with others,
> [http://pasl.eng.auburn.edu/pubs/sc11-netlev.pdf]
> # I am attaching 2 documents with suggested Top Level Design for both plugins
> (currently, based on 1.0 branch)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3020) Node link in reduce task attempt page is not working [Job History Page]
[ https://issues.apache.org/jira/browse/MAPREDUCE-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114527#comment-13114527 ] chackaravarthy commented on MAPREDUCE-3020: --- This is trivial change. In Job History Page (Reduce Tasks -> Task ID -> Node link) Earlier it was redirecting to wrong page (http://containerMgrAddress). It should be http://hostname > Node link in reduce task attempt page is not working [Job History Page] > --- > > Key: MAPREDUCE-3020 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3020 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobhistoryserver >Affects Versions: 0.23.0, 0.24.0 >Reporter: chackaravarthy > Fix For: 0.23.0, 0.24.0 > > Attachments: MAPREDUCE-3020.patch > > > RM UI -> Applications -> Application(Job History) -> Reduce Tasks -> Task ID > -> Node link is not working > hostname for ReduceAttemptFinishedEvent is coming wrong when loading from > history file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3020) Node link in reduce task attempt page is not working [Job History Page]
[ https://issues.apache.org/jira/browse/MAPREDUCE-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114493#comment-13114493 ] chackaravarthy commented on MAPREDUCE-3020: --- MAPREDUCE-3009 issue exists for this reduce task page also. Already submitted one patch for that issue. > Node link in reduce task attempt page is not working [Job History Page] > --- > > Key: MAPREDUCE-3020 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3020 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobhistoryserver >Affects Versions: 0.23.0, 0.24.0 >Reporter: chackaravarthy > Fix For: 0.23.0, 0.24.0 > > Attachments: MAPREDUCE-3020.patch > > > RM UI -> Applications -> Application(Job History) -> Reduce Tasks -> Task ID > -> Node link is not working > hostname for ReduceAttemptFinishedEvent is coming wrong when loading from > history file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3020) Node link in reduce task attempt page is not working [Job History Page]
[ https://issues.apache.org/jira/browse/MAPREDUCE-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114490#comment-13114490 ] chackaravarthy commented on MAPREDUCE-3020: --- The issue was : "when creating ReduceAttemptFinishedEvent, instead of passing nodeHostName for hostname, containerMgrAddress was passed".. But creation of MapAttemptFinishedEvent is done in right way.Hence changed the code with respect to that. > Node link in reduce task attempt page is not working [Job History Page] > --- > > Key: MAPREDUCE-3020 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3020 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobhistoryserver >Affects Versions: 0.23.0, 0.24.0 >Reporter: chackaravarthy > Fix For: 0.23.0, 0.24.0 > > Attachments: MAPREDUCE-3020.patch > > > RM UI -> Applications -> Application(Job History) -> Reduce Tasks -> Task ID > -> Node link is not working > hostname for ReduceAttemptFinishedEvent is coming wrong when loading from > history file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3020) Node link in reduce task attempt page is not working [Job History Page]
[ https://issues.apache.org/jira/browse/MAPREDUCE-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chackaravarthy updated MAPREDUCE-3020: -- Status: Patch Available (was: Open) Attached the patch. > Node link in reduce task attempt page is not working [Job History Page] > --- > > Key: MAPREDUCE-3020 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3020 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobhistoryserver >Affects Versions: 0.23.0, 0.24.0 >Reporter: chackaravarthy > Fix For: 0.23.0, 0.24.0 > > Attachments: MAPREDUCE-3020.patch > > > RM UI -> Applications -> Application(Job History) -> Reduce Tasks -> Task ID > -> Node link is not working > hostname for ReduceAttemptFinishedEvent is coming wrong when loading from > history file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3020) Node link in reduce task attempt page is not working [Job History Page]
[ https://issues.apache.org/jira/browse/MAPREDUCE-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chackaravarthy updated MAPREDUCE-3020: -- Attachment: MAPREDUCE-3020.patch > Node link in reduce task attempt page is not working [Job History Page] > --- > > Key: MAPREDUCE-3020 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3020 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobhistoryserver >Affects Versions: 0.23.0, 0.24.0 >Reporter: chackaravarthy > Fix For: 0.23.0, 0.24.0 > > Attachments: MAPREDUCE-3020.patch > > > RM UI -> Applications -> Application(Job History) -> Reduce Tasks -> Task ID > -> Node link is not working > hostname for ReduceAttemptFinishedEvent is coming wrong when loading from > history file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3009) RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> Node link is not working
[ https://issues.apache.org/jira/browse/MAPREDUCE-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107780#comment-13107780 ] chackaravarthy commented on MAPREDUCE-3009: --- pls check. Thanks > RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> > Node link is not working > - > > Key: MAPREDUCE-3009 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3009 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobhistoryserver >Affects Versions: 0.23.0, 0.24.0 >Reporter: chackaravarthy > Fix For: 0.24.0 > > Attachments: MAPREDUCE-3009.patch, invalid_url.png, > invalid_url_latest_code.png > > > RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> > Node link is not working. The URL contains extra '/' which is causing the > problem. Please find in the attached screen shots. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3009) RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> Node link is not working
[ https://issues.apache.org/jira/browse/MAPREDUCE-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chackaravarthy updated MAPREDUCE-3009: -- Attachment: invalid_url_latest_code.png I checked with updated code also. The same issue exists. Actually when I raised this issue, there were 2 links in this page (one for node and other one for logs) After HsTaskPage is updated (on 18th Sep) and hence there is only one link in that page (only node link) and i checked whether this has been resolved or not.. but that still exists.. so i changed the issue description removing logs link and keeping node link alone.. (Also you can see the advanced search boxes (in the attached snapshot invalid_url_latest_code.png) there for each column which is because of updated code on sep18th) > RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> > Node link is not working > - > > Key: MAPREDUCE-3009 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3009 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobhistoryserver >Affects Versions: 0.23.0, 0.24.0 >Reporter: chackaravarthy > Fix For: 0.24.0 > > Attachments: MAPREDUCE-3009.patch, invalid_url.png, > invalid_url_latest_code.png > > > RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> > Node link is not working. The URL contains extra '/' which is causing the > problem. Please find in the attached screen shots. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3009) RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> Node link is not working
[ https://issues.apache.org/jira/browse/MAPREDUCE-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107715#comment-13107715 ] chackaravarthy commented on MAPREDUCE-3009: --- Test cases are not required because it is a trivial change. > RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> > Node link is not working > - > > Key: MAPREDUCE-3009 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3009 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobhistoryserver >Affects Versions: 0.23.0, 0.24.0 >Reporter: chackaravarthy > Fix For: 0.24.0 > > Attachments: MAPREDUCE-3009.patch, invalid_url.png > > > RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> > Node link is not working. The URL contains extra '/' which is causing the > problem. Please find in the attached screen shots. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-3009) RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> Node link is not working
[
https://issues.apache.org/jira/browse/MAPREDUCE-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107622#comment-13107622
]
chackaravarthy commented on MAPREDUCE-3009:
---
Steps to verify :
=
RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID
Here task attempt page will open.
In the page, click on node link.
Earlier it was not working.. Now it will work
change in HsTaskPage.java:
==
Earlier the URL it was linked in anchor tag was http:///nodeHttpAddr
but it should be http://nodeHttpAddr
It is because "http://"; and nodeHttpAddr was passed as 2 strings to method
url(String... parts) in View.java
It should be passed as single string to url method.
hence the change as
before :td().a(".nodelink", url("http://";, nodeHttpAddr),
nodeHttpAddr)._();
after the fix : td().a(".nodelink", url("http://"+ nodeHttpAddr),
nodeHttpAddr)._();
> RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID ->
> Node link is not working
> -
>
> Key: MAPREDUCE-3009
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3009
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
>Affects Versions: 0.23.0, 0.24.0
>Reporter: chackaravarthy
> Fix For: 0.24.0
>
> Attachments: MAPREDUCE-3009.patch, invalid_url.png
>
>
> RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID ->
> Node link is not working. The URL contains extra '/' which is causing the
> problem. Please find in the attached screen shots.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3009) RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> Node link is not working
[ https://issues.apache.org/jira/browse/MAPREDUCE-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chackaravarthy updated MAPREDUCE-3009: -- Description: RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> Node link is not working. The URL contains extra '/' which is causing the problem. Please find in the attached screen shots. was: RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> Node & logs links are not working. The URL contains extra '/' which is causing the problem. Please find in the attached screen shots. Summary: RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> Node link is not working (was: RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> Node & logs links are not working) > RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> > Node link is not working > - > > Key: MAPREDUCE-3009 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3009 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobhistoryserver >Affects Versions: 0.23.0, 0.24.0 >Reporter: chackaravarthy > Fix For: 0.24.0 > > Attachments: MAPREDUCE-3009.patch, invalid_url.png > > > RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> > Node link is not working. The URL contains extra '/' which is causing the > problem. Please find in the attached screen shots. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3009) RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> Node & logs links are not working
[ https://issues.apache.org/jira/browse/MAPREDUCE-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chackaravarthy updated MAPREDUCE-3009: -- Fix Version/s: 0.24.0 Status: Patch Available (was: Open) Attached the patch > RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> > Node & logs links are not working > -- > > Key: MAPREDUCE-3009 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3009 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobhistoryserver >Affects Versions: 0.23.0, 0.24.0 >Reporter: chackaravarthy > Fix For: 0.24.0 > > Attachments: MAPREDUCE-3009.patch, invalid_url.png > > > RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> > Node & logs links are not working. The URL contains extra '/' which is > causing the problem. Please find in the attached screen shots. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3009) RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> Node & logs links are not working
[ https://issues.apache.org/jira/browse/MAPREDUCE-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chackaravarthy updated MAPREDUCE-3009: -- Attachment: MAPREDUCE-3009.patch > RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> > Node & logs links are not working > -- > > Key: MAPREDUCE-3009 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3009 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobhistoryserver >Affects Versions: 0.23.0, 0.24.0 >Reporter: chackaravarthy > Attachments: MAPREDUCE-3009.patch, invalid_url.png > > > RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> > Node & logs links are not working. The URL contains extra '/' which is > causing the problem. Please find in the attached screen shots. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MAPREDUCE-3020) Node link in reduce task attempt page is not working [Job History Page]
Node link in reduce task attempt page is not working [Job History Page] --- Key: MAPREDUCE-3020 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3020 Project: Hadoop Map/Reduce Issue Type: Bug Components: jobhistoryserver Affects Versions: 0.23.0, 0.24.0 Reporter: chackaravarthy Fix For: 0.23.0, 0.24.0 RM UI -> Applications -> Application(Job History) -> Reduce Tasks -> Task ID -> Node link is not working hostname for ReduceAttemptFinishedEvent is coming wrong when loading from history file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MAPREDUCE-3009) RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> Node & logs links are not working
RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> Node & logs links are not working -- Key: MAPREDUCE-3009 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3009 Project: Hadoop Map/Reduce Issue Type: Bug Components: jobhistoryserver Affects Versions: 0.23.0, 0.24.0 Reporter: chackaravarthy Attachments: invalid_url.png RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> Node & logs links are not working. The URL contains extra '/' which is causing the problem. Please find in the attached screen shots. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3009) RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> Node & logs links are not working
[ https://issues.apache.org/jira/browse/MAPREDUCE-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chackaravarthy updated MAPREDUCE-3009: -- Attachment: invalid_url.png > RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> > Node & logs links are not working > -- > > Key: MAPREDUCE-3009 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3009 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobhistoryserver >Affects Versions: 0.23.0, 0.24.0 >Reporter: chackaravarthy > Attachments: invalid_url.png > > > RM UI -> Applications -> Application(Job History) -> Map Tasks -> Task ID -> > Node & logs links are not working. The URL contains extra '/' which is > causing the problem. Please find in the attached screen shots. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
