http://git-wip-us.apache.org/repos/asf/ambari/blob/3148759f/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HBASE/configuration/hbase-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HBASE/configuration/hbase-site.xml b/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HBASE/configuration/hbase-site.xml index 4d3ef22..39481d7 100644 --- a/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HBASE/configuration/hbase-site.xml +++ b/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HBASE/configuration/hbase-site.xml @@ -22,7 +22,7 @@ <configuration> <property> <name>hbase.rootdir</name> - <value/> + <value></value> <description>The directory shared by region servers and into which HBase persists. The URL should be 'fully-qualified' to include the filesystem scheme. For example, to specify the @@ -32,8 +32,6 @@ into /tmp. Change this configuration else all data will be lost on machine restart. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.cluster.distributed</name> @@ -43,70 +41,54 @@ false, startup will run all HBase and ZooKeeper daemons together in the one JVM. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.tmp.dir</name> - <value/> + <value></value> <description>Temporary directory on the local filesystem. Change this setting to point to a location more permanent than '/tmp' (The '/tmp' directory is often cleared on machine restart). </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.master.info.bindAddress</name> - <value/> + <value></value> <description>The bind address for the HBase Master web UI </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.master.info.port</name> - <value/> + <value></value> <description>The port for the HBase Master web UI.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.regionserver.info.port</name> - <value/> + <value></value> <description>The port for the HBase RegionServer web UI.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.regionserver.global.memstore.upperLimit</name> - <value/> + <value></value> <description>Maximum size of all memstores in a region server before new updates are blocked and flushes are forced. Defaults to 40% of heap </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.regionserver.handler.count</name> - <value/> + <value></value> <description>Count of RPC Listener instances spun up on RegionServers. Same property is used by the Master for count of master handlers. Default is 10. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.hregion.majorcompaction</name> - <value/> + <value></value> <description>The time (in miliseconds) between 'major' compactions of all HStoreFiles in a region. Default: 1 day. Set to 0 to disable automated major compactions. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.master.lease.thread.wakefrequency</name> @@ -115,24 +97,20 @@ This value has been reduced due to the other reduced values above so that the master will notice a dead region server sooner. The default is 15 seconds. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.regionserver.global.memstore.lowerLimit</name> - <value/> + <value></value> <description>When memstores are being forced to flush to make room in memory, keep flushing until we hit this mark. Defaults to 35% of heap. This value equal to hbase.regionserver.global.memstore.upperLimit causes the minimum possible flushing to occur when updates are blocked due to memstore limiting. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.hregion.memstore.block.multiplier</name> - <value/> + <value></value> <description>Block updates if memstore has hbase.hregion.memstore.block.multiplier time hbase.hregion.flush.size bytes. Useful preventing runaway memstore during spikes in update traffic. Without an @@ -140,46 +118,38 @@ resultant flush files take a long time to compact or split, or worse, we OOME </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.hregion.memstore.flush.size</name> - <value/> + <value></value> <description> Memstore will be flushed to disk if size of the memstore exceeds this number of bytes. Value is checked by a thread that runs every hbase.server.thread.wakefrequency. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.hregion.memstore.mslab.enabled</name> - <value/> + <value></value> <description> Enables the MemStore-Local Allocation Buffer, a feature which works to prevent heap fragmentation under heavy write loads. This can reduce the frequency of stop-the-world GC pauses on large heaps. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.hregion.max.filesize</name> - <value/> + <value></value> <description> Maximum HStoreFile size. If any one of a column families' HStoreFiles has grown to exceed this value, the hosting HRegion is split in two. Default: 1G. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.client.scanner.caching</name> - <value/> + <value></value> <description>Number of rows that will be fetched when calling next on a scanner if it is not served from (local, client) memory. Higher caching values will enable faster scanners but will eat up more memory @@ -187,12 +157,10 @@ Do not set this value such that the time between invocations is greater than the scanner timeout; i.e. hbase.regionserver.lease.period </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>zookeeper.session.timeout</name> - <value/> + <value></value> <description>ZooKeeper session timeout. HBase passes this to the zk quorum as suggested maximum time for a session (This setting becomes zookeeper's 'maxSessionTimeout'). See @@ -200,12 +168,10 @@ "The client sends a requested timeout, the server responds with the timeout that it can give the client. " In milliseconds. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.client.keyvalue.maxsize</name> - <value/> + <value></value> <description>Specifies the combined maximum allowed size of a KeyValue instance. This is to set an upper boundary for a single entry saved in a storage file. Since they cannot be split it helps avoiding that a region @@ -213,80 +179,67 @@ to set this to a fraction of the maximum region size. Setting it to zero or less disables the check. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.hstore.compactionThreshold</name> - <value/> + <value></value> <description> If more than this number of HStoreFiles in any one HStore (one HStoreFile is written per flush of memstore) then a compaction is run to rewrite all HStoreFiles files as one. Larger numbers put off compaction but when it runs, it takes longer to complete. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.hstore.blockingStoreFiles</name> - <value/> + <value></value> <description> If more than this number of StoreFiles in any one Store (one StoreFile is written per flush of MemStore) then updates are blocked for this HRegion until a compaction is completed, or until hbase.hstore.blockingWaitTime has been exceeded. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hfile.block.cache.size</name> - <value/> + <value></value> <description> Percentage of maximum heap (-Xmx setting) to allocate to block cache used by HFile/StoreFile. Default of 0.25 means allocate 25%. Set to 0 to disable but it's not recommended. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <!-- The following properties configure authentication information for HBase processes when using Kerberos security. There are no default values, included here for documentation purposes --> <property> <name>hbase.master.keytab.file</name> - <value/> + <value></value> <description>Full path to the kerberos keytab file to use for logging in the configured HMaster server principal. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.master.kerberos.principal</name> - <value/> + <value></value> <description>Ex. "hbase/_h...@example.com". The kerberos principal name that should be used to run the HMaster process. The principal name should be in the form: user/hostname@DOMAIN. If "_HOST" is used as the hostname portion, it will be replaced with the actual hostname of the running instance. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.regionserver.keytab.file</name> - <value/> + <value></value> <description>Full path to the kerberos keytab file to use for logging in the configured HRegionServer server principal. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.regionserver.kerberos.principal</name> - <value/> + <value></value> <description>Ex. "hbase/_h...@example.com". The kerberos principal name that should be used to run the HRegionServer process. The principal name should be in the form: user/hostname@DOMAIN. If "_HOST" is used as the @@ -294,9 +247,8 @@ running instance. An entry for this principal must exist in the file specified in hbase.regionserver.keytab.file </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <!-- Additional configuration specific to HBase security --> <property> <name>hbase.superuser</name> @@ -305,24 +257,22 @@ full privileges, regardless of stored ACLs, across the cluster. Only used when HBase security is enabled. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>hbase.coprocessor.region.classes</name> - <value/> + <value></value> <description>A comma-separated list of Coprocessors that are loaded by default on all tables. For any override coprocessor method, these classes will be called in order. After implementing your own Coprocessor, just put it in HBase's classpath and add the fully qualified class name here. A coprocessor can also be loaded on demand by setting HTableDescriptor. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>hbase.coprocessor.master.classes</name> - <value/> + <value></value> <description>A comma-separated list of org.apache.hadoop.hbase.coprocessor.MasterObserver coprocessors that are loaded by default on the active HMaster process. For any implemented @@ -330,25 +280,23 @@ implementing your own MasterObserver, just put it in HBase's classpath and add the fully qualified class name here. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>hbase.zookeeper.property.clientPort</name> <value>2181</value> <description>Property from ZooKeeper's config zoo.cfg. The port at which the clients will connect. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <!-- The following three properties are used together to create the list of host:peer_port:leader_port quorum servers for ZooKeeper. --> <property> <name>hbase.zookeeper.quorum</name> - <value/> + <value></value> <description>Comma separated list of servers in the ZooKeeper Quorum. For example, "host1.mydomain.com,host2.mydomain.com,host3.mydomain.com". By default this is set to localhost for local and pseudo-distributed modes @@ -356,38 +304,34 @@ list of ZooKeeper quorum servers. If HBASE_MANAGES_ZK is set in hbase-env.sh this is the list of servers which we will start/stop ZooKeeper on. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <!-- End of properties used to generate ZooKeeper host:port quorum list. --> + <property> <name>dfs.support.append</name> - <value/> + <value></value> <description>Does HDFS allow appends to files? This is an hdfs config. set in here so the hdfs client will do append support. You must ensure that this config. is true serverside too when running hbase (You will have to restart your cluster after setting it). </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.client.read.shortcircuit</name> - <value/> + <value></value> <description>Enable/Disable short circuit read for your client. Hadoop servers should be configured to allow short circuit read for the hbase user for this to take effect </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.client.read.shortcircuit.skip.checksum</name> - <value/> + <value></value> <description>Enable/disbale skipping the checksum check</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>hbase.regionserver.optionalcacheflushinterval</name> <value>10000</value> @@ -395,7 +339,6 @@ Amount of time to wait since the last time a region was flushed before invoking an optional cache flush. Default 60,000. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + </configuration>
http://git-wip-us.apache.org/repos/asf/ambari/blob/3148759f/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HDFS/configuration/core-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HDFS/configuration/core-site.xml b/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HDFS/configuration/core-site.xml index 07cb6f5..561ea6b 100644 --- a/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HDFS/configuration/core-site.xml +++ b/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HDFS/configuration/core-site.xml @@ -1,6 +1,7 @@ <?xml version="1.0"?> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?> -<!-- + + <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. @@ -16,9 +17,13 @@ See the License for the specific language governing permissions and limitations under the License. --> + <!-- Put site-specific property overrides in this file. --> + <configuration xmlns:xi="http://www.w3.org/2001/XInclude";> - <!-- i/o properties --> + +<!-- i/o properties --> + <property> <name>io.file.buffer.size</name> <value>131072</value> @@ -26,61 +31,55 @@ The size of this buffer should probably be a multiple of hardware page size (4096 on Intel x86), and it determines how much data is buffered during read and write operations.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>io.serializations</name> <value>org.apache.hadoop.io.serializer.WritableSerialization</value> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>io.compression.codecs</name> - <value/> + <value></value> <description>A list of the compression codec classes that can be used for compression/decompression.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>io.compression.codec.lzo.class</name> <value>com.hadoop.compression.lzo.LzoCodec</value> <description>The implementation for lzo codec.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <!-- file system properties --> + +<!-- file system properties --> + <property> <name>fs.default.name</name> <!-- cluster variant --> - <value/> + <value></value> <description>The name of the default file system. Either the literal string "local" or a host:port for HDFS.</description> <final>true</final> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>fs.trash.interval</name> <value>360</value> <description>Number of minutes between trash checkpoints. If zero, the trash feature is disabled. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>fs.checkpoint.dir</name> - <value/> + <value></value> <description>Determines where on the local filesystem the DFS secondary name node should store the temporary images to merge. If this is a comma-delimited list of directories then the image is replicated in all of the directories for redundancy. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>fs.checkpoint.edits.dir</name> <value>${fs.checkpoint.dir}</value> @@ -90,26 +89,23 @@ replicated in all of the directoires for redundancy. Default value is same as fs.checkpoint.dir </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>fs.checkpoint.period</name> <value>21600</value> <description>The number of seconds between two periodic checkpoints. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>fs.checkpoint.size</name> <value>536870912</value> <description>The size of the current edit log (in bytes) that triggers a periodic checkpoint even if the fs.checkpoint.period hasn't expired. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <!-- ipc properties: copied from kryptonite configuration --> <property> <name>ipc.client.idlethreshold</name> @@ -117,25 +113,22 @@ <description>Defines the threshold number of connections after which connections will be inspected for idleness. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>ipc.client.connection.maxidletime</name> <value>30000</value> <description>The maximum time after which a client will bring down the connection to the server. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>ipc.client.connect.max.retries</name> <value>50</value> <description>Defines the maximum number of retries for IPC connections.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <!-- Web Interface Configuration --> <property> <name>webinterface.private.actions</name> @@ -145,32 +138,28 @@ not be exposed to public. Enable this option if the interfaces are only reachable by those who have the right authorization. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> - <name>hadoop.security.authentication</name> - <value/> - <description> + + <property> + <name>hadoop.security.authentication</name> + <value></value> + <description> Set the authentication for the cluster. Valid values are: simple or kerberos. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>hadoop.security.authorization</name> - <value/> - <description> + </property> +<property> + <name>hadoop.security.authorization</name> + <value></value> + <description> Enable authorization for different protocols. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> +</property> + <property> <name>hadoop.security.auth_to_local</name> - <value/> - <description>The mapping from kerberos principal names to local OS user names. + <value></value> +<description>The mapping from kerberos principal names to local OS user names. So the default rule is just "DEFAULT" which takes all principals in your default domain to their first component. "omal...@apache.org" and "omalley/ad...@apache.org" to "omalley", if your default domain is APACHE.ORG. The translations rules have 3 sections: @@ -208,10 +197,9 @@ If you want to treat all principals from APACHE.ORG with /admin as "admin", your RULE[2:$1%$2@$0](.%ad...@apache.org)s/./admin/ DEFAULT </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <!-- + +<!-- <property> <name>hadoop.proxyuser.scope.function_hdp_user("hcat_user").groups</name> <value></value> http://git-wip-us.apache.org/repos/asf/ambari/blob/3148759f/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HDFS/configuration/hadoop-policy.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HDFS/configuration/hadoop-policy.xml b/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HDFS/configuration/hadoop-policy.xml index 57b10c8..900da99 100644 --- a/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HDFS/configuration/hadoop-policy.xml +++ b/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HDFS/configuration/hadoop-policy.xml @@ -1,5 +1,6 @@ <?xml version="1.0"?> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?> + <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -16,7 +17,9 @@ See the License for the specific language governing permissions and limitations under the License. --> + <!-- Put site-specific property overrides in this file. --> + <configuration> <property> <name>security.client.protocol.acl</name> @@ -26,9 +29,8 @@ The ACL is a comma-separated list of user and group names. The user and group list is separated by a blank. For e.g. "alice,bob users,wheel". A special value of "*" means all users are allowed.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>security.client.datanode.protocol.acl</name> <value>*</value> @@ -37,9 +39,8 @@ The ACL is a comma-separated list of user and group names. The user and group list is separated by a blank. For e.g. "alice,bob users,wheel". A special value of "*" means all users are allowed.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>security.datanode.protocol.acl</name> <value>*</value> @@ -48,9 +49,8 @@ The ACL is a comma-separated list of user and group names. The user and group list is separated by a blank. For e.g. "alice,bob users,wheel". A special value of "*" means all users are allowed.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>security.inter.datanode.protocol.acl</name> <value>*</value> @@ -59,9 +59,8 @@ The ACL is a comma-separated list of user and group names. The user and group list is separated by a blank. For e.g. "alice,bob users,wheel". A special value of "*" means all users are allowed.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>security.namenode.protocol.acl</name> <value>*</value> @@ -70,9 +69,8 @@ The ACL is a comma-separated list of user and group names. The user and group list is separated by a blank. For e.g. "alice,bob users,wheel". A special value of "*" means all users are allowed.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>security.inter.tracker.protocol.acl</name> <value>*</value> @@ -81,9 +79,8 @@ The ACL is a comma-separated list of user and group names. The user and group list is separated by a blank. For e.g. "alice,bob users,wheel". A special value of "*" means all users are allowed.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>security.job.submission.protocol.acl</name> <value>*</value> @@ -92,9 +89,8 @@ The ACL is a comma-separated list of user and group names. The user and group list is separated by a blank. For e.g. "alice,bob users,wheel". A special value of "*" means all users are allowed.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>security.task.umbilical.protocol.acl</name> <value>*</value> @@ -103,39 +99,36 @@ The ACL is a comma-separated list of user and group names. The user and group list is separated by a blank. For e.g. "alice,bob users,wheel". A special value of "*" means all users are allowed.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + + <property> <name>security.admin.operations.protocol.acl</name> - <value/> + <value></value> <description>ACL for AdminOperationsProtocol. Used for admin commands. The ACL is a comma-separated list of user and group names. The user and group list is separated by a blank. For e.g. "alice,bob users,wheel". A special value of "*" means all users are allowed.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>security.refresh.usertogroups.mappings.protocol.acl</name> - <value/> + <value></value> <description>ACL for RefreshUserMappingsProtocol. Used to refresh users mappings. The ACL is a comma-separated list of user and group names. The user and group list is separated by a blank. For e.g. "alice,bob users,wheel". A special value of "*" means all users are allowed.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + +<property> <name>security.refresh.policy.protocol.acl</name> - <value/> + <value></value> <description>ACL for RefreshAuthorizationPolicyProtocol, used by the dfsadmin and mradmin commands to refresh the security policy in-effect. The ACL is a comma-separated list of user and group names. The user and group list is separated by a blank. For e.g. "alice,bob users,wheel". A special value of "*" means all users are allowed.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + + </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/3148759f/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HDFS/configuration/hdfs-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HDFS/configuration/hdfs-site.xml b/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HDFS/configuration/hdfs-site.xml index 6ef39b8..3918bc1 100644 --- a/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HDFS/configuration/hdfs-site.xml +++ b/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HDFS/configuration/hdfs-site.xml @@ -1,5 +1,6 @@ <?xml version="1.0"?> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?> + <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -16,65 +17,63 @@ See the License for the specific language governing permissions and limitations under the License. --> + <!-- Put site-specific property overrides in this file. --> + <configuration> - <!-- file system properties --> + +<!-- file system properties --> + <property> <name>dfs.name.dir</name> <!-- cluster variant --> - <value/> + <value></value> <description>Determines where on the local filesystem the DFS name node should store the name table. If this is a comma-delimited list of directories then the name table is replicated in all of the directories, for redundancy. </description> <final>true</final> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.support.append</name> - <value/> + <value></value> <description>to enable dfs append</description> <final>true</final> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.webhdfs.enabled</name> - <value/> + <value></value> <description>to enable webhdfs</description> <final>true</final> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + + <property> <name>dfs.datanode.socket.write.timeout</name> <value>0</value> <description>DFS Client write socket timeout</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.datanode.failed.volumes.tolerated</name> - <value/> + <value></value> <description>#of failed disks dn would tolerate</description> <final>true</final> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.block.local-path-access.user</name> - <value/> + <value></value> <description>the user who is allowed to perform short circuit reads. </description> <final>true</final> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.data.dir</name> - <value/> + <value></value> <description>Determines where on the local filesystem an DFS data node should store its blocks. If this is a comma-delimited list of directories, then data will be stored in all named @@ -82,52 +81,46 @@ Directories that do not exist are ignored. </description> <final>true</final> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.hosts.exclude</name> - <value/> + <value></value> <description>Names a file that contains a list of hosts that are not permitted to connect to the namenode. The full pathname of the file must be specified. If the value is empty, no hosts are excluded.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.hosts</name> - <value/> + <value></value> <description>Names a file that contains a list of hosts that are permitted to connect to the namenode. The full pathname of the file must be specified. If the value is empty, all hosts are permitted.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.replication.max</name> <value>50</value> <description>Maximal block replication. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.replication</name> - <value/> + <value></value> <description>Default block replication. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.heartbeat.interval</name> <value>3</value> <description>Determines datanode heartbeat interval in seconds.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.safemode.threshold.pct</name> <value>1.0f</value> @@ -137,9 +130,8 @@ Values less than or equal to 0 mean not to start in safe mode. Values greater than 1 will make safe mode permanent. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.balance.bandwidthPerSec</name> <value>6250000</value> @@ -148,300 +140,269 @@ can utilize for the balancing purpose in term of the number of bytes per second. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.datanode.address</name> - <value/> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> + <value></value> </property> + <property> <name>dfs.datanode.http.address</name> - <value/> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> + <value></value> </property> + <property> <name>dfs.block.size</name> <value>134217728</value> <description>The default block size for new files.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.http.address</name> - <value/> - <description>The name of the default file system. Either the + <value></value> +<description>The name of the default file system. Either the literal string "local" or a host:port for HDFS.</description> - <final>true</final> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>dfs.datanode.du.reserved</name> - <!-- cluster variant --> - <value/> - <description>Reserved space in bytes per volume. Always leave this much space free for non dfs use. +<final>true</final> +</property> + +<property> +<name>dfs.datanode.du.reserved</name> +<!-- cluster variant --> +<value></value> +<description>Reserved space in bytes per volume. Always leave this much space free for non dfs use. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>dfs.datanode.ipc.address</name> - <value>0.0.0.0:8010</value> - <description> +</property> + +<property> +<name>dfs.datanode.ipc.address</name> +<value>0.0.0.0:8010</value> +<description> The datanode ipc server address and port. If the port is 0 then the server will start on a free port. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>dfs.blockreport.initialDelay</name> - <value>120</value> - <description>Delay for first block report in seconds.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>dfs.namenode.handler.count</name> - <value>40</value> - <description>The number of server threads for the namenode.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>dfs.datanode.max.xcievers</name> - <value>4096</value> - <description>PRIVATE CONFIG VARIABLE</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <!-- Permissions configuration --> - <property> - <name>dfs.umaskmode</name> - <value>077</value> - <description> +</property> + +<property> +<name>dfs.blockreport.initialDelay</name> +<value>120</value> +<description>Delay for first block report in seconds.</description> +</property> + +<property> +<name>dfs.namenode.handler.count</name> +<value>40</value> +<description>The number of server threads for the namenode.</description> +</property> + +<property> +<name>dfs.datanode.max.xcievers</name> +<value>4096</value> +<description>PRIVATE CONFIG VARIABLE</description> +</property> + +<!-- Permissions configuration --> + +<property> +<name>dfs.umaskmode</name> +<value>077</value> +<description> The octal umask used when creating files and directories. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>dfs.web.ugi</name> - <!-- cluster variant --> - <value>gopher,gopher</value> - <description>The user account used by the web interface. +</property> + +<property> +<name>dfs.web.ugi</name> +<!-- cluster variant --> +<value>gopher,gopher</value> +<description>The user account used by the web interface. Syntax: USERNAME,GROUP1,GROUP2, ... </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>dfs.permissions</name> - <value>true</value> - <description> +</property> + +<property> +<name>dfs.permissions</name> +<value>true</value> +<description> If "true", enable permission checking in HDFS. If "false", permission checking is turned off, but all other behavior is unchanged. Switching from one parameter value to the other does not change the mode, owner or group of files or directories. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>dfs.permissions.supergroup</name> - <value>hdfs</value> - <description>The name of the group of super-users.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>dfs.namenode.handler.count</name> - <value>100</value> - <description>Added to grow Queue size so that more client connections are allowed</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>ipc.server.max.response.size</name> - <value>5242880</value> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>dfs.block.access.token.enable</name> - <value>true</value> - <description> +</property> + +<property> +<name>dfs.permissions.supergroup</name> +<value>hdfs</value> +<description>The name of the group of super-users.</description> +</property> + +<property> +<name>dfs.namenode.handler.count</name> +<value>100</value> +<description>Added to grow Queue size so that more client connections are allowed</description> +</property> + +<property> +<name>ipc.server.max.response.size</name> +<value>5242880</value> +</property> +<property> +<name>dfs.block.access.token.enable</name> +<value>true</value> +<description> If "true", access tokens are used as capabilities for accessing datanodes. If "false", no access tokens are checked on accessing datanodes. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>dfs.namenode.kerberos.principal</name> - <value/> - <description> +</property> + +<property> +<name>dfs.namenode.kerberos.principal</name> +<value></value> +<description> Kerberos principal name for the NameNode </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>dfs.secondary.namenode.kerberos.principal</name> - <value/> +</property> + +<property> +<name>dfs.secondary.namenode.kerberos.principal</name> +<value></value> <description> Kerberos principal name for the secondary NameNode. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <!-- + + +<!-- This is KRB DOMAIN specific. The FQDN of the namenode has to be mentioned. --> <property> <name>dfs.namenode.kerberos.https.principal</name> - <value/> - <description>The Kerberos principal for the host that the NameNode runs on.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> + <value></value> + <description>The Kerberos principal for the host that the NameNode runs on.</description> + </property> + <property> <name>dfs.secondary.namenode.kerberos.https.principal</name> - <value/> + <value></value> <description>The Kerberos principal for the hostthat the secondary NameNode runs on.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> + </property> + <property> <!-- cluster variant --> <name>dfs.secondary.http.address</name> - <value/> + <value></value> <description>Address of secondary namenode web server</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.secondary.https.port</name> <value>50490</value> <description>The https port where secondary-namenode binds</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.web.authentication.kerberos.principal</name> - <value/> + <value></value> <description> The HTTP Kerberos principal used by Hadoop-Auth in the HTTP endpoint. The HTTP Kerberos principal MUST start with 'HTTP/' per Kerberos HTTP SPENGO specification. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.web.authentication.kerberos.keytab</name> - <value/> + <value></value> <description> The Kerberos keytab file with the credentials for the HTTP Kerberos principal used by Hadoop-Auth in the HTTP endpoint. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.datanode.kerberos.principal</name> - <value/> - <description> + <value></value> + <description> The Kerberos principal that the DataNode runs as. "_HOST" is replaced by the real host name. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.namenode.keytab.file</name> - <value/> - <description> + <value></value> + <description> Combined keytab file containing the namenode service and host principals. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.secondary.namenode.keytab.file</name> - <value/> - <description> + <value></value> + <description> Combined keytab file containing the namenode service and host principals. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.datanode.keytab.file</name> - <value/> - <description> + <value></value> + <description> The filename of the keytab file for the DataNode. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.https.port</name> <value>50470</value> - <description>The https port where namenode binds</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> + <description>The https port where namenode binds</description> + </property> + <property> <name>dfs.https.address</name> - <value/> - <description>The https address where namenode binds</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> + <value></value> + <description>The https address where namenode binds</description> + </property> + <property> <name>dfs.datanode.data.dir.perm</name> - <value/> - <description>The permissions that should be there on dfs.data.dir + <value></value> +<description>The permissions that should be there on dfs.data.dir directories. The datanode will not come up if the permissions are different on existing dfs.data.dir directories. If the directories don't exist, they will be created with this permission.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> - <name>dfs.access.time.precision</name> - <value>0</value> - <description>The access time for HDFS file is precise up to this value. + <name>dfs.access.time.precision</name> + <value>0</value> + <description>The access time for HDFS file is precise up to this value. The default value is 1 hour. Setting a value of 0 disables access times for HDFS. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>dfs.cluster.administrators</name> - <value> hdfs</value> - <description>ACL for who all can view the default servlets in the HDFS</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>ipc.server.read.threadpool.size</name> - <value>5</value> - <description/> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>dfs.datanode.failed.volumes.tolerated</name> - <value>0</value> - <description>Number of failed disks datanode would tolerate</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> +</property> + +<property> + <name>dfs.cluster.administrators</name> + <value> hdfs</value> + <description>ACL for who all can view the default servlets in the HDFS</description> +</property> + +<property> + <name>ipc.server.read.threadpool.size</name> + <value>5</value> + <description></description> +</property> + +<property> + <name>dfs.datanode.failed.volumes.tolerated</name> + <value>0</value> + <description>Number of failed disks datanode would tolerate</description> +</property> + </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/3148759f/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HIVE/configuration/hive-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HIVE/configuration/hive-site.xml b/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HIVE/configuration/hive-site.xml index c20372a..1113ef6 100644 --- a/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HIVE/configuration/hive-site.xml +++ b/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/HIVE/configuration/hive-site.xml @@ -16,134 +16,117 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> + <configuration> <property> <name>hive.metastore.local</name> <value>false</value> <description>controls whether to connect to remove metastore server or open a new metastore server in Hive Client JVM</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>javax.jdo.option.ConnectionURL</name> - <value/> + <value></value> <description>JDBC connect string for a JDBC metastore</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>javax.jdo.option.ConnectionDriverName</name> <value>com.mysql.jdbc.Driver</value> <description>Driver class name for a JDBC metastore</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>javax.jdo.option.ConnectionUserName</name> - <value/> + <value></value> <description>username to use against metastore database</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>javax.jdo.option.ConnectionPassword</name> - <value/> + <value></value> <description>password to use against metastore database</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>hive.metastore.warehouse.dir</name> <value>/apps/hive/warehouse</value> <description>location of default database for the warehouse</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>hive.metastore.sasl.enabled</name> - <value/> + <value></value> <description>If true, the metastore thrift interface will be secured with SASL. Clients must authenticate with Kerberos.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>hive.metastore.kerberos.keytab.file</name> - <value/> + <value></value> <description>The path to the Kerberos Keytab file containing the metastore thrift server's service principal.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>hive.metastore.kerberos.principal</name> - <value/> + <value></value> <description>The service principal for the metastore thrift server. The special string _HOST will be replaced automatically with the correct host name.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>hive.metastore.cache.pinobjtypes</name> <value>Table,Database,Type,FieldSchema,Order</value> <description>List of comma separated metastore object types that should be pinned in the cache</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>hive.metastore.uris</name> - <value/> + <value></value> <description>URI for client to contact metastore server</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>hadoop.clientside.fs.operations</name> <value>true</value> <description>FS operations are owned by client</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>hive.metastore.client.socket.timeout</name> <value>60</value> <description>MetaStore Client socket timeout in seconds</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>hive.metastore.execute.setugi</name> <value>true</value> <description>In unsecure mode, setting this property to true will cause the metastore to execute DFS operations using the client's reported user and group permissions. Note that this property must be set on both the client and server sides. Further note that its best effort. If client sets its to true and server sets it to false, client setting will be ignored.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>hive.security.authorization.enabled</name> <value>true</value> <description>enable or disable the hive client authorization</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>hive.security.authorization.manager</name> <value>org.apache.hcatalog.security.HdfsAuthorizationProvider</value> <description>the hive client authorization manager class name. The user defined authorization class should implement interface org.apache.hadoop.hive.ql.security.authorization.HiveAuthorizationProvider. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>hive.server2.enable.doAs</name> <value>true</value> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>fs.hdfs.impl.disable.cache</name> <value>true</value> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/3148759f/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/MAPREDUCE/configuration/capacity-scheduler.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/MAPREDUCE/configuration/capacity-scheduler.xml b/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/MAPREDUCE/configuration/capacity-scheduler.xml index 5b270c2..8034d19 100644 --- a/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/MAPREDUCE/configuration/capacity-scheduler.xml +++ b/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/MAPREDUCE/configuration/capacity-scheduler.xml @@ -1,4 +1,5 @@ <?xml version="1.0"?> + <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -15,29 +16,30 @@ See the License for the specific language governing permissions and limitations under the License. --> + <!-- This is the configuration file for the resource manager in Hadoop. --> <!-- You can configure various scheduling parameters related to queues. --> <!-- The properties for a queue follow a naming convention,such as, --> <!-- mapred.capacity-scheduler.queue.<queue-name>.property-name. --> + <configuration> + <property> <name>mapred.capacity-scheduler.maximum-system-jobs</name> <value>3000</value> <description>Maximum number of jobs in the system which can be initialized, concurrently, by the CapacityScheduler. - </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> + </description> </property> + <property> <name>mapred.capacity-scheduler.queue.default.capacity</name> <value>100</value> <description>Percentage of the number of slots in the cluster that are to be available for jobs in this queue. - </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> + </description> </property> + <property> <name>mapred.capacity-scheduler.queue.default.maximum-capacity</name> <value>-1</value> @@ -54,19 +56,17 @@ One important thing to note is that maximum-capacity is a percentage , so based on the cluster's capacity the max capacity would change. So if large no of nodes or racks get added to the cluster , max Capacity in absolute terms would increase accordingly. - </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> + </description> </property> + <property> <name>mapred.capacity-scheduler.queue.default.supports-priority</name> <value>false</value> <description>If true, priorities of jobs will be taken into account in scheduling decisions. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.capacity-scheduler.queue.default.minimum-user-limit-percent</name> <value>100</value> @@ -81,18 +81,16 @@ or more users, no user can use more than 25% of the queue's resources. A value of 100 implies no user limits are imposed. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.capacity-scheduler.queue.default.user-limit-factor</name> <value>1</value> <description>The multiple of the queue capacity which can be configured to allow a single user to acquire more slots. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.capacity-scheduler.queue.default.maximum-initialized-active-tasks</name> <value>200000</value> @@ -100,9 +98,8 @@ which can be initialized concurrently. Once the queue's jobs exceed this limit they will be queued on disk. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.capacity-scheduler.queue.default.maximum-initialized-active-tasks-per-user</name> <value>100000</value> @@ -110,18 +107,16 @@ user's jobs in the queue, which can be initialized concurrently. Once the user's jobs exceed this limit they will be queued on disk. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.capacity-scheduler.queue.default.init-accept-jobs-factor</name> <value>10</value> <description>The multipe of (maximum-system-jobs * queue-capacity) used to determine the number of jobs which are accepted by the scheduler. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <!-- The default configuration settings for the capacity task scheduler --> <!-- The default values would be applied to all the queues which don't have --> <!-- the appropriate property for the particular queue --> @@ -131,27 +126,25 @@ <description>If true, priorities of jobs will be taken into account in scheduling decisions by default in a job queue. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.capacity-scheduler.default-minimum-user-limit-percent</name> <value>100</value> <description>The percentage of the resources limited to a particular user for the job queue at any given point of time by default. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + + <property> <name>mapred.capacity-scheduler.default-user-limit-factor</name> <value>1</value> <description>The default multiple of queue-capacity which is used to determine the amount of slots a single user can consume concurrently. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.capacity-scheduler.default-maximum-active-tasks-per-queue</name> <value>200000</value> @@ -159,9 +152,8 @@ queue, which can be initialized concurrently. Once the queue's jobs exceed this limit they will be queued on disk. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.capacity-scheduler.default-maximum-active-tasks-per-user</name> <value>100000</value> @@ -169,18 +161,16 @@ the user's jobs in the queue, which can be initialized concurrently. Once the user's jobs exceed this limit they will be queued on disk. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.capacity-scheduler.default-init-accept-jobs-factor</name> <value>10</value> <description>The default multipe of (maximum-system-jobs * queue-capacity) used to determine the number of jobs which are accepted by the scheduler. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <!-- Capacity scheduler Job Initialization configuration parameters --> <property> <name>mapred.capacity-scheduler.init-poll-interval</name> @@ -188,8 +178,6 @@ <description>The amount of time in miliseconds which is used to poll the job queues for jobs to initialize. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>mapred.capacity-scheduler.init-worker-threads</name> @@ -202,7 +190,6 @@ is greater then number of threads would be equal to number of job queues. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/3148759f/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/MAPREDUCE/configuration/mapred-queue-acls.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/MAPREDUCE/configuration/mapred-queue-acls.xml b/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/MAPREDUCE/configuration/mapred-queue-acls.xml index 2b6307e..ce12380 100644 --- a/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/MAPREDUCE/configuration/mapred-queue-acls.xml +++ b/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/MAPREDUCE/configuration/mapred-queue-acls.xml @@ -1,5 +1,6 @@ <?xml version="1.0"?> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?> + <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -16,20 +17,23 @@ See the License for the specific language governing permissions and limitations under the License. --> + <!-- mapred-queue-acls.xml --> <configuration> - <!-- queue default --> + + +<!-- queue default --> + <property> <name>mapred.queue.default.acl-submit-job</name> <value>*</value> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.queue.default.acl-administer-jobs</name> <value>*</value> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <!-- END ACLs --> + </configuration>
