Hunk®(Legacy)

Hunk User Manual

Download manual as PDF

Download topic as PDF

System and software requirements

Make sure you have access to at least one Hadoop cluster (with data in it) and the ability to run MapReduce jobs on that data.

Make sure you have Java 1.6 and above. However, we suggest you upgrade to a version higher than 1.6 for best results.

Hunk is supported on the following Hadoop distributions and versions:

  • Apache Hadoop
    • 0.20
    • 1.0.2
    • 1.0.3
    • 1.0.4
    • 2.4
    • 2.5
    • 2.6
    • 2.7
  • Cloudera Distribution Including Apache Hadoop
    • 4
    • 4.2
    • 4.3.0
    • 4.4 (HA NN and HA JT)
    • 5.0
    • 5.3
    • 5.3 (HA)
    • 5.4
    • 5.5
    • 5.6
  • Hortonworks Data Platform (HDP)
    • 1.3
    • 2.0
    • 2.1
    • 2.2
    • 2.3
    • 2.4
  • MapR
    • 2.1
    • 3.0
    • 5.0
  • Amazon Elastic MapReduce (EMR)
  • IBM InfoSphere BigInsights
    • 5.1
  • Pivotal HD

What you need on your Hadoop nodes

On Hadoop TaskTracker nodes you need a directory on the *nix file system running your Hadoop nodes that meets the following requirements:

  • One gigabyte of free disk space for a copy of Splunk.
  • 5-10GB of free disk space for temporary storage. This storage is used by the search processes.

What you need on your Hadoop file system

On your Hadoop file system (HDFS or otherwise) you will need:

  • A subdirectory under jobtracker.staging.root.dir (usually /user/) with the name of the user account under which Hunk is running on the search head. For example, if Hunk is started by user "hunk" and jobtracker.staging.root.dir=/user/ you need a directory /user/hunk that is accessible by user "hunk"
  • A subdirectory under the above directory that can be used by this Hunk server for intermediate storage, such as /user/hunk/server01/
PREVIOUS
About installing and configuring Hunk
  NEXT
Important information about installation and users

This documentation applies to the following versions of Hunk®(Legacy): 6.0, 6.0.1, 6.0.2, 6.0.3, 6.1, 6.1.1, 6.1.2, 6.1.3, 6.2, 6.2.1, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.2.6, 6.2.7, 6.2.8, 6.2.9, 6.2.10, 6.2.11, 6.2.12, 6.2.13, 6.3.0, 6.3.1, 6.3.2, 6.3.3, 6.3.4, 6.3.5, 6.3.6, 6.3.7, 6.3.8, 6.3.9, 6.3.10, 6.3.11, 6.3.12, 6.3.13, 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.4.5, 6.4.6, 6.4.7, 6.4.8, 6.4.9, 6.4.10, 6.4.11


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters