Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1CF2D19B05 for ; Wed, 30 Mar 2016 22:01:26 +0000 (UTC) Received: (qmail 18350 invoked by uid 500); 30 Mar 2016 22:01:25 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 18288 invoked by uid 500); 30 Mar 2016 22:01:25 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 18253 invoked by uid 99); 30 Mar 2016 22:01:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Mar 2016 22:01:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 7E0892C1F5C for ; Wed, 30 Mar 2016 22:01:25 +0000 (UTC) Date: Wed, 30 Mar 2016 22:01:25 +0000 (UTC) From: "Dave Latham (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-15564) HashTable job supposedly succeeded but manifest.tmp remain MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-15564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218956#comment-15218956 ] Dave Latham commented on HBASE-15564: ------------------------------------- It's probably best to start on the mailing list with problems you're having, and if we discover an actual bug or improvement to be done, then make a JIRA. In this case, if the HashTable MapReduce job completed but the manifest was never renamed from manifest.tmp it seems most likely that the HashTable main tool runner process died, was killed, or lost connection to the cluster and so was unable to perform that rename step. Be sure to leave it running until after completion. Since all it does afterward is rename the manifest.tmp file after the job succeeds, you can do that yourself if you like. > HashTable job supposedly succeeded but manifest.tmp remain > ---------------------------------------------------------- > > Key: HBASE-15564 > URL: https://issues.apache.org/jira/browse/HBASE-15564 > Project: HBase > Issue Type: Bug > Components: mapreduce, Replication > Affects Versions: 1.2.0 > Environment: Ubuntu 12.04 > Reporter: My Ho > > I'm using org.apache.hadoop.hbase.mapreduce.HashTable to create hashes for use in SyncTable. Occasionally, the job page in jobhistory will say the job succeeded, but in my filesystem, I see "manifest.tmp" instead of the expected "manifest". According to the code[1], the job must have failed, but I don't see failure anywhere. > [1]https://github.com/apache/hbase/blob/ad3feaa44800f10d102255a240c38ccf23a82d49/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/HashTable.java#L739-L741 -- This message was sent by Atlassian JIRA (v6.3.4#6332)