Grokbase › Groups › Hadoop › common-dev › June 2009
FAQ
jobtracker stops when namenode goes out of safemode runing capacit scheduler
----------------------------------------------------------------------------

Key: HADOOP-6035
URL: https://issues.apache.org/jira/browse/HADOOP-6035
Project: Hadoop Core
Issue Type: Bug
Affects Versions: 0.20.0
Environment: Fedora 10
Reporter: Anjali M
Priority: Minor


I am facing a problem running the capacity scheduler in hadoop-0.20.0.
The jobtracker is listing the queues when namenode is in the safemode.
Once the namenode goes out of the safemode the jt stops working. On
accessing jobqueue details it shows the following error.

HTTP ERROR: 500

INTERNAL_SERVER_ERROR

RequestURI=/jobqueue_details.jsp
Caused by:

java.lang.NullPointerException
at org.apache.hadoop.mapred.JobQueuesManager.getRunningJobQueue(JobQueuesManager.java:156)
at org.apache.hadoop.mapred.CapacityTaskScheduler.getJobs(CapacityTaskScheduler.java:1495)
at org.apache.hadoop.mapred.jobqueue_005fdetails_jsp._jspService(jobqueue_005fdetails_jsp.java:64)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)


Is it because any of the configuration in capacity-scheduler.xml is incorrect?

I tried forcing the namenode out of the safemode in bin/hadoop
dfsadmin, but still it does not work.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Search Discussions

  • Hemanth Yamijala (JIRA) at Jun 15, 2009 at 3:56 am ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719383#action_12719383 ]

    Hemanth Yamijala commented on HADOOP-6035:
    ------------------------------------------

    Hi, can you tell us what is the configuration for the capacity scheduler ? Have you changed any of the defaults ? Have you added any queues ?
    jobtracker stops when namenode goes out of safemode runing capacit scheduler
    ----------------------------------------------------------------------------

    Key: HADOOP-6035
    URL: https://issues.apache.org/jira/browse/HADOOP-6035
    Project: Hadoop Core
    Issue Type: Bug
    Affects Versions: 0.20.0
    Environment: Fedora 10
    Reporter: Anjali M
    Priority: Minor

    I am facing a problem running the capacity scheduler in hadoop-0.20.0.
    The jobtracker is listing the queues when namenode is in the safemode.
    Once the namenode goes out of the safemode the jt stops working. On
    accessing jobqueue details it shows the following error.
    HTTP ERROR: 500
    INTERNAL_SERVER_ERROR
    RequestURI=/jobqueue_details.jsp
    Caused by:
    java.lang.NullPointerException
    at org.apache.hadoop.mapred.JobQueuesManager.getRunningJobQueue(JobQueuesManager.java:156)
    at org.apache.hadoop.mapred.CapacityTaskScheduler.getJobs(CapacityTaskScheduler.java:1495)
    at org.apache.hadoop.mapred.jobqueue_005fdetails_jsp._jspService(jobqueue_005fdetails_jsp.java:64)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:324)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
    Is it because any of the configuration in capacity-scheduler.xml is incorrect?
    I tried forcing the namenode out of the safemode in bin/hadoop
    dfsadmin, but still it does not work.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Anjali M (JIRA) at Jun 15, 2009 at 6:46 am ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719424#action_12719424 ]

    Anjali M commented on HADOOP-6035:
    ----------------------------------

    I've added a single queue and has not changed any defaluts. I'm using hadoop-0.20.0. I used the capcity scheduler in contrib/ of hadoop. The fair scheduler is working fine. The queues of capacity scheduler are also being listed in the jobtrackerUI as long as namenode is in safemode. Once the namenode goes out of the safemode the jobtracker gets stopped.
    jobtracker stops when namenode goes out of safemode runing capacit scheduler
    ----------------------------------------------------------------------------

    Key: HADOOP-6035
    URL: https://issues.apache.org/jira/browse/HADOOP-6035
    Project: Hadoop Core
    Issue Type: Bug
    Affects Versions: 0.20.0
    Environment: Fedora 10
    Reporter: Anjali M
    Priority: Minor

    I am facing a problem running the capacity scheduler in hadoop-0.20.0.
    The jobtracker is listing the queues when namenode is in the safemode.
    Once the namenode goes out of the safemode the jt stops working. On
    accessing jobqueue details it shows the following error.
    HTTP ERROR: 500
    INTERNAL_SERVER_ERROR
    RequestURI=/jobqueue_details.jsp
    Caused by:
    java.lang.NullPointerException
    at org.apache.hadoop.mapred.JobQueuesManager.getRunningJobQueue(JobQueuesManager.java:156)
    at org.apache.hadoop.mapred.CapacityTaskScheduler.getJobs(CapacityTaskScheduler.java:1495)
    at org.apache.hadoop.mapred.jobqueue_005fdetails_jsp._jspService(jobqueue_005fdetails_jsp.java:64)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:324)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
    Is it because any of the configuration in capacity-scheduler.xml is incorrect?
    I tried forcing the namenode out of the safemode in bin/hadoop
    dfsadmin, but still it does not work.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Hemanth Yamijala (JIRA) at Jun 15, 2009 at 6:54 am ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719426#action_12719426 ]

    Hemanth Yamijala commented on HADOOP-6035:
    ------------------------------------------

    It would help me if you can provide the following information:

    - The value of mapred.queue.names from mapred-site.xml (or hadoop-site.xml, if you're using the older format)
    - The contents of capacity-scheduler.xml on the jobtracker node (if you can attach the file to this JIRA, that would help).

    FYI, I am trying to debug the exception you've reported in the description above. It may or may not be related to the jobtracker 'stopping' to work after the namenode comes out of safemode. We can go one problem at a time.


    jobtracker stops when namenode goes out of safemode runing capacit scheduler
    ----------------------------------------------------------------------------

    Key: HADOOP-6035
    URL: https://issues.apache.org/jira/browse/HADOOP-6035
    Project: Hadoop Core
    Issue Type: Bug
    Affects Versions: 0.20.0
    Environment: Fedora 10
    Reporter: Anjali M
    Priority: Minor

    I am facing a problem running the capacity scheduler in hadoop-0.20.0.
    The jobtracker is listing the queues when namenode is in the safemode.
    Once the namenode goes out of the safemode the jt stops working. On
    accessing jobqueue details it shows the following error.
    HTTP ERROR: 500
    INTERNAL_SERVER_ERROR
    RequestURI=/jobqueue_details.jsp
    Caused by:
    java.lang.NullPointerException
    at org.apache.hadoop.mapred.JobQueuesManager.getRunningJobQueue(JobQueuesManager.java:156)
    at org.apache.hadoop.mapred.CapacityTaskScheduler.getJobs(CapacityTaskScheduler.java:1495)
    at org.apache.hadoop.mapred.jobqueue_005fdetails_jsp._jspService(jobqueue_005fdetails_jsp.java:64)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:324)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
    Is it because any of the configuration in capacity-scheduler.xml is incorrect?
    I tried forcing the namenode out of the safemode in bin/hadoop
    dfsadmin, but still it does not work.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Anjali M (JIRA) at Jun 17, 2009 at 4:36 am ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720493#action_12720493 ]

    Anjali M commented on HADOOP-6035:
    ----------------------------------

    I am attching the files hadoop-site.xml and capacity-scheduler.xml in hadoop-0.19.1. While working with this version too the same errors are being generated.

    jobtracker stops when namenode goes out of safemode runing capacit scheduler
    ----------------------------------------------------------------------------

    Key: HADOOP-6035
    URL: https://issues.apache.org/jira/browse/HADOOP-6035
    Project: Hadoop Core
    Issue Type: Bug
    Affects Versions: 0.20.0
    Environment: Fedora 10
    Reporter: Anjali M
    Priority: Minor
    Attachments: capacity-scheduler.xml, hadoop-site.xml


    I am facing a problem running the capacity scheduler in hadoop-0.20.0.
    The jobtracker is listing the queues when namenode is in the safemode.
    Once the namenode goes out of the safemode the jt stops working. On
    accessing jobqueue details it shows the following error.
    HTTP ERROR: 500
    INTERNAL_SERVER_ERROR
    RequestURI=/jobqueue_details.jsp
    Caused by:
    java.lang.NullPointerException
    at org.apache.hadoop.mapred.JobQueuesManager.getRunningJobQueue(JobQueuesManager.java:156)
    at org.apache.hadoop.mapred.CapacityTaskScheduler.getJobs(CapacityTaskScheduler.java:1495)
    at org.apache.hadoop.mapred.jobqueue_005fdetails_jsp._jspService(jobqueue_005fdetails_jsp.java:64)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:324)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
    Is it because any of the configuration in capacity-scheduler.xml is incorrect?
    I tried forcing the namenode out of the safemode in bin/hadoop
    dfsadmin, but still it does not work.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Anjali M (JIRA) at Jun 17, 2009 at 4:36 am ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Anjali M updated HADOOP-6035:
    -----------------------------

    Attachment: hadoop-site.xml
    capacity-scheduler.xml
    jobtracker stops when namenode goes out of safemode runing capacit scheduler
    ----------------------------------------------------------------------------

    Key: HADOOP-6035
    URL: https://issues.apache.org/jira/browse/HADOOP-6035
    Project: Hadoop Core
    Issue Type: Bug
    Affects Versions: 0.20.0
    Environment: Fedora 10
    Reporter: Anjali M
    Priority: Minor
    Attachments: capacity-scheduler.xml, hadoop-site.xml


    I am facing a problem running the capacity scheduler in hadoop-0.20.0.
    The jobtracker is listing the queues when namenode is in the safemode.
    Once the namenode goes out of the safemode the jt stops working. On
    accessing jobqueue details it shows the following error.
    HTTP ERROR: 500
    INTERNAL_SERVER_ERROR
    RequestURI=/jobqueue_details.jsp
    Caused by:
    java.lang.NullPointerException
    at org.apache.hadoop.mapred.JobQueuesManager.getRunningJobQueue(JobQueuesManager.java:156)
    at org.apache.hadoop.mapred.CapacityTaskScheduler.getJobs(CapacityTaskScheduler.java:1495)
    at org.apache.hadoop.mapred.jobqueue_005fdetails_jsp._jspService(jobqueue_005fdetails_jsp.java:64)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:324)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
    Is it because any of the configuration in capacity-scheduler.xml is incorrect?
    I tried forcing the namenode out of the safemode in bin/hadoop
    dfsadmin, but still it does not work.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Hemanth Yamijala (JIRA) at Jun 17, 2009 at 5:16 am ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720499#action_12720499 ]

    Hemanth Yamijala commented on HADOOP-6035:
    ------------------------------------------

    I think the problem is that the key mapred.queue.names in hadoop-site.xml has a space at the end. AFAIK, this does not work. Can you please try removing the space and try ?
    jobtracker stops when namenode goes out of safemode runing capacit scheduler
    ----------------------------------------------------------------------------

    Key: HADOOP-6035
    URL: https://issues.apache.org/jira/browse/HADOOP-6035
    Project: Hadoop Core
    Issue Type: Bug
    Affects Versions: 0.20.0
    Environment: Fedora 10
    Reporter: Anjali M
    Priority: Minor
    Attachments: capacity-scheduler.xml, hadoop-site.xml


    I am facing a problem running the capacity scheduler in hadoop-0.20.0.
    The jobtracker is listing the queues when namenode is in the safemode.
    Once the namenode goes out of the safemode the jt stops working. On
    accessing jobqueue details it shows the following error.
    HTTP ERROR: 500
    INTERNAL_SERVER_ERROR
    RequestURI=/jobqueue_details.jsp
    Caused by:
    java.lang.NullPointerException
    at org.apache.hadoop.mapred.JobQueuesManager.getRunningJobQueue(JobQueuesManager.java:156)
    at org.apache.hadoop.mapred.CapacityTaskScheduler.getJobs(CapacityTaskScheduler.java:1495)
    at org.apache.hadoop.mapred.jobqueue_005fdetails_jsp._jspService(jobqueue_005fdetails_jsp.java:64)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:324)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
    Is it because any of the configuration in capacity-scheduler.xml is incorrect?
    I tried forcing the namenode out of the safemode in bin/hadoop
    dfsadmin, but still it does not work.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Anjali M (JIRA) at Jun 17, 2009 at 9:44 am ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720588#action_12720588 ]

    Anjali M commented on HADOOP-6035:
    ----------------------------------

    Thank you.I'll try it out. It never came to my notice. Thanks a lot.
    jobtracker stops when namenode goes out of safemode runing capacit scheduler
    ----------------------------------------------------------------------------

    Key: HADOOP-6035
    URL: https://issues.apache.org/jira/browse/HADOOP-6035
    Project: Hadoop Core
    Issue Type: Bug
    Affects Versions: 0.20.0
    Environment: Fedora 10
    Reporter: Anjali M
    Priority: Minor
    Attachments: capacity-scheduler.xml, hadoop-site.xml


    I am facing a problem running the capacity scheduler in hadoop-0.20.0.
    The jobtracker is listing the queues when namenode is in the safemode.
    Once the namenode goes out of the safemode the jt stops working. On
    accessing jobqueue details it shows the following error.
    HTTP ERROR: 500
    INTERNAL_SERVER_ERROR
    RequestURI=/jobqueue_details.jsp
    Caused by:
    java.lang.NullPointerException
    at org.apache.hadoop.mapred.JobQueuesManager.getRunningJobQueue(JobQueuesManager.java:156)
    at org.apache.hadoop.mapred.CapacityTaskScheduler.getJobs(CapacityTaskScheduler.java:1495)
    at org.apache.hadoop.mapred.jobqueue_005fdetails_jsp._jspService(jobqueue_005fdetails_jsp.java:64)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:324)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
    Is it because any of the configuration in capacity-scheduler.xml is incorrect?
    I tried forcing the namenode out of the safemode in bin/hadoop
    dfsadmin, but still it does not work.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Anjali M (JIRA) at Jun 17, 2009 at 5:14 pm ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720765#action_12720765 ]

    Anjali M commented on HADOOP-6035:
    ----------------------------------

    Sir, I tried removing the space, but still it does not work. This is the case with both 0.19.1 as well as 0.20.0. The same errors are being generated even after removing the space.
    jobtracker stops when namenode goes out of safemode runing capacit scheduler
    ----------------------------------------------------------------------------

    Key: HADOOP-6035
    URL: https://issues.apache.org/jira/browse/HADOOP-6035
    Project: Hadoop Core
    Issue Type: Bug
    Affects Versions: 0.20.0
    Environment: Fedora 10
    Reporter: Anjali M
    Priority: Minor
    Attachments: capacity-scheduler.xml, hadoop-site.xml


    I am facing a problem running the capacity scheduler in hadoop-0.20.0.
    The jobtracker is listing the queues when namenode is in the safemode.
    Once the namenode goes out of the safemode the jt stops working. On
    accessing jobqueue details it shows the following error.
    HTTP ERROR: 500
    INTERNAL_SERVER_ERROR
    RequestURI=/jobqueue_details.jsp
    Caused by:
    java.lang.NullPointerException
    at org.apache.hadoop.mapred.JobQueuesManager.getRunningJobQueue(JobQueuesManager.java:156)
    at org.apache.hadoop.mapred.CapacityTaskScheduler.getJobs(CapacityTaskScheduler.java:1495)
    at org.apache.hadoop.mapred.jobqueue_005fdetails_jsp._jspService(jobqueue_005fdetails_jsp.java:64)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:324)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
    Is it because any of the configuration in capacity-scheduler.xml is incorrect?
    I tried forcing the namenode out of the safemode in bin/hadoop
    dfsadmin, but still it does not work.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Hemanth Yamijala (JIRA) at Jun 18, 2009 at 4:13 am ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721049#action_12721049 ]

    Hemanth Yamijala commented on HADOOP-6035:
    ------------------------------------------

    Yikes. I noticed another error, probably the more important one. You have this in the mapred-site.xml:

    {noformat}
    <property>
    <name>mapred.job.tracker</name>
    <value>hdfs://localhost:9001</value>
    </property>
    {noformat}

    The value of this configuration variable should just be localhost:9001. It is not a URI, and definitely should not be prepended with 'hdfs://' which is the name of a filesystem URI. Can you please retry with this ?
    jobtracker stops when namenode goes out of safemode runing capacit scheduler
    ----------------------------------------------------------------------------

    Key: HADOOP-6035
    URL: https://issues.apache.org/jira/browse/HADOOP-6035
    Project: Hadoop Core
    Issue Type: Bug
    Affects Versions: 0.20.0
    Environment: Fedora 10
    Reporter: Anjali M
    Priority: Minor
    Attachments: capacity-scheduler.xml, hadoop-site.xml


    I am facing a problem running the capacity scheduler in hadoop-0.20.0.
    The jobtracker is listing the queues when namenode is in the safemode.
    Once the namenode goes out of the safemode the jt stops working. On
    accessing jobqueue details it shows the following error.
    HTTP ERROR: 500
    INTERNAL_SERVER_ERROR
    RequestURI=/jobqueue_details.jsp
    Caused by:
    java.lang.NullPointerException
    at org.apache.hadoop.mapred.JobQueuesManager.getRunningJobQueue(JobQueuesManager.java:156)
    at org.apache.hadoop.mapred.CapacityTaskScheduler.getJobs(CapacityTaskScheduler.java:1495)
    at org.apache.hadoop.mapred.jobqueue_005fdetails_jsp._jspService(jobqueue_005fdetails_jsp.java:64)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:324)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
    Is it because any of the configuration in capacity-scheduler.xml is incorrect?
    I tried forcing the namenode out of the safemode in bin/hadoop
    dfsadmin, but still it does not work.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Anjali M (JIRA) at Jun 18, 2009 at 5:34 pm ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721363#action_12721363 ]

    Anjali M commented on HADOOP-6035:
    ----------------------------------

    sorry sir... but this too does not work. I tried this out too. can you think of any reason why the namenode is going to the safemode as soon as we start running it.
    jobtracker stops when namenode goes out of safemode runing capacit scheduler
    ----------------------------------------------------------------------------

    Key: HADOOP-6035
    URL: https://issues.apache.org/jira/browse/HADOOP-6035
    Project: Hadoop Core
    Issue Type: Bug
    Affects Versions: 0.20.0
    Environment: Fedora 10
    Reporter: Anjali M
    Priority: Minor
    Attachments: capacity-scheduler.xml, hadoop-site.xml


    I am facing a problem running the capacity scheduler in hadoop-0.20.0.
    The jobtracker is listing the queues when namenode is in the safemode.
    Once the namenode goes out of the safemode the jt stops working. On
    accessing jobqueue details it shows the following error.
    HTTP ERROR: 500
    INTERNAL_SERVER_ERROR
    RequestURI=/jobqueue_details.jsp
    Caused by:
    java.lang.NullPointerException
    at org.apache.hadoop.mapred.JobQueuesManager.getRunningJobQueue(JobQueuesManager.java:156)
    at org.apache.hadoop.mapred.CapacityTaskScheduler.getJobs(CapacityTaskScheduler.java:1495)
    at org.apache.hadoop.mapred.jobqueue_005fdetails_jsp._jspService(jobqueue_005fdetails_jsp.java:64)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:324)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
    Is it because any of the configuration in capacity-scheduler.xml is incorrect?
    I tried forcing the namenode out of the safemode in bin/hadoop
    dfsadmin, but still it does not work.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Hemanth Yamijala (JIRA) at Jun 19, 2009 at 3:49 am ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721640#action_12721640 ]

    Hemanth Yamijala commented on HADOOP-6035:
    ------------------------------------------

    The namenode goes into the safemode if you are starting on an existing installation of HDFS. This is the time when it reconstructs state from the transaction logs that it has written. It also waits until it has information from the datanodes about blocks they have, etc. It is not a problem for the namenode to go into safemode at startup. If it doesn't automatically come out of it, then that could be a problem. So, is the namenode coming out of safemode ? And if you don't want to start on an existing installation, you must format the filesystem before you start. All this information is available at the Forrest documentation here: http://hadoop.apache.org/core/docs/r0.20.0/hdfs_user_guide.html.

    So, let us step back and see the problem statement: You are starting a cluster. The namenode goes into safemode and comes out of it (maybe you forcibly do this - using the dfsadmin command). Then the jobtracker goes down. This is happening only if you use the capacity scheduler, but not if you use the fairshare scheduler. Is this right so far ?

    Now that we've fixed the configuration, I think we could look at the logs. Can you please upload the jobtracker log to begin with ?




    jobtracker stops when namenode goes out of safemode runing capacit scheduler
    ----------------------------------------------------------------------------

    Key: HADOOP-6035
    URL: https://issues.apache.org/jira/browse/HADOOP-6035
    Project: Hadoop Core
    Issue Type: Bug
    Affects Versions: 0.20.0
    Environment: Fedora 10
    Reporter: Anjali M
    Priority: Minor
    Attachments: capacity-scheduler.xml, hadoop-site.xml


    I am facing a problem running the capacity scheduler in hadoop-0.20.0.
    The jobtracker is listing the queues when namenode is in the safemode.
    Once the namenode goes out of the safemode the jt stops working. On
    accessing jobqueue details it shows the following error.
    HTTP ERROR: 500
    INTERNAL_SERVER_ERROR
    RequestURI=/jobqueue_details.jsp
    Caused by:
    java.lang.NullPointerException
    at org.apache.hadoop.mapred.JobQueuesManager.getRunningJobQueue(JobQueuesManager.java:156)
    at org.apache.hadoop.mapred.CapacityTaskScheduler.getJobs(CapacityTaskScheduler.java:1495)
    at org.apache.hadoop.mapred.jobqueue_005fdetails_jsp._jspService(jobqueue_005fdetails_jsp.java:64)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:324)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
    Is it because any of the configuration in capacity-scheduler.xml is incorrect?
    I tried forcing the namenode out of the safemode in bin/hadoop
    dfsadmin, but still it does not work.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Anjali M (JIRA) at Jun 22, 2009 at 7:48 am ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722497#action_12722497 ]

    Anjali M commented on HADOOP-6035:
    ----------------------------------

    sorry abt the late response. whatever you have reported is right. that is the problem.
    the namenode is automaticaly coming out of the safemode without forcing it out. No job can be run because the jobtracker stops as soon as the namenode comes out of the safemode.
    The jobtracker log is attached.
    jobtracker stops when namenode goes out of safemode runing capacit scheduler
    ----------------------------------------------------------------------------

    Key: HADOOP-6035
    URL: https://issues.apache.org/jira/browse/HADOOP-6035
    Project: Hadoop Common
    Issue Type: Bug
    Affects Versions: 0.20.0
    Environment: Fedora 10
    Reporter: Anjali M
    Priority: Minor
    Attachments: capacity-scheduler.xml, hadoop-site.xml


    I am facing a problem running the capacity scheduler in hadoop-0.20.0.
    The jobtracker is listing the queues when namenode is in the safemode.
    Once the namenode goes out of the safemode the jt stops working. On
    accessing jobqueue details it shows the following error.
    HTTP ERROR: 500
    INTERNAL_SERVER_ERROR
    RequestURI=/jobqueue_details.jsp
    Caused by:
    java.lang.NullPointerException
    at org.apache.hadoop.mapred.JobQueuesManager.getRunningJobQueue(JobQueuesManager.java:156)
    at org.apache.hadoop.mapred.CapacityTaskScheduler.getJobs(CapacityTaskScheduler.java:1495)
    at org.apache.hadoop.mapred.jobqueue_005fdetails_jsp._jspService(jobqueue_005fdetails_jsp.java:64)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:324)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
    Is it because any of the configuration in capacity-scheduler.xml is incorrect?
    I tried forcing the namenode out of the safemode in bin/hadoop
    dfsadmin, but still it does not work.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Anjali M (JIRA) at Jun 22, 2009 at 7:50 am ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Anjali M updated HADOOP-6035:
    -----------------------------

    Attachment: hadoop-hadoop-jobtracker-anjus.in.log

    the attachment is of version-0.19.1.
    jobtracker stops when namenode goes out of safemode runing capacit scheduler
    ----------------------------------------------------------------------------

    Key: HADOOP-6035
    URL: https://issues.apache.org/jira/browse/HADOOP-6035
    Project: Hadoop Common
    Issue Type: Bug
    Affects Versions: 0.20.0
    Environment: Fedora 10
    Reporter: Anjali M
    Priority: Minor
    Attachments: capacity-scheduler.xml, hadoop-hadoop-jobtracker-anjus.in.log, hadoop-site.xml


    I am facing a problem running the capacity scheduler in hadoop-0.20.0.
    The jobtracker is listing the queues when namenode is in the safemode.
    Once the namenode goes out of the safemode the jt stops working. On
    accessing jobqueue details it shows the following error.
    HTTP ERROR: 500
    INTERNAL_SERVER_ERROR
    RequestURI=/jobqueue_details.jsp
    Caused by:
    java.lang.NullPointerException
    at org.apache.hadoop.mapred.JobQueuesManager.getRunningJobQueue(JobQueuesManager.java:156)
    at org.apache.hadoop.mapred.CapacityTaskScheduler.getJobs(CapacityTaskScheduler.java:1495)
    at org.apache.hadoop.mapred.jobqueue_005fdetails_jsp._jspService(jobqueue_005fdetails_jsp.java:64)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:324)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
    Is it because any of the configuration in capacity-scheduler.xml is incorrect?
    I tried forcing the namenode out of the safemode in bin/hadoop
    dfsadmin, but still it does not work.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • rahul k singh (JIRA) at Jun 23, 2009 at 6:17 am ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722982#action_12722982 ]

    rahul k singh commented on HADOOP-6035:
    ---------------------------------------

    2009-06-22 18:20:38,850 INFO org.apache.hadoop.mapred.JobTracker: Cleaning up the system directory
    2009-06-22 18:20:38,961 FATAL org.apache.hadoop.mapred.JobTracker: org.apache.hadoop.mapred.JobTracker$IllegalStateException: System has no default queue configured
    at org.apache.hadoop.mapred.CapacityTaskScheduler.start(CapacityTaskScheduler.java:1033)
    at org.apache.hadoop.mapred.JobTracker.offerService(JobTracker.java:1283)
    at org.apache.hadoop.mapred.JobTracker.main(JobTracker.java:2791)


    I can see following exception in the log , in the earlier versions of capacity scheduler we are specifically checking for a queue Name
    "default".

    Please create 1 more queue by name "default" and also add respective entries in capacity-scheduler.xml with proper settings , or change your existing queue name "q1" to "default" .

    I hope this helps.
    If you say further issues , do attach the logs and respective config files.


    jobtracker stops when namenode goes out of safemode runing capacit scheduler
    ----------------------------------------------------------------------------

    Key: HADOOP-6035
    URL: https://issues.apache.org/jira/browse/HADOOP-6035
    Project: Hadoop Common
    Issue Type: Bug
    Affects Versions: 0.20.0
    Environment: Fedora 10
    Reporter: Anjali M
    Priority: Minor
    Attachments: capacity-scheduler.xml, hadoop-hadoop-jobtracker-anjus.in.log, hadoop-site.xml


    I am facing a problem running the capacity scheduler in hadoop-0.20.0.
    The jobtracker is listing the queues when namenode is in the safemode.
    Once the namenode goes out of the safemode the jt stops working. On
    accessing jobqueue details it shows the following error.
    HTTP ERROR: 500
    INTERNAL_SERVER_ERROR
    RequestURI=/jobqueue_details.jsp
    Caused by:
    java.lang.NullPointerException
    at org.apache.hadoop.mapred.JobQueuesManager.getRunningJobQueue(JobQueuesManager.java:156)
    at org.apache.hadoop.mapred.CapacityTaskScheduler.getJobs(CapacityTaskScheduler.java:1495)
    at org.apache.hadoop.mapred.jobqueue_005fdetails_jsp._jspService(jobqueue_005fdetails_jsp.java:64)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:324)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
    Is it because any of the configuration in capacity-scheduler.xml is incorrect?
    I tried forcing the namenode out of the safemode in bin/hadoop
    dfsadmin, but still it does not work.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Anjali M (JIRA) at Jun 24, 2009 at 3:25 pm ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723599#action_12723599 ]

    Anjali M commented on HADOOP-6035:
    ----------------------------------

    I tried that too. But still the problem persists. Two queues q1 and default were used. Attaching the log files. Now it also shows the problem of the namenode not coming out of the safemode automatically. Once it is forced out of safemode, the jobtracker stops running.
    jobtracker stops when namenode goes out of safemode runing capacit scheduler
    ----------------------------------------------------------------------------

    Key: HADOOP-6035
    URL: https://issues.apache.org/jira/browse/HADOOP-6035
    Project: Hadoop Common
    Issue Type: Bug
    Affects Versions: 0.20.0
    Environment: Fedora 10
    Reporter: Anjali M
    Priority: Minor
    Attachments: capacity-scheduler.xml, hadoop-hadoop-jobtracker-anjus.in.log, hadoop-site.xml


    I am facing a problem running the capacity scheduler in hadoop-0.20.0.
    The jobtracker is listing the queues when namenode is in the safemode.
    Once the namenode goes out of the safemode the jt stops working. On
    accessing jobqueue details it shows the following error.
    HTTP ERROR: 500
    INTERNAL_SERVER_ERROR
    RequestURI=/jobqueue_details.jsp
    Caused by:
    java.lang.NullPointerException
    at org.apache.hadoop.mapred.JobQueuesManager.getRunningJobQueue(JobQueuesManager.java:156)
    at org.apache.hadoop.mapred.CapacityTaskScheduler.getJobs(CapacityTaskScheduler.java:1495)
    at org.apache.hadoop.mapred.jobqueue_005fdetails_jsp._jspService(jobqueue_005fdetails_jsp.java:64)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:324)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
    Is it because any of the configuration in capacity-scheduler.xml is incorrect?
    I tried forcing the namenode out of the safemode in bin/hadoop
    dfsadmin, but still it does not work.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Anjali M (JIRA) at Jun 24, 2009 at 3:27 pm ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Anjali M updated HADOOP-6035:
    -----------------------------

    Attachment: hadoop-hadoop-tasktracker-anjus.in.log.2009-06-24
    jobtracker stops when namenode goes out of safemode runing capacit scheduler
    ----------------------------------------------------------------------------

    Key: HADOOP-6035
    URL: https://issues.apache.org/jira/browse/HADOOP-6035
    Project: Hadoop Common
    Issue Type: Bug
    Affects Versions: 0.20.0
    Environment: Fedora 10
    Reporter: Anjali M
    Priority: Minor
    Attachments: capacity-scheduler.xml, hadoop-hadoop-jobtracker-anjus.in.log, hadoop-hadoop-tasktracker-anjus.in.log.2009-06-24, hadoop-site.xml


    I am facing a problem running the capacity scheduler in hadoop-0.20.0.
    The jobtracker is listing the queues when namenode is in the safemode.
    Once the namenode goes out of the safemode the jt stops working. On
    accessing jobqueue details it shows the following error.
    HTTP ERROR: 500
    INTERNAL_SERVER_ERROR
    RequestURI=/jobqueue_details.jsp
    Caused by:
    java.lang.NullPointerException
    at org.apache.hadoop.mapred.JobQueuesManager.getRunningJobQueue(JobQueuesManager.java:156)
    at org.apache.hadoop.mapred.CapacityTaskScheduler.getJobs(CapacityTaskScheduler.java:1495)
    at org.apache.hadoop.mapred.jobqueue_005fdetails_jsp._jspService(jobqueue_005fdetails_jsp.java:64)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:324)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
    Is it because any of the configuration in capacity-scheduler.xml is incorrect?
    I tried forcing the namenode out of the safemode in bin/hadoop
    dfsadmin, but still it does not work.
    --
    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 13, '09 at 6:19a
activeJun 24, '09 at 3:27p
posts17
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

Anjali M (JIRA): 17 posts

Content

People

Support

Translate

site design / logo © 2022 Grokbase