hdfs-rbf-default.xml 15 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468
  1. <?xml version="1.0"?>
  2. <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
  3. <!--
  4. Licensed to the Apache Software Foundation (ASF) under one or more
  5. contributor license agreements. See the NOTICE file distributed with
  6. this work for additional information regarding copyright ownership.
  7. The ASF licenses this file to You under the Apache License, Version 2.0
  8. (the "License"); you may not use this file except in compliance with
  9. the License. You may obtain a copy of the License at
  10. http://www.apache.org/licenses/LICENSE-2.0
  11. Unless required by applicable law or agreed to in writing, software
  12. distributed under the License is distributed on an "AS IS" BASIS,
  13. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  14. See the License for the specific language governing permissions and
  15. limitations under the License.
  16. -->
  17. <!-- Do not modify this file directly. Instead, copy entries that you -->
  18. <!-- wish to modify from this file into hdfs-site.xml and change them -->
  19. <!-- there. If hdfs-site.xml does not already exist, create it. -->
  20. <configuration>
  21. <property>
  22. <name>dfs.federation.router.default.nameserviceId</name>
  23. <value></value>
  24. <description>
  25. Nameservice identifier of the default subcluster to monitor.
  26. </description>
  27. </property>
  28. <property>
  29. <name>dfs.federation.router.default.nameservice.enable</name>
  30. <value>true</value>
  31. <description>
  32. The default subcluster is enabled to read and write files.
  33. </description>
  34. </property>
  35. <property>
  36. <name>dfs.federation.router.rpc.enable</name>
  37. <value>true</value>
  38. <description>
  39. If true, the RPC service to handle client requests in the router is
  40. enabled.
  41. </description>
  42. </property>
  43. <property>
  44. <name>dfs.federation.router.rpc-address</name>
  45. <value>0.0.0.0:8888</value>
  46. <description>
  47. RPC address that handles all clients requests.
  48. The value of this property will take the form of router-host1:rpc-port.
  49. </description>
  50. </property>
  51. <property>
  52. <name>dfs.federation.router.rpc-bind-host</name>
  53. <value></value>
  54. <description>
  55. The actual address the RPC server will bind to. If this optional address is
  56. set, it overrides only the hostname portion of
  57. dfs.federation.router.rpc-address. This is useful for making the name node
  58. listen on all interfaces by setting it to 0.0.0.0.
  59. </description>
  60. </property>
  61. <property>
  62. <name>dfs.federation.router.handler.count</name>
  63. <value>10</value>
  64. <description>
  65. The number of server threads for the router to handle RPC requests from
  66. clients.
  67. </description>
  68. </property>
  69. <property>
  70. <name>dfs.federation.router.handler.queue.size</name>
  71. <value>100</value>
  72. <description>
  73. The size of the queue for the number of handlers to handle RPC client requests.
  74. </description>
  75. </property>
  76. <property>
  77. <name>dfs.federation.router.reader.count</name>
  78. <value>1</value>
  79. <description>
  80. The number of readers for the router to handle RPC client requests.
  81. </description>
  82. </property>
  83. <property>
  84. <name>dfs.federation.router.reader.queue.size</name>
  85. <value>100</value>
  86. <description>
  87. The size of the queue for the number of readers for the router to handle RPC client requests.
  88. </description>
  89. </property>
  90. <property>
  91. <name>dfs.federation.router.connection.creator.queue-size</name>
  92. <value>100</value>
  93. <description>
  94. Size of async connection creator queue.
  95. </description>
  96. </property>
  97. <property>
  98. <name>dfs.federation.router.connection.pool-size</name>
  99. <value>1</value>
  100. <description>
  101. Size of the pool of connections from the router to namenodes.
  102. </description>
  103. </property>
  104. <property>
  105. <name>dfs.federation.router.connection.clean.ms</name>
  106. <value>10000</value>
  107. <description>
  108. Time interval, in milliseconds, to check if the connection pool should
  109. remove unused connections.
  110. </description>
  111. </property>
  112. <property>
  113. <name>dfs.federation.router.connection.pool.clean.ms</name>
  114. <value>60000</value>
  115. <description>
  116. Time interval, in milliseconds, to check if the connection manager should
  117. remove unused connection pools.
  118. </description>
  119. </property>
  120. <property>
  121. <name>dfs.federation.router.metrics.enable</name>
  122. <value>true</value>
  123. <description>
  124. If the metrics in the router are enabled.
  125. </description>
  126. </property>
  127. <property>
  128. <name>dfs.federation.router.metrics.class</name>
  129. <value>org.apache.hadoop.hdfs.server.federation.metrics.FederationRPCPerformanceMonitor</value>
  130. <description>
  131. Class to monitor the RPC system in the router. It must implement the
  132. RouterRpcMonitor interface.
  133. </description>
  134. </property>
  135. <property>
  136. <name>dfs.federation.router.admin.enable</name>
  137. <value>true</value>
  138. <description>
  139. If true, the RPC admin service to handle client requests in the router is
  140. enabled.
  141. </description>
  142. </property>
  143. <property>
  144. <name>dfs.federation.router.admin-address</name>
  145. <value>0.0.0.0:8111</value>
  146. <description>
  147. RPC address that handles the admin requests.
  148. The value of this property will take the form of router-host1:rpc-port.
  149. </description>
  150. </property>
  151. <property>
  152. <name>dfs.federation.router.admin-bind-host</name>
  153. <value></value>
  154. <description>
  155. The actual address the RPC admin server will bind to. If this optional
  156. address is set, it overrides only the hostname portion of
  157. dfs.federation.router.admin-address. This is useful for making the name
  158. node listen on all interfaces by setting it to 0.0.0.0.
  159. </description>
  160. </property>
  161. <property>
  162. <name>dfs.federation.router.admin.handler.count</name>
  163. <value>1</value>
  164. <description>
  165. The number of server threads for the router to handle RPC requests from
  166. admin.
  167. </description>
  168. </property>
  169. <property>
  170. <name>dfs.federation.router.http-address</name>
  171. <value>0.0.0.0:50071</value>
  172. <description>
  173. HTTP address that handles the web requests to the Router.
  174. The value of this property will take the form of router-host1:http-port.
  175. </description>
  176. </property>
  177. <property>
  178. <name>dfs.federation.router.http-bind-host</name>
  179. <value></value>
  180. <description>
  181. The actual address the HTTP server will bind to. If this optional
  182. address is set, it overrides only the hostname portion of
  183. dfs.federation.router.http-address. This is useful for making the name
  184. node listen on all interfaces by setting it to 0.0.0.0.
  185. </description>
  186. </property>
  187. <property>
  188. <name>dfs.federation.router.https-address</name>
  189. <value>0.0.0.0:50072</value>
  190. <description>
  191. HTTPS address that handles the web requests to the Router.
  192. The value of this property will take the form of router-host1:https-port.
  193. </description>
  194. </property>
  195. <property>
  196. <name>dfs.federation.router.https-bind-host</name>
  197. <value></value>
  198. <description>
  199. The actual address the HTTPS server will bind to. If this optional
  200. address is set, it overrides only the hostname portion of
  201. dfs.federation.router.https-address. This is useful for making the name
  202. node listen on all interfaces by setting it to 0.0.0.0.
  203. </description>
  204. </property>
  205. <property>
  206. <name>dfs.federation.router.http.enable</name>
  207. <value>true</value>
  208. <description>
  209. If the HTTP service to handle client requests in the router is enabled.
  210. </description>
  211. </property>
  212. <property>
  213. <name>dfs.federation.router.metrics.enable</name>
  214. <value>true</value>
  215. <description>
  216. If the metrics service in the router is enabled.
  217. </description>
  218. </property>
  219. <property>
  220. <name>dfs.federation.router.file.resolver.client.class</name>
  221. <value>org.apache.hadoop.hdfs.server.federation.resolver.MountTableResolver</value>
  222. <description>
  223. Class to resolve files to subclusters.
  224. </description>
  225. </property>
  226. <property>
  227. <name>dfs.federation.router.namenode.resolver.client.class</name>
  228. <value>org.apache.hadoop.hdfs.server.federation.resolver.MembershipNamenodeResolver</value>
  229. <description>
  230. Class to resolve the namenode for a subcluster.
  231. </description>
  232. </property>
  233. <property>
  234. <name>dfs.federation.router.store.enable</name>
  235. <value>true</value>
  236. <description>
  237. If true, the Router connects to the State Store.
  238. </description>
  239. </property>
  240. <property>
  241. <name>dfs.federation.router.store.serializer</name>
  242. <value>org.apache.hadoop.hdfs.server.federation.store.driver.impl.StateStoreSerializerPBImpl</value>
  243. <description>
  244. Class to serialize State Store records.
  245. </description>
  246. </property>
  247. <property>
  248. <name>dfs.federation.router.store.driver.class</name>
  249. <value>org.apache.hadoop.hdfs.server.federation.store.driver.impl.StateStoreZooKeeperImpl</value>
  250. <description>
  251. Class to implement the State Store. There are three implementation classes currently
  252. being supported:
  253. org.apache.hadoop.hdfs.server.federation.store.driver.impl.StateStoreFileImpl,
  254. org.apache.hadoop.hdfs.server.federation.store.driver.impl.StateStoreFileSystemImpl and
  255. org.apache.hadoop.hdfs.server.federation.store.driver.impl.StateStoreZooKeeperImpl.
  256. These implementation classes use the local file, filesystem and ZooKeeper as a backend respectively.
  257. By default it uses the ZooKeeper as the default State Store.
  258. </description>
  259. </property>
  260. <property>
  261. <name>dfs.federation.router.store.connection.test</name>
  262. <value>60000</value>
  263. <description>
  264. How often to check for the connection to the State Store in milliseconds.
  265. </description>
  266. </property>
  267. <property>
  268. <name>dfs.federation.router.cache.ttl</name>
  269. <value>1m</value>
  270. <description>
  271. How often to refresh the State Store caches in milliseconds. This setting
  272. supports multiple time unit suffixes as described in
  273. dfs.heartbeat.interval. If no suffix is specified then milliseconds is
  274. assumed.
  275. </description>
  276. </property>
  277. <property>
  278. <name>dfs.federation.router.store.membership.expiration</name>
  279. <value>300000</value>
  280. <description>
  281. Expiration time in milliseconds for a membership record.
  282. </description>
  283. </property>
  284. <property>
  285. <name>dfs.federation.router.heartbeat.enable</name>
  286. <value>true</value>
  287. <description>
  288. If true, the Router heartbeats into the State Store.
  289. </description>
  290. </property>
  291. <property>
  292. <name>dfs.federation.router.heartbeat.interval</name>
  293. <value>5000</value>
  294. <description>
  295. How often the Router should heartbeat into the State Store in milliseconds.
  296. </description>
  297. </property>
  298. <property>
  299. <name>dfs.federation.router.heartbeat-state.interval</name>
  300. <value>5s</value>
  301. <description>
  302. How often the Router should heartbeat its state into the State Store in
  303. milliseconds. This setting supports multiple time unit suffixes as
  304. described in dfs.federation.router.quota-cache.update.interval.
  305. </description>
  306. </property>
  307. <property>
  308. <name>dfs.federation.router.store.router.expiration</name>
  309. <value>5m</value>
  310. <description>
  311. Expiration time in milliseconds for a router state record. This setting
  312. supports multiple time unit suffixes as described in
  313. dfs.federation.router.quota-cache.update.interval.
  314. </description>
  315. </property>
  316. <property>
  317. <name>dfs.federation.router.safemode.enable</name>
  318. <value>true</value>
  319. <description>
  320. </description>
  321. </property>
  322. <property>
  323. <name>dfs.federation.router.safemode.extension</name>
  324. <value>30s</value>
  325. <description>
  326. Time after startup that the Router is in safe mode. This setting
  327. supports multiple time unit suffixes as described in
  328. dfs.heartbeat.interval. If no suffix is specified then milliseconds is
  329. assumed.
  330. </description>
  331. </property>
  332. <property>
  333. <name>dfs.federation.router.safemode.expiration</name>
  334. <value>3m</value>
  335. <description>
  336. Time without being able to reach the State Store to enter safe mode. This
  337. setting supports multiple time unit suffixes as described in
  338. dfs.heartbeat.interval. If no suffix is specified then milliseconds is
  339. assumed.
  340. </description>
  341. </property>
  342. <property>
  343. <name>dfs.federation.router.monitor.namenode</name>
  344. <value></value>
  345. <description>
  346. The identifier of the namenodes to monitor and heartbeat.
  347. </description>
  348. </property>
  349. <property>
  350. <name>dfs.federation.router.monitor.localnamenode.enable</name>
  351. <value>true</value>
  352. <description>
  353. If true, the Router should monitor the namenode in the local machine.
  354. </description>
  355. </property>
  356. <property>
  357. <name>dfs.federation.router.mount-table.max-cache-size</name>
  358. <value>10000</value>
  359. <description>
  360. Maximum number of mount table cache entries to have.
  361. By default, remove cache entries if we have more than 10k.
  362. </description>
  363. </property>
  364. <property>
  365. <name>dfs.federation.router.mount-table.cache.enable</name>
  366. <value>true</value>
  367. <description>
  368. Set to true to enable mount table cache (Path to Remote Location cache).
  369. Disabling the cache is recommended when a large amount of unique paths are queried.
  370. </description>
  371. </property>
  372. <property>
  373. <name>dfs.federation.router.quota.enable</name>
  374. <value>false</value>
  375. <description>
  376. Set to true to enable quota system in Router.
  377. </description>
  378. </property>
  379. <property>
  380. <name>dfs.federation.router.quota-cache.update.interval</name>
  381. <value>60s</value>
  382. <description>
  383. Interval time for updating quota usage cache in Router.
  384. This property is used only if the value of
  385. dfs.federation.router.quota.enable is true.
  386. This setting supports multiple time unit suffixes as described
  387. in dfs.heartbeat.interval. If no suffix is specified then milliseconds
  388. is assumed.
  389. </description>
  390. </property>
  391. <property>
  392. <name>dfs.federation.router.client.thread-size</name>
  393. <value>32</value>
  394. <description>
  395. Max threads size for the RouterClient to execute concurrent
  396. requests.
  397. </description>
  398. </property>
  399. <property>
  400. <name>dfs.federation.router.client.retry.max.attempts</name>
  401. <value>3</value>
  402. <description>
  403. Max retry attempts for the RouterClient talking to the Router.
  404. </description>
  405. </property>
  406. <property>
  407. <name>dfs.federation.router.client.reject.overload</name>
  408. <value>false</value>
  409. <description>
  410. Set to true to reject client requests when we run out of RPC client
  411. threads.
  412. </description>
  413. </property>
  414. </configuration>