Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-9478

Reason for failing ipc.FairCallQueue contruction should be thrown

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.8.0, 2.7.3, 3.0.0-alpha1
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      When FairCallQueue Construction fails, NN fails to start throwing RunTimeException without throwing any reason on why it fails.

      2015-11-30 17:45:26,661 INFO org.apache.hadoop.ipc.FairCallQueue: FairCallQueue is in use with 4 queues.
      2015-11-30 17:45:26,665 DEBUG org.apache.hadoop.metrics2.util.MBeans: Registered Hadoop:service=ipc.65110,name=DecayRpcScheduler
      2015-11-30 17:45:26,666 ERROR org.apache.hadoop.hdfs.server.namenode.NameNode: Failed to start namenode.
      java.lang.RuntimeException: org.apache.hadoop.ipc.FairCallQueue could not be constructed.
      at org.apache.hadoop.ipc.CallQueueManager.createCallQueueInstance(CallQueueManager.java:96)
      at org.apache.hadoop.ipc.CallQueueManager.<init>(CallQueueManager.java:55)
      at org.apache.hadoop.ipc.Server.<init>(Server.java:2241)
      at org.apache.hadoop.ipc.RPC$Server.<init>(RPC.java:942)
      at org.apache.hadoop.ipc.ProtobufRpcEngine$Server.<init>(ProtobufRpcEngine.java:534)
      at org.apache.hadoop.ipc.ProtobufRpcEngine.getServer(ProtobufRpcEngine.java:509)
      at org.apache.hadoop.ipc.RPC$Builder.build(RPC.java:784)
      at org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.<init>(NameNodeRpcServer.java:346)
      at org.apache.hadoop.hdfs.server.namenode.NameNode.createRpcServer(NameNode.java:750)
      at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:687)
      at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:889)
      at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:872)

      Example: reason for above failure could have been –
      1. the weights were not equal to the number of queues configured.
      2. decay-scheduler.thresholds not in sync with number of queues.

        Attachments

        1. HDFS-9478.3.patch
          3 kB
          Ajith S
        2. HDFS-9478.2.patch
          3 kB
          Ajith S
        3. HDFS-9478.patch
          2 kB
          Ajith S

          Activity

            People

            • Assignee:
              ajithshetty Ajith S
              Reporter:
              archanat Archana T
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: