[
https://issues.apache.org/jira/browse/AMBARI-14365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055972#comment-15055972
]
Andrii Babiichuk commented on AMBARI-14365:
-------------------------------------------
+1 for the patch
> HDFS Smart Configs: Inconsistent values on slider
> -------------------------------------------------
>
> Key: AMBARI-14365
> URL: https://issues.apache.org/jira/browse/AMBARI-14365
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.3.0
> Environment: ambari-server version: ambari-server-2.1.3.0-517.x86_64
> ambari-server --hash: 863d787b3c2f06b9593aa3cca6656f9ee666817d
> HDP Stack: 2.3
> HDP Version: 2.3.4.0-3360
> Ambari DB: :MySQL
> Oozie/Hive DB: MySQL/MySQL
> Security:yes
> Security Type:AD/AD
> Umask: 027
> JDK: OracleJDK8
> OS: CentOS 6
> Ambari User: slava
> Agents User: agentslava
> MOTD enabled: true
> Customized service users: true
> Is tmp exec: true
> Reporter: Oleg Nechiporenko
> Assignee: Oleg Nechiporenko
> Fix For: 2.3.0
>
> Attachments: AMBARI-14365.patch
>
>
> Please see the screen recording from the system tests artifacts attached.
> - Upon opening the HDFS configs page we can see that NameNode Java heap size
> slider value is 1GB.
> - Even when slider was moved to increase the value, we can see that its still
> showing 1GB
> - Another issue noticed is that when configs tab was opened the max value and
> recommended values are at a higher range (max= 262144GB, recommend =
> 131072GB).
> - But when slider is moved its changed to 15.577GB and 7.75GB respectively.
> This doesn't look right as in both cases it showed the unit as GB.
> Please help take a look
> UI should show spinner until the API response from recommendation API is
> received meaning spinner to be shown until slider's scale is set to final
> value of minimum, maximum and final position of the marker value on the
> slider.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
