FAQ
[ https://issues.apache.org/jira/browse/HADOOP-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602587#action_12602587 ]

Hadoop QA commented on HADOOP-2393:
-----------------------------------

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12383440/patch-2393.txt
against trunk revision 663487.

+1 @author. The patch does not contain any @author tags.

-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no tests are needed for this patch.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac compiler warnings.

+1 findbugs. The patch does not introduce any new Findbugs warnings.

+1 release audit. The applied patch does not increase the total number of release audit warnings.

-1 core tests. The patch failed core unit tests.

-1 contrib tests. The patch failed contrib unit tests.

Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2585/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2585/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2585/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2585/console

This message is automatically generated.
TaskTracker locks up removing job files within a synchronized method
---------------------------------------------------------------------

Key: HADOOP-2393
URL: https://issues.apache.org/jira/browse/HADOOP-2393
Project: Hadoop Core
Issue Type: Bug
Components: mapred
Affects Versions: 0.14.4
Environment: 0.13.1, quad-code x86-64, FC-linux. -xmx2048
ipc.client.timeout = 10000
Reporter: Joydeep Sen Sarma
Assignee: Amareshwari Sriramadasu
Priority: Critical
Fix For: 0.18.0

Attachments: patch-2393.txt, patch-2393.txt


we have some bad jobs where the reduces are getting stalled (for unknown reason). The task tracker kills these processes from time to time.
Everytime one of these events happens - other (healthy) map tasks in the same node are also killed. Looking at the logs and code up to 0.14.3 - it seems like the child tasks pings to the task tracker are timed out and the child task self-terminates.
tasktracker log:
// notice the good 10+ second gap in logs on otherwise busy node:
2007-12-10 09:26:53,047 INFO org.apache.hadoop.mapred.TaskRunner: task_0120_r_000001_47 done; removing files.
2007-12-10 09:27:26,878 INFO org.apache.hadoop.mapred.TaskRunner: task_0120_m_000618_0 done; removing files.
2007-12-10 09:27:26,883 INFO org.apache.hadoop.ipc.Server: Process Thread Dump: Discarding call ping(task_0149_m_000007_0) from 10.16.158.113:43941
24 active threads
... huge stack trace dump in logfile ...
something was going on at this time which caused to the tasktracker to essentially stall. all the pings are discarded. after stack trace dump:
2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 0 on 50050, call ping(task_0149_m_000007_0) from 10.16.158.113:43941:\
discarded for being too old (21380)
2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 1 on 50050, call ping(task_0149_m_000002_1) from 10.16.158.113:44183:\
discarded for being too old (21380)
2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 0 on 50050, call ping(task_0149_m_000007_0) from 10.16.158.113:43941:\
discarded for being too old (10367)
2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 1 on 50050, call ping(task_0149_m_000002_1) from 10.16.158.113:44183:\
discarded for being too old (10360)
2007-12-10 09:27:26,982 WARN org.apache.hadoop.mapred.TaskRunner: task_0149_m_000002_1 Child Error
looking at code, failure of client to ping causes termination:
else {
// send ping
taskFound = umbilical.ping(taskId);
}
...
catch (Throwable t) {
LOG.info("Communication exception: " + StringUtils.stringifyException(t));
remainingRetries -=1;
if (remainingRetries == 0) {
ReflectionUtils.logThreadInfo(LOG, "Communication exception", 0);
LOG.warn("Last retry, killing "+taskId);
System.exit(65);
exit code is 65 as reported by task tracker.
i don't see an option to turn off stack trace dump (which could be a likely cause) - and i would hate to bump up timeout because of this. Crap.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Search Discussions

  • Amareshwari Sriramadasu (JIRA) at Jun 5, 2008 at 9:38 am
    [ https://issues.apache.org/jira/browse/HADOOP-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602596#action_12602596 ]

    Amareshwari Sriramadasu commented on HADOOP-2393:
    -------------------------------------------------

    Testfailures org.apache.hadoop.fs.TestHarFileSystem.testArchives, org.apache.hadoop.streaming.TestStreamingFailure.testCommandLine are not related to the patch.
    This issue is fixing the bug by moving cleaup code from synchronization block. Test case is not written, because the existing tests will verify the correctness.
    TaskTracker locks up removing job files within a synchronized method
    ---------------------------------------------------------------------

    Key: HADOOP-2393
    URL: https://issues.apache.org/jira/browse/HADOOP-2393
    Project: Hadoop Core
    Issue Type: Bug
    Components: mapred
    Affects Versions: 0.14.4
    Environment: 0.13.1, quad-code x86-64, FC-linux. -xmx2048
    ipc.client.timeout = 10000
    Reporter: Joydeep Sen Sarma
    Assignee: Amareshwari Sriramadasu
    Priority: Critical
    Fix For: 0.18.0

    Attachments: patch-2393.txt, patch-2393.txt


    we have some bad jobs where the reduces are getting stalled (for unknown reason). The task tracker kills these processes from time to time.
    Everytime one of these events happens - other (healthy) map tasks in the same node are also killed. Looking at the logs and code up to 0.14.3 - it seems like the child tasks pings to the task tracker are timed out and the child task self-terminates.
    tasktracker log:
    // notice the good 10+ second gap in logs on otherwise busy node:
    2007-12-10 09:26:53,047 INFO org.apache.hadoop.mapred.TaskRunner: task_0120_r_000001_47 done; removing files.
    2007-12-10 09:27:26,878 INFO org.apache.hadoop.mapred.TaskRunner: task_0120_m_000618_0 done; removing files.
    2007-12-10 09:27:26,883 INFO org.apache.hadoop.ipc.Server: Process Thread Dump: Discarding call ping(task_0149_m_000007_0) from 10.16.158.113:43941
    24 active threads
    ... huge stack trace dump in logfile ...
    something was going on at this time which caused to the tasktracker to essentially stall. all the pings are discarded. after stack trace dump:
    2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 0 on 50050, call ping(task_0149_m_000007_0) from 10.16.158.113:43941:\
    discarded for being too old (21380)
    2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 1 on 50050, call ping(task_0149_m_000002_1) from 10.16.158.113:44183:\
    discarded for being too old (21380)
    2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 0 on 50050, call ping(task_0149_m_000007_0) from 10.16.158.113:43941:\
    discarded for being too old (10367)
    2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 1 on 50050, call ping(task_0149_m_000002_1) from 10.16.158.113:44183:\
    discarded for being too old (10360)
    2007-12-10 09:27:26,982 WARN org.apache.hadoop.mapred.TaskRunner: task_0149_m_000002_1 Child Error
    looking at code, failure of client to ping causes termination:
    else {
    // send ping
    taskFound = umbilical.ping(taskId);
    }
    ...
    catch (Throwable t) {
    LOG.info("Communication exception: " + StringUtils.stringifyException(t));
    remainingRetries -=1;
    if (remainingRetries == 0) {
    ReflectionUtils.logThreadInfo(LOG, "Communication exception", 0);
    LOG.warn("Last retry, killing "+taskId);
    System.exit(65);
    exit code is 65 as reported by task tracker.
    i don't see an option to turn off stack trace dump (which could be a likely cause) - and i would hate to bump up timeout because of this. Crap.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Devaraj Das (JIRA) at Jun 5, 2008 at 10:26 am
    [ https://issues.apache.org/jira/browse/HADOOP-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602607#action_12602607 ]

    Devaraj Das commented on HADOOP-2393:
    -------------------------------------

    Pls make the shuttingDown volatile.
    TaskTracker locks up removing job files within a synchronized method
    ---------------------------------------------------------------------

    Key: HADOOP-2393
    URL: https://issues.apache.org/jira/browse/HADOOP-2393
    Project: Hadoop Core
    Issue Type: Bug
    Components: mapred
    Affects Versions: 0.14.4
    Environment: 0.13.1, quad-code x86-64, FC-linux. -xmx2048
    ipc.client.timeout = 10000
    Reporter: Joydeep Sen Sarma
    Assignee: Amareshwari Sriramadasu
    Priority: Critical
    Fix For: 0.18.0

    Attachments: patch-2393.txt, patch-2393.txt


    we have some bad jobs where the reduces are getting stalled (for unknown reason). The task tracker kills these processes from time to time.
    Everytime one of these events happens - other (healthy) map tasks in the same node are also killed. Looking at the logs and code up to 0.14.3 - it seems like the child tasks pings to the task tracker are timed out and the child task self-terminates.
    tasktracker log:
    // notice the good 10+ second gap in logs on otherwise busy node:
    2007-12-10 09:26:53,047 INFO org.apache.hadoop.mapred.TaskRunner: task_0120_r_000001_47 done; removing files.
    2007-12-10 09:27:26,878 INFO org.apache.hadoop.mapred.TaskRunner: task_0120_m_000618_0 done; removing files.
    2007-12-10 09:27:26,883 INFO org.apache.hadoop.ipc.Server: Process Thread Dump: Discarding call ping(task_0149_m_000007_0) from 10.16.158.113:43941
    24 active threads
    ... huge stack trace dump in logfile ...
    something was going on at this time which caused to the tasktracker to essentially stall. all the pings are discarded. after stack trace dump:
    2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 0 on 50050, call ping(task_0149_m_000007_0) from 10.16.158.113:43941:\
    discarded for being too old (21380)
    2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 1 on 50050, call ping(task_0149_m_000002_1) from 10.16.158.113:44183:\
    discarded for being too old (21380)
    2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 0 on 50050, call ping(task_0149_m_000007_0) from 10.16.158.113:43941:\
    discarded for being too old (10367)
    2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 1 on 50050, call ping(task_0149_m_000002_1) from 10.16.158.113:44183:\
    discarded for being too old (10360)
    2007-12-10 09:27:26,982 WARN org.apache.hadoop.mapred.TaskRunner: task_0149_m_000002_1 Child Error
    looking at code, failure of client to ping causes termination:
    else {
    // send ping
    taskFound = umbilical.ping(taskId);
    }
    ...
    catch (Throwable t) {
    LOG.info("Communication exception: " + StringUtils.stringifyException(t));
    remainingRetries -=1;
    if (remainingRetries == 0) {
    ReflectionUtils.logThreadInfo(LOG, "Communication exception", 0);
    LOG.warn("Last retry, killing "+taskId);
    System.exit(65);
    exit code is 65 as reported by task tracker.
    i don't see an option to turn off stack trace dump (which could be a likely cause) - and i would hate to bump up timeout because of this. Crap.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Hadoop QA (JIRA) at Jun 5, 2008 at 4:20 pm
    [ https://issues.apache.org/jira/browse/HADOOP-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602694#action_12602694 ]

    Hadoop QA commented on HADOOP-2393:
    -----------------------------------

    -1 overall. Here are the results of testing the latest attachment
    http://issues.apache.org/jira/secure/attachment/12383453/patch-2393.txt
    against trunk revision 663487.

    +1 @author. The patch does not contain any @author tags.

    -1 tests included. The patch doesn't appear to include any new or modified tests.
    Please justify why no tests are needed for this patch.

    +1 javadoc. The javadoc tool did not generate any warning messages.

    +1 javac. The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs. The patch does not introduce any new Findbugs warnings.

    +1 release audit. The applied patch does not increase the total number of release audit warnings.

    -1 core tests. The patch failed core unit tests.

    -1 contrib tests. The patch failed contrib unit tests.

    Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2590/testReport/
    Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2590/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
    Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2590/artifact/trunk/build/test/checkstyle-errors.html
    Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2590/console

    This message is automatically generated.
    TaskTracker locks up removing job files within a synchronized method
    ---------------------------------------------------------------------

    Key: HADOOP-2393
    URL: https://issues.apache.org/jira/browse/HADOOP-2393
    Project: Hadoop Core
    Issue Type: Bug
    Components: mapred
    Affects Versions: 0.14.4
    Environment: 0.13.1, quad-code x86-64, FC-linux. -xmx2048
    ipc.client.timeout = 10000
    Reporter: Joydeep Sen Sarma
    Assignee: Amareshwari Sriramadasu
    Priority: Critical
    Fix For: 0.18.0

    Attachments: patch-2393.txt, patch-2393.txt, patch-2393.txt


    we have some bad jobs where the reduces are getting stalled (for unknown reason). The task tracker kills these processes from time to time.
    Everytime one of these events happens - other (healthy) map tasks in the same node are also killed. Looking at the logs and code up to 0.14.3 - it seems like the child tasks pings to the task tracker are timed out and the child task self-terminates.
    tasktracker log:
    // notice the good 10+ second gap in logs on otherwise busy node:
    2007-12-10 09:26:53,047 INFO org.apache.hadoop.mapred.TaskRunner: task_0120_r_000001_47 done; removing files.
    2007-12-10 09:27:26,878 INFO org.apache.hadoop.mapred.TaskRunner: task_0120_m_000618_0 done; removing files.
    2007-12-10 09:27:26,883 INFO org.apache.hadoop.ipc.Server: Process Thread Dump: Discarding call ping(task_0149_m_000007_0) from 10.16.158.113:43941
    24 active threads
    ... huge stack trace dump in logfile ...
    something was going on at this time which caused to the tasktracker to essentially stall. all the pings are discarded. after stack trace dump:
    2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 0 on 50050, call ping(task_0149_m_000007_0) from 10.16.158.113:43941:\
    discarded for being too old (21380)
    2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 1 on 50050, call ping(task_0149_m_000002_1) from 10.16.158.113:44183:\
    discarded for being too old (21380)
    2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 0 on 50050, call ping(task_0149_m_000007_0) from 10.16.158.113:43941:\
    discarded for being too old (10367)
    2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 1 on 50050, call ping(task_0149_m_000002_1) from 10.16.158.113:44183:\
    discarded for being too old (10360)
    2007-12-10 09:27:26,982 WARN org.apache.hadoop.mapred.TaskRunner: task_0149_m_000002_1 Child Error
    looking at code, failure of client to ping causes termination:
    else {
    // send ping
    taskFound = umbilical.ping(taskId);
    }
    ...
    catch (Throwable t) {
    LOG.info("Communication exception: " + StringUtils.stringifyException(t));
    remainingRetries -=1;
    if (remainingRetries == 0) {
    ReflectionUtils.logThreadInfo(LOG, "Communication exception", 0);
    LOG.warn("Last retry, killing "+taskId);
    System.exit(65);
    exit code is 65 as reported by task tracker.
    i don't see an option to turn off stack trace dump (which could be a likely cause) - and i would hate to bump up timeout because of this. Crap.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Hadoop QA (JIRA) at Jun 6, 2008 at 10:17 am
    [ https://issues.apache.org/jira/browse/HADOOP-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602978#action_12602978 ]

    Hadoop QA commented on HADOOP-2393:
    -----------------------------------

    -1 overall. Here are the results of testing the latest attachment
    http://issues.apache.org/jira/secure/attachment/12383535/patch-2393.txt
    against trunk revision 663841.

    +1 @author. The patch does not contain any @author tags.

    -1 tests included. The patch doesn't appear to include any new or modified tests.
    Please justify why no tests are needed for this patch.

    +1 javadoc. The javadoc tool did not generate any warning messages.

    +1 javac. The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs. The patch does not introduce any new Findbugs warnings.

    +1 release audit. The applied patch does not increase the total number of release audit warnings.

    -1 core tests. The patch failed core unit tests.

    +1 contrib tests. The patch passed contrib unit tests.

    Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2603/testReport/
    Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2603/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
    Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2603/artifact/trunk/build/test/checkstyle-errors.html
    Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2603/console

    This message is automatically generated.
    TaskTracker locks up removing job files within a synchronized method
    ---------------------------------------------------------------------

    Key: HADOOP-2393
    URL: https://issues.apache.org/jira/browse/HADOOP-2393
    Project: Hadoop Core
    Issue Type: Bug
    Components: mapred
    Affects Versions: 0.14.4
    Environment: 0.13.1, quad-code x86-64, FC-linux. -xmx2048
    ipc.client.timeout = 10000
    Reporter: Joydeep Sen Sarma
    Assignee: Amareshwari Sriramadasu
    Priority: Critical
    Fix For: 0.18.0

    Attachments: patch-2393.txt, patch-2393.txt, patch-2393.txt, patch-2393.txt


    we have some bad jobs where the reduces are getting stalled (for unknown reason). The task tracker kills these processes from time to time.
    Everytime one of these events happens - other (healthy) map tasks in the same node are also killed. Looking at the logs and code up to 0.14.3 - it seems like the child tasks pings to the task tracker are timed out and the child task self-terminates.
    tasktracker log:
    // notice the good 10+ second gap in logs on otherwise busy node:
    2007-12-10 09:26:53,047 INFO org.apache.hadoop.mapred.TaskRunner: task_0120_r_000001_47 done; removing files.
    2007-12-10 09:27:26,878 INFO org.apache.hadoop.mapred.TaskRunner: task_0120_m_000618_0 done; removing files.
    2007-12-10 09:27:26,883 INFO org.apache.hadoop.ipc.Server: Process Thread Dump: Discarding call ping(task_0149_m_000007_0) from 10.16.158.113:43941
    24 active threads
    ... huge stack trace dump in logfile ...
    something was going on at this time which caused to the tasktracker to essentially stall. all the pings are discarded. after stack trace dump:
    2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 0 on 50050, call ping(task_0149_m_000007_0) from 10.16.158.113:43941:\
    discarded for being too old (21380)
    2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 1 on 50050, call ping(task_0149_m_000002_1) from 10.16.158.113:44183:\
    discarded for being too old (21380)
    2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 0 on 50050, call ping(task_0149_m_000007_0) from 10.16.158.113:43941:\
    discarded for being too old (10367)
    2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 1 on 50050, call ping(task_0149_m_000002_1) from 10.16.158.113:44183:\
    discarded for being too old (10360)
    2007-12-10 09:27:26,982 WARN org.apache.hadoop.mapred.TaskRunner: task_0149_m_000002_1 Child Error
    looking at code, failure of client to ping causes termination:
    else {
    // send ping
    taskFound = umbilical.ping(taskId);
    }
    ...
    catch (Throwable t) {
    LOG.info("Communication exception: " + StringUtils.stringifyException(t));
    remainingRetries -=1;
    if (remainingRetries == 0) {
    ReflectionUtils.logThreadInfo(LOG, "Communication exception", 0);
    LOG.warn("Last retry, killing "+taskId);
    System.exit(65);
    exit code is 65 as reported by task tracker.
    i don't see an option to turn off stack trace dump (which could be a likely cause) - and i would hate to bump up timeout because of this. Crap.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Amareshwari Sriramadasu (JIRA) at Jun 6, 2008 at 10:29 am
    [ https://issues.apache.org/jira/browse/HADOOP-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602980#action_12602980 ]

    Amareshwari Sriramadasu commented on HADOOP-2393:
    -------------------------------------------------

    TestFailures are not related to the patch.
    TaskTracker locks up removing job files within a synchronized method
    ---------------------------------------------------------------------

    Key: HADOOP-2393
    URL: https://issues.apache.org/jira/browse/HADOOP-2393
    Project: Hadoop Core
    Issue Type: Bug
    Components: mapred
    Affects Versions: 0.14.4
    Environment: 0.13.1, quad-code x86-64, FC-linux. -xmx2048
    ipc.client.timeout = 10000
    Reporter: Joydeep Sen Sarma
    Assignee: Amareshwari Sriramadasu
    Priority: Critical
    Fix For: 0.18.0

    Attachments: patch-2393.txt, patch-2393.txt, patch-2393.txt, patch-2393.txt


    we have some bad jobs where the reduces are getting stalled (for unknown reason). The task tracker kills these processes from time to time.
    Everytime one of these events happens - other (healthy) map tasks in the same node are also killed. Looking at the logs and code up to 0.14.3 - it seems like the child tasks pings to the task tracker are timed out and the child task self-terminates.
    tasktracker log:
    // notice the good 10+ second gap in logs on otherwise busy node:
    2007-12-10 09:26:53,047 INFO org.apache.hadoop.mapred.TaskRunner: task_0120_r_000001_47 done; removing files.
    2007-12-10 09:27:26,878 INFO org.apache.hadoop.mapred.TaskRunner: task_0120_m_000618_0 done; removing files.
    2007-12-10 09:27:26,883 INFO org.apache.hadoop.ipc.Server: Process Thread Dump: Discarding call ping(task_0149_m_000007_0) from 10.16.158.113:43941
    24 active threads
    ... huge stack trace dump in logfile ...
    something was going on at this time which caused to the tasktracker to essentially stall. all the pings are discarded. after stack trace dump:
    2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 0 on 50050, call ping(task_0149_m_000007_0) from 10.16.158.113:43941:\
    discarded for being too old (21380)
    2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 1 on 50050, call ping(task_0149_m_000002_1) from 10.16.158.113:44183:\
    discarded for being too old (21380)
    2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 0 on 50050, call ping(task_0149_m_000007_0) from 10.16.158.113:43941:\
    discarded for being too old (10367)
    2007-12-10 09:27:26,883 WARN org.apache.hadoop.ipc.Server: IPC Server handler 1 on 50050, call ping(task_0149_m_000002_1) from 10.16.158.113:44183:\
    discarded for being too old (10360)
    2007-12-10 09:27:26,982 WARN org.apache.hadoop.mapred.TaskRunner: task_0149_m_000002_1 Child Error
    looking at code, failure of client to ping causes termination:
    else {
    // send ping
    taskFound = umbilical.ping(taskId);
    }
    ...
    catch (Throwable t) {
    LOG.info("Communication exception: " + StringUtils.stringifyException(t));
    remainingRetries -=1;
    if (remainingRetries == 0) {
    ReflectionUtils.logThreadInfo(LOG, "Communication exception", 0);
    LOG.warn("Last retry, killing "+taskId);
    System.exit(65);
    exit code is 65 as reported by task tracker.
    i don't see an option to turn off stack trace dump (which could be a likely cause) - and i would hate to bump up timeout because of this. Crap.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcommon-dev @
categorieshadoop
postedJun 5, '08 at 9:08a
activeJun 6, '08 at 10:29a
posts6
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

Amareshwari Sriramadasu (JIRA): 6 posts

People

Translate

site design / logo © 2022 Grokbase