Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
2.1.0
-
None
Description
With AMBARI-11069 commit, ambari-web did not displayed any site-properties.js configuration if API did not send that property's definition.
Thus deleting a property in backend without deleting the same in site-properties for any particular stack largely became possible.
There was a corner case that wasn't addressed by AMBARI-11069 commit which is related to a property that has multiple definition in different configuration file.
Thus removing hbae.regionserver.global.memstore.upperLimit and hbae.regionserver.global.memstore.loweLimit from hbase-site of HDP-2.3 stack (which is present in hbase-site and ams-hbase-site) resulted into the property definition from site-property being honored instead of skipping it. This showed hbae.regionserver.global.memstore.upperLimit and hbae.regionserver.global.memstore.loweLimit on hbase config page with empty values invalidated with 2 error counts.
Attachments
Attachments
Issue Links
- is related to
-
AMBARI-11069 Kafka config "port" is deprecated but still shows up in the UI config page
- Resolved
-
AMBARI-12224 Ambari should not configure hbase.regionserver.global.memstore.upperLimit in HDP-2.3
- Resolved