云计算课程实验
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

173 regels
5.4 KiB

4 jaren geleden
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <!--
  3. Licensed under the Apache License, Version 2.0 (the "License");
  4. you may not use this file except in compliance with the License.
  5. You may obtain a copy of the License at
  6. http://www.apache.org/licenses/LICENSE-2.0
  7. Unless required by applicable law or agreed to in writing, software
  8. distributed under the License is distributed on an "AS IS" BASIS,
  9. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  10. See the License for the specific language governing permissions and
  11. limitations under the License.
  12. -->
  13. <configuration>
  14. <!-- KMS Backend KeyProvider -->
  15. <property>
  16. <name>hadoop.kms.key.provider.uri</name>
  17. <value>jceks://file@/${user.home}/kms.keystore</value>
  18. <description>
  19. URI of the backing KeyProvider for the KMS.
  20. </description>
  21. </property>
  22. <property>
  23. <name>hadoop.security.keystore.java-keystore-provider.password-file</name>
  24. <value>kms.keystore.password</value>
  25. <description>
  26. If using the JavaKeyStoreProvider, the file name for the keystore password.
  27. </description>
  28. </property>
  29. <!-- KMS Cache -->
  30. <property>
  31. <name>hadoop.kms.cache.enable</name>
  32. <value>true</value>
  33. <description>
  34. Whether the KMS will act as a cache for the backing KeyProvider.
  35. When the cache is enabled, operations like getKeyVersion, getMetadata,
  36. and getCurrentKey will sometimes return cached data without consulting
  37. the backing KeyProvider. Cached values are flushed when keys are deleted
  38. or modified.
  39. </description>
  40. </property>
  41. <property>
  42. <name>hadoop.kms.cache.timeout.ms</name>
  43. <value>600000</value>
  44. <description>
  45. Expiry time for the KMS key version and key metadata cache, in
  46. milliseconds. This affects getKeyVersion and getMetadata.
  47. </description>
  48. </property>
  49. <property>
  50. <name>hadoop.kms.current.key.cache.timeout.ms</name>
  51. <value>30000</value>
  52. <description>
  53. Expiry time for the KMS current key cache, in milliseconds. This
  54. affects getCurrentKey operations.
  55. </description>
  56. </property>
  57. <!-- KMS Audit -->
  58. <property>
  59. <name>hadoop.kms.audit.aggregation.window.ms</name>
  60. <value>10000</value>
  61. <description>
  62. Duplicate audit log events within the aggregation window (specified in
  63. ms) are quashed to reduce log traffic. A single message for aggregated
  64. events is printed at the end of the window, along with a count of the
  65. number of aggregated events.
  66. </description>
  67. </property>
  68. <!-- KMS Security -->
  69. <property>
  70. <name>hadoop.kms.authentication.type</name>
  71. <value>simple</value>
  72. <description>
  73. Authentication type for the KMS. Can be either &quot;simple&quot;
  74. or &quot;kerberos&quot;.
  75. </description>
  76. </property>
  77. <property>
  78. <name>hadoop.kms.authentication.kerberos.keytab</name>
  79. <value>${user.home}/kms.keytab</value>
  80. <description>
  81. Path to the keytab with credentials for the configured Kerberos principal.
  82. </description>
  83. </property>
  84. <property>
  85. <name>hadoop.kms.authentication.kerberos.principal</name>
  86. <value>HTTP/localhost</value>
  87. <description>
  88. The Kerberos principal to use for the HTTP endpoint.
  89. The principal must start with 'HTTP/' as per the Kerberos HTTP SPNEGO specification.
  90. </description>
  91. </property>
  92. <property>
  93. <name>hadoop.kms.authentication.kerberos.name.rules</name>
  94. <value>DEFAULT</value>
  95. <description>
  96. Rules used to resolve Kerberos principal names.
  97. </description>
  98. </property>
  99. <!-- Authentication cookie signature source -->
  100. <property>
  101. <name>hadoop.kms.authentication.signer.secret.provider</name>
  102. <value>random</value>
  103. <description>
  104. Indicates how the secret to sign the authentication cookies will be
  105. stored. Options are 'random' (default), 'string' and 'zookeeper'.
  106. If using a setup with multiple KMS instances, 'zookeeper' should be used.
  107. </description>
  108. </property>
  109. <!-- Configuration for 'zookeeper' authentication cookie signature source -->
  110. <property>
  111. <name>hadoop.kms.authentication.signer.secret.provider.zookeeper.path</name>
  112. <value>/hadoop-kms/hadoop-auth-signature-secret</value>
  113. <description>
  114. The Zookeeper ZNode path where the KMS instances will store and retrieve
  115. the secret from.
  116. </description>
  117. </property>
  118. <property>
  119. <name>hadoop.kms.authentication.signer.secret.provider.zookeeper.connection.string</name>
  120. <value>#HOSTNAME#:#PORT#,...</value>
  121. <description>
  122. The Zookeeper connection string, a list of hostnames and port comma
  123. separated.
  124. </description>
  125. </property>
  126. <property>
  127. <name>hadoop.kms.authentication.signer.secret.provider.zookeeper.auth.type</name>
  128. <value>none</value>
  129. <description>
  130. The Zookeeper authentication type, 'none' (default) or 'sasl' (Kerberos).
  131. </description>
  132. </property>
  133. <property>
  134. <name>hadoop.kms.authentication.signer.secret.provider.zookeeper.kerberos.keytab</name>
  135. <value>/etc/hadoop/conf/kms.keytab</value>
  136. <description>
  137. The absolute path for the Kerberos keytab with the credentials to
  138. connect to Zookeeper.
  139. </description>
  140. </property>
  141. <property>
  142. <name>hadoop.kms.authentication.signer.secret.provider.zookeeper.kerberos.principal</name>
  143. <value>kms/#HOSTNAME#</value>
  144. <description>
  145. The Kerberos service principal used to connect to Zookeeper.
  146. </description>
  147. </property>
  148. </configuration>