[HBASE-6824] Introduce ${hbase.local.dir} and save coprocessor jars there

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.94.3, 0.95.2
• Fix Version/s: 0.94.5, 0.95.0
• Hadoop Flags: Reviewed
• Release Note: Added a configuration "hbase.local.dir" which defaults to ${hbase.tmp.dir}/local/. Coprocessor jars, and other local data for region servers are written to this location.
• Assignee: Enis Soztutar
• Reporter: Enis Soztutar
• Created: 19/Sep/12 00:02
• Updated: 26/Feb/13 08:27
• Resolved: 09/Jan/13 21:16

Description

We need to make the temp directory where coprocessor jars are saved configurable. For this we will add hbase.local.dir configuration parameter.

Windows tests are failing due to the pathing problems for coprocessor jars:
Two HBase TestClassLoading unit tests failed due to a failiure in loading the test file from HDFS:

testClassLoadingFromHDFS(org.apache.hadoop.hbase.coprocessor.TestClassLoading): Class TestCP1 was missing on a region
testClassLoadingFromLibDirInJar(org.apache.hadoop.hbase.coprocessor.TestClassLoading): Class TestCP1 was missing on a region

The problem is that CoprocessorHost.load() copies the jar file locally, and schedules the local file to be deleted on exit, but calling FileSystem.deleteOnExit(). However, the filesystem is not the file system of the local file, it is the distributed file system, so on windows, the Path fails.

Issue Links

• is part of: HBASE-6817 [WINDOWS] Get HBase tests working under Windows
• is related to: HBASE-6842 the jar used in coprocessor is not deleted in local which will exhaust the space of /tmp
• is related to: HBASE-7522 Tests should not be writing under /tmp/