Hunk®(Legacy)

Hunk User Manual

Acrobat logo Download manual as PDF


This documentation does not apply to the most recent version of Hunk®(Legacy). For documentation on the most recent version, go to the latest release.
Acrobat logo Download topic as PDF

Known and resolved issues

This topic lists known and resolved issues for Hunk functionality. For a full list of issues, see the Splunk 6.1 Known Issues.

Known Issues

  • In 6.1, you cannot configure Hunk to run reports as a different user. Instead, use the new pass-through authentication functionality to run users with the Hunk Superuser acting as a proxy. See About pass-through authentication for more information. (ERP-709)
  • The Cloudera tarball (v4.5 and higher) comes with two bin directories, each for YARN (default) and MapReduce1, when specifying HADOOP_HOME in Hunk however "bin" is implicit. If you are running MapReduce1 using the Cloudera tarball v4.5 or higher, when you untar the Hadoop libraries from http://archive.cloudera.com/cdh4/cdh/4/hadoop-2.0.0-cdh4.5.0.tar.gz or higher you should rename these folders as follows:
    • rename bin to bin-yarn
    • rename bin-mapreduce1 to bin (ERP-575)
  • Unable to edit provider names that contain special characters. To mitigate this, avoid using special characters when naming new providers. (ERP-672)
Last modified on 28 May, 2014
PREVIOUS
Manage report acceleration 		  NEXT
Troubleshoot Hunk

This documentation applies to the following versions of Hunk®(Legacy): 6.1

Was this documentation topic helpful?


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