<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: what is the right approtch to set update parameters in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/what-is-the-right-approtch-to-set-update-parameters/m-p/229622#M67417</link>
    <description>&lt;P&gt;all the cluster the old and the new are the same except the parameters !  (for sure), so I not understand why on the new cluster with the update json all parameters are update and when we want to do upgrade parametes on the old cluster we get the not start services/components &lt;/P&gt;</description>
    <pubDate>Tue, 29 Aug 2017 12:27:35 GMT</pubDate>
    <dc:creator>mike_bronson7</dc:creator>
    <dc:date>2017-08-29T12:27:35Z</dc:date>
    <item>
      <title>what is the right approtch to set update parameters</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/what-is-the-right-approtch-to-set-update-parameters/m-p/229620#M67415</link>
      <description>&lt;P&gt;I need to update the following parameters in my old ambari cluster to be most updated ( each parameter have config type)&lt;/P&gt;&lt;P&gt;recovery_enabled
fs.trash.interval
dfs.datanode.data.dir
dfs.namenode.accesstime.precision
delete.topic.enable
log.retention.bytes
spark.history.fs.cleaner.enabled
spark.history.fs.cleaner.interval
spark.history.fs.cleaner.maxAge
spark_daemon_memory
spark_thrift_cmd_opts
spark.broadcast.blockSize
spark.driver.maxResultSize
spark.dynamicAllocation.executorIdleTimeout
spark.dynamicAllocation.initialExecutors
spark.dynamicAllocation.maxExecutors
spark.dynamicAllocation.schedulerBacklogTimeout
spark.executor.memory
spark.files.maxPartitionBytes
spark.files.openCostInBytes
spark.kryoserializer.buffer.max
spark.memory.offHeap.enabled
spark.memory.offHeap.size
spark.sql.autoBroadcastJoinThreshold
spark.sql.shuffle.partitions
spark.storage.memoryMapThreshold
tez.runtime.io.sort.mb
tez.runtime.unordered.output.buffer.size-mb
tez.task.resource.memory.mb
initLimit
syncLimit
hive.auto.convert.join.noconditionaltask.size
hive.tez.container.size
mapreduce.map.java.opts
mapreduce.map.memory.mb
mapreduce.reduce.java.opts
mapreduce.reduce.memory.mb
mapreduce.task.io.sort.mb
yarn.app.mapreduce.am.command-opts
yarn.app.mapreduce.am.resource.mb
spark_thrift_cmd_opts
resourcemanager_heapsize
yarn.nodemanager.resource.cpu-vcores
yarn.nodemanager.resource.memory-mb
yarn.resourcemanager.am.max-attempts
yarn.scheduler.maximum-allocation-mb
yarn.scheduler.maximum-allocation-vcores
syncLimit&lt;/P&gt;&lt;P&gt;after we set all parameters and with their updated values ( with config.sh script ) , and perform restart on all required services / components &lt;/P&gt;&lt;P&gt;some of the services/components cannot started&lt;/P&gt;&lt;P&gt;what is wrong with my procedure?&lt;/P&gt;&lt;P&gt;list of the config type for the parameters :&lt;/P&gt;&lt;P&gt;cluster-env
core-site
hdfs-site
hive-interactive-site
hive-site
kafka-broker
mapred-site
spark2-defaults
spark2-env
spark2-thrift-sparkconf
tez-interactive-site
tez-site
yarn-env
yarn-site
zoo.cfg &lt;/P&gt;&lt;P&gt;remark - all the updated parameters already set on other new ambari cluster &lt;/P&gt;</description>
      <pubDate>Tue, 29 Aug 2017 11:54:53 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/what-is-the-right-approtch-to-set-update-parameters/m-p/229620#M67415</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2017-08-29T11:54:53Z</dc:date>
    </item>
    <item>
      <title>Re: what is the right approtch to set update parameters</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/what-is-the-right-approtch-to-set-update-parameters/m-p/229621#M67416</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/26229/uribarih.html" nodeid="26229"&gt;@uri ben-ari&lt;/A&gt;&lt;/P&gt;&lt;P&gt;After setting those parameters , you mentioned that "some of the services/components cannot started".&lt;/P&gt;&lt;P&gt;So can you please check the logs of those services and let us know if you see any error?&lt;/P&gt;&lt;P&gt;As we see that the above mentioned parameters are somewhere related to tuning like Heap and other memory related parameters that differ from environment to environment. So the other clusters values might not be exactly same and applicable for this cluster nodes as well. &lt;/P&gt;</description>
      <pubDate>Tue, 29 Aug 2017 12:18:31 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/what-is-the-right-approtch-to-set-update-parameters/m-p/229621#M67416</guid>
      <dc:creator>jsensharma</dc:creator>
      <dc:date>2017-08-29T12:18:31Z</dc:date>
    </item>
    <item>
      <title>Re: what is the right approtch to set update parameters</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/what-is-the-right-approtch-to-set-update-parameters/m-p/229622#M67417</link>
      <description>&lt;P&gt;all the cluster the old and the new are the same except the parameters !  (for sure), so I not understand why on the new cluster with the update json all parameters are update and when we want to do upgrade parametes on the old cluster we get the not start services/components &lt;/P&gt;</description>
      <pubDate>Tue, 29 Aug 2017 12:27:35 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/what-is-the-right-approtch-to-set-update-parameters/m-p/229622#M67417</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2017-08-29T12:27:35Z</dc:date>
    </item>
    <item>
      <title>Re: what is the right approtch to set update parameters</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/what-is-the-right-approtch-to-set-update-parameters/m-p/229623#M67418</link>
      <description>&lt;P&gt;maybe we need to restart after each parameter update ? , or do the update according to config type preiority ? &lt;/P&gt;</description>
      <pubDate>Tue, 29 Aug 2017 12:35:19 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/what-is-the-right-approtch-to-set-update-parameters/m-p/229623#M67418</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2017-08-29T12:35:19Z</dc:date>
    </item>
    <item>
      <title>Re: what is the right approtch to set update parameters</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/what-is-the-right-approtch-to-set-update-parameters/m-p/229624#M67419</link>
      <description>&lt;P&gt;is it possible to know from all the parameters list what is the values from parameters that cause the problems?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Aug 2017 12:39:17 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/what-is-the-right-approtch-to-set-update-parameters/m-p/229624#M67419</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2017-08-29T12:39:17Z</dc:date>
    </item>
    <item>
      <title>Re: what is the right approtch to set update parameters</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/what-is-the-right-approtch-to-set-update-parameters/m-p/229625#M67420</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/26229/uribarih.html" nodeid="26229"&gt;@uri ben-ari&lt;BR /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I am not sure at this point regarding your last query.  However it will be good to first see what error are we getting to understand why the services are not starting. Looking at the service/components logs or the Ambari UI operation history will give us fare idea on why the service start failed.&lt;BR /&gt;&lt;A rel="user" href="https://community.cloudera.com/users/26229/uribarih.html" nodeid="26229"&gt;&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Tue, 29 Aug 2017 12:43:49 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/what-is-the-right-approtch-to-set-update-parameters/m-p/229625#M67420</guid>
      <dc:creator>jsensharma</dc:creator>
      <dc:date>2017-08-29T12:43:49Z</dc:date>
    </item>
    <item>
      <title>Re: what is the right approtch to set update parameters</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/what-is-the-right-approtch-to-set-update-parameters/m-p/229626#M67421</link>
      <description>&lt;P&gt;generic question , do we need to do restart after each parameter settings ?   or we can do after we set all parameters?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Aug 2017 17:14:18 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/what-is-the-right-approtch-to-set-update-parameters/m-p/229626#M67421</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2017-08-29T17:14:18Z</dc:date>
    </item>
  </channel>
</rss>

