Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D3EB1111B0 for ; Tue, 15 Apr 2014 23:49:42 +0000 (UTC) Received: (qmail 82130 invoked by uid 500); 15 Apr 2014 23:49:27 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 81729 invoked by uid 500); 15 Apr 2014 23:49:18 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 81677 invoked by uid 99); 15 Apr 2014 23:49:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Apr 2014 23:49:17 +0000 Date: Tue, 15 Apr 2014 23:49:16 +0000 (UTC) From: "Lohit Vijayarenu (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HDFS-6248) SNN crash during replay of FSEditLog of files inside directories having QuotaExceeded directories MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Lohit Vijayarenu created HDFS-6248: -------------------------------------- Summary: SNN crash during replay of FSEditLog of files inside directories having QuotaExceeded directories Key: HDFS-6248 URL: https://issues.apache.org/jira/browse/HDFS-6248 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 2.4.0, 2.0.6-alpha Environment: NameNode HA setup with Active/Standby using QJM Reporter: Lohit Vijayarenu We are seeing cases when Secondary NameNode crashes without recovery when it tries to replay edit log of files which are part of directories which have exceeded Quota. While debugging we got stack trace but we are still trying to reproduce this and wanted to note this to see if anyone else had seen this issue already. -- This message was sent by Atlassian JIRA (v6.2#6252)