http://git-wip-us.apache.org/repos/asf/ambari/blob/0aeaa956/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/MAPREDUCE/configuration/mapred-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/MAPREDUCE/configuration/mapred-site.xml b/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/MAPREDUCE/configuration/mapred-site.xml index 8ad15dd..2ac81c4 100644 --- a/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/MAPREDUCE/configuration/mapred-site.xml +++ b/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/MAPREDUCE/configuration/mapred-site.xml @@ -1,5 +1,6 @@ <?xml version="1.0"?> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?> + <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -16,50 +17,50 @@ See the License for the specific language governing permissions and limitations under the License. --> + <!-- Put site-specific property overrides in this file. --> + <configuration xmlns:xi="http://www.w3.org/2001/XInclude"> - <!-- i/o properties --> + +<!-- i/o properties --> + <property> <name>io.sort.mb</name> - <value/> + <value></value> <description>No description</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>io.sort.record.percent</name> <value>.2</value> <description>No description</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>io.sort.spill.percent</name> - <value/> + <value></value> <description>No description</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>io.sort.factor</name> <value>100</value> <description>No description</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <!-- map/reduce properties --> - <property> - <name>mapred.tasktracker.tasks.sleeptime-before-sigkill</name> - <value>250</value> - <description>Normally, this is the amount of time before killing + +<!-- map/reduce properties --> + +<property> + <name>mapred.tasktracker.tasks.sleeptime-before-sigkill</name> + <value>250</value> + <description>Normally, this is the amount of time before killing processes, and the recommended-default is 5.000 seconds - a value of 5000 here. In this case, we are using it solely to blast tasks before killing them, and killing them very quickly (1/4 second) to guarantee that we do not leave VMs around for later jobs. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> +</property> + <property> <name>mapred.job.tracker.handler.count</name> <value>50</value> @@ -67,99 +68,86 @@ The number of server threads for the JobTracker. This should be roughly 4% of the number of tasktracker nodes. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.system.dir</name> <value>/mapred/system</value> <description>No description</description> <final>true</final> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.job.tracker</name> <!-- cluster variant --> - <value/> + <value></value> <description>No description</description> <final>true</final> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.job.tracker.http.address</name> <!-- cluster variant --> - <value/> + <value></value> <description>No description</description> <final>true</final> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <!-- cluster specific --> <name>mapred.local.dir</name> - <value/> + <value></value> <description>No description</description> <final>true</final> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> - <name>mapreduce.cluster.administrators</name> - <value> hadoop</value> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> + <name>mapreduce.cluster.administrators</name> + <value> hadoop</value> </property> + <property> <name>mapred.reduce.parallel.copies</name> <value>30</value> <description>No description</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.tasktracker.map.tasks.maximum</name> - <value/> + <value></value> <description>No description</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.tasktracker.reduce.tasks.maximum</name> - <value/> + <value></value> <description>No description</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>tasktracker.http.threads</name> <value>50</value> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.reduce.slowstart.completed.maps</name> <value>0.05</value> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.inmem.merge.threshold</name> <value>1000</value> @@ -169,9 +157,8 @@ 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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.job.shuffle.merge.percent</name> <value>0.66</value> @@ -180,57 +167,51 @@ storing in-memory map outputs, as defined by mapred.job.shuffle.input.buffer.percent. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.job.shuffle.input.buffer.percent</name> <value>0.7</value> <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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.map.output.compression.codec</name> - <value/> + <value></value> <description>If the map outputs are compressed, how should they be compressed </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> - <name>mapred.output.compression.type</name> - <value>BLOCK</value> - <description>If the job outputs are to compressed as SequenceFiles, how should + +<property> + <name>mapred.output.compression.type</name> + <value>BLOCK</value> + <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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> +</property> + + <property> <name>mapred.jobtracker.completeuserjobs.maximum</name> <value>5</value> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.jobtracker.taskScheduler</name> - <value/> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> + <value></value> </property> + <property> <name>mapred.jobtracker.restart.recover</name> <value>false</value> <description>"true" to enable (job) recovery upon restart, "false" to start afresh </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.job.reduce.input.buffer.percent</name> <value>0.0</value> @@ -239,26 +220,25 @@ remaining map outputs in memory must consume less than this threshold before the reduce can begin. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> - <name>mapreduce.reduce.input.limit</name> - <value>10737418240</value> - <description>The limit on the input size of the reduce. (This value + + <property> + <name>mapreduce.reduce.input.limit</name> + <value>10737418240</value> + <description>The limit on the input size of the reduce. (This value 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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> +</property> + + <!-- copied from kryptonite configuration --> <property> <name>mapred.compress.map.output</name> - <value/> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> + <value></value> </property> + + <property> <name>mapred.task.timeout</name> <value>600000</value> @@ -266,273 +246,240 @@ terminated if it neither reads an input, writes an output, nor updates its status string. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>jetty.connector</name> <value>org.mortbay.jetty.nio.SelectChannelConnector</value> <description>No description</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.task.tracker.task-controller</name> - <value/> - <description> + <value></value> + <description> TaskController which is used to launch and manage task execution. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.child.root.logger</name> <value>INFO,TLA</value> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.child.java.opts</name> - <value/> + <value></value> + <description>No description</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapred.cluster.map.memory.mb</name> - <value/> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> + <value></value> </property> + <property> <name>mapred.cluster.reduce.memory.mb</name> - <value/> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> + <value></value> </property> + <property> <name>mapred.job.map.memory.mb</name> - <value/> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> + <value></value> </property> + <property> <name>mapred.job.reduce.memory.mb</name> - <value/> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> + <value></value> </property> + <property> <name>mapred.cluster.max.map.memory.mb</name> - <value/> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> + <value></value> </property> + <property> <name>mapred.cluster.max.reduce.memory.mb</name> - <value/> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> + <value></value> </property> - <property> - <name>mapred.hosts</name> - <value/> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapred.hosts.exclude</name> - <value/> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapred.max.tracker.blacklists</name> - <value>16</value> - <description> + +<property> + <name>mapred.hosts</name> + <value></value> +</property> + +<property> + <name>mapred.hosts.exclude</name> + <value></value> +</property> + +<property> + <name>mapred.max.tracker.blacklists</name> + <value>16</value> + <description> if node is reported blacklisted by 16 successful jobs within timeout-window, it will be graylisted </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapred.healthChecker.script.path</name> - <value/> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapred.healthChecker.interval</name> - <value>135000</value> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapred.healthChecker.script.timeout</name> - <value>60000</value> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapred.job.tracker.persist.jobstatus.active</name> - <value>false</value> - <description>Indicates if persistency of job status information is +</property> + +<property> + <name>mapred.healthChecker.script.path</name> + <value></value> +</property> + +<property> + <name>mapred.healthChecker.interval</name> + <value>135000</value> +</property> + +<property> + <name>mapred.healthChecker.script.timeout</name> + <value>60000</value> +</property> + +<property> + <name>mapred.job.tracker.persist.jobstatus.active</name> + <value>false</value> + <description>Indicates if persistency of job status information is active or not. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapred.job.tracker.persist.jobstatus.hours</name> - <value>1</value> - <description>The number of hours job status information is persisted in DFS. +</property> + +<property> + <name>mapred.job.tracker.persist.jobstatus.hours</name> + <value>1</value> + <description>The number of hours job status information is persisted in DFS. The job status information will be available after it drops of the memory queue and between jobtracker restarts. With a zero value the job status information is not persisted at all in DFS. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapred.job.tracker.persist.jobstatus.dir</name> - <value/> - <description>The directory where the job status information is persisted +</property> + +<property> + <name>mapred.job.tracker.persist.jobstatus.dir</name> + <value></value> + <description>The directory where the job status information is persisted in a file system to be available after it drops of the memory queue and between jobtracker restarts. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapred.jobtracker.retirejob.check</name> - <value>10000</value> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapred.jobtracker.retirejob.interval</name> - <value>0</value> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapred.job.tracker.history.completed.location</name> - <value>/mapred/history/done</value> - <description>No description</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapred.task.maxvmem</name> - <value/> - <final>true</final> - <description>No description</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapred.jobtracker.maxtasks.per.job</name> - <value/> - <final>true</final> - <description>The maximum number of tasks for a single job. +</property> + +<property> + <name>mapred.jobtracker.retirejob.check</name> + <value>10000</value> +</property> + +<property> + <name>mapred.jobtracker.retirejob.interval</name> + <value>0</value> +</property> + +<property> + <name>mapred.job.tracker.history.completed.location</name> + <value>/mapred/history/done</value> + <description>No description</description> +</property> + +<property> + <name>mapred.task.maxvmem</name> + <value></value> + <final>true</final> + <description>No description</description> +</property> + +<property> + <name>mapred.jobtracker.maxtasks.per.job</name> + <value></value> + <final>true</final> + <description>The maximum number of tasks for a single job. A value of -1 indicates that there is no maximum. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapreduce.fileoutputcommitter.marksuccessfuljobs</name> - <value>false</value> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapred.userlog.retain.hours</name> - <value/> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapred.job.reuse.jvm.num.tasks</name> - <value>1</value> - <description> +</property> + +<property> + <name>mapreduce.fileoutputcommitter.marksuccessfuljobs</name> + <value>false</value> +</property> + +<property> + <name>mapred.userlog.retain.hours</name> + <value></value> +</property> + +<property> + <name>mapred.job.reuse.jvm.num.tasks</name> + <value>1</value> + <description> How many tasks to run per jvm. If set to -1, there is no limit </description> - <final>true</final> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapreduce.jobtracker.kerberos.principal</name> - <value/> - <description> + <final>true</final> +</property> + +<property> + <name>mapreduce.jobtracker.kerberos.principal</name> + <value></value> + <description> JT user name key. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapreduce.tasktracker.kerberos.principal</name> - <value/> - <description> +</property> + +<property> + <name>mapreduce.tasktracker.kerberos.principal</name> + <value></value> + <description> tt user name key. "_HOST" is replaced by the host name of the task tracker. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> +</property> + + <property> <name>hadoop.job.history.user.location</name> <value>none</value> <final>true</final> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> - <name>mapreduce.jobtracker.keytab.file</name> - <value/> - <description> + + + <property> + <name>mapreduce.jobtracker.keytab.file</name> + <value></value> + <description> The keytab for the jobtracker principal. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapreduce.tasktracker.keytab.file</name> - <value/> + +</property> + + <property> + <name>mapreduce.tasktracker.keytab.file</name> + <value></value> <description>The filename of the keytab for the task tracker</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> + </property> + <property> <name>mapred.task.tracker.http.address</name> - <value/> + <value></value> <description>Http address for task tracker.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> - <name>mapreduce.jobtracker.staging.root.dir</name> - <value>/user</value> - <description>The Path prefix for where the staging directories should be placed. The next level is always the user's + + <property> + <name>mapreduce.jobtracker.staging.root.dir</name> + <value>/user</value> + <description>The Path prefix for where the staging directories should be placed. The next level is always the user's name. It is a path in the default file system.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapreduce.tasktracker.group</name> - <value>hadoop</value> - <description>The group that the task controller uses for accessing the task controller. The mapred user must be a member and users should *not* be members.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> + </property> + + <property> + <name>mapreduce.tasktracker.group</name> + <value>hadoop</value> + <description>The group that the task controller uses for accessing the task controller. The mapred user must be a member and users should *not* be members.</description> + + </property> + <property> <name>mapreduce.jobtracker.split.metainfo.maxsize</name> <value>50000000</value> <final>true</final> - <description>If the size of the split metainfo file is larger than this, the JobTracker will fail the job during + <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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>mapreduce.history.server.embedded</name> @@ -540,58 +487,51 @@ <description>Should job history server be embedded within Job tracker process</description> <final>true</final> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapreduce.history.server.http.address</name> <!-- cluster variant --> - <value/> + <value></value> <description>Http address of the history server</description> <final>true</final> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>mapreduce.jobhistory.kerberos.principal</name> <!-- cluster variant --> - <value/> + <value></value> <description>Job history user name key. (must map to same user as JT user)</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> - <name>mapreduce.jobhistory.keytab.file</name> + + <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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapred.jobtracker.blacklist.fault-timeout-window</name> - <value>180</value> - <description> + <value></value> + <description>The keytab for the job history server principal.</description> + </property> + +<property> + <name>mapred.jobtracker.blacklist.fault-timeout-window</name> + <value>180</value> + <description> 3-hour sliding window (value is in minutes) </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapred.jobtracker.blacklist.fault-bucket-width</name> - <value>15</value> - <description> +</property> + +<property> + <name>mapred.jobtracker.blacklist.fault-bucket-width</name> + <value>15</value> + <description> 15-minute bucket size (value is in minutes) </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>mapred.queue.names</name> - <value>default</value> - <description> Comma separated list of queues configured for this jobtracker.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> +</property> + +<property> + <name>mapred.queue.names</name> + <value>default</value> + <description> Comma separated list of queues configured for this jobtracker.</description> +</property> + </configuration>
http://git-wip-us.apache.org/repos/asf/ambari/blob/0aeaa956/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/OOZIE/configuration/oozie-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/OOZIE/configuration/oozie-site.xml b/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/OOZIE/configuration/oozie-site.xml index ffc37d8..0f81146 100644 --- a/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/OOZIE/configuration/oozie-site.xml +++ b/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/OOZIE/configuration/oozie-site.xml @@ -15,9 +15,11 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ---> +--> + <configuration> - <!-- + +<!-- Refer to the oozie-default.xml file for the complete list of Oozie configuration properties and their default values. --> @@ -25,164 +27,145 @@ <name>oozie.base.url</name> <value>http://localhost:11000/oozie</value> <description>Base Oozie URL.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> + </property> + <property> <name>oozie.system.id</name> <value>oozie-${user.name}</value> <description> The Oozie system ID. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>oozie.systemmode</name> - <value>NORMAL</value> - <description> + </property> + + <property> + <name>oozie.systemmode</name> + <value>NORMAL</value> + <description> System mode for Oozie at startup. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>oozie.service.AuthorizationService.security.enabled</name> - <value>true</value> - <description> + </property> + + <property> + <name>oozie.service.AuthorizationService.security.enabled</name> + <value>true</value> + <description> 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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>oozie.service.PurgeService.older.than</name> - <value>30</value> - <description> + </property> + + <property> + <name>oozie.service.PurgeService.older.than</name> + <value>30</value> + <description> Jobs older than this value, in days, will be purged by the PurgeService. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>oozie.service.PurgeService.purge.interval</name> - <value>3600</value> - <description> + </property> + + <property> + <name>oozie.service.PurgeService.purge.interval</name> + <value>3600</value> + <description> Interval at which the purge service will run, in seconds. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>oozie.service.CallableQueueService.queue.size</name> - <value>1000</value> - <description>Max callable queue size</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>oozie.service.CallableQueueService.callable.concurrency</name> - <value>3</value> - <description> + </property> + + <property> + <name>oozie.service.CallableQueueService.queue.size</name> + <value>1000</value> + <description>Max callable queue size</description> + </property> + + <property> + <name>oozie.service.CallableQueueService.threads</name> + <value>10</value> + <description>Number of threads used for executing callables</description> + </property> + + <property> + <name>oozie.service.CallableQueueService.callable.concurrency</name> + <value>3</value> + <description> Maximum concurrency for a given callable type. Each command is a callable type (submit, start, run, signal, job, jobs, suspend,resume, etc). Each action type is a callable type (Map-Reduce, Pig, SSH, FS, sub-workflow, etc). 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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </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. + </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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>oozie.db.schema.name</name> - <value>oozie</value> - <description> + </property> + + <property> + <name>oozie.db.schema.name</name> + <value>oozie</value> + <description> Oozie DataBase Name </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>oozie.service.HadoopAccessorService.jobTracker.whitelist</name> - <value> </value> - <description> + </property> + + <property> + <name>oozie.service.HadoopAccessorService.jobTracker.whitelist</name> + <value> </value> + <description> Whitelisted job tracker for Oozie service. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>oozie.authentication.type</name> - <value>simple</value> - <description> + </property> + + <property> + <name>oozie.authentication.type</name> + <value>simple</value> + <description> </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>oozie.service.HadoopAccessorService.nameNode.whitelist</name> - <value> </value> - <description> + </property> + + <property> + <name>oozie.service.HadoopAccessorService.nameNode.whitelist</name> + <value> </value> + <description> </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>oozie.service.WorkflowAppService.system.libpath</name> - <value>/user/${user.name}/share/lib</value> - <description> + </property> + + <property> + <name>oozie.service.WorkflowAppService.system.libpath</name> + <value>/user/${user.name}/share/lib</value> + <description> System library path to use for workflow applications. 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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>use.system.libpath.for.mapreduce.and.pig.jobs</name> - <value>false</value> - <description> + </property> + + <property> + <name>use.system.libpath.for.mapreduce.and.pig.jobs</name> + <value>false</value> + <description> If set to true, submissions of MapReduce and Pig jobs will include automatically the system library path, thus not requiring users to specify where the Pig JAR files are. Instead, the ones from the system library path are used. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>oozie.authentication.kerberos.name.rules</name> - <value> + </property> + <property> + <name>oozie.authentication.kerberos.name.rules</name> + <value> </value> - <description>The mapping from kerberos principal names to local OS user names.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>oozie.service.HadoopAccessorService.hadoop.configurations</name> - <value>*=/etc/hadoop/conf</value> - <description> + <description>The mapping from kerberos principal names to local OS user names.</description> + </property> + <property> + <name>oozie.service.HadoopAccessorService.hadoop.configurations</name> + <value>*=/etc/hadoop/conf</value> + <description> Comma separated AUTHORITY=HADOOP_CONF_DIR, where AUTHORITY is the HOST:PORT of the Hadoop service (JobTracker, HDFS). The wildcard '*' configuration is used when there is no exact match for an authority. The HADOOP_CONF_DIR contains @@ -190,85 +173,73 @@ 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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>oozie.service.ActionService.executor.ext.classes</name> - <value> + </property> + <property> + <name>oozie.service.ActionService.executor.ext.classes</name> + <value> org.apache.oozie.action.email.EmailActionExecutor, org.apache.oozie.action.hadoop.HiveActionExecutor, org.apache.oozie.action.hadoop.ShellActionExecutor, org.apache.oozie.action.hadoop.SqoopActionExecutor, org.apache.oozie.action.hadoop.DistcpActionExecutor </value> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>oozie.service.JPAService.create.db.schema</name> - <value>false</value> - <description> + </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> + </property> + <property> + <name>oozie.service.JPAService.create.db.schema</name> + <value>false</value> + <description> Creates Oozie DB. 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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>oozie.service.JPAService.jdbc.driver</name> - <value>org.apache.derby.jdbc.EmbeddedDriver</value> - <description> + </property> + + <property> + <name>oozie.service.JPAService.jdbc.driver</name> + <value>org.apache.derby.jdbc.EmbeddedDriver</value> + <description> JDBC driver class. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>oozie.service.JPAService.jdbc.url</name> - <value>jdbc:derby:${oozie.data.dir}/${oozie.db.schema.name}-db;create=true</value> - <description> + </property> + + <property> + <name>oozie.service.JPAService.jdbc.url</name> + <value>jdbc:derby:${oozie.data.dir}/${oozie.db.schema.name}-db;create=true</value> + <description> JDBC URL. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>oozie.service.JPAService.jdbc.username</name> - <value>sa</value> - <description> + </property> + + <property> + <name>oozie.service.JPAService.jdbc.username</name> + <value>sa</value> + <description> DB user name. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>oozie.service.JPAService.jdbc.password</name> - <value> </value> - <description> + </property> + + <property> + <name>oozie.service.JPAService.jdbc.password</name> + <value> </value> + <description> DB user password. 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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> - <name>oozie.service.JPAService.pool.max.active.conn</name> - <value>10</value> - <description> + </property> + + <property> + <name>oozie.service.JPAService.pool.max.active.conn</name> + <value>10</value> + <description> Max number of connections. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> -</configuration> + </property> +</configuration> \ No newline at end of file http://git-wip-us.apache.org/repos/asf/ambari/blob/0aeaa956/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/WEBHCAT/configuration/webhcat-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/WEBHCAT/configuration/webhcat-site.xml b/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/WEBHCAT/configuration/webhcat-site.xml index e7539a1..31d0113 100644 --- a/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/WEBHCAT/configuration/webhcat-site.xml +++ b/ambari-server/src/test/resources/stacks/HDP/1.2.0/services/WEBHCAT/configuration/webhcat-site.xml @@ -16,122 +16,111 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> + <!-- The default settings for Templeton. --> <!-- Edit templeton-site.xml to change settings for your local --> <!-- install. --> + <configuration> + <property> <name>templeton.port</name> - <value>50111</value> + <value>50111</value> <description>The HTTP port for the main server.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + + <property> <name>templeton.hadoop</name> <value>/usr/bin/hadoop</value> <description>The path to the Hadoop executable.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>templeton.hcat</name> <value>/usr/bin/hcat</value> <description>The path to the hcatalog executable.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>templeton.hive.properties</name> - <value/> + <value></value> <description>Properties to set when running hive.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + + <property> <name>templeton.zookeeper.hosts</name> - <value/> + <value></value> <description>ZooKeeper servers, as comma separated host:port pairs</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> - <name>templeton.override.enabled</name> - <value>false</value> - <description> + <name>templeton.override.enabled</name> + <value>false</value> + <description> Enable the override path in templeton.override.jars </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> - <property> + </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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> - </property> + </property> + <property> <name>templeton.exec.timeout</name> <value>60000</value> <description>Time out for templeton api</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/0aeaa956/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/GANGLIA/configuration/global.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/GANGLIA/configuration/global.xml b/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/GANGLIA/configuration/global.xml index 3eddcfc..16df0b8 100644 --- a/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/GANGLIA/configuration/global.xml +++ b/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/GANGLIA/configuration/global.xml @@ -19,47 +19,37 @@ * limitations under the License. */ --> + <configuration> <property> <name>ganglia_conf_dir</name> <value>/etc/ganglia/hdp</value> <description>Config directory for Ganglia</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>ganglia_runtime_dir</name> <value>/var/run/ganglia/hdp</value> <description>Run directories for Ganglia</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>ganglia_runtime_dir</name> <value>/var/run/ganglia/hdp</value> <description>Run directories for Ganglia</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>gmetad_user</name> <value>nobody</value> <description>User </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + <property> <name>gmond_user</name> <value>nobody</value> <description>User </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>rrdcached_base_dir</name> <value>/var/lib/ganglia/rrds</value> <description>Default directory for saving the rrd files on ganglia server</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/0aeaa956/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/HBASE/configuration/global.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/HBASE/configuration/global.xml b/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/HBASE/configuration/global.xml index ecfe4ba..749fe18 100644 --- a/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/HBASE/configuration/global.xml +++ b/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/HBASE/configuration/global.xml @@ -19,48 +19,37 @@ * limitations under the License. */ --> + <configuration> <property> <name>hbasemaster_host</name> - <value/> + <value></value> <description>HBase Master Host.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>regionserver_hosts</name> - <value/> + <value></value> <description>Region Server Hosts</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase_log_dir</name> <value>/var/log/hbase</value> <description>Log Directories for HBase.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase_pid_dir</name> <value>/var/run/hbase</value> <description>Log Directories for HBase.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase_log_dir</name> <value>/var/log/hbase</value> <description>Log Directories for HBase.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase_regionserver_heapsize</name> <value>1024</value> <description>RegionServer heap size.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase_regionserver_xmn_max</name> @@ -70,168 +59,121 @@ 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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase_master_heapsize</name> <value>1024</value> <description>HBase Master Heap Size</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hstore_compactionthreshold</name> <value>3</value> <description>HBase HStore compaction threshold.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hfile_blockcache_size</name> <value>0.25</value> <description>HFile block cache size.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hstorefile_maxsize</name> <value>1073741824</value> <description>Maximum HStoreFile Size</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + <property> <name>regionserver_handlers</name> <value>30</value> <description>HBase RegionServer Handler</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + <property> <name>hregion_majorcompaction</name> <value>86400000</value> <description>HBase Major Compaction.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + <property> <name>hregion_blockmultiplier</name> <value>2</value> <description>HBase Region Block Multiplier</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + <property> <name>hregion_memstoreflushsize</name> - <value/> + <value></value> <description>HBase Region MemStore Flush Size.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + <property> <name>client_scannercaching</name> <value>100</value> <description>Base Client Scanner Caching</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + <property> <name>zookeeper_sessiontimeout</name> <value>60000</value> <description>ZooKeeper Session Timeout</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + <property> <name>hfile_max_keyvalue_size</name> <value>10485760</value> <description>HBase Client Maximum key-value Size</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + <property> <name>hbase_tmp_dir</name> <value>/var/log/hbase</value> <description>Hbase temp directory</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + <property> <name>hbase_conf_dir</name> <value>/etc/hbase</value> <description>Config Directory for HBase.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + <property> <name>hdfs_enable_shortcircuit_read</name> <value>true</value> <description>HDFS Short Circuit Read</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + <property> <name>hdfs_support_append</name> <value>true</value> <description>HDFS append support</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + <property> <name>hstore_blockingstorefiles</name> <value>7</value> <description>HStore blocking storefiles.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + <property> <name>regionserver_memstore_lab</name> <value>true</value> <description>Region Server memstore.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + <property> <name>regionserver_memstore_lowerlimit</name> <value>0.35</value> <description>Region Server memstore lower limit.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + <property> <name>regionserver_memstore_upperlimit</name> <value>0.4</value> <description>Region Server memstore upper limit.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + <property> <name>hbase_conf_dir</name> <value>/etc/hbase</value> <description>HBase conf dir.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> - <property> + <property> <name>hbase_user</name> <value>hbase</value> <description>HBase User Name.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/0aeaa956/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/HBASE/configuration/hbase-policy.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/HBASE/configuration/hbase-policy.xml b/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/HBASE/configuration/hbase-policy.xml index ecfbfe3..e45f23c 100644 --- a/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/HBASE/configuration/hbase-policy.xml +++ b/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/HBASE/configuration/hbase-policy.xml @@ -19,6 +19,7 @@ * limitations under the License. */ --> + <configuration> <property> <name>security.client.protocol.acl</name> @@ -28,9 +29,8 @@ The ACL is a comma-separated list of user and group names. The user and group list is separated by a blank. For e.g. "alice,bob users,wheel". A special value of "*" means all users are allowed.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>security.admin.protocol.acl</name> <value>*</value> @@ -39,9 +39,8 @@ The ACL is a comma-separated list of user and group names. The user and group list is separated by a blank. For e.g. "alice,bob users,wheel". A special value of "*" means all users are allowed.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>security.masterregion.protocol.acl</name> <value>*</value> @@ -50,7 +49,5 @@ The ACL is a comma-separated list of user and group names. The user and group list is separated by a blank. For e.g. "alice,bob users,wheel". A special value of "*" means all users are allowed.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/0aeaa956/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/HBASE/configuration/hbase-site.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/HBASE/configuration/hbase-site.xml b/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/HBASE/configuration/hbase-site.xml index d771cdb..92181ba 100644 --- a/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/HBASE/configuration/hbase-site.xml +++ b/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/HBASE/configuration/hbase-site.xml @@ -22,7 +22,7 @@ <configuration> <property> <name>hbase.rootdir</name> - <value/> + <value></value> <description>The directory shared by region servers and into which HBase persists. The URL should be 'fully-qualified' to include the filesystem scheme. For example, to specify the @@ -32,8 +32,6 @@ into /tmp. Change this configuration else all data will be lost on machine restart. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.cluster.distributed</name> @@ -43,70 +41,54 @@ false, startup will run all HBase and ZooKeeper daemons together in the one JVM. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.tmp.dir</name> - <value/> + <value></value> <description>Temporary directory on the local filesystem. Change this setting to point to a location more permanent than '/tmp' (The '/tmp' directory is often cleared on machine restart). </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.master.info.bindAddress</name> - <value/> + <value></value> <description>The bind address for the HBase Master web UI </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.master.info.port</name> - <value/> + <value></value> <description>The port for the HBase Master web UI.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.regionserver.info.port</name> - <value/> + <value></value> <description>The port for the HBase RegionServer web UI.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.regionserver.global.memstore.upperLimit</name> - <value/> + <value></value> <description>Maximum size of all memstores in a region server before new updates are blocked and flushes are forced. Defaults to 40% of heap </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.regionserver.handler.count</name> - <value/> + <value></value> <description>Count of RPC Listener instances spun up on RegionServers. Same property is used by the Master for count of master handlers. Default is 10. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.hregion.majorcompaction</name> - <value/> + <value></value> <description>The time (in miliseconds) between 'major' compactions of all HStoreFiles in a region. Default: 1 day. Set to 0 to disable automated major compactions. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.master.lease.thread.wakefrequency</name> @@ -115,24 +97,20 @@ This value has been reduced due to the other reduced values above so that the master will notice a dead region server sooner. The default is 15 seconds. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.regionserver.global.memstore.lowerLimit</name> - <value/> + <value></value> <description>When memstores are being forced to flush to make room in memory, keep flushing until we hit this mark. Defaults to 35% of heap. This value equal to hbase.regionserver.global.memstore.upperLimit causes the minimum possible flushing to occur when updates are blocked due to memstore limiting. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.hregion.memstore.block.multiplier</name> - <value/> + <value></value> <description>Block updates if memstore has hbase.hregion.memstore.block.multiplier time hbase.hregion.flush.size bytes. Useful preventing runaway memstore during spikes in update traffic. Without an @@ -140,46 +118,38 @@ resultant flush files take a long time to compact or split, or worse, we OOME </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.hregion.memstore.flush.size</name> - <value/> + <value></value> <description> Memstore will be flushed to disk if size of the memstore exceeds this number of bytes. Value is checked by a thread that runs every hbase.server.thread.wakefrequency. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.hregion.memstore.mslab.enabled</name> - <value/> + <value></value> <description> Enables the MemStore-Local Allocation Buffer, a feature which works to prevent heap fragmentation under heavy write loads. This can reduce the frequency of stop-the-world GC pauses on large heaps. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.hregion.max.filesize</name> - <value/> + <value></value> <description> Maximum HStoreFile size. If any one of a column families' HStoreFiles has grown to exceed this value, the hosting HRegion is split in two. Default: 1G. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.client.scanner.caching</name> - <value/> + <value></value> <description>Number of rows that will be fetched when calling next on a scanner if it is not served from (local, client) memory. Higher caching values will enable faster scanners but will eat up more memory @@ -187,8 +157,6 @@ Do not set this value such that the time between invocations is greater than the scanner timeout; i.e. hbase.regionserver.lease.period </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>zookeeper.session.timeout</name> @@ -200,12 +168,10 @@ "The client sends a requested timeout, the server responds with the timeout that it can give the client. " In milliseconds. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.client.keyvalue.maxsize</name> - <value/> + <value></value> <description>Specifies the combined maximum allowed size of a KeyValue instance. This is to set an upper boundary for a single entry saved in a storage file. Since they cannot be split it helps avoiding that a region @@ -213,80 +179,67 @@ to set this to a fraction of the maximum region size. Setting it to zero or less disables the check. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.hstore.compactionThreshold</name> - <value/> + <value></value> <description> If more than this number of HStoreFiles in any one HStore (one HStoreFile is written per flush of memstore) then a compaction is run to rewrite all HStoreFiles files as one. Larger numbers put off compaction but when it runs, it takes longer to complete. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.hstore.blockingStoreFiles</name> - <value/> + <value></value> <description> If more than this number of StoreFiles in any one Store (one StoreFile is written per flush of MemStore) then updates are blocked for this HRegion until a compaction is completed, or until hbase.hstore.blockingWaitTime has been exceeded. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hfile.block.cache.size</name> - <value/> + <value></value> <description> Percentage of maximum heap (-Xmx setting) to allocate to block cache used by HFile/StoreFile. Default of 0.25 means allocate 25%. Set to 0 to disable but it's not recommended. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <!-- The following properties configure authentication information for HBase processes when using Kerberos security. There are no default values, included here for documentation purposes --> <property> <name>hbase.master.keytab.file</name> - <value/> + <value></value> <description>Full path to the kerberos keytab file to use for logging in the configured HMaster server principal. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.master.kerberos.principal</name> - <value/> + <value></value> <description>Ex. "hbase/_h...@example.com". The kerberos principal name that should be used to run the HMaster process. The principal name should be in the form: user/hostname@DOMAIN. If "_HOST" is used as the hostname portion, it will be replaced with the actual hostname of the running instance. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.regionserver.keytab.file</name> - <value/> + <value></value> <description>Full path to the kerberos keytab file to use for logging in the configured HRegionServer server principal. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.regionserver.kerberos.principal</name> - <value/> + <value></value> <description>Ex. "hbase/_h...@example.com". The kerberos principal name that should be used to run the HRegionServer process. The principal name should be in the form: user/hostname@DOMAIN. If "_HOST" is used as the @@ -294,35 +247,32 @@ running instance. An entry for this principal must exist in the file specified in hbase.regionserver.keytab.file </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <!-- Additional configuration specific to HBase security --> <property> <name>hbase.superuser</name> - <value/> + <value></value> <description>List of users or groups (comma-separated), who are allowed full privileges, regardless of stored ACLs, across the cluster. Only used when HBase security is enabled. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>hbase.coprocessor.region.classes</name> - <value/> + <value></value> <description>A comma-separated list of Coprocessors that are loaded by default on all tables. For any override coprocessor method, these classes will be called in order. After implementing your own Coprocessor, just put it in HBase's classpath and add the fully qualified class name here. A coprocessor can also be loaded on demand by setting HTableDescriptor. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>hbase.coprocessor.master.classes</name> - <value/> + <value></value> <description>A comma-separated list of org.apache.hadoop.hbase.coprocessor.MasterObserver coprocessors that are loaded by default on the active HMaster process. For any implemented @@ -330,25 +280,23 @@ implementing your own MasterObserver, just put it in HBase's classpath and add the fully qualified class name here. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>hbase.zookeeper.property.clientPort</name> <value>2181</value> <description>Property from ZooKeeper's config zoo.cfg. The port at which the clients will connect. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <!-- The following three properties are used together to create the list of host:peer_port:leader_port quorum servers for ZooKeeper. --> <property> <name>hbase.zookeeper.quorum</name> - <value/> + <value></value> <description>Comma separated list of servers in the ZooKeeper Quorum. For example, "host1.mydomain.com,host2.mydomain.com,host3.mydomain.com". By default this is set to localhost for local and pseudo-distributed modes @@ -356,38 +304,34 @@ list of ZooKeeper quorum servers. If HBASE_MANAGES_ZK is set in hbase-env.sh this is the list of servers which we will start/stop ZooKeeper on. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <!-- End of properties used to generate ZooKeeper host:port quorum list. --> + <property> <name>dfs.support.append</name> - <value/> + <value></value> <description>Does HDFS allow appends to files? This is an hdfs config. set in here so the hdfs client will do append support. You must ensure that this config. is true serverside too when running hbase (You will have to restart your cluster after setting it). </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.client.read.shortcircuit</name> - <value/> + <value></value> <description>Enable/Disable short circuit read for your client. Hadoop servers should be configured to allow short circuit read for the hbase user for this to take effect </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>dfs.client.read.shortcircuit.skip.checksum</name> - <value/> + <value></value> <description>Enable/disbale skipping the checksum check</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + <property> <name>hbase.regionserver.optionalcacheflushinterval</name> <value>10000</value> @@ -395,31 +339,27 @@ Amount of time to wait since the last time a region was flushed before invoking an optional cache flush. Default 60,000. </description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hbase.zookeeper.useMulti</name> <value>true</value> <description>Instructs HBase to make use of ZooKeeper's multi-update functionality. This allows certain ZooKeeper operations to complete more quickly and prevents some issues - with rare Replication failure scenarios (see the release note of HBASE-2611 for an example).· + with rare Replication failure scenarios (see the release note of HBASE-2611 for an example).· IMPORTANT: only set this to true if all ZooKeeper servers in the cluster are on version 3.4+ 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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>zookeeper.znode.parent</name> - <value/> + <value></value> <description>Root ZNode for HBase in ZooKeeper. All of HBase's ZooKeeper files that are configured with a relative path will go under this node. 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" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + + </configuration> http://git-wip-us.apache.org/repos/asf/ambari/blob/0aeaa956/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/HCATALOG/configuration/global.xml ---------------------------------------------------------------------- diff --git a/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/HCATALOG/configuration/global.xml b/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/HCATALOG/configuration/global.xml index b435209..b0c7eb6 100644 --- a/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/HCATALOG/configuration/global.xml +++ b/ambari-server/src/test/resources/stacks/HDP/1.3.0/services/HCATALOG/configuration/global.xml @@ -19,33 +19,27 @@ * limitations under the License. */ --> + <configuration> <property> <name>hcat_log_dir</name> <value>/var/log/webhcat</value> <description>WebHCat Log Dir.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hcat_pid_dir</name> <value>/var/run/webhcat</value> <description>WebHCat Pid Dir.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>hcat_user</name> <value>hcat</value> <description>HCat User.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> <property> <name>webhcat_user</name> <value>hcat</value> <description>WebHCat User.</description> - <on-ambari-upgrade add="true" change="false" delete="false"/> - <on-stack-upgrade add="true" change="false" delete="false"/> </property> + </configuration>