hadoop-default.html 43 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906
  1. <html>
  2. <body>
  3. <table border="1">
  4. <tr>
  5. <td>name</td><td>value</td><td>description</td>
  6. </tr>
  7. <tr>
  8. <td><a name="hadoop.tmp.dir">hadoop.tmp.dir</a></td><td>/tmp/hadoop-${user.name}</td><td>A base for other temporary directories.</td>
  9. </tr>
  10. <tr>
  11. <td><a name="hadoop.native.lib">hadoop.native.lib</a></td><td>true</td><td>Should native hadoop libraries, if present, be used.</td>
  12. </tr>
  13. <tr>
  14. <td><a name="hadoop.http.filter.initializers">hadoop.http.filter.initializers</a></td><td></td><td>A comma separated list of class names. Each class in the list must extend org.apache.hadoop.http.FilterInitializer.
  15. The corresponding Filter will be initialized. Then, the Filter will be applied to all user facing jsp and servlet web pages. The ordering of the list defines the ordering of the filters.
  16. The value can be empty.
  17. </td>
  18. </tr>
  19. <tr>
  20. <td><a name="hadoop.logfile.size">hadoop.logfile.size</a></td><td>10000000</td><td>The max size of each log file</td>
  21. </tr>
  22. <tr>
  23. <td><a name="hadoop.logfile.count">hadoop.logfile.count</a></td><td>10</td><td>The max number of log files</td>
  24. </tr>
  25. <tr>
  26. <td><a name="hadoop.job.history.location">hadoop.job.history.location</a></td><td></td><td> If job tracker is static the history files are stored
  27. in this single well known place. If No value is set here, by default,
  28. it is in the local file system at ${hadoop.log.dir}/history.
  29. </td>
  30. </tr>
  31. <tr>
  32. <td><a name="hadoop.job.history.user.location">hadoop.job.history.user.location</a></td><td></td><td> User can specify a location to store the history files of
  33. a particular job. If nothing is specified, the logs are stored in
  34. output directory. The files are stored in "_logs/history/" in the directory.
  35. User can stop logging by giving the value "none".
  36. </td>
  37. </tr>
  38. <tr>
  39. <td><a name="dfs.namenode.logging.level">dfs.namenode.logging.level</a></td><td>info</td><td>The logging level for dfs namenode. Other values are "dir"(trac
  40. e namespace mutations), "block"(trace block under/over replications and block
  41. creations/deletions), or "all".</td>
  42. </tr>
  43. <tr>
  44. <td><a name="io.sort.factor">io.sort.factor</a></td><td>10</td><td>The number of streams to merge at once while sorting
  45. files. This determines the number of open file handles.</td>
  46. </tr>
  47. <tr>
  48. <td><a name="io.sort.mb">io.sort.mb</a></td><td>100</td><td>The total amount of buffer memory to use while sorting
  49. files, in megabytes. By default, gives each merge stream 1MB, which
  50. should minimize seeks.</td>
  51. </tr>
  52. <tr>
  53. <td><a name="io.sort.record.percent">io.sort.record.percent</a></td><td>0.05</td><td>The percentage of io.sort.mb dedicated to tracking record
  54. boundaries. Let this value be r, io.sort.mb be x. The maximum number
  55. of records collected before the collection thread must block is equal
  56. to (r * x) / 4</td>
  57. </tr>
  58. <tr>
  59. <td><a name="io.sort.spill.percent">io.sort.spill.percent</a></td><td>0.80</td><td>The soft limit in either the buffer or record collection
  60. buffers. Once reached, a thread will begin to spill the contents to disk
  61. in the background. Note that this does not imply any chunking of data to
  62. the spill. A value less than 0.5 is not recommended.</td>
  63. </tr>
  64. <tr>
  65. <td><a name="io.file.buffer.size">io.file.buffer.size</a></td><td>4096</td><td>The size of buffer for use in sequence files.
  66. The size of this buffer should probably be a multiple of hardware
  67. page size (4096 on Intel x86), and it determines how much data is
  68. buffered during read and write operations.</td>
  69. </tr>
  70. <tr>
  71. <td><a name="io.bytes.per.checksum">io.bytes.per.checksum</a></td><td>512</td><td>The number of bytes per checksum. Must not be larger than
  72. io.file.buffer.size.</td>
  73. </tr>
  74. <tr>
  75. <td><a name="io.skip.checksum.errors">io.skip.checksum.errors</a></td><td>false</td><td>If true, when a checksum error is encountered while
  76. reading a sequence file, entries are skipped, instead of throwing an
  77. exception.</td>
  78. </tr>
  79. <tr>
  80. <td><a name="io.map.index.skip">io.map.index.skip</a></td><td>0</td><td>Number of index entries to skip between each entry.
  81. Zero by default. Setting this to values larger than zero can
  82. facilitate opening large map files using less memory.</td>
  83. </tr>
  84. <tr>
  85. <td><a name="io.compression.codecs">io.compression.codecs</a></td><td>org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.BZip2Codec</td><td>A list of the compression codec classes that can be used
  86. for compression/decompression.</td>
  87. </tr>
  88. <tr>
  89. <td><a name="io.serializations">io.serializations</a></td><td>org.apache.hadoop.io.serializer.WritableSerialization</td><td>A list of serialization classes that can be used for
  90. obtaining serializers and deserializers.</td>
  91. </tr>
  92. <tr>
  93. <td><a name="fs.default.name">fs.default.name</a></td><td>file:///</td><td>The name of the default file system. A URI whose
  94. scheme and authority determine the FileSystem implementation. The
  95. uri's scheme determines the config property (fs.SCHEME.impl) naming
  96. the FileSystem implementation class. The uri's authority is used to
  97. determine the host, port, etc. for a filesystem.</td>
  98. </tr>
  99. <tr>
  100. <td><a name="fs.trash.interval">fs.trash.interval</a></td><td>0</td><td>Number of minutes between trash checkpoints.
  101. If zero, the trash feature is disabled.
  102. </td>
  103. </tr>
  104. <tr>
  105. <td><a name="fs.file.impl">fs.file.impl</a></td><td>org.apache.hadoop.fs.LocalFileSystem</td><td>The FileSystem for file: uris.</td>
  106. </tr>
  107. <tr>
  108. <td><a name="fs.hdfs.impl">fs.hdfs.impl</a></td><td>org.apache.hadoop.hdfs.DistributedFileSystem</td><td>The FileSystem for hdfs: uris.</td>
  109. </tr>
  110. <tr>
  111. <td><a name="fs.s3.impl">fs.s3.impl</a></td><td>org.apache.hadoop.fs.s3.S3FileSystem</td><td>The FileSystem for s3: uris.</td>
  112. </tr>
  113. <tr>
  114. <td><a name="fs.s3n.impl">fs.s3n.impl</a></td><td>org.apache.hadoop.fs.s3native.NativeS3FileSystem</td><td>The FileSystem for s3n: (Native S3) uris.</td>
  115. </tr>
  116. <tr>
  117. <td><a name="fs.kfs.impl">fs.kfs.impl</a></td><td>org.apache.hadoop.fs.kfs.KosmosFileSystem</td><td>The FileSystem for kfs: uris.</td>
  118. </tr>
  119. <tr>
  120. <td><a name="fs.hftp.impl">fs.hftp.impl</a></td><td>org.apache.hadoop.hdfs.HftpFileSystem</td><td></td>
  121. </tr>
  122. <tr>
  123. <td><a name="fs.hsftp.impl">fs.hsftp.impl</a></td><td>org.apache.hadoop.hdfs.HsftpFileSystem</td><td></td>
  124. </tr>
  125. <tr>
  126. <td><a name="fs.ftp.impl">fs.ftp.impl</a></td><td>org.apache.hadoop.fs.ftp.FTPFileSystem</td><td>The FileSystem for ftp: uris.</td>
  127. </tr>
  128. <tr>
  129. <td><a name="fs.ramfs.impl">fs.ramfs.impl</a></td><td>org.apache.hadoop.fs.InMemoryFileSystem</td><td>The FileSystem for ramfs: uris.</td>
  130. </tr>
  131. <tr>
  132. <td><a name="fs.har.impl">fs.har.impl</a></td><td>org.apache.hadoop.fs.HarFileSystem</td><td>The filesystem for Hadoop archives. </td>
  133. </tr>
  134. <tr>
  135. <td><a name="fs.inmemory.size.mb">fs.inmemory.size.mb</a></td><td>75</td><td>The size of the in-memory filsystem instance in MB</td>
  136. </tr>
  137. <tr>
  138. <td><a name="fs.checkpoint.dir">fs.checkpoint.dir</a></td><td>${hadoop.tmp.dir}/dfs/namesecondary</td><td>Determines where on the local filesystem the DFS secondary
  139. name node should store the temporary images to merge.
  140. If this is a comma-delimited list of directories then the image is
  141. replicated in all of the directories for redundancy.
  142. </td>
  143. </tr>
  144. <tr>
  145. <td><a name="fs.checkpoint.edits.dir">fs.checkpoint.edits.dir</a></td><td>${fs.checkpoint.dir}</td><td>Determines where on the local filesystem the DFS secondary
  146. name node should store the temporary edits to merge.
  147. If this is a comma-delimited list of directoires then teh edits is
  148. replicated in all of the directoires for redundancy.
  149. Default value is same as fs.checkpoint.dir
  150. </td>
  151. </tr>
  152. <tr>
  153. <td><a name="fs.checkpoint.period">fs.checkpoint.period</a></td><td>3600</td><td>The number of seconds between two periodic checkpoints.
  154. </td>
  155. </tr>
  156. <tr>
  157. <td><a name="fs.checkpoint.size">fs.checkpoint.size</a></td><td>67108864</td><td>The size of the current edit log (in bytes) that triggers
  158. a periodic checkpoint even if the fs.checkpoint.period hasn't expired.
  159. </td>
  160. </tr>
  161. <tr>
  162. <td><a name="dfs.secondary.http.address">dfs.secondary.http.address</a></td><td>0.0.0.0:50090</td><td>
  163. The secondary namenode http server address and port.
  164. If the port is 0 then the server will start on a free port.
  165. </td>
  166. </tr>
  167. <tr>
  168. <td><a name="dfs.datanode.address">dfs.datanode.address</a></td><td>0.0.0.0:50010</td><td>
  169. The address where the datanode server will listen to.
  170. If the port is 0 then the server will start on a free port.
  171. </td>
  172. </tr>
  173. <tr>
  174. <td><a name="dfs.datanode.http.address">dfs.datanode.http.address</a></td><td>0.0.0.0:50075</td><td>
  175. The datanode http server address and port.
  176. If the port is 0 then the server will start on a free port.
  177. </td>
  178. </tr>
  179. <tr>
  180. <td><a name="dfs.datanode.ipc.address">dfs.datanode.ipc.address</a></td><td>0.0.0.0:50020</td><td>
  181. The datanode ipc server address and port.
  182. If the port is 0 then the server will start on a free port.
  183. </td>
  184. </tr>
  185. <tr>
  186. <td><a name="dfs.datanode.handler.count">dfs.datanode.handler.count</a></td><td>3</td><td>The number of server threads for the datanode.</td>
  187. </tr>
  188. <tr>
  189. <td><a name="dfs.http.address">dfs.http.address</a></td><td>0.0.0.0:50070</td><td>
  190. The address and the base port where the dfs namenode web ui will listen on.
  191. If the port is 0 then the server will start on a free port.
  192. </td>
  193. </tr>
  194. <tr>
  195. <td><a name="dfs.datanode.https.address">dfs.datanode.https.address</a></td><td>0.0.0.0:50475</td><td></td>
  196. </tr>
  197. <tr>
  198. <td><a name="dfs.https.address">dfs.https.address</a></td><td>0.0.0.0:50470</td><td></td>
  199. </tr>
  200. <tr>
  201. <td><a name="https.keystore.info.rsrc">https.keystore.info.rsrc</a></td><td>sslinfo.xml</td><td>The name of the resource from which ssl keystore information
  202. will be extracted
  203. </td>
  204. </tr>
  205. <tr>
  206. <td><a name="dfs.datanode.dns.interface">dfs.datanode.dns.interface</a></td><td>default</td><td>The name of the Network Interface from which a data node should
  207. report its IP address.
  208. </td>
  209. </tr>
  210. <tr>
  211. <td><a name="dfs.datanode.dns.nameserver">dfs.datanode.dns.nameserver</a></td><td>default</td><td>The host name or IP address of the name server (DNS)
  212. which a DataNode should use to determine the host name used by the
  213. NameNode for communication and display purposes.
  214. </td>
  215. </tr>
  216. <tr>
  217. <td><a name="dfs.replication.considerLoad">dfs.replication.considerLoad</a></td><td>true</td><td>Decide if chooseTarget considers the target's load or not
  218. </td>
  219. </tr>
  220. <tr>
  221. <td><a name="dfs.default.chunk.view.size">dfs.default.chunk.view.size</a></td><td>32768</td><td>The number of bytes to view for a file on the browser.
  222. </td>
  223. </tr>
  224. <tr>
  225. <td><a name="dfs.datanode.du.reserved">dfs.datanode.du.reserved</a></td><td>0</td><td>Reserved space in bytes per volume. Always leave this much space free for non dfs use.
  226. </td>
  227. </tr>
  228. <tr>
  229. <td><a name="dfs.datanode.du.pct">dfs.datanode.du.pct</a></td><td>0.98f</td><td>When calculating remaining space, only use this percentage of the real available space
  230. </td>
  231. </tr>
  232. <tr>
  233. <td><a name="dfs.name.dir">dfs.name.dir</a></td><td>${hadoop.tmp.dir}/dfs/name</td><td>Determines where on the local filesystem the DFS name node
  234. should store the name table(fsimage). If this is a comma-delimited list
  235. of directories then the name table is replicated in all of the
  236. directories, for redundancy. </td>
  237. </tr>
  238. <tr>
  239. <td><a name="dfs.name.edits.dir">dfs.name.edits.dir</a></td><td>${dfs.name.dir}</td><td>Determines where on the local filesystem the DFS name node
  240. should store the transaction (edits) file. If this is a comma-delimited list
  241. of directories then the transaction file is replicated in all of the
  242. directories, for redundancy. Default value is same as dfs.name.dir
  243. </td>
  244. </tr>
  245. <tr>
  246. <td><a name="dfs.web.ugi">dfs.web.ugi</a></td><td>webuser,webgroup</td><td>The user account used by the web interface.
  247. Syntax: USERNAME,GROUP1,GROUP2, ...
  248. </td>
  249. </tr>
  250. <tr>
  251. <td><a name="dfs.permissions">dfs.permissions</a></td><td>true</td><td>
  252. If "true", enable permission checking in HDFS.
  253. If "false", permission checking is turned off,
  254. but all other behavior is unchanged.
  255. Switching from one parameter value to the other does not change the mode,
  256. owner or group of files or directories.
  257. </td>
  258. </tr>
  259. <tr>
  260. <td><a name="dfs.permissions.supergroup">dfs.permissions.supergroup</a></td><td>supergroup</td><td>The name of the group of super-users.</td>
  261. </tr>
  262. <tr>
  263. <td><a name="dfs.data.dir">dfs.data.dir</a></td><td>${hadoop.tmp.dir}/dfs/data</td><td>Determines where on the local filesystem an DFS data node
  264. should store its blocks. If this is a comma-delimited
  265. list of directories, then data will be stored in all named
  266. directories, typically on different devices.
  267. Directories that do not exist are ignored.
  268. </td>
  269. </tr>
  270. <tr>
  271. <td><a name="dfs.replication">dfs.replication</a></td><td>3</td><td>Default block replication.
  272. The actual number of replications can be specified when the file is created.
  273. The default is used if replication is not specified in create time.
  274. </td>
  275. </tr>
  276. <tr>
  277. <td><a name="dfs.replication.max">dfs.replication.max</a></td><td>512</td><td>Maximal block replication.
  278. </td>
  279. </tr>
  280. <tr>
  281. <td><a name="dfs.replication.min">dfs.replication.min</a></td><td>1</td><td>Minimal block replication.
  282. </td>
  283. </tr>
  284. <tr>
  285. <td><a name="dfs.block.size">dfs.block.size</a></td><td>67108864</td><td>The default block size for new files.</td>
  286. </tr>
  287. <tr>
  288. <td><a name="dfs.df.interval">dfs.df.interval</a></td><td>60000</td><td>Disk usage statistics refresh interval in msec.</td>
  289. </tr>
  290. <tr>
  291. <td><a name="dfs.client.block.write.retries">dfs.client.block.write.retries</a></td><td>3</td><td>The number of retries for writing blocks to the data nodes,
  292. before we signal failure to the application.
  293. </td>
  294. </tr>
  295. <tr>
  296. <td><a name="dfs.blockreport.intervalMsec">dfs.blockreport.intervalMsec</a></td><td>3600000</td><td>Determines block reporting interval in milliseconds.</td>
  297. </tr>
  298. <tr>
  299. <td><a name="dfs.blockreport.initialDelay">dfs.blockreport.initialDelay</a></td><td>0</td><td>Delay for first block report in seconds.</td>
  300. </tr>
  301. <tr>
  302. <td><a name="dfs.heartbeat.interval">dfs.heartbeat.interval</a></td><td>3</td><td>Determines datanode heartbeat interval in seconds.</td>
  303. </tr>
  304. <tr>
  305. <td><a name="dfs.namenode.handler.count">dfs.namenode.handler.count</a></td><td>10</td><td>The number of server threads for the namenode.</td>
  306. </tr>
  307. <tr>
  308. <td><a name="dfs.safemode.threshold.pct">dfs.safemode.threshold.pct</a></td><td>0.999f</td><td>
  309. Specifies the percentage of blocks that should satisfy
  310. the minimal replication requirement defined by dfs.replication.min.
  311. Values less than or equal to 0 mean not to start in safe mode.
  312. Values greater than 1 will make safe mode permanent.
  313. </td>
  314. </tr>
  315. <tr>
  316. <td><a name="dfs.safemode.extension">dfs.safemode.extension</a></td><td>30000</td><td>
  317. Determines extension of safe mode in milliseconds
  318. after the threshold level is reached.
  319. </td>
  320. </tr>
  321. <tr>
  322. <td><a name="dfs.balance.bandwidthPerSec">dfs.balance.bandwidthPerSec</a></td><td>1048576</td><td>
  323. Specifies the maximum amount of bandwidth that each datanode
  324. can utilize for the balancing purpose in term of
  325. the number of bytes per second.
  326. </td>
  327. </tr>
  328. <tr>
  329. <td><a name="dfs.hosts">dfs.hosts</a></td><td></td><td>Names a file that contains a list of hosts that are
  330. permitted to connect to the namenode. The full pathname of the file
  331. must be specified. If the value is empty, all hosts are
  332. permitted.</td>
  333. </tr>
  334. <tr>
  335. <td><a name="dfs.hosts.exclude">dfs.hosts.exclude</a></td><td></td><td>Names a file that contains a list of hosts that are
  336. not permitted to connect to the namenode. The full pathname of the
  337. file must be specified. If the value is empty, no hosts are
  338. excluded.</td>
  339. </tr>
  340. <tr>
  341. <td><a name="dfs.max.objects">dfs.max.objects</a></td><td>0</td><td>The maximum number of files, directories and blocks
  342. dfs supports. A value of zero indicates no limit to the number
  343. of objects that dfs supports.
  344. </td>
  345. </tr>
  346. <tr>
  347. <td><a name="dfs.namenode.decommission.interval">dfs.namenode.decommission.interval</a></td><td>300</td><td>Namenode periodicity in seconds to check if decommission is complete.</td>
  348. </tr>
  349. <tr>
  350. <td><a name="dfs.replication.interval">dfs.replication.interval</a></td><td>3</td><td>The periodicity in seconds with which the namenode computes repliaction work for datanodes. </td>
  351. </tr>
  352. <tr>
  353. <td><a name="fs.s3.block.size">fs.s3.block.size</a></td><td>67108864</td><td>Block size to use when writing files to S3.</td>
  354. </tr>
  355. <tr>
  356. <td><a name="fs.s3.buffer.dir">fs.s3.buffer.dir</a></td><td>${hadoop.tmp.dir}/s3</td><td>Determines where on the local filesystem the S3 filesystem
  357. should store files before sending them to S3
  358. (or after retrieving them from S3).
  359. </td>
  360. </tr>
  361. <tr>
  362. <td><a name="fs.s3.maxRetries">fs.s3.maxRetries</a></td><td>4</td><td>The maximum number of retries for reading or writing files to S3,
  363. before we signal failure to the application.
  364. </td>
  365. </tr>
  366. <tr>
  367. <td><a name="fs.s3.sleepTimeSeconds">fs.s3.sleepTimeSeconds</a></td><td>10</td><td>The number of seconds to sleep between each S3 retry.
  368. </td>
  369. </tr>
  370. <tr>
  371. <td><a name="mapred.job.tracker">mapred.job.tracker</a></td><td>local</td><td>The host and port that the MapReduce job tracker runs
  372. at. If "local", then jobs are run in-process as a single map
  373. and reduce task.
  374. </td>
  375. </tr>
  376. <tr>
  377. <td><a name="mapred.job.tracker.http.address">mapred.job.tracker.http.address</a></td><td>0.0.0.0:50030</td><td>
  378. The job tracker http server address and port the server will listen on.
  379. If the port is 0 then the server will start on a free port.
  380. </td>
  381. </tr>
  382. <tr>
  383. <td><a name="mapred.job.tracker.handler.count">mapred.job.tracker.handler.count</a></td><td>10</td><td>
  384. The number of server threads for the JobTracker. This should be roughly
  385. 4% of the number of tasktracker nodes.
  386. </td>
  387. </tr>
  388. <tr>
  389. <td><a name="mapred.task.tracker.report.address">mapred.task.tracker.report.address</a></td><td>127.0.0.1:0</td><td>The interface and port that task tracker server listens on.
  390. Since it is only connected to by the tasks, it uses the local interface.
  391. EXPERT ONLY. Should only be changed if your host does not have the loopback
  392. interface.</td>
  393. </tr>
  394. <tr>
  395. <td><a name="mapred.local.dir">mapred.local.dir</a></td><td>${hadoop.tmp.dir}/mapred/local</td><td>The local directory where MapReduce stores intermediate
  396. data files. May be a comma-separated list of
  397. directories on different devices in order to spread disk i/o.
  398. Directories that do not exist are ignored.
  399. </td>
  400. </tr>
  401. <tr>
  402. <td><a name="local.cache.size">local.cache.size</a></td><td>10737418240</td><td>The limit on the size of cache you want to keep, set by default
  403. to 10GB. This will act as a soft limit on the cache directory for out of band data.
  404. </td>
  405. </tr>
  406. <tr>
  407. <td><a name="mapred.system.dir">mapred.system.dir</a></td><td>${hadoop.tmp.dir}/mapred/system</td><td>The shared directory where MapReduce stores control files.
  408. </td>
  409. </tr>
  410. <tr>
  411. <td><a name="mapred.temp.dir">mapred.temp.dir</a></td><td>${hadoop.tmp.dir}/mapred/temp</td><td>A shared directory for temporary files.
  412. </td>
  413. </tr>
  414. <tr>
  415. <td><a name="mapred.local.dir.minspacestart">mapred.local.dir.minspacestart</a></td><td>0</td><td>If the space in mapred.local.dir drops under this,
  416. do not ask for more tasks.
  417. Value in bytes.
  418. </td>
  419. </tr>
  420. <tr>
  421. <td><a name="mapred.local.dir.minspacekill">mapred.local.dir.minspacekill</a></td><td>0</td><td>If the space in mapred.local.dir drops under this,
  422. do not ask more tasks until all the current ones have finished and
  423. cleaned up. Also, to save the rest of the tasks we have running,
  424. kill one of them, to clean up some space. Start with the reduce tasks,
  425. then go with the ones that have finished the least.
  426. Value in bytes.
  427. </td>
  428. </tr>
  429. <tr>
  430. <td><a name="mapred.tasktracker.expiry.interval">mapred.tasktracker.expiry.interval</a></td><td>600000</td><td>Expert: The time-interval, in miliseconds, after which
  431. a tasktracker is declared 'lost' if it doesn't send heartbeats.
  432. </td>
  433. </tr>
  434. <tr>
  435. <td><a name="mapred.tasktracker.instrumentation">mapred.tasktracker.instrumentation</a></td><td>org.apache.hadoop.mapred.TaskTrackerMetricsInst</td><td>Expert: The instrumentation class to associate with each TaskTracker.
  436. </td>
  437. </tr>
  438. <tr>
  439. <td><a name="mapred.map.tasks">mapred.map.tasks</a></td><td>2</td><td>The default number of map tasks per job. Typically set
  440. to a prime several times greater than number of available hosts.
  441. Ignored when mapred.job.tracker is "local".
  442. </td>
  443. </tr>
  444. <tr>
  445. <td><a name="mapred.reduce.tasks">mapred.reduce.tasks</a></td><td>1</td><td>The default number of reduce tasks per job. Typically set
  446. to a prime close to the number of available hosts. Ignored when
  447. mapred.job.tracker is "local".
  448. </td>
  449. </tr>
  450. <tr>
  451. <td><a name="mapred.jobtracker.taskScheduler">mapred.jobtracker.taskScheduler</a></td><td>org.apache.hadoop.mapred.JobQueueTaskScheduler</td><td>The class responsible for scheduling the tasks.</td>
  452. </tr>
  453. <tr>
  454. <td><a name="mapred.jobtracker.taskScheduler.maxRunningTasksPerJob">mapred.jobtracker.taskScheduler.maxRunningTasksPerJob</a></td><td></td><td>The maximum number of running tasks for a job before
  455. it gets preempted. No limits if undefined.
  456. </td>
  457. </tr>
  458. <tr>
  459. <td><a name="mapred.map.max.attempts">mapred.map.max.attempts</a></td><td>4</td><td>Expert: The maximum number of attempts per map task.
  460. In other words, framework will try to execute a map task these many number
  461. of times before giving up on it.
  462. </td>
  463. </tr>
  464. <tr>
  465. <td><a name="mapred.reduce.max.attempts">mapred.reduce.max.attempts</a></td><td>4</td><td>Expert: The maximum number of attempts per reduce task.
  466. In other words, framework will try to execute a reduce task these many number
  467. of times before giving up on it.
  468. </td>
  469. </tr>
  470. <tr>
  471. <td><a name="mapred.reduce.parallel.copies">mapred.reduce.parallel.copies</a></td><td>5</td><td>The default number of parallel transfers run by reduce
  472. during the copy(shuffle) phase.
  473. </td>
  474. </tr>
  475. <tr>
  476. <td><a name="mapred.reduce.copy.backoff">mapred.reduce.copy.backoff</a></td><td>300</td><td>The maximum amount of time (in seconds) a reducer spends on
  477. fetching one map output before declaring it as failed.
  478. </td>
  479. </tr>
  480. <tr>
  481. <td><a name="mapred.task.timeout">mapred.task.timeout</a></td><td>600000</td><td>The number of milliseconds before a task will be
  482. terminated if it neither reads an input, writes an output, nor
  483. updates its status string.
  484. </td>
  485. </tr>
  486. <tr>
  487. <td><a name="mapred.tasktracker.map.tasks.maximum">mapred.tasktracker.map.tasks.maximum</a></td><td>2</td><td>The maximum number of map tasks that will be run
  488. simultaneously by a task tracker.
  489. </td>
  490. </tr>
  491. <tr>
  492. <td><a name="mapred.tasktracker.reduce.tasks.maximum">mapred.tasktracker.reduce.tasks.maximum</a></td><td>2</td><td>The maximum number of reduce tasks that will be run
  493. simultaneously by a task tracker.
  494. </td>
  495. </tr>
  496. <tr>
  497. <td><a name="mapred.jobtracker.completeuserjobs.maximum">mapred.jobtracker.completeuserjobs.maximum</a></td><td>100</td><td>The maximum number of complete jobs per user to keep around before delegating them to the job history.
  498. </td>
  499. </tr>
  500. <tr>
  501. <td><a name="mapred.jobtracker.instrumentation">mapred.jobtracker.instrumentation</a></td><td>org.apache.hadoop.mapred.JobTrackerMetricsInst</td><td>Expert: The instrumentation class to associate with each JobTracker.
  502. </td>
  503. </tr>
  504. <tr>
  505. <td><a name="mapred.child.java.opts">mapred.child.java.opts</a></td><td>-Xmx200m</td><td>Java opts for the task tracker child processes.
  506. The following symbol, if present, will be interpolated: @taskid@ is replaced
  507. by current TaskID. Any other occurrences of '@' will go unchanged.
  508. For example, to enable verbose gc logging to a file named for the taskid in
  509. /tmp and to set the heap maximum to be a gigabyte, pass a 'value' of:
  510. -Xmx1024m -verbose:gc -Xloggc:/tmp/@taskid@.gc
  511. The configuration variable mapred.child.ulimit can be used to control the
  512. maximum virtual memory of the child processes.
  513. </td>
  514. </tr>
  515. <tr>
  516. <td><a name="mapred.child.ulimit">mapred.child.ulimit</a></td><td></td><td>The maximum virtual memory, in KB, of a process launched by the
  517. Map-Reduce framework. This can be used to control both the Mapper/Reducer
  518. tasks and applications using Hadoop Pipes, Hadoop Streaming etc.
  519. By default it is left unspecified to let cluster admins control it via
  520. limits.conf and other such relevant mechanisms.
  521. Note: mapred.child.ulimit must be greater than or equal to the -Xmx passed to
  522. JavaVM, else the VM might not start.
  523. </td>
  524. </tr>
  525. <tr>
  526. <td><a name="mapred.child.tmp">mapred.child.tmp</a></td><td>./tmp</td><td> To set the value of tmp directory for map and reduce tasks.
  527. If the value is an absolute path, it is directly assigned. Otherwise, it is
  528. prepended with task's working directory. The java tasks are executed with
  529. option -Djava.io.tmpdir='the absolute path of the tmp dir'. Pipes and
  530. streaming are set with environment variable,
  531. TMPDIR='the absolute path of the tmp dir'
  532. </td>
  533. </tr>
  534. <tr>
  535. <td><a name="mapred.inmem.merge.threshold">mapred.inmem.merge.threshold</a></td><td>1000</td><td>The threshold, in terms of the number of files
  536. for the in-memory merge process. When we accumulate threshold number of files
  537. we initiate the in-memory merge and spill to disk. A value of 0 or less than
  538. 0 indicates we want to DON'T have any threshold and instead depend only on
  539. the ramfs's memory consumption to trigger the merge.
  540. </td>
  541. </tr>
  542. <tr>
  543. <td><a name="mapred.map.tasks.speculative.execution">mapred.map.tasks.speculative.execution</a></td><td>true</td><td>If true, then multiple instances of some map tasks
  544. may be executed in parallel.</td>
  545. </tr>
  546. <tr>
  547. <td><a name="mapred.reduce.tasks.speculative.execution">mapred.reduce.tasks.speculative.execution</a></td><td>true</td><td>If true, then multiple instances of some reduce tasks
  548. may be executed in parallel.</td>
  549. </tr>
  550. <tr>
  551. <td><a name="mapred.min.split.size">mapred.min.split.size</a></td><td>0</td><td>The minimum size chunk that map input should be split
  552. into. Note that some file formats may have minimum split sizes that
  553. take priority over this setting.</td>
  554. </tr>
  555. <tr>
  556. <td><a name="mapred.submit.replication">mapred.submit.replication</a></td><td>10</td><td>The replication level for submitted job files. This
  557. should be around the square root of the number of nodes.
  558. </td>
  559. </tr>
  560. <tr>
  561. <td><a name="mapred.tasktracker.dns.interface">mapred.tasktracker.dns.interface</a></td><td>default</td><td>The name of the Network Interface from which a task
  562. tracker should report its IP address.
  563. </td>
  564. </tr>
  565. <tr>
  566. <td><a name="mapred.tasktracker.dns.nameserver">mapred.tasktracker.dns.nameserver</a></td><td>default</td><td>The host name or IP address of the name server (DNS)
  567. which a TaskTracker should use to determine the host name used by
  568. the JobTracker for communication and display purposes.
  569. </td>
  570. </tr>
  571. <tr>
  572. <td><a name="tasktracker.http.threads">tasktracker.http.threads</a></td><td>40</td><td>The number of worker threads that for the http server. This is
  573. used for map output fetching
  574. </td>
  575. </tr>
  576. <tr>
  577. <td><a name="mapred.task.tracker.http.address">mapred.task.tracker.http.address</a></td><td>0.0.0.0:50060</td><td>
  578. The task tracker http server address and port.
  579. If the port is 0 then the server will start on a free port.
  580. </td>
  581. </tr>
  582. <tr>
  583. <td><a name="keep.failed.task.files">keep.failed.task.files</a></td><td>false</td><td>Should the files for failed tasks be kept. This should only be
  584. used on jobs that are failing, because the storage is never
  585. reclaimed. It also prevents the map outputs from being erased
  586. from the reduce directory as they are consumed.</td>
  587. </tr>
  588. <tr>
  589. <td><a name="mapred.output.compress">mapred.output.compress</a></td><td>false</td><td>Should the job outputs be compressed?
  590. </td>
  591. </tr>
  592. <tr>
  593. <td><a name="mapred.output.compression.type">mapred.output.compression.type</a></td><td>RECORD</td><td>If the job outputs are to compressed as SequenceFiles, how should
  594. they be compressed? Should be one of NONE, RECORD or BLOCK.
  595. </td>
  596. </tr>
  597. <tr>
  598. <td><a name="mapred.output.compression.codec">mapred.output.compression.codec</a></td><td>org.apache.hadoop.io.compress.DefaultCodec</td><td>If the job outputs are compressed, how should they be compressed?
  599. </td>
  600. </tr>
  601. <tr>
  602. <td><a name="mapred.compress.map.output">mapred.compress.map.output</a></td><td>false</td><td>Should the outputs of the maps be compressed before being
  603. sent across the network. Uses SequenceFile compression.
  604. </td>
  605. </tr>
  606. <tr>
  607. <td><a name="mapred.map.output.compression.codec">mapred.map.output.compression.codec</a></td><td>org.apache.hadoop.io.compress.DefaultCodec</td><td>If the map outputs are compressed, how should they be
  608. compressed?
  609. </td>
  610. </tr>
  611. <tr>
  612. <td><a name="io.seqfile.compress.blocksize">io.seqfile.compress.blocksize</a></td><td>1000000</td><td>The minimum block size for compression in block compressed
  613. SequenceFiles.
  614. </td>
  615. </tr>
  616. <tr>
  617. <td><a name="io.seqfile.lazydecompress">io.seqfile.lazydecompress</a></td><td>true</td><td>Should values of block-compressed SequenceFiles be decompressed
  618. only when necessary.
  619. </td>
  620. </tr>
  621. <tr>
  622. <td><a name="io.seqfile.sorter.recordlimit">io.seqfile.sorter.recordlimit</a></td><td>1000000</td><td>The limit on number of records to be kept in memory in a spill
  623. in SequenceFiles.Sorter
  624. </td>
  625. </tr>
  626. <tr>
  627. <td><a name="map.sort.class">map.sort.class</a></td><td>org.apache.hadoop.util.QuickSort</td><td>The default sort class for sorting keys.
  628. </td>
  629. </tr>
  630. <tr>
  631. <td><a name="mapred.userlog.limit.kb">mapred.userlog.limit.kb</a></td><td>0</td><td>The maximum size of user-logs of each task in KB. 0 disables the cap.
  632. </td>
  633. </tr>
  634. <tr>
  635. <td><a name="mapred.userlog.retain.hours">mapred.userlog.retain.hours</a></td><td>24</td><td>The maximum time, in hours, for which the user-logs are to be
  636. retained.
  637. </td>
  638. </tr>
  639. <tr>
  640. <td><a name="mapred.hosts">mapred.hosts</a></td><td></td><td>Names a file that contains the list of nodes that may
  641. connect to the jobtracker. If the value is empty, all hosts are
  642. permitted.</td>
  643. </tr>
  644. <tr>
  645. <td><a name="mapred.hosts.exclude">mapred.hosts.exclude</a></td><td></td><td>Names a file that contains the list of hosts that
  646. should be excluded by the jobtracker. If the value is empty, no
  647. hosts are excluded.</td>
  648. </tr>
  649. <tr>
  650. <td><a name="mapred.max.tracker.failures">mapred.max.tracker.failures</a></td><td>4</td><td>The number of task-failures on a tasktracker of a given job
  651. after which new tasks of that job aren't assigned to it.
  652. </td>
  653. </tr>
  654. <tr>
  655. <td><a name="jobclient.output.filter">jobclient.output.filter</a></td><td>FAILED</td><td>The filter for controlling the output of the task's userlogs sent
  656. to the console of the JobClient.
  657. The permissible options are: NONE, KILLED, FAILED, SUCCEEDED and
  658. ALL.
  659. </td>
  660. </tr>
  661. <tr>
  662. <td><a name="mapred.job.tracker.persist.jobstatus.active">mapred.job.tracker.persist.jobstatus.active</a></td><td>false</td><td>Indicates if persistency of job status information is
  663. active or not.
  664. </td>
  665. </tr>
  666. <tr>
  667. <td><a name="mapred.job.tracker.persist.jobstatus.hours">mapred.job.tracker.persist.jobstatus.hours</a></td><td>0</td><td>The number of hours job status information is persisted in DFS.
  668. The job status information will be available after it drops of the memory
  669. queue and between jobtracker restarts. With a zero value the job status
  670. information is not persisted at all in DFS.
  671. </td>
  672. </tr>
  673. <tr>
  674. <td><a name="mapred.job.tracker.persist.jobstatus.dir">mapred.job.tracker.persist.jobstatus.dir</a></td><td>/jobtracker/jobsInfo</td><td>The directory where the job status information is persisted
  675. in a file system to be available after it drops of the memory queue and
  676. between jobtracker restarts.
  677. </td>
  678. </tr>
  679. <tr>
  680. <td><a name="mapred.task.profile">mapred.task.profile</a></td><td>false</td><td>To set whether the system should collect profiler
  681. information for some of the tasks in this job? The information is stored
  682. in the the user log directory. The value is "true" if task profiling
  683. is enabled.</td>
  684. </tr>
  685. <tr>
  686. <td><a name="mapred.task.profile.maps">mapred.task.profile.maps</a></td><td>0-2</td><td> To set the ranges of map tasks to profile.
  687. mapred.task.profile has to be set to true for the value to be accounted.
  688. </td>
  689. </tr>
  690. <tr>
  691. <td><a name="mapred.task.profile.reduces">mapred.task.profile.reduces</a></td><td>0-2</td><td> To set the ranges of reduce tasks to profile.
  692. mapred.task.profile has to be set to true for the value to be accounted.
  693. </td>
  694. </tr>
  695. <tr>
  696. <td><a name="mapred.line.input.format.linespermap">mapred.line.input.format.linespermap</a></td><td>1</td><td> Number of lines per split in NLineInputFormat.
  697. </td>
  698. </tr>
  699. <tr>
  700. <td><a name="mapred.skip.mode.enabled">mapred.skip.mode.enabled</a></td><td>false</td><td> Indicates whether skipping of bad records is enabled or not.
  701. If enabled the framework will try to find bad records and skip
  702. them on further attempts.
  703. </td>
  704. </tr>
  705. <tr>
  706. <td><a name="mapred.skip.attempts.to.start.skipping">mapred.skip.attempts.to.start.skipping</a></td><td>2</td><td> The number of Task attempts AFTER which skip mode
  707. will be kicked off. When skip mode is kicked off, the
  708. tasks reports the range of records which it will process
  709. next, to the TaskTracker. So that on failures, TT knows which
  710. ones are possibly the bad records. On further executions,
  711. those are skipped.
  712. </td>
  713. </tr>
  714. <tr>
  715. <td><a name="mapred.skip.map.auto.incr.proc.count">mapred.skip.map.auto.incr.proc.count</a></td><td>true</td><td> The flag which if set to true,
  716. Counters.Application.MAP_PROCESSED_RECORDS is incremented
  717. by MapRunner after invoking the map function. This value must be set to
  718. false for applications which process the records asynchronously
  719. or buffer the input records. For example streaming.
  720. In such cases applications should increment this counter on their own.
  721. </td>
  722. </tr>
  723. <tr>
  724. <td><a name="mapred.skip.reduce.auto.incr.proc.count">mapred.skip.reduce.auto.incr.proc.count</a></td><td>true</td><td> The flag which if set to true,
  725. Counters.Application.REDUCE_PROCESSED_RECORDS is incremented
  726. by framework after invoking the reduce function. This value must be set to
  727. false for applications which process the records asynchronously
  728. or buffer the input records. For example streaming.
  729. In such cases applications should increment this counter on their own.
  730. </td>
  731. </tr>
  732. <tr>
  733. <td><a name="ipc.client.idlethreshold">ipc.client.idlethreshold</a></td><td>4000</td><td>Defines the threshold number of connections after which
  734. connections will be inspected for idleness.
  735. </td>
  736. </tr>
  737. <tr>
  738. <td><a name="ipc.client.kill.max">ipc.client.kill.max</a></td><td>10</td><td>Defines the maximum number of clients to disconnect in one go.
  739. </td>
  740. </tr>
  741. <tr>
  742. <td><a name="ipc.client.connection.maxidletime">ipc.client.connection.maxidletime</a></td><td>10000</td><td>The maximum time in msec after which a client will bring down the
  743. connection to the server.
  744. </td>
  745. </tr>
  746. <tr>
  747. <td><a name="ipc.client.connect.max.retries">ipc.client.connect.max.retries</a></td><td>10</td><td>Indicates the number of retries a client will make to establish
  748. a server connection.
  749. </td>
  750. </tr>
  751. <tr>
  752. <td><a name="ipc.server.listen.queue.size">ipc.server.listen.queue.size</a></td><td>128</td><td>Indicates the length of the listen queue for servers accepting
  753. client connections.
  754. </td>
  755. </tr>
  756. <tr>
  757. <td><a name="ipc.server.tcpnodelay">ipc.server.tcpnodelay</a></td><td>false</td><td>Turn on/off Nagle's algorithm for the TCP socket connection on
  758. the server. Setting to true disables the algorithm and may decrease latency
  759. with a cost of more/smaller packets.
  760. </td>
  761. </tr>
  762. <tr>
  763. <td><a name="ipc.client.tcpnodelay">ipc.client.tcpnodelay</a></td><td>false</td><td>Turn on/off Nagle's algorithm for the TCP socket connection on
  764. the client. Setting to true disables the algorithm and may decrease latency
  765. with a cost of more/smaller packets.
  766. </td>
  767. </tr>
  768. <tr>
  769. <td><a name="job.end.retry.attempts">job.end.retry.attempts</a></td><td>0</td><td>Indicates how many times hadoop should attempt to contact the
  770. notification URL </td>
  771. </tr>
  772. <tr>
  773. <td><a name="job.end.retry.interval">job.end.retry.interval</a></td><td>30000</td><td>Indicates time in milliseconds between notification URL retry
  774. calls</td>
  775. </tr>
  776. <tr>
  777. <td><a name="webinterface.private.actions">webinterface.private.actions</a></td><td>false</td><td> If set to true, the web interfaces of JT and NN may contain
  778. actions, such as kill job, delete file, etc., that should
  779. not be exposed to public. Enable this option if the interfaces
  780. are only reachable by those who have the right authorization.
  781. </td>
  782. </tr>
  783. <tr>
  784. <td><a name="hadoop.rpc.socket.factory.class.default">hadoop.rpc.socket.factory.class.default</a></td><td>org.apache.hadoop.net.StandardSocketFactory</td><td> Default SocketFactory to use. This parameter is expected to be
  785. formatted as "package.FactoryClassName".
  786. </td>
  787. </tr>
  788. <tr>
  789. <td><a name="hadoop.rpc.socket.factory.class.ClientProtocol">hadoop.rpc.socket.factory.class.ClientProtocol</a></td><td></td><td> SocketFactory to use to connect to a DFS. If null or empty, use
  790. hadoop.rpc.socket.class.default. This socket factory is also used by
  791. DFSClient to create sockets to DataNodes.
  792. </td>
  793. </tr>
  794. <tr>
  795. <td><a name="hadoop.rpc.socket.factory.class.JobSubmissionProtocol">hadoop.rpc.socket.factory.class.JobSubmissionProtocol</a></td><td></td><td> SocketFactory to use to connect to a Map/Reduce master
  796. (JobTracker). If null or empty, then use hadoop.rpc.socket.class.default.
  797. </td>
  798. </tr>
  799. <tr>
  800. <td><a name="hadoop.socks.server">hadoop.socks.server</a></td><td></td><td> Address (host:port) of the SOCKS server to be used by the
  801. SocksSocketFactory.
  802. </td>
  803. </tr>
  804. <tr>
  805. <td><a name="topology.node.switch.mapping.impl">topology.node.switch.mapping.impl</a></td><td>org.apache.hadoop.net.ScriptBasedMapping</td><td> The default implementation of the DNSToSwitchMapping. It
  806. invokes a script specified in topology.script.file.name to resolve
  807. node names. If the value for topology.script.file.name is not set, the
  808. default value of DEFAULT_RACK is returned for all node names.
  809. </td>
  810. </tr>
  811. <tr>
  812. <td><a name="topology.script.file.name">topology.script.file.name</a></td><td></td><td> The script name that should be invoked to resolve DNS names to
  813. NetworkTopology names. Example: the script would take host.foo.bar as an
  814. argument, and return /rack1 as the output.
  815. </td>
  816. </tr>
  817. <tr>
  818. <td><a name="topology.script.number.args">topology.script.number.args</a></td><td>100</td><td> The max number of args that the script configured with
  819. topology.script.file.name should be run with. Each arg is an
  820. IP address.
  821. </td>
  822. </tr>
  823. <tr>
  824. <td><a name="mapred.task.cache.levels">mapred.task.cache.levels</a></td><td>2</td><td> This is the max level of the task cache. For example, if
  825. the level is 2, the tasks cached are at the host level and at the rack
  826. level.
  827. </td>
  828. </tr>
  829. <tr>
  830. <td><a name="mapred.tasktracker.tasks.maxmemory">mapred.tasktracker.tasks.maxmemory</a></td><td>-1</td><td> The maximum amount of virtual memory all tasks running on a
  831. tasktracker, including sub-processes they launch, can use. This value is
  832. used to compute the amount of free memory available for tasks. Any task
  833. scheduled on this tasktracker is guaranteed and constrained to use a
  834. share of this amount. Any task exceeding its share will be killed.
  835. If set to -1, this functionality is disabled, and mapred.task.maxmemory
  836. is ignored.
  837. </td>
  838. </tr>
  839. <tr>
  840. <td><a name="mapred.task.maxmemory">mapred.task.maxmemory</a></td><td>-1</td><td> The maximum amount of memory any task of a job will use.
  841. A task of this job will be scheduled on a tasktracker, only if the
  842. amount of free memory on the tasktracker is greater than or
  843. equal to this value. If set to -1, tasks are assured a memory limit on
  844. the tasktracker equal to
  845. mapred.tasktracker.tasks.maxmemory/number of slots. If the value of
  846. mapred.tasktracker.tasks.maxmemory is set to -1, this value is ignored.
  847. Note: If mapred.child.java.opts is specified with an Xmx value, or if
  848. mapred.child.ulimit is specified, then the value of mapred.task.maxmemory
  849. must be set to a higher value than these. If not, the task might be
  850. killed even though these limits are not reached.
  851. </td>
  852. </tr>
  853. <tr>
  854. <td><a name="mapred.queue.names">mapred.queue.names</a></td><td>default</td><td> Comma separated list of queues configured for this jobtracker.
  855. Jobs are added to queues and schedulers can configure different
  856. scheduling properties for the various queues. To configure a property
  857. for a queue, the name of the queue must match the name specified in this
  858. value. Queue properties that are common to all schedulers are configured
  859. here with the naming convention, mapred.queue.$QUEUE-NAME.$PROPERTY-NAME,
  860. for e.g. mapred.queue.default.submit-job-acl.
  861. The number of queues configured in this parameter could depend on the
  862. type of scheduler being used, as specified in
  863. mapred.jobtracker.taskScheduler. For example, the JobQueueTaskScheduler
  864. supports only a single queue, which is the default configured here.
  865. Before adding more queues, ensure that the scheduler you've configured
  866. supports multiple queues.
  867. </td>
  868. </tr>
  869. <tr>
  870. <td><a name="mapred.acls.enabled">mapred.acls.enabled</a></td><td>false</td><td> Specifies whether ACLs are enabled, and should be checked
  871. for various operations.
  872. </td>
  873. </tr>
  874. <tr>
  875. <td><a name="mapred.queue.default.acl-submit-job">mapred.queue.default.acl-submit-job</a></td><td>*</td><td> Comma separated list of user and group names that are allowed
  876. to submit jobs to the 'default' queue. The user list and the group list
  877. are separated by a blank. For e.g. alice,bob group1,group2.
  878. If set to the special value '*', it means all users are allowed to
  879. submit jobs.
  880. </td>
  881. </tr>
  882. <tr>
  883. <td><a name="mapred.queue.default.acl-administer-jobs">mapred.queue.default.acl-administer-jobs</a></td><td>*</td><td> Comma separated list of user and group names that are allowed
  884. to delete jobs or modify job's priority for jobs not owned by the current
  885. user in the 'default' queue. The user list and the group list
  886. are separated by a blank. For e.g. alice,bob group1,group2.
  887. If set to the special value '*', it means all users are allowed to do
  888. this operation.
  889. </td>
  890. </tr>
  891. <tr>
  892. <td><a name="queue.name">queue.name</a></td><td>default</td><td> Queue to which a job is submitted. This must match one of the
  893. queues defined in mapred.queue.names for the system. Also, the ACL setup
  894. for the queue must allow the current user to submit a job to the queue.
  895. Before specifying a queue, ensure that the system is configured with
  896. the queue, and access is allowed for submitting jobs to the queue.
  897. </td>
  898. </tr>
  899. </table>
  900. </body>
  901. </html>