Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 26 Jul 2016 01:47:20 +0000 (UTC)
From: "Jing Zhao (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12992355.1469469079000.130089.1469497640761@Atlassian.JIRA>
In-Reply-To: <JIRA.12992355.1469469079000@Atlassian.JIRA>
References: <JIRA.12992355.1469469079000@Atlassian.JIRA> <JIRA.12992355.1469469079835@arcas>
Subject: [jira] [Updated] (HDFS-10688) BPServiceActor may run into a tight
 loop for sending block report when hitting IOException
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 26 Jul 2016 01:47:27 -0000


     [ https://issues.apache.org/jira/browse/HDFS-10688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jing Zhao updated HDFS-10688:
-----------------------------
    Description: 
Currently in BPServiceActor#offerService, when datanode runs into a local IOException, the DataNode only logs the exception and runs into the while loop again:
{code}
      } catch(RemoteException re) {
        .......
        LOG.warn("RemoteException in offerService", re);
        try {
          long sleepTime = Math.min(1000, dnConf.heartBeatInterval);
          Thread.sleep(sleepTime);
        } catch (InterruptedException ie) {
          Thread.currentThread().interrupt();
        }
      } catch (IOException e) {
        LOG.warn("IOException in offerService", e);
      }
{code}

This tight loop may cause some issue. For example, in a production cluster, we saw a DataNode hit exception when doing kerberos realm lookup. This tight loop finally caused the DataNode to send hundreds of DNS lookup queries per second.

  was:
Currently in BPServiceActor#offerService, when datanode runs into a local IOException, the DataNode only logs the exception and runs into the while loop again:
{code}
      } catch(RemoteException re) {
        .......
        LOG.warn("RemoteException in offerService", re);
        try {
          long sleepTime = Math.min(1000, dnConf.heartBeatInterval);
          Thread.sleep(sleepTime);
        } catch (InterruptedException ie) {
          Thread.currentThread().interrupt();
        }
      } catch (IOException e) {
        LOG.warn("IOException in offerService", e);
      }
{code}

This tight loop may cause some issue. For example, in a production cluster, we saw a DataNode hit exception when doing kerberos realm lookup. This tight loop finally caused the DataNode to send hundreds of DNS lookup queries.


> BPServiceActor may run into a tight loop for sending block report when hitting IOException
> ------------------------------------------------------------------------------------------
>
>                 Key: HDFS-10688
>                 URL: https://issues.apache.org/jira/browse/HDFS-10688
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>            Reporter: Jing Zhao
>            Assignee: Chen Liang
>             Fix For: 2.8.0
>
>         Attachments: HDFS-10688.001.patch, HDFS-10688.002.patch
>
>
> Currently in BPServiceActor#offerService, when datanode runs into a local IOException, the DataNode only logs the exception and runs into the while loop again:
> {code}
>       } catch(RemoteException re) {
>         .......
>         LOG.warn("RemoteException in offerService", re);
>         try {
>           long sleepTime = Math.min(1000, dnConf.heartBeatInterval);
>           Thread.sleep(sleepTime);
>         } catch (InterruptedException ie) {
>           Thread.currentThread().interrupt();
>         }
>       } catch (IOException e) {
>         LOG.warn("IOException in offerService", e);
>       }
> {code}
> This tight loop may cause some issue. For example, in a production cluster, we saw a DataNode hit exception when doing kerberos realm lookup. This tight loop finally caused the DataNode to send hundreds of DNS lookup queries per second.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org