hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Esteban Gutierrez (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (HBASE-9003) TableMapReduceUtil should not rely on org.apache.hadoop.util.JarFinder#getJar
Date Tue, 29 Apr 2014 01:47:15 GMT

     [ https://issues.apache.org/jira/browse/HBASE-9003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Esteban Gutierrez reassigned HBASE-9003:
----------------------------------------

    Assignee: Esteban Gutierrez

> TableMapReduceUtil should not rely on org.apache.hadoop.util.JarFinder#getJar
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-9003
>                 URL: https://issues.apache.org/jira/browse/HBASE-9003
>             Project: HBase
>          Issue Type: Bug
>          Components: mapreduce
>    Affects Versions: 0.92.2, 0.95.1, 0.94.9
>            Reporter: Esteban Gutierrez
>            Assignee: Esteban Gutierrez
>         Attachments: HBASE-9003.v0.patch
>
>
> This is the problem: {{TableMapReduceUtil#addDependencyJars}} relies on {{org.apache.hadoop.util.JarFinder}}
if available to call {{getJar()}}. However {{getJar()}} uses File.createTempFile() to create
a temporary file under {{hadoop.tmp.dir}}{{/target/test-dir}}. Due HADOOP-9737 the created
jar and its content is not purged after the JVM is destroyed. Since most configurations point
{{hadoop.tmp.dir}} under {{/tmp}} the generated jar files get purged by {{tmpwatch}} or a
similar tool, but boxes that have {{hadoop.tmp.dir}} pointing to a different location not
monitored by {{tmpwatch}} will pile up a collection of jars causing all kind of issues. Since
{{JarFinder#getJar}} is not a public API from Hadoop (see [~tucu00] comment on HADOOP-9737)
we shouldn't use that as part of {{TableMapReduceUtil}} in order to avoid this kind of issues.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message