Hadoop Common
  1. Hadoop Common
  2. HADOOP-7163

"java.net.SocketTimeoutException: 60000 millis timeout" happens a lot

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.20.203.0
    • Component/s: ipc
    • Labels:
      None

      Description

      We don't have retries for the case where the secure SASL connection is getting created from the tasks. There is retry
      for TCP connections, but once the TCP connection has been set up, communication at the RPC layer (and that includes
      SASL handshake) happens without retries. So for example, a client's "read" can timeout.

        Activity

        Hide
        Eli Collins added a comment -

        What change fixed this?

        Show
        Eli Collins added a comment - What change fixed this?
        Hide
        Owen O'Malley added a comment -

        Closing for 0.20.203.0

        Show
        Owen O'Malley added a comment - Closing for 0.20.203.0
        Hide
        Dave Thompson added a comment -

        It looks like the client code cleans up and is capable of handling connection failures, ready for retry. Would RetryProxy be suitable for the particular scenario you're thinking of?

        Show
        Dave Thompson added a comment - It looks like the client code cleans up and is capable of handling connection failures, ready for retry. Would RetryProxy be suitable for the particular scenario you're thinking of?
        Hide
        Steve Loughran added a comment -

        Have you got a stack trace?

        Show
        Steve Loughran added a comment - Have you got a stack trace?

          People

          • Assignee:
            Devaraj Das
            Reporter:
            Owen O'Malley
          • Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development