Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C11A617444 for ; Wed, 25 Feb 2015 09:41:06 +0000 (UTC) Received: (qmail 57077 invoked by uid 500); 25 Feb 2015 09:41:05 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 56965 invoked by uid 500); 25 Feb 2015 09:41:05 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 56893 invoked by uid 99); 25 Feb 2015 09:41:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Feb 2015 09:41:05 +0000 Date: Wed, 25 Feb 2015 09:41:05 +0000 (UTC) From: "J.Andreina (JIRA)" To: hdfs-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HDFS-7842) Blocks missed while performing downgrade immediately after rolling back the cluster. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 J.Andreina created HDFS-7842: -------------------------------- Summary: Blocks missed while performing downgrade immediately after rolling back the cluster. Key: HDFS-7842 URL: https://issues.apache.org/jira/browse/HDFS-7842 Project: Hadoop HDFS Issue Type: Bug Reporter: J.Andreina Assignee: J.Andreina Priority: Critical Performing downgrade immediately after rolling back the cluster , will replace the blocks from trash Since the block id for the files created before rollback will be same as the file created before downgrade, namenode will get into safemode , as the block size reported from Datanode will be different from the one in block map (corrupted blocks) . Steps to Reproduce {noformat} Step 1: Prepare rolling upgrade using "hdfs dfsadmin -rollingUpgrade prepare" Step 2: Shutdown SNN and NN Step 3: Start NN with the "hdfs namenode -rollingUpgrade started" option. Step 4: Executed "hdfs dfsadmin -shutdownDatanode upgrade" and restarted Datanode Step 5: Create File_1 of size 11526 Step 6: Shutdown both NN and DN Step 7: Start NNs with the "hdfs namenode -rollingUpgrade rollback" option. Start DNs with the "-rollback" option. Step 8: Prepare rolling upgrade using "hdfs dfsadmin -rollingUpgrade prepare" Step 9: Shutdown SNN and NN Step 10: Start NN with the "hdfs namenode -rollingUpgrade started" option . Step 11: Executed "hdfs dfsadmin -shutdownDatanode upgrade" and restarted Datanode step 12: Add file File_2 with size 6324 (which has same blockid as previous created File_1 with block size 11526) Step 13: Shutdown both NN and DN Step 14: Start NNs with the "hdfs namenode -rollingUpgrade downgrade" option.Start DNs normally. {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)