Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B196F200D24 for ; Tue, 24 Oct 2017 12:14:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B033D160BF1; Tue, 24 Oct 2017 10:14:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 0A47E160BDB for ; Tue, 24 Oct 2017 12:14:04 +0200 (CEST) Received: (qmail 20681 invoked by uid 500); 24 Oct 2017 10:14:04 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 20670 invoked by uid 99); 24 Oct 2017 10:14:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Oct 2017 10:14:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 31CC9C206E for ; Tue, 24 Oct 2017 10:14:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id cde5UXje5Qwb for ; Tue, 24 Oct 2017 10:14:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id C5E775FC9D for ; Tue, 24 Oct 2017 10:14:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id DE7B5E0EF6 for ; Tue, 24 Oct 2017 10:14:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 49CB8212FD for ; Tue, 24 Oct 2017 10:14:00 +0000 (UTC) Date: Tue, 24 Oct 2017 10:14:00 +0000 (UTC) From: "Surendra Singh Lilhore (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-12310) [SPS]: Provide an option to track the status of in progress requests MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 24 Oct 2017 10:14:05 -0000 [ https://issues.apache.org/jira/browse/HDFS-12310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16216656#comment-16216656 ] Surendra Singh Lilhore commented on HDFS-12310: ----------------------------------------------- Attached V4 patch.. bq. Please fix the comments: Fixed bq. It should put spsStatusInfo into the map? Yes, need to put in map. null check I added only for safety, spsStatusInfo never be null. bq. The above code is in muitple places, i.e., removeItemTrackInfo, looks suspicious. {{removeItemTrackInfo}} handling three cases and trying to clean the status from map in all the case. Status will be cleand from map only if it is in SUCCESS status more than 5 minute. # If trackInfo is directory and inode is null, means start inode is delete but status still there in statusInfo map. We need to clean it, so marking it success. # If trackInfo is directory and inode not null, check pending work for directory. If all the files processed in directory then mark is success. # If trackInfo is file then just mark is success becuase all the blocks satisfy the policy. bq. Would it make sense to put cleanSpsStatus(); into {{ if (!namesystem.isInSafeMode()) }}, and avoid run it for every processed inode. Fixed. Added check to run {{cleanSpsStatus()}} every 5 minute. bq. StoragePolicySatisfyPathStatusInfo#setSuccessStatus()/setInProgress() / canRemoveStatus() can be project-private. Fixed bq. Could you add comment to DFSClient# checkStoragePolicySatisfyPathStatus() as well? Fixed Please review.. > [SPS]: Provide an option to track the status of in progress requests > -------------------------------------------------------------------- > > Key: HDFS-12310 > URL: https://issues.apache.org/jira/browse/HDFS-12310 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: datanode, namenode > Reporter: Uma Maheswara Rao G > Assignee: Surendra Singh Lilhore > Attachments: HDFS-12310-HDFS-10285-01.patch, HDFS-12310-HDFS-10285-02.patch, HDFS-12310-HDFS-10285-03.patch, HDFS-12310-HDFS-10285-04.patch > > > As per the [~andrew.wang] 's review comments in HDFS-10285, This is the JIRA for tracking about the options how we track the progress of SPS requests. > -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org