[
https://issues.apache.org/jira/browse/AMBARI-19127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15749523#comment-15749523
]
Hudson commented on AMBARI-19127:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #530 (See
[https://builds.apache.org/job/Ambari-branch-2.5/530/])
AMBARI-19127. hbase_regionserver_shutdown_timeout should be editable all
(aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=10cb81af4fb0ae21391db489485a93398b92bca5])
* (edit)
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/configuration/hbase-env.xml
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-hbase-env.xml
> hbase_regionserver_shutdown_timeout should be editable all the time
> -------------------------------------------------------------------
>
> Key: AMBARI-19127
> URL: https://issues.apache.org/jira/browse/AMBARI-19127
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19127.patch, AMBARI-19127.patch
>
>
> hbase_regionserver_shutdown_timeout should be editable any time. Its now only
> editable during install.
>
>
>
> <property>
> <name>hbase_regionserver_shutdown_timeout</name>
> <value>30</value>
> <display-name>HBase RegionServer shutdown timeout</display-name>
> <description>
> After this number of seconds waiting for graceful stop of HBase Master it
> will be forced to exit with SIGKILL.
> The timeout is introduced because there is a known bug when from time to
> time HBase RegionServer hangs forever on stop if NN safemode is on.
> </description>
> <value-attributes>
> <type>int</type>
> <overridable>false</overridable>
> <editable-only-at-install>true</editable-only-at-install>
> </value-attributes>
> <on-ambari-upgrade add="false"/>
> </property>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
