http://git-wip-us.apache.org/repos/asf/ambari/blob/1d31dcfc/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/HDFS/configuration/hdfs-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/HDFS/configuration/hdfs-site.xml b/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/HDFS/configuration/hdfs-site.xml index 5910895..3590b77 100644 --- a/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/HDFS/configuration/hdfs-site.xml +++ b/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/HDFS/configuration/hdfs-site.xml @@ -28,21 +28,21 @@ of directories then the name table is replicated in all of the directories, for redundancy. </description> <final>true</final> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.support.append</name> <value>true</value> <description>to enable dfs append</description> <final>true</final> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.webhdfs.enabled</name> <value>true</value> <description>to enable webhdfs</description> <final>true</final> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <!-- <property> @@ -56,7 +56,7 @@ <value>0</value> <description>#of failed disks dn would tolerate</description> <final>true</final> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.block.local-path-access.user</name> @@ -65,7 +65,7 @@ circuit reads. </description> <final>true</final> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.data.dir</name> @@ -77,7 +77,7 @@ Directories that do not exist are ignored. </description> <final>true</final> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.hosts.exclude</name> @@ -86,7 +86,7 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <!-- <property> @@ -105,33 +105,33 @@ compatibility, it is being set to CRC32. Once all migration steps are complete, we can change it to CRC32C and take advantage of the additional performance benefit.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.replication.max</name> <value>50</value> <description>Maximal block replication. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.replication</name> <value>3</value> <description>Default block replication. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.heartbeat.interval</name> <value>3</value> <description>Determines datanode heartbeat interval in seconds.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.heartbeat.interval</name> <value>3</value> <description>Determines datanode heartbeat interval in seconds.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.safemode.threshold.pct</name> @@ -142,7 +142,7 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.balance.bandwidthPerSec</name> @@ -152,23 +152,23 @@ can utilize for the balancing purpose in term of the number of bytes per second. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.datanode.address</name> <value>0.0.0.0:50010</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.datanode.http.address</name> <value>0.0.0.0:50075</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.block.size</name> <value>134217728</value> <description>The default block size for new files.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.http.address</name> @@ -176,7 +176,7 @@ <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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.datanode.du.reserved</name> @@ -184,7 +184,7 @@ literal string "local" or a host:port for HDFS.</description> <value>1073741824</value> <description>Reserved space in bytes per volume. Always leave this much space free for non dfs use. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.datanode.ipc.address</name> @@ -193,25 +193,25 @@ literal string "local" or a host:port for HDFS.</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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.blockreport.initialDelay</name> <value>120</value> <description>Delay for first block report in seconds.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.datanode.max.xcievers</name> <value>1024</value> <description>PRIVATE CONFIG VARIABLE</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <!-- Permissions configuration --> <property> @@ -220,7 +220,7 @@ If the port is 0 then the server will start on a free port. <description> The octal umask used when creating files and directories. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.web.ugi</name> @@ -229,7 +229,7 @@ The octal umask used when creating files and directories. <description>The user account used by the web interface. Syntax: USERNAME,GROUP1,GROUP2, ... </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.permissions</name> @@ -241,24 +241,24 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>ipc.server.max.response.size</name> <value>5242880</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.block.access.token.enable</name> @@ -267,7 +267,7 @@ owner or group of files or directories. 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.namenode.kerberos.principal</name> @@ -275,7 +275,7 @@ If "false", no access tokens are checked on accessing datanodes. <description> Kerberos principal name for the NameNode </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.secondary.namenode.kerberos.principal</name> @@ -283,7 +283,7 @@ Kerberos principal name for the NameNode <description> Kerberos principal name for the secondary NameNode. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <!-- This is KRB DOMAIN specific. The FQDN of the namenode has to be mentioned. @@ -292,26 +292,26 @@ Kerberos principal name for the NameNode <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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.secondary.namenode.kerberos.https.principal</name> <value/> <description>The Kerberos principal for the hostthat the secondary NameNode runs on.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <!-- cluster variant --> <name>dfs.secondary.http.address</name> <value/> <description>Address of secondary namenode web server</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.web.authentication.kerberos.principal</name> @@ -321,7 +321,7 @@ Kerberos principal name for the NameNode The HTTP Kerberos principal MUST start with 'HTTP/' per Kerberos HTTP SPENGO specification. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.web.authentication.kerberos.keytab</name> @@ -330,7 +330,7 @@ Kerberos principal name for the NameNode 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.datanode.kerberos.principal</name> @@ -338,7 +338,7 @@ Kerberos principal name for the NameNode <description> The Kerberos principal that the DataNode runs as. "_HOST" is replaced by the real host name. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.namenode.keytab.file</name> @@ -346,7 +346,7 @@ Kerberos principal name for the NameNode <description> Combined keytab file containing the namenode service and host principals. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.secondary.namenode.keytab.file</name> @@ -354,7 +354,7 @@ Kerberos principal name for the NameNode <description> Combined keytab file containing the namenode service and host principals. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.datanode.keytab.file</name> @@ -362,19 +362,19 @@ Kerberos principal name for the NameNode <description> The filename of the keytab file for the DataNode. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.https.port</name> <value>50470</value> <description>The https port where namenode binds</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.https.address</name> <value/> <description>The https address where namenode binds</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.datanode.data.dir.perm</name> @@ -383,7 +383,7 @@ Kerberos principal name for the NameNode 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.access.time.precision</name> @@ -392,19 +392,19 @@ don't exist, they will be created with this permission.</description> The default value is 1 hour. Setting a value of 0 disables access times for HDFS. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>ipc.server.read.threadpool.size</name> <value>5</value> <description/> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.namenode.check.stale.datanode</name> @@ -414,6 +414,6 @@ don't exist, they will be created with this permission.</description> for more than 30s (i.e. in a stale state) are used for reads only if all other remote replicas have failed. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> </configuration>
http://git-wip-us.apache.org/repos/asf/ambari/blob/1d31dcfc/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/HIVE/configuration/hive-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/HIVE/configuration/hive-site.xml b/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/HIVE/configuration/hive-site.xml index d004110..879b768 100644 --- a/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/HIVE/configuration/hive-site.xml +++ b/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/HIVE/configuration/hive-site.xml @@ -22,25 +22,25 @@ limitations under the License. <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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>javax.jdo.option.ConnectionURL</name> <value/> <description>JDBC connect string for a JDBC metastore</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>javax.jdo.option.ConnectionUserName</name> <value/> <description>username to use against metastore database</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property require-input="true"> <name>javax.jdo.option.ConnectionPassword</name> @@ -50,86 +50,86 @@ limitations under the License. <value-attributes> <type>password</type> </value-attributes> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.metastore.sasl.enabled</name> <value/> <description>If true, the metastore thrift interface will be secured with SASL. Clients must authenticate with Kerberos.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.metastore.kerberos.keytab.file</name> <value/> <description>The path to the Kerberos Keytab file containing the metastore thrift server's service principal.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.metastore.kerberos.principal</name> <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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.metastore.uris</name> <value/> <description>URI for client to contact metastore server</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hadoop.clientside.fs.operations</name> <value>true</value> <description>FS operations are owned by client</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.server2.enable.doAs</name> <value>true</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>fs.hdfs.impl.disable.cache</name> <value>true</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/1d31dcfc/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/MAPREDUCE2/configuration/global.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/MAPREDUCE2/configuration/global.xml b/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/MAPREDUCE2/configuration/global.xml index 5aefdeb..3629ad0 100644 --- a/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/MAPREDUCE2/configuration/global.xml +++ b/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/MAPREDUCE2/configuration/global.xml @@ -24,24 +24,24 @@ <name>hs_host</name> <value/> <description>History Server.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred_log_dir_prefix</name> <value>/var/log/hadoop-mapreduce</value> <description>Mapreduce Log Dir Prefix</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred_pid_dir_prefix</name> <value>/var/run/hadoop-mapreduce</value> <description>Mapreduce PID Dir Prefix</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred_user</name> <value>mapred</value> <description>Mapreduce User</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/1d31dcfc/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/MAPREDUCE2/configuration/mapred-queue-acls.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/MAPREDUCE2/configuration/mapred-queue-acls.xml b/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/MAPREDUCE2/configuration/mapred-queue-acls.xml index 94be6ac..36b3f29 100644 --- a/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/MAPREDUCE2/configuration/mapred-queue-acls.xml +++ b/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/MAPREDUCE2/configuration/mapred-queue-acls.xml @@ -22,12 +22,12 @@ <property> <name>mapred.queue.default.acl-submit-job</name> <value>*</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.queue.default.acl-administer-jobs</name> <value>*</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <!-- END ACLs --> </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/1d31dcfc/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/MAPREDUCE2/configuration/mapred-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/MAPREDUCE2/configuration/mapred-site.xml b/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/MAPREDUCE2/configuration/mapred-site.xml index 450bc21..608ae3f 100644 --- a/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/MAPREDUCE2/configuration/mapred-site.xml +++ b/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/MAPREDUCE2/configuration/mapred-site.xml @@ -23,25 +23,25 @@ <name>io.sort.mb</name> <value>100</value> <description>No description</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>io.sort.record.percent</name> <value>.2</value> <description>No description</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>io.sort.spill.percent</name> <value>0.1</value> <description>No description</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>io.sort.factor</name> <value>100</value> <description>No description</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <!-- map/reduce properties --> <property> @@ -49,7 +49,7 @@ <value/> <description>No description</description> <final>true</final> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <!-- cluster specific --> @@ -57,38 +57,38 @@ <value/> <description>No description</description> <final>true</final> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.reduce.parallel.copies</name> <value>30</value> <description>No description</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.tasktracker.map.tasks.maximum</name> <value/> <description>No description</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.map.tasks.speculative.execution</name> <value>false</value> <description>If true, then multiple instances of some map tasks may be executed in parallel.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.reduce.tasks.speculative.execution</name> <value>false</value> <description>If true, then multiple instances of some reduce tasks may be executed in parallel.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.reduce.slowstart.completed.maps</name> <value>0.05</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.inmem.merge.threshold</name> @@ -99,7 +99,7 @@ 0 indicates we want to DON'T have any threshold and instead depend only on the ramfs's memory consumption to trigger the merge. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.job.shuffle.merge.percent</name> @@ -109,7 +109,7 @@ storing in-memory map outputs, as defined by mapred.job.shuffle.input.buffer.percent. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.job.shuffle.input.buffer.percent</name> @@ -117,7 +117,7 @@ <description>The percentage of memory to be allocated from the maximum heap size to storing map outputs during the shuffle. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.map.output.compression.codec</name> @@ -125,7 +125,7 @@ <description>If the map outputs are compressed, how should they be compressed </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.output.compression.type</name> @@ -133,7 +133,7 @@ <description>If the job outputs are to compressed as SequenceFiles, how should they be compressed? Should be one of NONE, RECORD or BLOCK. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.job.reduce.input.buffer.percent</name> @@ -143,7 +143,7 @@ remaining map outputs in memory must consume less than this threshold before the reduce can begin. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapreduce.reduce.input.limit</name> @@ -152,13 +152,13 @@ is 10 Gb.) If the estimated input size of the reduce is greater than this value, job is failed. A value of -1 means that there is no limit set. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <!-- copied from kryptonite configuration --> <property> <name>mapred.compress.map.output</name> <value/> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.task.timeout</name> @@ -167,39 +167,39 @@ terminated if it neither reads an input, writes an output, nor updates its status string. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>jetty.connector</name> <value>org.mortbay.jetty.nio.SelectChannelConnector</value> <description>No description</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.child.root.logger</name> <value>INFO,TLA</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.child.java.opts</name> <value>-Xmx512m</value> <description>No description</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.cluster.reduce.memory.mb</name> <value/> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.job.map.memory.mb</name> <value>1024</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.job.reduce.memory.mb</name> <value>1024</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.max.tracker.blacklists</name> @@ -207,35 +207,35 @@ <description> if node is reported blacklisted by 16 successful jobs within timeout-window, it will be graylisted </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.healthChecker.script.path</name> <value/> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.healthChecker.script.timeout</name> <value>60000</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapred.task.maxvmem</name> <value/> <final>true</final> <description>No description</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapreduce.fileoutputcommitter.marksuccessfuljobs</name> <value>false</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapreduce.tasktracker.keytab.file</name> <value/> <description>The filename of the keytab for the task tracker</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapreduce.jobtracker.split.metainfo.maxsize</name> @@ -244,49 +244,49 @@ <description>If the size of the split metainfo file is larger than this, the JobTracker will fail the job during initialize. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapreduce.jobhistory.keytab.file</name> <!-- cluster variant --> <value/> <description>The keytab for the job history server principal.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapreduce.shuffle.port</name> <value>8081</value> <description>Default port that the ShuffleHandler will run on. ShuffleHandler is a service run at the NodeManager to facilitate transfers of intermediate Map outputs to requesting Reducers.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapreduce.jobhistory.intermediate-done-dir</name> <value>/mr-history/tmp</value> <description>Directory where history files are written by MapReduce jobs.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapreduce.jobhistory.done-dir</name> <value>/mr-history/done</value> <description>Directory where history files are managed by the MR JobHistory Server.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapreduce.jobhistory.address</name> <value>localhost:10020</value> <description>Enter your JobHistoryServer hostname.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapreduce.jobhistory.webapp.address</name> <value>localhost:19888</value> <description>Enter your JobHistoryServer hostname.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>mapreduce.framework.name</name> <value>yarn</value> <description>No description</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/1d31dcfc/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/OOZIE/configuration/oozie-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/OOZIE/configuration/oozie-site.xml b/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/OOZIE/configuration/oozie-site.xml index 5dc5bde..29e9bd5 100644 --- a/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/OOZIE/configuration/oozie-site.xml +++ b/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/OOZIE/configuration/oozie-site.xml @@ -25,7 +25,7 @@ <name>oozie.base.url</name> <value>http://localhost:11000/oozie</value> <description>Base Oozie URL.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.system.id</name> @@ -33,7 +33,7 @@ <description> The Oozie system ID. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.systemmode</name> @@ -41,7 +41,7 @@ <description> System mode for Oozie at startup. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.service.AuthorizationService.security.enabled</name> @@ -50,7 +50,7 @@ Specifies whether security (user name/admin role) is enabled or not. If disabled any user can manage Oozie system and manage any job. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.service.PurgeService.older.than</name> @@ -58,7 +58,7 @@ <description> Jobs older than this value, in days, will be purged by the PurgeService. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.service.PurgeService.purge.interval</name> @@ -66,19 +66,19 @@ <description> Interval at which the purge service will run, in seconds. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.service.CallableQueueService.queue.size</name> <value>1000</value> <description>Max callable queue size</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.service.CallableQueueService.threads</name> <value>10</value> <description>Number of threads used for executing callables</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.service.CallableQueueService.callable.concurrency</name> @@ -90,14 +90,14 @@ All commands that use action executors (action-start, action-end, action-kill and action-check) use the action type as the callable type. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.service.coord.normal.default.timeout</name> <value>120</value> <description>Default timeout for a coordinator action input check (in minutes) for normal job. -1 means infinite timeout</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.db.schema.name</name> @@ -105,7 +105,7 @@ <description> Oozie DataBase Name </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.service.HadoopAccessorService.jobTracker.whitelist</name> @@ -113,21 +113,21 @@ <description> Whitelisted job tracker for Oozie service. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.authentication.type</name> <value>simple</value> <description> </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.service.HadoopAccessorService.nameNode.whitelist</name> <value> </value> <description> </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.service.WorkflowAppService.system.libpath</name> @@ -137,7 +137,7 @@ This path is added to workflow application if their job properties sets the property 'oozie.use.system.libpath' to true. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>use.system.libpath.for.mapreduce.and.pig.jobs</name> @@ -148,7 +148,7 @@ specify where the Pig JAR files are. Instead, the ones from the system library path are used. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.authentication.kerberos.name.rules</name> @@ -160,7 +160,7 @@ </value> <description>The mapping from kerberos principal names to local OS user names.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.service.HadoopAccessorService.hadoop.configurations</name> @@ -173,7 +173,7 @@ the Oozie configuration directory; though the path can be absolute (i.e. to point to Hadoop client conf/ directories in the local filesystem. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.service.ActionService.executor.ext.classes</name> @@ -184,12 +184,12 @@ org.apache.oozie.action.hadoop.SqoopActionExecutor, org.apache.oozie.action.hadoop.DistcpActionExecutor </value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.service.SchemaService.wf.ext.schemas</name> <value>shell-action-0.1.xsd,email-action-0.1.xsd,hive-action-0.2.xsd,sqoop-action-0.2.xsd,ssh-action-0.1.xsd,distcp-action-0.1.xsd,hive-action-0.3.xsd</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.service.JPAService.create.db.schema</name> @@ -200,7 +200,7 @@ If set to true, it creates the DB schema if it does not exist. If the DB schema exists is a NOP. If set to false, it does not create the DB schema. If the DB schema does not exist it fails start up. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.service.JPAService.jdbc.driver</name> @@ -208,7 +208,7 @@ <description> JDBC driver class. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.service.JPAService.jdbc.url</name> @@ -216,7 +216,7 @@ <description> JDBC URL. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.service.JPAService.jdbc.username</name> @@ -224,7 +224,7 @@ <description> DB user name. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.service.JPAService.jdbc.password</name> @@ -235,7 +235,7 @@ IMPORTANT: if password is emtpy leave a 1 space string, the service trims the value, if empty Configuration assumes it is NULL. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>oozie.service.JPAService.pool.max.active.conn</name> @@ -243,6 +243,6 @@ <description> Max number of connections. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/1d31dcfc/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/WEBHCAT/configuration/webhcat-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/WEBHCAT/configuration/webhcat-site.xml b/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/WEBHCAT/configuration/webhcat-site.xml index 0cd37f3..57f8554 100644 --- a/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/WEBHCAT/configuration/webhcat-site.xml +++ b/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/WEBHCAT/configuration/webhcat-site.xml @@ -24,79 +24,79 @@ limitations under the License. <name>templeton.port</name> <value>50111</value> <description>The HTTP port for the main server.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>templeton.hadoop.conf.dir</name> <value>/etc/hadoop/conf</value> <description>The path to the Hadoop configuration.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>templeton.jar</name> <value>/usr/lib/hcatalog/share/webhcat/svr/webhcat.jar</value> <description>The path to the Templeton jar file.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>templeton.libjars</name> <value>/usr/lib/zookeeper/zookeeper.jar</value> <description>Jars to add the the classpath.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>templeton.hadoop</name> <value>/usr/bin/hadoop</value> <description>The path to the Hadoop executable.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>templeton.pig.archive</name> <value>hdfs:///apps/webhcat/pig.tar.gz</value> <description>The path to the Pig archive.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>templeton.pig.path</name> <value>pig.tar.gz/pig/bin/pig</value> <description>The path to the Pig executable.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>templeton.hcat</name> <value>/usr/bin/hcat</value> <description>The path to the hcatalog executable.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>templeton.hive.archive</name> <value>hdfs:///apps/webhcat/hive.tar.gz</value> <description>The path to the Hive archive.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>templeton.hive.path</name> <value>hive.tar.gz/hive/bin/hive</value> <description>The path to the Hive executable.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>templeton.hive.properties</name> <value/> <description>Properties to set when running hive.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>templeton.zookeeper.hosts</name> <value/> <description>ZooKeeper servers, as comma separated host:port pairs</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>templeton.storage.class</name> <value>org.apache.hcatalog.templeton.tool.ZooKeeperStorage</value> <description>The class to use as storage</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>templeton.override.enabled</name> @@ -104,18 +104,18 @@ limitations under the License. <description> Enable the override path in templeton.override.jars </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>templeton.streaming.jar</name> <value>hdfs:///apps/webhcat/hadoop-streaming.jar</value> <description>The hdfs path to the Hadoop streaming jar file.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>templeton.exec.timeout</name> <value>60000</value> <description>Time out for templeton api</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/1d31dcfc/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/YARN/configuration/capacity-scheduler.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/YARN/configuration/capacity-scheduler.xml b/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/YARN/configuration/capacity-scheduler.xml index 9da9507..a4a2a33 100644 --- a/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/YARN/configuration/capacity-scheduler.xml +++ b/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/YARN/configuration/capacity-scheduler.xml @@ -22,7 +22,7 @@ <description> Maximum number of applications that can be pending and running. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.scheduler.capacity.maximum-am-resource-percent</name> @@ -32,7 +32,7 @@ application masters i.e. controls number of concurrent running applications. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.scheduler.capacity.root.queues</name> @@ -40,7 +40,7 @@ <description> The queues at the this level (root is the root queue). </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.scheduler.capacity.root.capacity</name> @@ -51,13 +51,13 @@ The child queues capacity should add up to their parent queue's capacity or less. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.scheduler.capacity.root.default.capacity</name> <value>100</value> <description>Default queue target capacity.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.scheduler.capacity.root.default.user-limit-factor</name> @@ -65,7 +65,7 @@ <description> Default queue user limit a percentage from 0.0 to 1.0. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.scheduler.capacity.root.default.maximum-capacity</name> @@ -73,7 +73,7 @@ <description> The maximum capacity of the default queue. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.scheduler.capacity.root.default.state</name> @@ -81,7 +81,7 @@ <description> The state of the default queue. State can be one of RUNNING or STOPPED. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.scheduler.capacity.root.default.acl_submit_jobs</name> @@ -89,7 +89,7 @@ <description> The ACL of who can submit jobs to the default queue. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.scheduler.capacity.root.default.acl_administer_jobs</name> @@ -97,7 +97,7 @@ <description> The ACL of who can administer jobs on the default queue. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.scheduler.capacity.root.acl_administer_queues</name> @@ -106,6 +106,6 @@ The ACL for who can administer this queue i.e. change sub-queue allocations. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/1d31dcfc/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/YARN/configuration/global.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/YARN/configuration/global.xml b/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/YARN/configuration/global.xml index 308f307..d635890 100644 --- a/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/YARN/configuration/global.xml +++ b/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/YARN/configuration/global.xml @@ -24,30 +24,30 @@ <name>rm_host</name> <value/> <description>ResourceManager.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>nm_hosts</name> <value/> <description>List of NodeManager Hosts.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn_log_dir_prefix</name> <value>/var/log/hadoop-yarn</value> <description>YARN Log Dir Prefix</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn_pid_dir_prefix</name> <value>/var/run/hadoop-yarn</value> <description>YARN PID Dir Prefix</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn_user</name> <value>yarn</value> <description>YARN User</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/1d31dcfc/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/YARN/configuration/yarn-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/YARN/configuration/yarn-site.xml b/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/YARN/configuration/yarn-site.xml index 7ddb9c6..25b9841 100644 --- a/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/YARN/configuration/yarn-site.xml +++ b/ambari-server/src/test/resources/stacks/HDP/2.0.1/services/YARN/configuration/yarn-site.xml @@ -22,56 +22,56 @@ <property> <name>yarn.resourcemanager.resource-tracker.address</name> <value>localhost:8025</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.resourcemanager.scheduler.address</name> <value>localhost:8030</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.resourcemanager.address</name> <value>localhost:8050</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.resourcemanager.admin.address</name> <value>localhost:8141</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.resourcemanager.scheduler.class</name> <value>org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.scheduler.minimum-allocation-mb</name> <value>1024</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.scheduler.maximum-allocation-mb</name> <value>8192</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <!-- NodeManager --> <property> <name>yarn.nodemanager.address</name> <value>0.0.0.0:45454</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.nodemanager.resource.memory-mb</name> <value>8192</value> <description>Amount of physical memory, in MB, that can be allocated for containers.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.application.classpath</name> <value>/etc/hadoop/conf,/usr/lib/hadoop/*,/usr/lib/hadoop/lib/*,/usr/lib/hadoop-hdfs/*,/usr/lib/hadoop-hdfs/lib/*,/usr/lib/hadoop-yarn/*,/usr/lib/hadoop-yarn/lib/*,/usr/lib/hadoop-mapreduce/*,/usr/lib/hadoop-mapreduce/lib/*</value> <description>Classpath for typical applications.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.nodemanager.vmem-pmem-ratio</name> @@ -81,34 +81,34 @@ expressed in terms of physical memory, and virtual memory usage is allowed to exceed this allocation by this ratio. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.nodemanager.container-executor.class</name> <value>org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor</value> <description>ContainerExecutor for launching containers</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.nodemanager.aux-services</name> <value>mapreduce.shuffle</value> <description>Auxilliary services of NodeManager</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.nodemanager.aux-services.class</name> <value>org.apache.hadoop.mapred.ShuffleHandler</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.nodemanager.aux-services.mapreduce.shuffle.class</name> <value>org.apache.hadoop.mapred.ShuffleHandler</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.nodemanager.log-dirs</name> <value>/var/log/hadoop/yarn</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.nodemanager.container-monitor.interval-ms</name> @@ -116,51 +116,51 @@ <description>The interval, in milliseconds, for which the node manager waits between two cycles of monitoring its containers' memory usage. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.nodemanager.health-checker.script.path</name> <value>/etc/hadoop/conf/health_check</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.nodemanager.health-checker.interval-ms</name> <value>135000</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.nodemanager.health-checker.script.timeout-ms</name> <value>60000</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.nodemanager.log.retain-second</name> <value>604800</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.log-aggregation-enable</name> <value>true</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.nodemanager.remote-app-log-dir</name> <value>/app-logs</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.nodemanager.remote-app-log-dir-suffix</name> <value>logs</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.nodemanager.log-aggregation.compression-type</name> <value>gz</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.nodemanager.delete.debug-delay-sec</name> <value>36000</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/1d31dcfc/ambari-server/src/test/resources/stacks/HDP/2.0.5/services/HBASE/configuration/global.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/2.0.5/services/HBASE/configuration/global.xml b/ambari-server/src/test/resources/stacks/HDP/2.0.5/services/HBASE/configuration/global.xml index b028662..47d51f0 100644 --- a/ambari-server/src/test/resources/stacks/HDP/2.0.5/services/HBASE/configuration/global.xml +++ b/ambari-server/src/test/resources/stacks/HDP/2.0.5/services/HBASE/configuration/global.xml @@ -24,37 +24,37 @@ <name>hbasemaster_host</name> <value/> <description>HBase Master Host.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>regionserver_hosts</name> <value/> <description>Region Server Hosts</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase_log_dir</name> <value>/var/log/hbase</value> <description>Log Directories for HBase.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase_pid_dir</name> <value>/var/run/hbase</value> <description>Log Directories for HBase.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase_log_dir</name> <value>/var/log/hbase</value> <description>Log Directories for HBase.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase_regionserver_heapsize</name> <value>1024</value> <description>RegionServers heap size.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase_regionserver_xmn_max</name> @@ -64,144 +64,144 @@ Sets the upper bound on HBase RegionServers' young generation size. This value is used in case the young generation size (-Xmn) calculated based on the max heapsize (hbase_regionserver_heapsize) and the -Xmn ratio (hbase_regionserver_xmn_ratio) exceeds this value. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase_regionserver_xmn_ratio</name> <value>0.2</value> <description>Percentage of max heap size which used for young generation heap (-Xmx).</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase_master_heapsize</name> <value>1024</value> <description>HBase Master Heap Size</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hstore_compactionthreshold</name> <value>3</value> <description>HBase HStore compaction threshold.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hfile_blockcache_size</name> <value>0.25</value> <description>HFile block cache size.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hstorefile_maxsize</name> <value>1073741824</value> <description>Maximum HStoreFile Size</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>regionserver_handlers</name> <value>30</value> <description>HBase RegionServer Handler</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hregion_majorcompaction</name> <value>86400000</value> <description>HBase Major Compaction.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hregion_blockmultiplier</name> <value>2</value> <description>HBase Region Block Multiplier</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hregion_memstoreflushsize</name> <value/> <description>HBase Region MemStore Flush Size.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>client_scannercaching</name> <value>100</value> <description>Base Client Scanner Caching</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>zookeeper_sessiontimeout</name> <value>60000</value> <description>ZooKeeper Session Timeout</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hfile_max_keyvalue_size</name> <value>10485760</value> <description>HBase Client Maximum key-value Size</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase_hdfs_root_dir</name> <value>/apps/hbase/data</value> <description>HBase Relative Path to HDFS.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase_tmp_dir</name> <value>/var/log/hbase</value> <description>Hbase temp directory</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase_conf_dir</name> <value>/etc/hbase</value> <description>Config Directory for HBase.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hdfs_enable_shortcircuit_read</name> <value>true</value> <description>HDFS Short Circuit Read</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hdfs_support_append</name> <value>true</value> <description>HDFS append support</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hstore_blockingstorefiles</name> <value>7</value> <description>HStore blocking storefiles.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>regionserver_memstore_lab</name> <value>true</value> <description>Region Server memstore.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>regionserver_memstore_lowerlimit</name> <value>0.35</value> <description>Region Server memstore lower limit.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>regionserver_memstore_upperlimit</name> <value>0.4</value> <description>Region Server memstore upper limit.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase_conf_dir</name> <value>/etc/hbase</value> <description>HBase conf dir.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase_user</name> <value>hbase</value> <description>HBase User Name.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/1d31dcfc/ambari-server/src/test/resources/stacks/HDP/2.0.5/services/HBASE/configuration/hbase-policy.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/2.0.5/services/HBASE/configuration/hbase-policy.xml b/ambari-server/src/test/resources/stacks/HDP/2.0.5/services/HBASE/configuration/hbase-policy.xml index 497dd02..e72dc75 100644 --- a/ambari-server/src/test/resources/stacks/HDP/2.0.5/services/HBASE/configuration/hbase-policy.xml +++ b/ambari-server/src/test/resources/stacks/HDP/2.0.5/services/HBASE/configuration/hbase-policy.xml @@ -28,7 +28,7 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>security.admin.protocol.acl</name> @@ -38,7 +38,7 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>security.masterregion.protocol.acl</name> @@ -48,6 +48,6 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/1d31dcfc/ambari-server/src/test/resources/stacks/HDP/2.0.5/services/HBASE/configuration/hbase-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/2.0.5/services/HBASE/configuration/hbase-site.xml b/ambari-server/src/test/resources/stacks/HDP/2.0.5/services/HBASE/configuration/hbase-site.xml index 3b4bfbd..2ed9c1f 100644 --- a/ambari-server/src/test/resources/stacks/HDP/2.0.5/services/HBASE/configuration/hbase-site.xml +++ b/ambari-server/src/test/resources/stacks/HDP/2.0.5/services/HBASE/configuration/hbase-site.xml @@ -32,7 +32,7 @@ into /tmp. Change this configuration else all data will be lost on machine restart. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.cluster.distributed</name> @@ -42,7 +42,7 @@ false, startup will run all HBase and ZooKeeper daemons together in the one JVM. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.tmp.dir</name> @@ -52,26 +52,26 @@ than '/tmp' (The '/tmp' directory is often cleared on machine restart). </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.master.info.bindAddress</name> <value/> <description>The bind address for the HBase Master web UI </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.master.info.port</name> <value/> <description>The port for the HBase Master web UI.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.info.port</name> <value/> <description>The port for the HBase RegionServer web UI.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.global.memstore.upperLimit</name> @@ -79,7 +79,7 @@ <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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.handler.count</name> @@ -88,7 +88,7 @@ Same property is used by the Master for count of master handlers. Default is 10. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.hregion.majorcompaction</name> @@ -97,7 +97,7 @@ HStoreFiles in a region. Default: 1 day. Set to 0 to disable automated major compactions. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.global.memstore.lowerLimit</name> @@ -108,7 +108,7 @@ the minimum possible flushing to occur when updates are blocked due to memstore limiting. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.hregion.memstore.block.multiplier</name> @@ -120,7 +120,7 @@ resultant flush files take a long time to compact or split, or worse, we OOME </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.hregion.memstore.flush.size</name> @@ -130,7 +130,7 @@ exceeds this number of bytes. Value is checked by a thread that runs every hbase.server.thread.wakefrequency. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.hregion.memstore.mslab.enabled</name> @@ -141,7 +141,7 @@ heavy write loads. This can reduce the frequency of stop-the-world GC pauses on large heaps. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.hregion.max.filesize</name> @@ -151,7 +151,7 @@ grown to exceed this value, the hosting HRegion is split in two. Default: 1G. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.client.scanner.caching</name> @@ -163,7 +163,7 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>zookeeper.session.timeout</name> @@ -175,7 +175,7 @@ "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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.client.keyvalue.maxsize</name> @@ -187,7 +187,7 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.hstore.compactionThreshold</name> @@ -198,7 +198,7 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.hstore.blockingStoreFiles</name> @@ -209,7 +209,7 @@ blocked for this HRegion until a compaction is completed, or until hbase.hstore.blockingWaitTime has been exceeded. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hfile.block.cache.size</name> @@ -219,7 +219,7 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <!-- The following properties configure authentication information for HBase processes when using Kerberos security. There are no default @@ -230,7 +230,7 @@ <description>Full path to the kerberos keytab file to use for logging in the configured HMaster server principal. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.master.kerberos.principal</name> @@ -241,7 +241,7 @@ portion, it will be replaced with the actual hostname of the running instance. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.keytab.file</name> @@ -249,7 +249,7 @@ <description>Full path to the kerberos keytab file to use for logging in the configured HRegionServer server principal. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.kerberos.principal</name> @@ -261,7 +261,7 @@ running instance. An entry for this principal must exist in the file specified in hbase.regionserver.keytab.file </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <!-- Additional configuration specific to HBase security --> <property> @@ -271,24 +271,24 @@ full privileges, regardless of stored ACLs, across the cluster. Only used when HBase security is enabled. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.security.authentication</name> <value>simple</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.rpc.engine</name> <value>org.apache.hadoop.hbase.ipc.WritableRpcEngine</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.security.authorization</name> <value>false</value> <description>Enables HBase authorization. Set the value of this property to false to disable HBase authorization. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.coprocessor.region.classes</name> @@ -299,7 +299,7 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.coprocessor.master.classes</name> @@ -311,7 +311,7 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.zookeeper.property.clientPort</name> @@ -319,7 +319,7 @@ <description>Property from ZooKeeper's config zoo.cfg. The port at which the clients will connect. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <!-- The following three properties are used together to create the list of @@ -335,7 +335,7 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <!-- End of properties used to generate ZooKeeper host:port quorum list. --> <property> @@ -346,7 +346,7 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.zookeeper.useMulti</name> @@ -358,7 +358,7 @@ and will not be downgraded. ZooKeeper versions before 3.4 do not support multi-update and will not fail gracefully if multi-update is invoked (see ZOOKEEPER-1495). </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>zookeeper.znode.parent</name> @@ -368,18 +368,18 @@ By default, all of HBase's ZooKeeper file path are configured with a relative path, so they will all go under this directory unless changed. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.defaults.for.version.skip</name> <value>true</value> <description>Disables version verification.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.domain.socket.path</name> <value>/var/lib/hadoop-hdfs/dn_socket</value> <description>Path to domain socket.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> </configuration>
