1
0

ozone-default.xml 27 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940
  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 ozone-site.xml and change them -->
  19. <!-- there. If ozone-site.xml does not already exist, create it. -->
  20. <configuration>
  21. <property>
  22. <name>ozone.enabled</name>
  23. <value>false</value>
  24. <description>
  25. Status of the Ozone Object Storage service is enabled.
  26. Set to true to enable Ozone.
  27. Set to false to disable Ozone.
  28. </description>
  29. </property>
  30. <property>
  31. <name>ozone.handler.type</name>
  32. <value>distributed</value>
  33. <description>
  34. The second key dfs.storage.handler.type tells ozone which storage
  35. handler to use. The possible values are:
  36. distributed - The Ozone distributed storage handler.
  37. local - Local Storage handler strictly for testing.
  38. </description>
  39. </property>
  40. <property>
  41. <name>ozone.localstorage.root</name>
  42. <value>/tmp/ozone</value>
  43. <description>
  44. </description>
  45. </property>
  46. <property>
  47. <name>ozone.trace.enabled</name>
  48. <value>false</value>
  49. <description>
  50. </description>
  51. </property>
  52. <property>
  53. <name>ozone.container.metadata.dirs</name>
  54. <value></value>
  55. <description>
  56. Ozone metadata dir path.
  57. </description>
  58. </property>
  59. <property>
  60. <name>ozone.key.cache.size</name>
  61. <value>1024</value>
  62. <description>
  63. </description>
  64. </property>
  65. <property>
  66. <name>ozone.administrators</name>
  67. <value></value>
  68. <description>
  69. Ozone administrator users delimited by comma.
  70. If not set, only the user who launches an ozone service will be the
  71. admin user. This property must be set if ozone services are started by
  72. different users. Otherwise the RPC layer will reject calls from
  73. other servers which are started by users not in the list.
  74. </description>
  75. </property>
  76. <property>
  77. <name>ozone.client.protocol</name>
  78. <value>org.apache.hadoop.ozone.client.rpc.RpcClient</value>
  79. <description>
  80. Protocol class to be used by client to connect to ozone cluster.
  81. The build-in implementation includes:
  82. org.apache.hadoop.ozone.client.rpc.RpcClient for RPC
  83. org.apache.hadoop.ozone.client.rest.RestClient for REST
  84. </description>
  85. </property>
  86. <property>
  87. <name>ozone.client.socket.timeout.ms</name>
  88. <value>5000</value>
  89. <description>
  90. Socket timeout for Ozone client in milliseconds.
  91. </description>
  92. </property>
  93. <property>
  94. <name>ozone.client.connection.timeout.ms</name>
  95. <value>5000</value>
  96. <description>
  97. Connection timeout for Ozone client in milliseconds.
  98. </description>
  99. </property>
  100. <property>
  101. <name>ozone.scm.client.address</name>
  102. <value></value>
  103. <description>
  104. The address of the Ozone SCM client service. This is a required
  105. setting.
  106. It is a string in the host:port format. The port number is optional
  107. and defaults to 9860.
  108. </description>
  109. </property>
  110. <property>
  111. <name>ozone.scm.client.port</name>
  112. <value>9860</value>
  113. <description>
  114. The port number of the Ozone SCM client service.
  115. </description>
  116. </property>
  117. <property>
  118. <name>ozone.scm.datanode.address</name>
  119. <value></value>
  120. <description>
  121. The address of the Ozone SCM service used for internal communication
  122. between the DataNodes and the SCM.
  123. It is a string in the host:port format. The port number is optional
  124. and defaults to 9861.
  125. This setting is optional. If unspecified then the hostname portion
  126. is picked from the ozone.scm.client.address setting and the
  127. default service port of 9861 is chosen.
  128. </description>
  129. </property>
  130. <property>
  131. <name>ozone.scm.datanode.bind.host</name>
  132. <value></value>
  133. <description>
  134. The hostname or IP address used by the SCM service endpoint to bind.
  135. </description>
  136. </property>
  137. <property>
  138. <name>ozone.scm.datanode.port</name>
  139. <value>9861</value>
  140. <description>
  141. The port number of the Ozone SCM service.
  142. </description>
  143. </property>
  144. <property>
  145. <name>ozone.scm.client.bind.host</name>
  146. <value>0.0.0.0</value>
  147. <description>
  148. The hostname or IP address used by the SCM client endpoint to bind.
  149. This setting is used by the SCM only and never used by clients.
  150. The setting can be useful in multi-homed setups to restrict the
  151. availability of the SCM client service to a specific interface.
  152. The default is appropriate for most clusters.
  153. </description>
  154. </property>
  155. <property>
  156. <name>ozone.scm.block.client.address</name>
  157. <value></value>
  158. <description>
  159. The address of the Ozone SCM block client service. If not defined
  160. value of ozone.scm.client.address is used.
  161. </description>
  162. </property>
  163. <property>
  164. <name>ozone.scm.block.client.bind.host</name>
  165. <value>0.0.0.0</value>
  166. <description>
  167. The hostname or IP address used by the SCM block client
  168. endpoint to bind.
  169. </description>
  170. </property>
  171. <property>
  172. <name>ozone.scm.block.client.port</name>
  173. <value>9863</value>
  174. <description>
  175. The port number of the Ozone SCM block client service.
  176. </description>
  177. </property>
  178. <property>
  179. <name>ozone.scm.handler.count.key</name>
  180. <value>10</value>
  181. <description>
  182. The number of RPC handler threads for each SCM service endpoint.
  183. The default is appropriate for small clusters (tens of nodes).
  184. </description>
  185. </property>
  186. <property>
  187. <name>ozone.scm.chunk.size</name>
  188. <value>1048576</value>
  189. <description>
  190. The chunk size for read/write chunk operations in bytes.
  191. The chunk size defaults to 1MB. If the value configured is more
  192. than the maximum size (1MB), it will be reset to the maximum
  193. size.
  194. </description>
  195. </property>
  196. <property>
  197. <name>ozone.scm.heartbeat.interval.seconds</name>
  198. <value>30</value>
  199. <description>
  200. The heartbeat interval from a datanode to SCM in seconds.
  201. </description>
  202. </property>
  203. <property>
  204. <name>ozone.scm.stale.node.interval.ms</name>
  205. <value>90000</value>
  206. <description>
  207. The interval in milliseconds for stale node flagging.
  208. </description>
  209. </property>
  210. <property>
  211. <name>ozone.scm.dead.node.interval.ms</name>
  212. <value>600000</value>
  213. <description>
  214. The interval in milliseconds for dead node flagging.
  215. </description>
  216. </property>
  217. <property>
  218. <name>ozone.scm.max.hb.count.to.process</name>
  219. <value>5000</value>
  220. <description>
  221. The maximum number of heartbeat to process per loop of the process
  222. thread.
  223. </description>
  224. </property>
  225. <property>
  226. <name>ozone.scm.heartbeat.thread.interval.ms</name>
  227. <value>3000</value>
  228. <description>
  229. The interval in milliseconds that the heartbeat processor thread runs.
  230. </description>
  231. </property>
  232. <property>
  233. <name>ozone.scm.heartbeat.rpc-timeout</name>
  234. <value>1000</value>
  235. <description>
  236. Timeout value for the RPC from Datanode to SCM in milliseconds.
  237. </description>
  238. </property>
  239. <property>
  240. <name>ozone.scm.block.deletion.max.retry</name>
  241. <value>4096</value>
  242. <description>
  243. SCM wraps up a number of blocks in a deletion transaction and send that
  244. to datanode for physically deletion periodically. This property
  245. determines how many times at most for SCM to retry sending a deletion
  246. transaction to datanode. The default value 4096 is relatively big so
  247. that SCM could try enough times before giving up, as the actual deletion
  248. is async so time required is unpredictable.
  249. </description>
  250. </property>
  251. <property>
  252. <name>ozone.scm.heartbeat.log.warn.interval.count</name>
  253. <value>10</value>
  254. <description>
  255. Defines how frequently we will log the missing of heartbeat to SCM.
  256. For example in the default case, we will write a warning message for each 10
  257. sequential heartbeats that we miss to SCM.
  258. </description>
  259. </property>
  260. <property>
  261. <name>ozone.scm.names</name>
  262. <value></value>
  263. <description>
  264. The value of this property is a set of DNS | DNS:PORT | IP Address | IP:PORT.
  265. Written as a comma separated string. e.g. scm1, scm2:8020, 7.7.7.7:7777.
  266. This property allows datanodes to discover where SCM is, so that
  267. datanodes can send heartbeat to SCM.
  268. </description>
  269. </property>
  270. <property>
  271. <name>ozone.scm.datanode.id</name>
  272. <value></value>
  273. <description>
  274. The path that datanodes will created to store the datanode ID.
  275. If this value is not set, datanodes will fail to come up.
  276. </description>
  277. </property>
  278. <property>
  279. <name>ozone.scm.db.cache.size.mb</name>
  280. <value>128</value>
  281. <description>
  282. The cache size for SCM level db store in MB.
  283. </description>
  284. </property>
  285. <property>
  286. <name>ozone.scm.container.size.gb</name>
  287. <value>5</value>
  288. <description>
  289. Storage container size in GB for block allocations.
  290. </description>
  291. </property>
  292. <property>
  293. <name>ozone.scm.container.placement.impl</name>
  294. <value>org.apache.hadoop.ozone.scm.container.placement.algorithms.SCMContainerPlacementRandom</value>
  295. <description>
  296. Placement policy class for containers.
  297. Defaults to SCMContainerPlacementRandom.class
  298. </description>
  299. </property>
  300. <property>
  301. <name>ozone.scm.container.provision_batch_size</name>
  302. <value>1</value>
  303. <description>
  304. Pre-provision specified number of containers to creare for
  305. block creation.
  306. </description>
  307. </property>
  308. <property>
  309. <name>ozone.scm.max.container.report.threads</name>
  310. <value>100</value>
  311. <description>
  312. Maximum number of threads to process container reports in scm.
  313. Each container report from a datanode is processed by scm in
  314. a worker thread, fetched from a thread pool. This property is
  315. used to control the maximum size of the thread pool.
  316. </description>
  317. </property>
  318. <property>
  319. <name>ozone.scm.container.reports.wait.timeout.seconds</name>
  320. <value>300</value>
  321. <description>
  322. Maximum time to wait in seconds for processing all container
  323. reports from a node pool. It determines the timeout for a
  324. node pool reports.
  325. </description>
  326. </property>
  327. <property>
  328. <name>ozone.scm.container.report.processing.interval.seconds</name>
  329. <value>60</value>
  330. <description>
  331. Time interval in seconds for scm to process container reports
  332. for a node pool. Scm handles node pool reports in a cyclic clock
  333. manner, it fetches pools periodically with this time interval.
  334. </description>
  335. </property>
  336. <property>
  337. <name>ozone.block.deleting.service.interval.ms</name>
  338. <value>60000</value>
  339. <description>
  340. Time interval in milliseconds of the block deleting service.
  341. The block deleting service runs on each datanode to scan staled
  342. blocks and delete them asynchronously.
  343. </description>
  344. </property>
  345. <property>
  346. <name>ozone.block.deleting.service.timeout</name>
  347. <value>300000ms</value>
  348. <description>
  349. Timeout value of block deletion service. If this is set greater than 0,
  350. the service will stop waiting for the block deleting completion after this
  351. time. If timeout happens to a large proportion of block deletion, this needs
  352. to be increased with ozone.block.deleting.limit.per.task. This setting supports
  353. multiple time unit suffixes as described in dfs.heartbeat.interval. If no suffix
  354. is specified then milliseconds is assumed.
  355. </description>
  356. </property>
  357. <property>
  358. <name>ozone.block.deleting.limit.per.task</name>
  359. <value>1000</value>
  360. <description>
  361. Maximum number of blocks to be deleted by block deleting service
  362. per time interval. This property is used to throttle the actual number
  363. of block deletions on a datanode per container.
  364. </description>
  365. </property>
  366. <property>
  367. <name>ozone.block.deleting.container.limit.per.interval</name>
  368. <value>10</value>
  369. <description>
  370. Maximum number of containers to be scanned by block deleting service
  371. per time interval. The block deleting service spawns a thread to handle
  372. block deletions in a container. This property is used to throttle
  373. the number of threads spawned for block deletions.
  374. </description>
  375. </property>
  376. <property>
  377. <name>ozone.scm.container.deletion-choosing.policy</name>
  378. <value>org.apache.hadoop.ozone.container.common.impl.TopNOrderedContainerDeletionChoosingPolicy</value>
  379. <description>
  380. The policy used for choosing desire containers for block deletion.
  381. Datanode selects a number of containers to process block deletion
  382. in a certain interval defined by ozone.block.deleting.service.interval.ms,
  383. the number of containers to process in each interval is defined
  384. by ozone.block.deleting.container.limit.per.interval. This property
  385. is used to configure the policy applied while selecting containers.
  386. There are two policies supporting now: RandomContainerDeletionChoosingPolicy and
  387. TopNOrderedContainerDeletionChoosingPolicy.
  388. org.apache.hadoop.ozone.container.common.impl.RandomContainerDeletionChoosingPolicy
  389. implements a simply random policy that to return a random list of containers.
  390. org.apache.hadoop.ozone.container.common.impl.TopNOrderedContainerDeletionChoosingPolicy
  391. implements a policy that choosing top count number of containers in a pending-deletion-blocks's num
  392. based descending order.
  393. </description>
  394. </property>
  395. <property>
  396. <name>ozone.key.deleting.limit.per.task</name>
  397. <value>1000</value>
  398. <description>
  399. Maximum number of keys to be scanned by key deleting service per
  400. time interval in KSM. Those keys are sent to delete metadata and
  401. generate transactions in SCM for next async deletion between SCM
  402. and DataNode.
  403. </description>
  404. </property>
  405. <property>
  406. <name>dfs.container.ipc</name>
  407. <value>50011</value>
  408. <description>
  409. The ipc port number of container.
  410. </description>
  411. </property>
  412. <property>
  413. <name>dfs.container.ipc.random.port</name>
  414. <value>false</value>
  415. <description>
  416. Whether allocates a random free port for ozone container.
  417. </description>
  418. </property>
  419. <property>
  420. <name>scm.container.client.idle.threshold</name>
  421. <value>10000</value>
  422. <description>
  423. </description>
  424. </property>
  425. <property>
  426. <name>scm.container.client.max.size</name>
  427. <value>256</value>
  428. <description>
  429. </description>
  430. </property>
  431. <property>
  432. <name>dfs.container.ratis.enabled</name>
  433. <value>false</value>
  434. <description>
  435. </description>
  436. </property>
  437. <property>
  438. <name>dfs.container.ratis.rpc.type</name>
  439. <value>GRPC</value>
  440. <description>
  441. </description>
  442. </property>
  443. <property>
  444. <name>dfs.container.ratis.server.id</name>
  445. <value></value>
  446. <description>
  447. The unique ID to identify a Ratis server.
  448. </description>
  449. </property>
  450. <property>
  451. <name>dfs.container.ratis.datanode.storage.dir</name>
  452. <value></value>
  453. <description>
  454. </description>
  455. </property>
  456. <!--KSM properties-->
  457. <property>
  458. <name>ozone.ksm.handler.count.key</name>
  459. <value>200</value>
  460. <description>
  461. The number of RPC handler threads for each KSM service endpoint.
  462. </description>
  463. </property>
  464. <property>
  465. <name>ozone.ksm.address</name>
  466. <value>0.0.0.0</value>
  467. <description>
  468. The address of the Ozone KSM service.
  469. </description>
  470. </property>
  471. <property>
  472. <name>ozone.ksm.leveldb.cache.size.mb</name>
  473. <value>128</value>
  474. <description>
  475. The size of KSM LevelDB cache in MB that used for caching files.
  476. </description>
  477. </property>
  478. <property>
  479. <name>ozone.ksm.user.max.volume</name>
  480. <value>1024</value>
  481. <description>
  482. The maximum number of volumes that each user can create.
  483. </description>
  484. </property>
  485. <property>
  486. <name>ozone.ksm.user.rights</name>
  487. <value>READ_WRITE</value>
  488. <description>
  489. Default user permissions in Ozone KSM.
  490. </description>
  491. </property>
  492. <property>
  493. <name>ozone.ksm.group.rights</name>
  494. <value>READ_WRITE</value>
  495. <description>
  496. Default group permissions in Ozone KSM.
  497. </description>
  498. </property>
  499. <property>
  500. <name>ozone.scm.http.enabled</name>
  501. <value>true</value>
  502. <description>
  503. Property to enable or disable SCM web ui.
  504. </description>
  505. </property>
  506. <property>
  507. <name>ozone.scm.http-address</name>
  508. <value>0.0.0.0:9876</value>
  509. <description>
  510. The address and the base port where the SCM web ui will listen on.
  511. If the port is 0 then the server will start on a free port.
  512. </description>
  513. </property>
  514. <property>
  515. <name>ozone.scm.http-bind-host</name>
  516. <value>0.0.0.0</value>
  517. <description>
  518. The actual address the SCM web server will bind to. If this optional
  519. address is set, it overrides only the hostname portion of
  520. ozone.scm.http-address.
  521. </description>
  522. </property>
  523. <property>
  524. <name>ozone.scm.https-address</name>
  525. <value>0.0.0.0:9877</value>
  526. <description>
  527. The address and the base port where the SCM web ui will listen on
  528. using HTTPS.
  529. If the port is 0 then the server will start on a free port.
  530. </description>
  531. </property>
  532. <property>
  533. <name>ozone.scm.https-bind-host</name>
  534. <value>0.0.0.0</value>
  535. <description>
  536. The actual address the SCM web server will bind to using HTTPS. If this
  537. optional address is set, it overrides only the hostname portion of
  538. ozone.scm.http-address.
  539. </description>
  540. </property>
  541. <property>
  542. <name>ozone.ksm.http.enabled</name>
  543. <value>true</value>
  544. <description>
  545. Property to enable or disable KSM web ui.
  546. </description>
  547. </property>
  548. <property>
  549. <name>ozone.ksm.http-address</name>
  550. <value>0.0.0.0:9874</value>
  551. <description>
  552. The address and the base port where the KSM web ui will listen on.
  553. If the port is 0 then the server will start on a free port.
  554. </description>
  555. </property>
  556. <property>
  557. <name>ozone.ksm.http-bind-host</name>
  558. <value>0.0.0.0</value>
  559. <description>
  560. The actual address the KSM web server will bind to. If this optional
  561. address is set, it overrides only the hostname portion of
  562. ozone.ksm.http-address.
  563. </description>
  564. </property>
  565. <property>
  566. <name>ozone.ksm.https-address</name>
  567. <value>0.0.0.0:9875</value>
  568. <description>
  569. The address and the base port where the KSM web ui will listen on
  570. using HTTPS.
  571. If the port is 0 then the server will start on a free port.
  572. </description>
  573. </property>
  574. <property>
  575. <name>ozone.ksm.https-bind-host</name>
  576. <value>0.0.0.0</value>
  577. <description>
  578. The actual address the KSM web server will bind to using HTTPS. If this
  579. optional address is set, it overrides only the hostname portion of
  580. ozone.ksm.http-address.
  581. </description>
  582. </property>
  583. <property>
  584. <name>ozone.web.authentication.kerberos.principal</name>
  585. <value></value>
  586. <description>
  587. The server principal used by the SCM and KSM for web UI SPNEGO
  588. authentication when Kerberos security is enabled. This is
  589. typically set to HTTP/_HOST@REALM.TLD The SPNEGO server principal
  590. begins with the prefix HTTP/ by convention.
  591. If the value is '*', the web server will attempt to login with
  592. every principal specified in the keytab file.
  593. </description>
  594. </property>
  595. <property>
  596. <name>ozone.scm.keytab.file</name>
  597. <value></value>
  598. <description>
  599. The keytab file for Kerberos authentication in SCM.
  600. </description>
  601. </property>
  602. <property>
  603. <name>ozone.ksm.keytab.file</name>
  604. <value></value>
  605. <description>
  606. The keytab file for Kerberos authentication in KSM.
  607. </description>
  608. </property>
  609. <property>
  610. <name>ozone.metastore.impl</name>
  611. <value>RocksDB</value>
  612. <description>
  613. Ozone metadata store implementation. Ozone metadata are well distributed
  614. to multiple services such as ksm, scm. They are stored in some local
  615. key-value databases. This property determines which database library to
  616. use. Supported value is either LevelDB or RocksDB.
  617. </description>
  618. </property>
  619. <property>
  620. <name>dfs.cblock.servicerpc-address</name>
  621. <value></value>
  622. <description>
  623. The address that cblock will be bind to, should be a host:port format,
  624. this setting is required for cblock server to start.
  625. This address is used for cblock management operations like create,
  626. delete, info and list volumes
  627. </description>
  628. </property>
  629. <property>
  630. <name>dfs.cblock.service.rpc-bind-host</name>
  631. <value>0.0.0.0</value>
  632. <description>
  633. The actual address the cblock service rpc server will bind to. If this
  634. optional address is set, it overrides only the hostname portion of
  635. dfs.cblock.servicerpc-address.
  636. </description>
  637. </property>
  638. <property>
  639. <name>dfs.cblock.jscsi-address</name>
  640. <value></value>
  641. <description>
  642. The address that cblock will be bind to, should be a host:port format,
  643. this setting is required for cblock server to start.
  644. This address to be used by jscsi to mount volume.
  645. </description>
  646. </property>
  647. <property>
  648. <name>dfs.cblock.jscsi.rpc-bind-host</name>
  649. <value>0.0.0.0</value>
  650. <description>
  651. The actual address the cblock jscsi rpc server will bind to. If this
  652. optional address is set, it overrides only the hostname portion of
  653. dfs.cblock.jscsi-address.
  654. </description>
  655. </property>
  656. <property>
  657. <name>dfs.cblock.jscsi.port</name>
  658. <value>9811</value>
  659. <description>
  660. The port on CBlockManager node for jSCSI to talk to.
  661. </description>
  662. </property>
  663. <property>
  664. <name>dfs.storage.service.handler.count</name>
  665. <value>10</value>
  666. <description>
  667. Default number of handlers for CBlock service rpc.
  668. </description>
  669. </property>
  670. <property>
  671. <name>dfs.cblock.service.leveldb.path</name>
  672. <value>/tmp/cblock_levelDB.dat</value>
  673. <description>
  674. Default path for the cblock meta data disk store.
  675. </description>
  676. </property>
  677. <property>
  678. <name>dfs.cblock.disk.cache.path</name>
  679. <value>/tmp/cblockCacheDB</value>
  680. <description>
  681. Default path for the cblock local cache.
  682. </description>
  683. </property>
  684. <property>
  685. <name>dfs.cblock.trace.io</name>
  686. <value>false</value>
  687. <description>
  688. Default flag for enabling trace io.
  689. </description>
  690. </property>
  691. <property>
  692. <name>dfs.cblock.short.circuit.io</name>
  693. <value>false</value>
  694. <description>
  695. Default flag to enable cblock local cache.
  696. </description>
  697. </property>
  698. <property>
  699. <name>dfs.cblock.cache.cache.size.in.kb</name>
  700. <value>256</value>
  701. <description>
  702. Default cblock cache queue size, in number of kb.
  703. </description>
  704. </property>
  705. <property>
  706. <name>dfs.cblock.cache.core.min.pool.size</name>
  707. <value>16</value>
  708. <description>
  709. Minimum number of thread pool thread that cBlock cache will use for background I/O.
  710. </description>
  711. </property>
  712. <property>
  713. <name>dfs.cblock.cache.max.pool.size</name>
  714. <value>256</value>
  715. <description>
  716. Maximum number of thread pool thread that cBlcok cache will use for background I/O.
  717. </description>
  718. </property>
  719. <property>
  720. <name>dfs.cblock.cache.keep.alive.seconds</name>
  721. <value>60</value>
  722. <description>
  723. Number of seconds to keep the Thread alive when it is idle.
  724. </description>
  725. </property>
  726. <property>
  727. <name>dfs.cblock.cache.thread.priority</name>
  728. <value>5</value>
  729. <description>
  730. Priority of cache flusher thread, affecting the relative
  731. performance of write and read.upported values are 1, 5, 10.
  732. Use 10 for high priority and 1 for low priority.
  733. </description>
  734. </property>
  735. <property>
  736. <name>dfs.cblock.cache.block.buffer.size</name>
  737. <value>512</value>
  738. <description>
  739. Block Buffer size in terms of blockID entries, in number of blockIDs.
  740. </description>
  741. </property>
  742. <property>
  743. <name>dfs.cblock.block.buffer.flush.interval.seconds</name>
  744. <value>60</value>
  745. <description>
  746. The interval to flush cblock buffer in seconds.
  747. </description>
  748. </property>
  749. <property>
  750. <name>dfs.cblock.jscsi.server.address</name>
  751. <value>0.0.0.0</value>
  752. <description>
  753. The address that jscsi server will be running, should have one
  754. local jscsi server for each client that tries to mount cblock.
  755. </description>
  756. </property>
  757. <property>
  758. <name>dfs.cblock.jscsi.cblock.server.address</name>
  759. <value>127.0.0.1</value>
  760. <description>
  761. The address local jscsi server will use to talk to cblock manager.
  762. </description>
  763. </property>
  764. <property>
  765. <name>dfs.cblock.container.size</name>
  766. <value>5</value>
  767. <description>
  768. The size of ozone container in number of GBs. Note that this is
  769. not setting container size for ozone, but rather, this is setting
  770. that assumption that cblock manager will make about ozone.
  771. </description>
  772. </property>
  773. <property>
  774. <name>dfs.cblock.cache.leveldb.cache.size.mb</name>
  775. <value>256</value>
  776. <description>
  777. The size of LevelDB cache file which uses an off-heap cache in LevelDB.
  778. </description>
  779. </property>
  780. <property>
  781. <name>dfs.cblock.cache.max.retry</name>
  782. <value>65536</value>
  783. <description>
  784. The maximum number of retries when writing a block to container.
  785. </description>
  786. </property>
  787. <property>
  788. <name>dfs.cblock.scm.ipaddress</name>
  789. <value>127.0.0.1</value>
  790. <description>
  791. IP address used by cblock to connect to SCM.
  792. </description>
  793. </property>
  794. <property>
  795. <name>dfs.cblock.scm.port</name>
  796. <value>9860</value>
  797. <description>
  798. Port used by cblock to connect to SCM.
  799. </description>
  800. </property>
  801. <property>
  802. <name>ozone.scm.block.size</name>
  803. <value>268435456</value>
  804. <description>
  805. The default size of a scm block in bytes.
  806. </description>
  807. </property>
  808. <property>
  809. <name>dfs.container.ratis.ipc</name>
  810. <value>50012</value>
  811. <description>
  812. The ipc port number of container.
  813. </description>
  814. </property>
  815. <property>
  816. <name>dfs.container.ratis.ipc.random.port</name>
  817. <value>false</value>
  818. <description>
  819. Whether allocates a random free port for ozone ratis port for container.
  820. </description>
  821. </property>
  822. </configuration>