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

hdfs dfsclient newConnectedPeer has no write timeout

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.3.0, 2.6.0
    • 2.8.0, 3.0.0-alpha1
    • fuse-dfs, hdfs-client
    • None
    • hdfs 2.3.0 hbase 0.98.6

    Description

      problem:
      hbase compactSplitThread may lock forever on read datanode blocks.

      debug found: epollwait timeout set to 0,so epollwait can not run out.

      cause: in hdfs 2.3.0
      hbase using DFSClient to read and write blocks.
      DFSClient creates one socket using newConnectedPeer(addr), but has no read or write timeout.

      in v 2.6.0, newConnectedPeer has added readTimeout to deal with the problem,but did not add writeTimeout. why did not add write Timeout?

      I think NioInetPeer need a default socket timeout,so appalications will no need to force adding timeout by themselives.

      Attachments

        1. HDFS-7608.2.patch
          4 kB
          Esteban Gutierrez
        2. HDFS-7608.1.patch
          6 kB
          Xiaoyu Yao
        3. HDFS-7608.0.patch
          4 kB
          Xiaoyu Yao

        Issue Links

          Activity

            People

              xyao Xiaoyu Yao
              zsl2007 zhangshilong
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 24h
                  24h
                  Remaining:
                  Remaining Estimate - 24h
                  24h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified