| <?xml version="1.0"?> |
| <?xml-stylesheet type="text/xsl" href="configuration.xsl"?> |
| <!-- |
| Licensed to the Apache Software Foundation (ASF) under one or more |
| contributor license agreements. See the NOTICE file distributed with |
| this work for additional information regarding copyright ownership. |
| The ASF licenses this file to You under the Apache License, Version 2.0 |
| (the "License"); you may not use this file except in compliance with |
| the License. You may obtain a copy of the License at |
| |
| http://www.apache.org/licenses/LICENSE-2.0 |
| |
| Unless required by applicable law or agreed to in writing, software |
| distributed under the License is distributed on an "AS IS" BASIS, |
| WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| See the License for the specific language governing permissions and |
| limitations under the License. |
| --> |
| |
| <!-- Do not modify this file directly. Instead, copy entries that you --> |
| <!-- wish to modify from this file into mapred-site.xml and change them --> |
| <!-- there. If mapred-site.xml does not already exist, create it. --> |
| |
| <configuration> |
| |
| <property> |
| <name>mapreduce.job.committer.setup.cleanup.needed</name> |
| <value>true</value> |
| <description> true, if job needs job-setup and job-cleanup. |
| false, otherwise |
| </description> |
| </property> |
| <!-- i/o properties --> |
| |
| <property> |
| <name>mapreduce.task.io.sort.factor</name> |
| <value>10</value> |
| <description>The number of streams to merge at once while sorting |
| files. This determines the number of open file handles.</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.task.io.sort.mb</name> |
| <value>100</value> |
| <description>The total amount of buffer memory to use while sorting |
| files, in megabytes. By default, gives each merge stream 1MB, which |
| should minimize seeks.</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.map.sort.spill.percent</name> |
| <value>0.80</value> |
| <description>The soft limit in the serialization buffer. Once reached, a |
| thread will begin to spill the contents to disk in the background. Note that |
| collection will not block if this threshold is exceeded while a spill is |
| already in progress, so spills may be larger than this threshold when it is |
| set to less than .5</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.local.clientfactory.class.name</name> |
| <value>org.apache.hadoop.mapred.LocalClientFactory</value> |
| <description>This the client factory that is responsible for |
| creating local job runner client</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.maps</name> |
| <value>2</value> |
| <description>The default number of map tasks per job. |
| Ignored when mapreduce.framework.name is "local". |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.reduces</name> |
| <value>1</value> |
| <description>The default number of reduce tasks per job. Typically set to 99% |
| of the cluster's reduce capacity, so that if a node fails the reduces can |
| still be executed in a single wave. |
| Ignored when mapreduce.framework.name is "local". |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.reducer.preempt.delay.sec</name> |
| <value>0</value> |
| <description>The threshold in terms of seconds after which an unsatisfied mapper |
| request triggers reducer preemption to free space. Default 0 implies that the |
| reduces should be preempted immediately after allocation if there is currently no |
| room for newly allocated mappers. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.max.split.locations</name> |
| <value>10</value> |
| <description>The max number of block locations to store for each split for |
| locality calculation. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.split.metainfo.maxsize</name> |
| <value>10000000</value> |
| <description>The maximum permissible size of the split metainfo file. |
| The MapReduce ApplicationMaster won't attempt to read submitted split metainfo |
| files bigger than this configured value. |
| No limits if set to -1. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.map.maxattempts</name> |
| <value>4</value> |
| <description>Expert: The maximum number of attempts per map task. |
| In other words, framework will try to execute a map task these many number |
| of times before giving up on it. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.reduce.maxattempts</name> |
| <value>4</value> |
| <description>Expert: The maximum number of attempts per reduce task. |
| In other words, framework will try to execute a reduce task these many number |
| of times before giving up on it. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.reduce.shuffle.retry-delay.max.ms</name> |
| <value>60000</value> |
| <description>The maximum number of ms the reducer will delay before retrying |
| to download map data. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.reduce.shuffle.parallelcopies</name> |
| <value>5</value> |
| <description>The default number of parallel transfers run by reduce |
| during the copy(shuffle) phase. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.reduce.shuffle.connect.timeout</name> |
| <value>180000</value> |
| <description>Expert: The maximum amount of time (in milli seconds) reduce |
| task spends in trying to connect to a remote node for getting map output. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.reduce.shuffle.read.timeout</name> |
| <value>180000</value> |
| <description>Expert: The maximum amount of time (in milli seconds) reduce |
| task waits for map output data to be available for reading after obtaining |
| connection. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.shuffle.connection-keep-alive.enable</name> |
| <value>false</value> |
| <description>set to true to support keep-alive connections.</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.shuffle.connection-keep-alive.timeout</name> |
| <value>5</value> |
| <description>The number of seconds a shuffle client attempts to retain |
| http connection. Refer "Keep-Alive: timeout=" header in |
| Http specification |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.task.timeout</name> |
| <value>600000</value> |
| <description>The number of milliseconds before a task will be |
| terminated if it neither reads an input, writes an output, nor |
| updates its status string. A value of 0 disables the timeout. |
| </description> |
| </property> |
| |
| |
| <property> |
| <name>mapred.child.java.opts</name> |
| <value>-Xmx200m</value> |
| <description>Java opts for the task tracker child processes. |
| The following symbol, if present, will be interpolated: @taskid@ is replaced |
| by current TaskID. Any other occurrences of '@' will go unchanged. |
| For example, to enable verbose gc logging to a file named for the taskid in |
| /tmp and to set the heap maximum to be a gigabyte, pass a 'value' of: |
| -Xmx1024m -verbose:gc -Xloggc:/tmp/@taskid@.gc |
| |
| Usage of -Djava.library.path can cause programs to no longer function if |
| hadoop native libraries are used. These values should instead be set as part |
| of LD_LIBRARY_PATH in the map / reduce JVM env using the mapreduce.map.env and |
| mapreduce.reduce.env config settings. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapred.child.env</name> |
| <value></value> |
| <description>User added environment variables for the task tracker child |
| processes. Example : |
| 1) A=foo This will set the env variable A to foo |
| 2) B=$B:c This is inherit nodemanager's B env variable on Unix. |
| 3) B=%B%;c This is inherit nodemanager's B env variable on Windows. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.admin.user.env</name> |
| <value></value> |
| <description> |
| Expert: Additional execution environment entries for |
| map and reduce task processes. This is not an additive property. |
| You must preserve the original value if you want your map and |
| reduce tasks to have access to native libraries (compression, etc). |
| When this value is empty, the command to set execution |
| envrionment will be OS dependent: |
| For linux, use LD_LIBRARY_PATH=$HADOOP_COMMON_HOME/lib/native. |
| For windows, use PATH = %PATH%;%HADOOP_COMMON_HOME%\\bin. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.task.tmp.dir</name> |
| <value>./tmp</value> |
| <description> To set the value of tmp directory for map and reduce tasks. |
| If the value is an absolute path, it is directly assigned. Otherwise, it is |
| prepended with task's working directory. The java tasks are executed with |
| option -Djava.io.tmpdir='the absolute path of the tmp dir'. Pipes and |
| streaming are set with environment variable, |
| TMPDIR='the absolute path of the tmp dir' |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.map.log.level</name> |
| <value>INFO</value> |
| <description>The logging level for the map task. The allowed levels are: |
| OFF, FATAL, ERROR, WARN, INFO, DEBUG, TRACE and ALL. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.reduce.log.level</name> |
| <value>INFO</value> |
| <description>The logging level for the reduce task. The allowed levels are: |
| OFF, FATAL, ERROR, WARN, INFO, DEBUG, TRACE and ALL. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.map.cpu.vcores</name> |
| <value>1</value> |
| <description> |
| The number of virtual cores required for each map task. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.reduce.cpu.vcores</name> |
| <value>1</value> |
| <description> |
| The number of virtual cores required for each reduce task. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.reduce.merge.inmem.threshold</name> |
| <value>1000</value> |
| <description>The threshold, in terms of the number of files |
| for the in-memory merge process. When we accumulate threshold number of files |
| we initiate the in-memory merge and spill to disk. A value of 0 or less than |
| 0 indicates we want to DON'T have any threshold and instead depend only on |
| the ramfs's memory consumption to trigger the merge. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.reduce.shuffle.merge.percent</name> |
| <value>0.66</value> |
| <description>The usage threshold at which an in-memory merge will be |
| initiated, expressed as a percentage of the total memory allocated to |
| storing in-memory map outputs, as defined by |
| mapreduce.reduce.shuffle.input.buffer.percent. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.reduce.shuffle.input.buffer.percent</name> |
| <value>0.70</value> |
| <description>The percentage of memory to be allocated from the maximum heap |
| size to storing map outputs during the shuffle. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.reduce.input.buffer.percent</name> |
| <value>0.0</value> |
| <description>The percentage of memory- relative to the maximum heap size- to |
| retain map outputs during the reduce. When the shuffle is concluded, any |
| remaining map outputs in memory must consume less than this threshold before |
| the reduce can begin. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.reduce.shuffle.memory.limit.percent</name> |
| <value>0.25</value> |
| <description>Expert: Maximum percentage of the in-memory limit that a |
| single shuffle can consume</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.shuffle.ssl.enabled</name> |
| <value>false</value> |
| <description> |
| Whether to use SSL for for the Shuffle HTTP endpoints. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.shuffle.ssl.file.buffer.size</name> |
| <value>65536</value> |
| <description>Buffer size for reading spills from file when using SSL. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.shuffle.max.connections</name> |
| <value>0</value> |
| <description>Max allowed connections for the shuffle. Set to 0 (zero) |
| to indicate no limit on the number of connections. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.shuffle.max.threads</name> |
| <value>0</value> |
| <description>Max allowed threads for serving shuffle connections. Set to zero |
| to indicate the default of 2 times the number of available |
| processors (as reported by Runtime.availableProcessors()). Netty is used to |
| serve requests, so a thread is not needed for each connection. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.shuffle.transferTo.allowed</name> |
| <value></value> |
| <description>This option can enable/disable using nio transferTo method in |
| the shuffle phase. NIO transferTo does not perform well on windows in the |
| shuffle phase. Thus, with this configuration property it is possible to |
| disable it, in which case custom transfer method will be used. Recommended |
| value is false when running Hadoop on Windows. For Linux, it is recommended |
| to set it to true. If nothing is set then the default value is false for |
| Windows, and true for Linux. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.shuffle.transfer.buffer.size</name> |
| <value>131072</value> |
| <description>This property is used only if |
| mapreduce.shuffle.transferTo.allowed is set to false. In that case, |
| this property defines the size of the buffer used in the buffer copy code |
| for the shuffle phase. The size of this buffer determines the size of the IO |
| requests. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.reduce.markreset.buffer.percent</name> |
| <value>0.0</value> |
| <description>The percentage of memory -relative to the maximum heap size- to |
| be used for caching values when using the mark-reset functionality. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.map.speculative</name> |
| <value>true</value> |
| <description>If true, then multiple instances of some map tasks |
| may be executed in parallel.</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.reduce.speculative</name> |
| <value>true</value> |
| <description>If true, then multiple instances of some reduce tasks |
| may be executed in parallel.</description> |
| </property> |
| <property> |
| <name>mapreduce.job.speculative.speculativecap</name> |
| <value>0.1</value> |
| <description>The max percent (0-1) of running tasks that |
| can be speculatively re-executed at any time.</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.map.output.collector.class</name> |
| <value>org.apache.hadoop.mapred.MapTask$MapOutputBuffer</value> |
| <description> |
| The MapOutputCollector implementation(s) to use. This may be a comma-separated |
| list of class names, in which case the map task will try to initialize each |
| of the collectors in turn. The first to successfully initialize will be used. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.speculative.slowtaskthreshold</name> |
| <value>1.0</value>The number of standard deviations by which a task's |
| ave progress-rates must be lower than the average of all running tasks' |
| for the task to be considered too slow. |
| <description> |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.speculative.slownodethreshold</name> |
| <value>1.0</value> |
| <description>The number of standard deviations by which a Task |
| Tracker's average map and reduce progress-rates (finishTime-dispatchTime) |
| must be lower than the average of all successful map/reduce task's for |
| the NodeManager to be considered too slow to give a speculative task to. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.ubertask.enable</name> |
| <value>false</value> |
| <description>Whether to enable the small-jobs "ubertask" optimization, |
| which runs "sufficiently small" jobs sequentially within a single JVM. |
| "Small" is defined by the following maxmaps, maxreduces, and maxbytes |
| settings. Users may override this value. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.ubertask.maxmaps</name> |
| <value>9</value> |
| <description>Threshold for number of maps, beyond which job is considered |
| too big for the ubertasking optimization. Users may override this value, |
| but only downward. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.ubertask.maxreduces</name> |
| <value>1</value> |
| <description>Threshold for number of reduces, beyond which job is considered |
| too big for the ubertasking optimization. CURRENTLY THE CODE CANNOT SUPPORT |
| MORE THAN ONE REDUCE and will ignore larger values. (Zero is a valid max, |
| however.) Users may override this value, but only downward. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.ubertask.maxbytes</name> |
| <value></value> |
| <description>Threshold for number of input bytes, beyond which job is |
| considered too big for the ubertasking optimization. If no value is |
| specified, dfs.block.size is used as a default. Be sure to specify a |
| default value in mapred-site.xml if the underlying filesystem is not HDFS. |
| Users may override this value, but only downward. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.input.fileinputformat.split.minsize</name> |
| <value>0</value> |
| <description>The minimum size chunk that map input should be split |
| into. Note that some file formats may have minimum split sizes that |
| take priority over this setting.</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.input.fileinputformat.list-status.num-threads</name> |
| <value>1</value> |
| <description>The number of threads to use to list and fetch block locations |
| for the specified input paths. Note: multiple threads should not be used |
| if a custom non thread-safe path filter is used. |
| </description> |
| </property> |
| |
| |
| |
| <property> |
| <name>mapreduce.client.submit.file.replication</name> |
| <value>10</value> |
| <description>The replication level for submitted job files. This |
| should be around the square root of the number of nodes. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.task.files.preserve.failedtasks</name> |
| <value>false</value> |
| <description>Should the files for failed tasks be kept. This should only be |
| used on jobs that are failing, because the storage is never |
| reclaimed. It also prevents the map outputs from being erased |
| from the reduce directory as they are consumed.</description> |
| </property> |
| |
| |
| <!-- |
| <property> |
| <name>mapreduce.task.files.preserve.filepattern</name> |
| <value>.*_m_123456_0</value> |
| <description>Keep all files from tasks whose task names match the given |
| regular expression. Defaults to none.</description> |
| </property> |
| --> |
| |
| <property> |
| <name>mapreduce.output.fileoutputformat.compress</name> |
| <value>false</value> |
| <description>Should the job outputs be compressed? |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.output.fileoutputformat.compress.type</name> |
| <value>RECORD</value> |
| <description>If the job outputs are to compressed as SequenceFiles, how should |
| they be compressed? Should be one of NONE, RECORD or BLOCK. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.output.fileoutputformat.compress.codec</name> |
| <value>org.apache.hadoop.io.compress.DefaultCodec</value> |
| <description>If the job outputs are compressed, how should they be compressed? |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.map.output.compress</name> |
| <value>false</value> |
| <description>Should the outputs of the maps be compressed before being |
| sent across the network. Uses SequenceFile compression. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.map.output.compress.codec</name> |
| <value>org.apache.hadoop.io.compress.DefaultCodec</value> |
| <description>If the map outputs are compressed, how should they be |
| compressed? |
| </description> |
| </property> |
| |
| <property> |
| <name>map.sort.class</name> |
| <value>org.apache.hadoop.util.QuickSort</value> |
| <description>The default sort class for sorting keys. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.task.userlog.limit.kb</name> |
| <value>0</value> |
| <description>The maximum size of user-logs of each task in KB. 0 disables the cap. |
| </description> |
| </property> |
| |
| <property> |
| <name>yarn.app.mapreduce.am.container.log.limit.kb</name> |
| <value>0</value> |
| <description>The maximum size of the MRAppMaster attempt container logs in KB. |
| 0 disables the cap. |
| </description> |
| </property> |
| |
| <property> |
| <name>yarn.app.mapreduce.task.container.log.backups</name> |
| <value>0</value> |
| <description>Number of backup files for task logs when using |
| ContainerRollingLogAppender (CRLA). See |
| org.apache.log4j.RollingFileAppender.maxBackupIndex. By default, |
| ContainerLogAppender (CLA) is used, and container logs are not rolled. CRLA |
| is enabled for tasks when both mapreduce.task.userlog.limit.kb and |
| yarn.app.mapreduce.task.container.log.backups are greater than zero. |
| </description> |
| </property> |
| |
| <property> |
| <name>yarn.app.mapreduce.am.container.log.backups</name> |
| <value>0</value> |
| <description>Number of backup files for the ApplicationMaster logs when using |
| ContainerRollingLogAppender (CRLA). See |
| org.apache.log4j.RollingFileAppender.maxBackupIndex. By default, |
| ContainerLogAppender (CLA) is used, and container logs are not rolled. CRLA |
| is enabled for the ApplicationMaster when both |
| mapreduce.task.userlog.limit.kb and |
| yarn.app.mapreduce.am.container.log.backups are greater than zero. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.maxtaskfailures.per.tracker</name> |
| <value>3</value> |
| <description>The number of task-failures on a node manager of a given job |
| after which new tasks of that job aren't assigned to it. It |
| MUST be less than mapreduce.map.maxattempts and |
| mapreduce.reduce.maxattempts otherwise the failed task will |
| never be tried on a different node. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.client.output.filter</name> |
| <value>FAILED</value> |
| <description>The filter for controlling the output of the task's userlogs sent |
| to the console of the JobClient. |
| The permissible options are: NONE, KILLED, FAILED, SUCCEEDED and |
| ALL. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.client.completion.pollinterval</name> |
| <value>5000</value> |
| <description>The interval (in milliseconds) between which the JobClient |
| polls the MapReduce ApplicationMaster for updates about job status. You may want to |
| set this to a lower value to make tests run faster on a single node system. Adjusting |
| this value in production may lead to unwanted client-server traffic. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.client.progressmonitor.pollinterval</name> |
| <value>1000</value> |
| <description>The interval (in milliseconds) between which the JobClient |
| reports status to the console and checks for job completion. You may want to set this |
| to a lower value to make tests run faster on a single node system. Adjusting |
| this value in production may lead to unwanted client-server traffic. |
| </description> |
| </property> |
| |
| |
| <property> |
| <name>mapreduce.task.profile</name> |
| <value>false</value> |
| <description>To set whether the system should collect profiler |
| information for some of the tasks in this job? The information is stored |
| in the user log directory. The value is "true" if task profiling |
| is enabled.</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.task.profile.maps</name> |
| <value>0-2</value> |
| <description> To set the ranges of map tasks to profile. |
| mapreduce.task.profile has to be set to true for the value to be accounted. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.task.profile.reduces</name> |
| <value>0-2</value> |
| <description> To set the ranges of reduce tasks to profile. |
| mapreduce.task.profile has to be set to true for the value to be accounted. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.task.profile.params</name> |
| <value>-agentlib:hprof=cpu=samples,heap=sites,force=n,thread=y,verbose=n,file=%s</value> |
| <description>JVM profiler parameters used to profile map and reduce task |
| attempts. This string may contain a single format specifier %s that will |
| be replaced by the path to profile.out in the task attempt log directory. |
| To specify different profiling options for map tasks and reduce tasks, |
| more specific parameters mapreduce.task.profile.map.params and |
| mapreduce.task.profile.reduce.params should be used.</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.task.profile.map.params</name> |
| <value>${mapreduce.task.profile.params}</value> |
| <description>Map-task-specific JVM profiler parameters. See |
| mapreduce.task.profile.params</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.task.profile.reduce.params</name> |
| <value>${mapreduce.task.profile.params}</value> |
| <description>Reduce-task-specific JVM profiler parameters. See |
| mapreduce.task.profile.params</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.task.skip.start.attempts</name> |
| <value>2</value> |
| <description> The number of Task attempts AFTER which skip mode |
| will be kicked off. When skip mode is kicked off, the |
| tasks reports the range of records which it will process |
| next, to the MR ApplicationMaster. So that on failures, the MR AM |
| knows which ones are possibly the bad records. On further executions, |
| those are skipped. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.map.skip.proc.count.autoincr</name> |
| <value>true</value> |
| <description> The flag which if set to true, |
| SkipBadRecords.COUNTER_MAP_PROCESSED_RECORDS is incremented |
| by MapRunner after invoking the map function. This value must be set to |
| false for applications which process the records asynchronously |
| or buffer the input records. For example streaming. |
| In such cases applications should increment this counter on their own. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.reduce.skip.proc.count.autoincr</name> |
| <value>true</value> |
| <description> The flag which if set to true, |
| SkipBadRecords.COUNTER_REDUCE_PROCESSED_GROUPS is incremented |
| by framework after invoking the reduce function. This value must be set to |
| false for applications which process the records asynchronously |
| or buffer the input records. For example streaming. |
| In such cases applications should increment this counter on their own. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.skip.outdir</name> |
| <value></value> |
| <description> If no value is specified here, the skipped records are |
| written to the output directory at _logs/skip. |
| User can stop writing skipped records by giving the value "none". |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.map.skip.maxrecords</name> |
| <value>0</value> |
| <description> The number of acceptable skip records surrounding the bad |
| record PER bad record in mapper. The number includes the bad record as well. |
| To turn the feature of detection/skipping of bad records off, set the |
| value to 0. |
| The framework tries to narrow down the skipped range by retrying |
| until this threshold is met OR all attempts get exhausted for this task. |
| Set the value to Long.MAX_VALUE to indicate that framework need not try to |
| narrow down. Whatever records(depends on application) get skipped are |
| acceptable. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.reduce.skip.maxgroups</name> |
| <value>0</value> |
| <description> The number of acceptable skip groups surrounding the bad |
| group PER bad group in reducer. The number includes the bad group as well. |
| To turn the feature of detection/skipping of bad groups off, set the |
| value to 0. |
| The framework tries to narrow down the skipped range by retrying |
| until this threshold is met OR all attempts get exhausted for this task. |
| Set the value to Long.MAX_VALUE to indicate that framework need not try to |
| narrow down. Whatever groups(depends on application) get skipped are |
| acceptable. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.ifile.readahead</name> |
| <value>true</value> |
| <description>Configuration key to enable/disable IFile readahead. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.ifile.readahead.bytes</name> |
| <value>4194304</value> |
| <description>Configuration key to set the IFile readahead length in bytes. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.queuename</name> |
| <value>default</value> |
| <description> Queue to which a job is submitted. This must match one of the |
| queues defined in mapred-queues.xml for the system. Also, the ACL setup |
| for the queue must allow the current user to submit a job to the queue. |
| Before specifying a queue, ensure that the system is configured with |
| the queue, and access is allowed for submitting jobs to the queue. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.tags</name> |
| <value></value> |
| <description> Tags for the job that will be passed to YARN at submission |
| time. Queries to YARN for applications can filter on these tags. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.cluster.local.dir</name> |
| <value>${hadoop.tmp.dir}/mapred/local</value> |
| <description> |
| The local directory where MapReduce stores intermediate |
| data files. May be a comma-separated list of |
| directories on different devices in order to spread disk i/o. |
| Directories that do not exist are ignored. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.cluster.acls.enabled</name> |
| <value>false</value> |
| <description> Specifies whether ACLs should be checked |
| for authorization of users for doing various queue and job level operations. |
| ACLs are disabled by default. If enabled, access control checks are made by |
| MapReduce ApplicationMaster when requests are made by users for queue |
| operations like submit job to a queue and kill a job in the queue and job |
| operations like viewing the job-details (See mapreduce.job.acl-view-job) |
| or for modifying the job (See mapreduce.job.acl-modify-job) using |
| Map/Reduce APIs, RPCs or via the console and web user interfaces. |
| For enabling this flag, set to true in mapred-site.xml file of all |
| MapReduce clients (MR job submitting nodes). |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.acl-modify-job</name> |
| <value> </value> |
| <description> Job specific access-control list for 'modifying' the job. It |
| is only used if authorization is enabled in Map/Reduce by setting the |
| configuration property mapreduce.cluster.acls.enabled to true. |
| This specifies the list of users and/or groups who can do modification |
| operations on the job. For specifying a list of users and groups the |
| format to use is "user1,user2 group1,group". If set to '*', it allows all |
| users/groups to modify this job. If set to ' '(i.e. space), it allows |
| none. This configuration is used to guard all the modifications with respect |
| to this job and takes care of all the following operations: |
| o killing this job |
| o killing a task of this job, failing a task of this job |
| o setting the priority of this job |
| Each of these operations are also protected by the per-queue level ACL |
| "acl-administer-jobs" configured via mapred-queues.xml. So a caller should |
| have the authorization to satisfy either the queue-level ACL or the |
| job-level ACL. |
| |
| Irrespective of this ACL configuration, (a) job-owner, (b) the user who |
| started the cluster, (c) members of an admin configured supergroup |
| configured via mapreduce.cluster.permissions.supergroup and (d) queue |
| administrators of the queue to which this job was submitted to configured |
| via acl-administer-jobs for the specific queue in mapred-queues.xml can |
| do all the modification operations on a job. |
| |
| By default, nobody else besides job-owner, the user who started the cluster, |
| members of supergroup and queue administrators can perform modification |
| operations on a job. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.acl-view-job</name> |
| <value> </value> |
| <description> Job specific access-control list for 'viewing' the job. It is |
| only used if authorization is enabled in Map/Reduce by setting the |
| configuration property mapreduce.cluster.acls.enabled to true. |
| This specifies the list of users and/or groups who can view private details |
| about the job. For specifying a list of users and groups the |
| format to use is "user1,user2 group1,group". If set to '*', it allows all |
| users/groups to modify this job. If set to ' '(i.e. space), it allows |
| none. This configuration is used to guard some of the job-views and at |
| present only protects APIs that can return possibly sensitive information |
| of the job-owner like |
| o job-level counters |
| o task-level counters |
| o tasks' diagnostic information |
| o task-logs displayed on the HistoryServer's web-UI and |
| o job.xml showed by the HistoryServer's web-UI |
| Every other piece of information of jobs is still accessible by any other |
| user, for e.g., JobStatus, JobProfile, list of jobs in the queue, etc. |
| |
| Irrespective of this ACL configuration, (a) job-owner, (b) the user who |
| started the cluster, (c) members of an admin configured supergroup |
| configured via mapreduce.cluster.permissions.supergroup and (d) queue |
| administrators of the queue to which this job was submitted to configured |
| via acl-administer-jobs for the specific queue in mapred-queues.xml can |
| do all the view operations on a job. |
| |
| By default, nobody else besides job-owner, the user who started the |
| cluster, memebers of supergroup and queue administrators can perform |
| view operations on a job. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.token.tracking.ids.enabled</name> |
| <value>false</value> |
| <description>Whether to write tracking ids of tokens to |
| job-conf. When true, the configuration property |
| "mapreduce.job.token.tracking.ids" is set to the token-tracking-ids of |
| the job</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.token.tracking.ids</name> |
| <value></value> |
| <description>When mapreduce.job.token.tracking.ids.enabled is |
| set to true, this is set by the framework to the |
| token-tracking-ids used by the job.</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.task.merge.progress.records</name> |
| <value>10000</value> |
| <description> The number of records to process during merge before |
| sending a progress notification to the MR ApplicationMaster. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.reduce.slowstart.completedmaps</name> |
| <value>0.05</value> |
| <description>Fraction of the number of maps in the job which should be |
| complete before reduces are scheduled for the job. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.complete.cancel.delegation.tokens</name> |
| <value>true</value> |
| <description> if false - do not unregister/cancel delegation tokens from |
| renewal, because same tokens may be used by spawned jobs |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.shuffle.port</name> |
| <value>13562</value> |
| <description>Default port that the ShuffleHandler will run on. ShuffleHandler |
| is a service run at the NodeManager to facilitate transfers of intermediate |
| Map outputs to requesting Reducers. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.reduce.shuffle.consumer.plugin.class</name> |
| <value>org.apache.hadoop.mapreduce.task.reduce.Shuffle</value> |
| <description> |
| Name of the class whose instance will be used |
| to send shuffle requests by reducetasks of this job. |
| The class must be an instance of org.apache.hadoop.mapred.ShuffleConsumerPlugin. |
| </description> |
| </property> |
| |
| <!-- MR YARN Application properties --> |
| |
| <property> |
| <name>mapreduce.job.counters.limit</name> |
| <value>120</value> |
| <description>Limit on the number of user counters allowed per job. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.framework.name</name> |
| <value>local</value> |
| <description>The runtime framework for executing MapReduce jobs. |
| Can be one of local, classic or yarn. |
| </description> |
| </property> |
| |
| <property> |
| <name>yarn.app.mapreduce.am.staging-dir</name> |
| <value>/tmp/hadoop-yarn/staging</value> |
| <description>The staging dir used while submitting jobs. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.am.max-attempts</name> |
| <value>2</value> |
| <description>The maximum number of application attempts. It is a |
| application-specific setting. It should not be larger than the global number |
| set by resourcemanager. Otherwise, it will be override. The default number is |
| set to 2, to allow at least one retry for AM.</description> |
| </property> |
| |
| <!-- Job Notification Configuration --> |
| <property> |
| <name>mapreduce.job.end-notification.url</name> |
| <!--<value>http://localhost:8080/jobstatus.php?jobId=$jobId&jobStatus=$jobStatus</value>--> |
| <description>Indicates url which will be called on completion of job to inform |
| end status of job. |
| User can give at most 2 variables with URI : $jobId and $jobStatus. |
| If they are present in URI, then they will be replaced by their |
| respective values. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.end-notification.retry.attempts</name> |
| <value>0</value> |
| <description>The number of times the submitter of the job wants to retry job |
| end notification if it fails. This is capped by |
| mapreduce.job.end-notification.max.attempts</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.end-notification.retry.interval</name> |
| <value>1000</value> |
| <description>The number of milliseconds the submitter of the job wants to |
| wait before job end notification is retried if it fails. This is capped by |
| mapreduce.job.end-notification.max.retry.interval</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.end-notification.max.attempts</name> |
| <value>5</value> |
| <final>true</final> |
| <description>The maximum number of times a URL will be read for providing job |
| end notification. Cluster administrators can set this to limit how long |
| after end of a job, the Application Master waits before exiting. Must be |
| marked as final to prevent users from overriding this. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.end-notification.max.retry.interval</name> |
| <value>5000</value> |
| <final>true</final> |
| <description>The maximum amount of time (in milliseconds) to wait before |
| retrying job end notification. Cluster administrators can set this to |
| limit how long the Application Master waits before exiting. Must be marked |
| as final to prevent users from overriding this.</description> |
| </property> |
| |
| <property> |
| <name>yarn.app.mapreduce.am.env</name> |
| <value></value> |
| <description>User added environment variables for the MR App Master |
| processes. Example : |
| 1) A=foo This will set the env variable A to foo |
| 2) B=$B:c This is inherit tasktracker's B env variable. |
| </description> |
| </property> |
| |
| <property> |
| <name>yarn.app.mapreduce.am.admin.user.env</name> |
| <value></value> |
| <description> Environment variables for the MR App Master |
| processes for admin purposes. These values are set first and can be |
| overridden by the user env (yarn.app.mapreduce.am.env) Example : |
| 1) A=foo This will set the env variable A to foo |
| 2) B=$B:c This is inherit app master's B env variable. |
| </description> |
| </property> |
| |
| <property> |
| <name>yarn.app.mapreduce.am.command-opts</name> |
| <value>-Xmx1024m</value> |
| <description>Java opts for the MR App Master processes. |
| The following symbol, if present, will be interpolated: @taskid@ is replaced |
| by current TaskID. Any other occurrences of '@' will go unchanged. |
| For example, to enable verbose gc logging to a file named for the taskid in |
| /tmp and to set the heap maximum to be a gigabyte, pass a 'value' of: |
| -Xmx1024m -verbose:gc -Xloggc:/tmp/@taskid@.gc |
| |
| Usage of -Djava.library.path can cause programs to no longer function if |
| hadoop native libraries are used. These values should instead be set as part |
| of LD_LIBRARY_PATH in the map / reduce JVM env using the mapreduce.map.env and |
| mapreduce.reduce.env config settings. |
| </description> |
| </property> |
| |
| <property> |
| <name>yarn.app.mapreduce.am.admin-command-opts</name> |
| <value></value> |
| <description>Java opts for the MR App Master processes for admin purposes. |
| It will appears before the opts set by yarn.app.mapreduce.am.command-opts and |
| thus its options can be overridden user. |
| |
| Usage of -Djava.library.path can cause programs to no longer function if |
| hadoop native libraries are used. These values should instead be set as part |
| of LD_LIBRARY_PATH in the map / reduce JVM env using the mapreduce.map.env and |
| mapreduce.reduce.env config settings. |
| </description> |
| </property> |
| |
| <property> |
| <name>yarn.app.mapreduce.am.job.task.listener.thread-count</name> |
| <value>30</value> |
| <description>The number of threads used to handle RPC calls in the |
| MR AppMaster from remote tasks</description> |
| </property> |
| |
| <property> |
| <name>yarn.app.mapreduce.am.job.client.port-range</name> |
| <value></value> |
| <description>Range of ports that the MapReduce AM can use when binding. |
| Leave blank if you want all possible ports. |
| For example 50000-50050,50100-50200</description> |
| </property> |
| |
| <property> |
| <name>yarn.app.mapreduce.am.job.committer.cancel-timeout</name> |
| <value>60000</value> |
| <description>The amount of time in milliseconds to wait for the output |
| committer to cancel an operation if the job is killed</description> |
| </property> |
| |
| <property> |
| <name>yarn.app.mapreduce.am.job.committer.commit-window</name> |
| <value>10000</value> |
| <description>Defines a time window in milliseconds for output commit |
| operations. If contact with the RM has occurred within this window then |
| commits are allowed, otherwise the AM will not allow output commits until |
| contact with the RM has been re-established.</description> |
| </property> |
| |
| <property> |
| <name>yarn.app.mapreduce.am.scheduler.heartbeat.interval-ms</name> |
| <value>1000</value> |
| <description>The interval in ms at which the MR AppMaster should send |
| heartbeats to the ResourceManager</description> |
| </property> |
| |
| <property> |
| <name>yarn.app.mapreduce.client-am.ipc.max-retries</name> |
| <value>3</value> |
| <description>The number of client retries to the AM - before reconnecting |
| to the RM to fetch Application Status.</description> |
| </property> |
| |
| <property> |
| <name>yarn.app.mapreduce.client-am.ipc.max-retries-on-timeouts</name> |
| <value>3</value> |
| <description>The number of client retries on socket timeouts to the AM - before |
| reconnecting to the RM to fetch Application Status.</description> |
| </property> |
| |
| <property> |
| <name>yarn.app.mapreduce.client.max-retries</name> |
| <value>3</value> |
| <description>The number of client retries to the RM/HS before |
| throwing exception. This is a layer above the ipc.</description> |
| </property> |
| |
| <property> |
| <name>yarn.app.mapreduce.am.resource.mb</name> |
| <value>1536</value> |
| <description>The amount of memory the MR AppMaster needs.</description> |
| </property> |
| |
| <property> |
| <name>yarn.app.mapreduce.am.resource.cpu-vcores</name> |
| <value>1</value> |
| <description> |
| The number of virtual CPU cores the MR AppMaster needs. |
| </description> |
| </property> |
| |
| <property> |
| <description>CLASSPATH for MR applications. A comma-separated list |
| of CLASSPATH entries. If mapreduce.application.framework is set then this |
| must specify the appropriate classpath for that archive, and the name of |
| the archive must be present in the classpath. |
| If mapreduce.app-submission.cross-platform is false, platform-specific |
| environment vairable expansion syntax would be used to construct the default |
| CLASSPATH entries. |
| For Linux: |
| $HADOOP_MAPRED_HOME/share/hadoop/mapreduce/*, |
| $HADOOP_MAPRED_HOME/share/hadoop/mapreduce/lib/*. |
| For Windows: |
| %HADOOP_MAPRED_HOME%/share/hadoop/mapreduce/*, |
| %HADOOP_MAPRED_HOME%/share/hadoop/mapreduce/lib/*. |
| |
| If mapreduce.app-submission.cross-platform is true, platform-agnostic default |
| CLASSPATH for MR applications would be used: |
| {{HADOOP_MAPRED_HOME}}/share/hadoop/mapreduce/*, |
| {{HADOOP_MAPRED_HOME}}/share/hadoop/mapreduce/lib/* |
| Parameter expansion marker will be replaced by NodeManager on container |
| launch based on the underlying OS accordingly. |
| </description> |
| <name>mapreduce.application.classpath</name> |
| <value></value> |
| </property> |
| |
| <property> |
| <description>If enabled, user can submit an application cross-platform |
| i.e. submit an application from a Windows client to a Linux/Unix server or |
| vice versa. |
| </description> |
| <name>mapreduce.app-submission.cross-platform</name> |
| <value>false</value> |
| </property> |
| |
| <property> |
| <description>Path to the MapReduce framework archive. If set, the framework |
| archive will automatically be distributed along with the job, and this |
| path would normally reside in a public location in an HDFS filesystem. As |
| with distributed cache files, this can be a URL with a fragment specifying |
| the alias to use for the archive name. For example, |
| hdfs:/mapred/framework/hadoop-mapreduce-2.1.1.tar.gz#mrframework would |
| alias the localized archive as "mrframework". |
| |
| Note that mapreduce.application.classpath must include the appropriate |
| classpath for the specified framework. The base name of the archive, or |
| alias of the archive if an alias is used, must appear in the specified |
| classpath. |
| </description> |
| <name>mapreduce.application.framework.path</name> |
| <value></value> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.classloader</name> |
| <value>false</value> |
| <description>Whether to use a separate (isolated) classloader for |
| user classes in the task JVM.</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.job.classloader.system.classes</name> |
| <value>java.,javax.,org.w3c.dom.,org.xml.sax.,org.apache.commons.logging., |
| org.apache.log4j.,org.apache.hadoop.,core-default.xml, |
| hdfs-default.xml,mapred-default.xml,yarn-default.xml</value> |
| <description>A comma-separated list of classes that should be loaded from the |
| system classpath, not the user-supplied JARs, when mapreduce.job.classloader |
| is enabled. Names ending in '.' (period) are treated as package names, |
| and names starting with a '-' are treated as negative matches. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jvm.system-properties-to-log</name> |
| <value>os.name,os.version,java.home,java.runtime.version,java.vendor,java.version,java.vm.name,java.class.path,java.io.tmpdir,user.dir,user.name</value> |
| <description>Comma-delimited list of system properties to log on mapreduce JVM start</description> |
| </property> |
| |
| <!-- jobhistory properties --> |
| |
| <property> |
| <name>mapreduce.jobhistory.address</name> |
| <value>0.0.0.0:10020</value> |
| <description>MapReduce JobHistory Server IPC host:port</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.webapp.address</name> |
| <value>0.0.0.0:19888</value> |
| <description>MapReduce JobHistory Server Web UI host:port</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.keytab</name> |
| <description> |
| Location of the kerberos keytab file for the MapReduce |
| JobHistory Server. |
| </description> |
| <value>/etc/security/keytab/jhs.service.keytab</value> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.principal</name> |
| <description> |
| Kerberos principal name for the MapReduce JobHistory Server. |
| </description> |
| <value>jhs/_HOST@REALM.TLD</value> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.intermediate-done-dir</name> |
| <value>${yarn.app.mapreduce.am.staging-dir}/history/done_intermediate</value> |
| <description></description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.done-dir</name> |
| <value>${yarn.app.mapreduce.am.staging-dir}/history/done</value> |
| <description></description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.cleaner.enable</name> |
| <value>true</value> |
| <description></description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.cleaner.interval-ms</name> |
| <value>86400000</value> |
| <description> How often the job history cleaner checks for files to delete, |
| in milliseconds. Defaults to 86400000 (one day). Files are only deleted if |
| they are older than mapreduce.jobhistory.max-age-ms. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.max-age-ms</name> |
| <value>604800000</value> |
| <description> Job history files older than this many milliseconds will |
| be deleted when the history cleaner runs. Defaults to 604800000 (1 week). |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.client.thread-count</name> |
| <value>10</value> |
| <description>The number of threads to handle client API requests</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.datestring.cache.size</name> |
| <value>200000</value> |
| <description>Size of the date string cache. Effects the number of directories |
| which will be scanned to find a job.</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.joblist.cache.size</name> |
| <value>20000</value> |
| <description>Size of the job list cache</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.loadedjobs.cache.size</name> |
| <value>5</value> |
| <description>Size of the loaded job cache</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.move.interval-ms</name> |
| <value>180000</value> |
| <description>Scan for history files to more from intermediate done dir to done |
| dir at this frequency. |
| </description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.move.thread-count</name> |
| <value>3</value> |
| <description>The number of threads used to move files.</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.store.class</name> |
| <value></value> |
| <description>The HistoryStorage class to use to cache history data.</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.minicluster.fixed.ports</name> |
| <value>false</value> |
| <description>Whether to use fixed ports with the minicluster</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.admin.address</name> |
| <value>0.0.0.0:10033</value> |
| <description>The address of the History server admin interface.</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.admin.acl</name> |
| <value>*</value> |
| <description>ACL of who can be admin of the History server.</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.recovery.enable</name> |
| <value>false</value> |
| <description>Enable the history server to store server state and recover |
| server state upon startup. If enabled then |
| mapreduce.jobhistory.recovery.store.class must be specified.</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.recovery.store.class</name> |
| <value>org.apache.hadoop.mapreduce.v2.hs.HistoryServerFileSystemStateStoreService</value> |
| <description>The HistoryServerStateStoreService class to store history server |
| state for recovery.</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.recovery.store.fs.uri</name> |
| <value>${hadoop.tmp.dir}/mapred/history/recoverystore</value> |
| <!--value>hdfs://localhost:9000/mapred/history/recoverystore</value--> |
| <description>The URI where history server state will be stored if |
| HistoryServerFileSystemStateStoreService is configured as the recovery |
| storage class.</description> |
| </property> |
| |
| <property> |
| <name>mapreduce.jobhistory.http.policy</name> |
| <value>HTTP_ONLY</value> |
| <description> |
| This configures the HTTP endpoint for JobHistoryServer web UI. |
| The following values are supported: |
| - HTTP_ONLY : Service is provided only on http |
| - HTTPS_ONLY : Service is provided only on https |
| </description> |
| </property> |
| </configuration> |