http://git-wip-us.apache.org/repos/asf/ambari/blob/1d31dcfc/ambari-server/src/test/resources/TestAmbaryServer.samples/dummy_stack/HIVE/configuration/hive-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/TestAmbaryServer.samples/dummy_stack/HIVE/configuration/hive-site.xml b/ambari-server/src/test/resources/TestAmbaryServer.samples/dummy_stack/HIVE/configuration/hive-site.xml index c706178..d56bfab 100644 --- a/ambari-server/src/test/resources/TestAmbaryServer.samples/dummy_stack/HIVE/configuration/hive-site.xml +++ b/ambari-server/src/test/resources/TestAmbaryServer.samples/dummy_stack/HIVE/configuration/hive-site.xml @@ -21,163 +21,163 @@ limitations under the License. <name>ambari.hive.db.schema.name</name> <value>hive</value> <description>Database name used as the Hive Metastore</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>javax.jdo.option.ConnectionURL</name> <value>jdbc</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>hive</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> <name>javax.jdo.option.ConnectionPassword</name> <value> </value> <description>password to use against metastore database</description> - <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>thrift://localhost:9083</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>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>false</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.hadoop.hive.ql.security.authorization.StorageBasedAuthorizationProvider</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.security.metastore.authorization.manager</name> <value>org.apache.hadoop.hive.ql.security.authorization.StorageBasedAuthorizationProvider</value> <description>The authorization manager class name to be used in the metastore for authorization. The user-defined authorization class should implement interface org.apache.hadoop.hive.ql.security.authorization.HiveMetastoreAuthorizationProvider. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.security.authenticator.manager</name> <value>org.apache.hadoop.hive.ql.security.ProxyUserAuthenticator</value> <description>Hive client authenticator manager class name. The user-defined authenticator class should implement interface org.apache.hadoop.hive.ql.security.HiveAuthenticationProvider. </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> <property> <name>fs.file.impl.disable.cache</name> <value>true</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.enforce.bucketing</name> <value>true</value> <description>Whether bucketing is enforced. If true, while inserting into the table, bucketing is enforced.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.enforce.sorting</name> <value>true</value> <description>Whether sorting is enforced. If true, while inserting into the table, sorting is enforced.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.map.aggr</name> <value>true</value> <description>Whether to use map-side aggregation in Hive Group By queries.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.optimize.bucketmapjoin</name> <value>true</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.optimize.bucketmapjoin.sortedmerge</name> <value>true</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.mapred.reduce.tasks.speculative.execution</name> <value>false</value> <description>Whether speculative execution for reducers should be turned on.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.auto.convert.join</name> <value>true</value> <description>Whether Hive enable the optimization about converting common join into mapjoin based on the input file size.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.auto.convert.sortmerge.join</name> @@ -185,12 +185,12 @@ limitations under the License. <description>Will the join be automatically converted to a sort-merge join, if the joined tables pass the criteria for sort-merge join. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.auto.convert.sortmerge.join.noconditionaltask</name> <value>true</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.auto.convert.join.noconditionaltask</name> @@ -199,7 +199,7 @@ limitations under the License. size. If this paramater is on, and the sum of size for n-1 of the tables/partitions for a n-way join is smaller than the specified size, the join is directly converted to a mapjoin (there is no conditional task). </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.auto.convert.join.noconditionaltask.size</name> @@ -208,7 +208,7 @@ limitations under the License. is on, and the sum of size for n-1 of the tables/partitions for a n-way join is smaller than this size, the join is directly converted to a mapjoin(there is no conditional task). The default is 10MB. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.optimize.reducededuplication.min.reducer</name> @@ -217,7 +217,7 @@ limitations under the License. That means if reducer-num of the child RS is fixed (order by or forced bucketing) and small, it can make very slow, single MR. The optimization will be disabled if number of reducers is less than specified value. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.optimize.mapjoin.mapreduce</name> @@ -227,7 +227,7 @@ limitations under the License. job (for e.g a group by), each map-only job is merged with the following map-reduce job. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.mapjoin.bucket.cache.size</name> @@ -236,17 +236,17 @@ limitations under the License. Size per reducer.The default is 1G, i.e if the input size is 10G, it will use 10 reducers. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.vectorized.execution.enabled</name> <value>false</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.optimize.reducededuplication</name> <value>true</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hive.optimize.index.filter</name> @@ -254,6 +254,6 @@ limitations under the License. <description> Whether to enable automatic use of indexes </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/bad-stacks/HDP/0.1/services/HDFS/configuration/hbase-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/HDFS/configuration/hbase-site.xml b/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/HDFS/configuration/hbase-site.xml index afe544c..1d56933 100644 --- a/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/HDFS/configuration/hbase-site.xml +++ b/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/HDFS/configuration/hbase-site.xml @@ -29,14 +29,14 @@ in milliseconds. Default is 15. Set this value low if you want unit tests to be responsive. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.client.pause</name> <value>5000</value> <description>General client pause value. Used mostly as value to wait before running a retry of a failed get, region lookup, etc.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.master.meta.thread.rescanfrequency</name> @@ -44,7 +44,7 @@ <description>How long the HMaster sleeps (in milliseconds) between scans of the root and meta tables. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.server.thread.wakefrequency</name> @@ -52,7 +52,7 @@ <description>Time to sleep in between searches for work (in milliseconds). Used as sleep interval by service threads such as META scanner and log roller. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.handler.count</name> @@ -61,7 +61,7 @@ Same property is used by the HMaster 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.master.lease.period</name> @@ -71,7 +71,7 @@ value has been reduced so that the master will notice a dead region server sooner. The default is 30 seconds. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.master.info.port</name> @@ -79,7 +79,7 @@ <description>The port for the hbase master web UI Set to -1 if you do not want the info server to run. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.info.port</name> @@ -87,7 +87,7 @@ <description>The port for the hbase regionserver web UI Set to -1 if you do not want the info server to run. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.info.port.auto</name> @@ -96,7 +96,7 @@ search if hbase.regionserver.info.port is already in use. Enabled for testing to run multiple tests on one machine. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.master.lease.thread.wakefrequency</name> @@ -105,7 +105,7 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.optionalcacheflushinterval</name> @@ -114,7 +114,7 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.safemode</name> @@ -123,7 +123,7 @@ Turn on/off safe mode in region server. Always on for production, always off for tests. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.hregion.max.filesize</name> @@ -134,12 +134,12 @@ Keep the maximum filesize small so we split more often in tests. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hadoop.log.dir</name> <value>${user.dir}/../logs</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.zookeeper.property.clientPort</name> @@ -147,6 +147,6 @@ <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> </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/1d31dcfc/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/HDFS/configuration/hdfs-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/HDFS/configuration/hdfs-site.xml b/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/HDFS/configuration/hdfs-site.xml index 6f96077..34960a9 100644 --- a/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/HDFS/configuration/hdfs-site.xml +++ b/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/HDFS/configuration/hdfs-site.xml @@ -28,28 +28,28 @@ 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>false</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> <name>dfs.datanode.failed.volumes.tolerated</name> <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> @@ -58,7 +58,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> @@ -70,7 +70,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> @@ -79,7 +79,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> <name>dfs.hosts</name> @@ -88,27 +88,27 @@ 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" 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.safemode.threshold.pct</name> @@ -119,7 +119,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> @@ -129,23 +129,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> @@ -153,7 +153,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> @@ -161,7 +161,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> @@ -170,25 +170,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> @@ -197,7 +197,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> @@ -206,7 +206,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> @@ -218,24 +218,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> @@ -244,7 +244,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> @@ -252,7 +252,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> @@ -260,7 +260,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. @@ -269,26 +269,26 @@ Kerberos principal name for the NameNode <name>dfs.namenode.kerberos.https.principal</name> <value>host/_HOST@</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>host/_HOST@</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>hdp2.cybervisiontech.com.ua:50090</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> @@ -298,7 +298,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> @@ -307,7 +307,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> @@ -315,7 +315,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> @@ -323,7 +323,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> @@ -331,7 +331,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> @@ -339,19 +339,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>hdp1.cybervisiontech.com.ua:50470</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> @@ -360,7 +360,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> @@ -369,18 +369,18 @@ 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> </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/1d31dcfc/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/MAPREDUCE/configuration/hbase-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/MAPREDUCE/configuration/hbase-site.xml b/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/MAPREDUCE/configuration/hbase-site.xml index afe544c..1d56933 100644 --- a/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/MAPREDUCE/configuration/hbase-site.xml +++ b/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/MAPREDUCE/configuration/hbase-site.xml @@ -29,14 +29,14 @@ in milliseconds. Default is 15. Set this value low if you want unit tests to be responsive. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.client.pause</name> <value>5000</value> <description>General client pause value. Used mostly as value to wait before running a retry of a failed get, region lookup, etc.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.master.meta.thread.rescanfrequency</name> @@ -44,7 +44,7 @@ <description>How long the HMaster sleeps (in milliseconds) between scans of the root and meta tables. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.server.thread.wakefrequency</name> @@ -52,7 +52,7 @@ <description>Time to sleep in between searches for work (in milliseconds). Used as sleep interval by service threads such as META scanner and log roller. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.handler.count</name> @@ -61,7 +61,7 @@ Same property is used by the HMaster 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.master.lease.period</name> @@ -71,7 +71,7 @@ value has been reduced so that the master will notice a dead region server sooner. The default is 30 seconds. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.master.info.port</name> @@ -79,7 +79,7 @@ <description>The port for the hbase master web UI Set to -1 if you do not want the info server to run. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.info.port</name> @@ -87,7 +87,7 @@ <description>The port for the hbase regionserver web UI Set to -1 if you do not want the info server to run. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.info.port.auto</name> @@ -96,7 +96,7 @@ search if hbase.regionserver.info.port is already in use. Enabled for testing to run multiple tests on one machine. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.master.lease.thread.wakefrequency</name> @@ -105,7 +105,7 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.optionalcacheflushinterval</name> @@ -114,7 +114,7 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.safemode</name> @@ -123,7 +123,7 @@ Turn on/off safe mode in region server. Always on for production, always off for tests. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.hregion.max.filesize</name> @@ -134,12 +134,12 @@ Keep the maximum filesize small so we split more often in tests. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hadoop.log.dir</name> <value>${user.dir}/../logs</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.zookeeper.property.clientPort</name> @@ -147,6 +147,6 @@ <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> </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/1d31dcfc/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/MAPREDUCE/configuration/hdfs-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/MAPREDUCE/configuration/hdfs-site.xml b/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/MAPREDUCE/configuration/hdfs-site.xml index 6f96077..34960a9 100644 --- a/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/MAPREDUCE/configuration/hdfs-site.xml +++ b/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/MAPREDUCE/configuration/hdfs-site.xml @@ -28,28 +28,28 @@ 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>false</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> <name>dfs.datanode.failed.volumes.tolerated</name> <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> @@ -58,7 +58,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> @@ -70,7 +70,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> @@ -79,7 +79,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> <name>dfs.hosts</name> @@ -88,27 +88,27 @@ 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" 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.safemode.threshold.pct</name> @@ -119,7 +119,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> @@ -129,23 +129,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> @@ -153,7 +153,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> @@ -161,7 +161,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> @@ -170,25 +170,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> @@ -197,7 +197,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> @@ -206,7 +206,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> @@ -218,24 +218,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> @@ -244,7 +244,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> @@ -252,7 +252,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> @@ -260,7 +260,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. @@ -269,26 +269,26 @@ Kerberos principal name for the NameNode <name>dfs.namenode.kerberos.https.principal</name> <value>host/_HOST@</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>host/_HOST@</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>hdp2.cybervisiontech.com.ua:50090</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> @@ -298,7 +298,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> @@ -307,7 +307,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> @@ -315,7 +315,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> @@ -323,7 +323,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> @@ -331,7 +331,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> @@ -339,19 +339,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>hdp1.cybervisiontech.com.ua:50470</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> @@ -360,7 +360,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> @@ -369,18 +369,18 @@ 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> </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/1d31dcfc/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/MAPREDUCE/configuration/mapred-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/MAPREDUCE/configuration/mapred-site.xml b/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/MAPREDUCE/configuration/mapred-site.xml index 8a4f566..257e045 100644 --- a/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/MAPREDUCE/configuration/mapred-site.xml +++ b/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/MAPREDUCE/configuration/mapred-site.xml @@ -28,28 +28,28 @@ 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>false</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> <name>dfs.datanode.failed.volumes.tolerated</name> <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> @@ -58,7 +58,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> @@ -70,7 +70,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> @@ -79,7 +79,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> <name>dfs.hosts</name> @@ -88,27 +88,27 @@ 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" 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.safemode.threshold.pct</name> @@ -119,7 +119,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> @@ -129,25 +129,25 @@ 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> <description>Address where the datanode binds</description> - <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> <description>HTTP address for the datanode</description> - <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> @@ -155,7 +155,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> @@ -163,7 +163,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> @@ -172,25 +172,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> @@ -199,7 +199,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> @@ -208,7 +208,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> @@ -220,25 +220,25 @@ 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> <description>The max response size for IPC</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>dfs.block.access.token.enable</name> @@ -247,7 +247,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> @@ -255,7 +255,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> @@ -263,7 +263,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. @@ -272,26 +272,26 @@ Kerberos principal name for the NameNode <name>dfs.namenode.kerberos.https.principal</name> <value>host/_HOST@</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>host/_HOST@</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>hdp2.cybervisiontech.com.ua:50090</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> @@ -301,7 +301,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> @@ -310,7 +310,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> @@ -318,7 +318,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> @@ -326,7 +326,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> @@ -334,7 +334,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> @@ -342,19 +342,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>hdp1.cybervisiontech.com.ua:50470</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> @@ -363,7 +363,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> @@ -372,18 +372,18 @@ 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>IPC thread size</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/bad-stacks/HDP/0.1/services/YARN/configuration/capacity-scheduler.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/YARN/configuration/capacity-scheduler.xml b/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/YARN/configuration/capacity-scheduler.xml index 4fe7e0a..f938677 100644 --- a/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/YARN/configuration/capacity-scheduler.xml +++ b/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/YARN/configuration/capacity-scheduler.xml @@ -21,7 +21,7 @@ <value>10000</value> <description>Maximum number of applications that can be pending and running.</description> <final>true</final> - <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> @@ -29,13 +29,13 @@ <deleted>true</deleted> <description>Maximum percent of resources in the cluster.</description> <final>false</final> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property require-input="true"> <name>yarn.scheduler.capacity.root.queues</name> <value>default</value> <deleted>false</deleted> <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> </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/1d31dcfc/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/YARN/configuration/yarn-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/YARN/configuration/yarn-site.xml b/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/YARN/configuration/yarn-site.xml index 94f290b..1efe20c 100644 --- a/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/YARN/configuration/yarn-site.xml +++ b/ambari-server/src/test/resources/bad-stacks/HDP/0.1/services/YARN/configuration/yarn-site.xml @@ -23,14 +23,14 @@ <name>yarn.resourcemanager.resource-tracker.address</name> <value>localhost:8025</value> <deleted>true</deleted> - <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> <description>The address of the scheduler interface.</description> <deleted>true</deleted> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.resourcemanager.address</name> @@ -39,18 +39,18 @@ The address of the applications manager interface in the RM. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>yarn.resourcemanager.admin.address</name> <value/> <description>The address of the RM admin interface.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>new-yarn-property</name> <value>some-value</value> <description>some 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/common-services/HBASE/1.0/configuration/hbase-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/common-services/HBASE/1.0/configuration/hbase-site.xml b/ambari-server/src/test/resources/common-services/HBASE/1.0/configuration/hbase-site.xml index afe544c..1d56933 100644 --- a/ambari-server/src/test/resources/common-services/HBASE/1.0/configuration/hbase-site.xml +++ b/ambari-server/src/test/resources/common-services/HBASE/1.0/configuration/hbase-site.xml @@ -29,14 +29,14 @@ in milliseconds. Default is 15. Set this value low if you want unit tests to be responsive. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.client.pause</name> <value>5000</value> <description>General client pause value. Used mostly as value to wait before running a retry of a failed get, region lookup, etc.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.master.meta.thread.rescanfrequency</name> @@ -44,7 +44,7 @@ <description>How long the HMaster sleeps (in milliseconds) between scans of the root and meta tables. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.server.thread.wakefrequency</name> @@ -52,7 +52,7 @@ <description>Time to sleep in between searches for work (in milliseconds). Used as sleep interval by service threads such as META scanner and log roller. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.handler.count</name> @@ -61,7 +61,7 @@ Same property is used by the HMaster 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.master.lease.period</name> @@ -71,7 +71,7 @@ value has been reduced so that the master will notice a dead region server sooner. The default is 30 seconds. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.master.info.port</name> @@ -79,7 +79,7 @@ <description>The port for the hbase master web UI Set to -1 if you do not want the info server to run. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.info.port</name> @@ -87,7 +87,7 @@ <description>The port for the hbase regionserver web UI Set to -1 if you do not want the info server to run. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.info.port.auto</name> @@ -96,7 +96,7 @@ search if hbase.regionserver.info.port is already in use. Enabled for testing to run multiple tests on one machine. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.master.lease.thread.wakefrequency</name> @@ -105,7 +105,7 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.optionalcacheflushinterval</name> @@ -114,7 +114,7 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.safemode</name> @@ -123,7 +123,7 @@ Turn on/off safe mode in region server. Always on for production, always off for tests. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.hregion.max.filesize</name> @@ -134,12 +134,12 @@ Keep the maximum filesize small so we split more often in tests. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hadoop.log.dir</name> <value>${user.dir}/../logs</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.zookeeper.property.clientPort</name> @@ -147,6 +147,6 @@ <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> </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/1d31dcfc/ambari-server/src/test/resources/common-services/HDFS/1.0/configuration/hbase-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/common-services/HDFS/1.0/configuration/hbase-site.xml b/ambari-server/src/test/resources/common-services/HDFS/1.0/configuration/hbase-site.xml index afe544c..1d56933 100644 --- a/ambari-server/src/test/resources/common-services/HDFS/1.0/configuration/hbase-site.xml +++ b/ambari-server/src/test/resources/common-services/HDFS/1.0/configuration/hbase-site.xml @@ -29,14 +29,14 @@ in milliseconds. Default is 15. Set this value low if you want unit tests to be responsive. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.client.pause</name> <value>5000</value> <description>General client pause value. Used mostly as value to wait before running a retry of a failed get, region lookup, etc.</description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.master.meta.thread.rescanfrequency</name> @@ -44,7 +44,7 @@ <description>How long the HMaster sleeps (in milliseconds) between scans of the root and meta tables. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.server.thread.wakefrequency</name> @@ -52,7 +52,7 @@ <description>Time to sleep in between searches for work (in milliseconds). Used as sleep interval by service threads such as META scanner and log roller. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.handler.count</name> @@ -61,7 +61,7 @@ Same property is used by the HMaster 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.master.lease.period</name> @@ -71,7 +71,7 @@ value has been reduced so that the master will notice a dead region server sooner. The default is 30 seconds. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.master.info.port</name> @@ -79,7 +79,7 @@ <description>The port for the hbase master web UI Set to -1 if you do not want the info server to run. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.info.port</name> @@ -87,7 +87,7 @@ <description>The port for the hbase regionserver web UI Set to -1 if you do not want the info server to run. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.info.port.auto</name> @@ -96,7 +96,7 @@ search if hbase.regionserver.info.port is already in use. Enabled for testing to run multiple tests on one machine. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.master.lease.thread.wakefrequency</name> @@ -105,7 +105,7 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.optionalcacheflushinterval</name> @@ -114,7 +114,7 @@ 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" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.regionserver.safemode</name> @@ -123,7 +123,7 @@ Turn on/off safe mode in region server. Always on for production, always off for tests. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.hregion.max.filesize</name> @@ -134,12 +134,12 @@ Keep the maximum filesize small so we split more often in tests. </description> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hadoop.log.dir</name> <value>${user.dir}/../logs</value> - <on-ambari-upgrade add="true" update="false" delete="false"/> + <on-ambari-upgrade add="true"/> </property> <property> <name>hbase.zookeeper.property.clientPort</name> @@ -147,6 +147,6 @@ <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> </configuration>
