[
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)
