[
https://issues.apache.org/jira/browse/AMBARI-15449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15203105#comment-15203105
]
Hudson commented on AMBARI-15449:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #4516 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4516/])
AMBARI-15449: HAWQ hdfs-client / output.replace-datanode-on-failure
(bchaudhary:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2dac4846a3382f57ad29cdf9c2c86d439b71318a])
* ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py
*
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/hdfs-client.xml
*
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/hawq-site.xml
* ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py
> HAWQ hdfs-client / output.replace-datanode-on-failure should be set to true
> by default
> --------------------------------------------------------------------------------------
>
> Key: AMBARI-15449
> URL: https://issues.apache.org/jira/browse/AMBARI-15449
> Project: Ambari
> Issue Type: Bug
> Reporter: Alexander Denissov
> Assignee: Alexander Denissov
> Priority: Minor
> Fix For: 2.3.0, 2.2.2
>
> Attachments: AMBARI-15449.branch_2_2.patch,
> AMBARI-15499.branch_2_2.patch.1, Screen Shot 2016-03-18 at 10.22.00 AM.png,
> Screen Shot 2016-03-18 at 10.22.47 AM.png, Screen Shot 2016-03-18 at 10.24.35
> AM.png, Screen Shot 2016-03-18 at 10.28.04 AM.png
>
>
> On large cluster, replace-datanode-on-failure should be set to true, but on
> small clusters (developers environment or testing environment), it should be
> set to false, otherwise, if datanodes are overloaded, it will report error.
> This is the reason it was set to false by default earlier.
> Ambari should set it to true when cluster size > 4, otherwise set it to false.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
