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

HDFS: add client rpc backoff metrics due to disconnection from lowest priority queue

    XMLWordPrintableJSON

Details

    • Reviewed

    Description

      Clients are backoff when rpcs cannot be enqueued. However there are different scenarios when backoff could happen. Currently there is no way to differenciate whether a backoff happened due to lowest prio+disconnection or queue overflow from higher priority queues when connection between client and namenode remains open. Currently IPC server just emits a single metrics for all the backoffs.

      Example:

      1. Client are directly enqueued into lowest priority queue and backoff when lowest queue is full. Client are expected to disconnect from namenode.
      2. Client are enqueued into non-lowest priority queue and overflowed all the way down to lowest priority queue and back off. In this case, connection between client and namenode remains open.

      We would like to add metrics for #1

      Attachments

        Issue Links

          Activity

            People

              Lei Yang Lei Yang
              Lei Yang Lei Yang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: