ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Szabo" <>
Subject Review Request 40916: Multiple Ranger KMS server cause exception with Blueprint provisioning
Date Thu, 03 Dec 2015 15:49:53 GMT

This is an automatically generated e-mail. To reply, visit:

Review request for Ambari, Robert Levas, Robert Nettleton, Srimanth Gunturi, and Sebastian

Bugs: AMBARI-14177

Repository: ambari


Blueprint provisioning with multiple Ranger KMS components is failed with the following exception:

java.lang.IllegalArgumentException: Unable to update configuration property 'hadoop.kms.key.provider.uri'
with topology information. Component 'RANGER_KMS_SERVER' is mapped to an invalid number of
hosts '2'

1. 'hadoop.kms.key.provider.uri' property is dbks://http@localhost:9292/kms (default) should
work as it is internal for KMS. Its not needed to replace 'localhost'
2. HDFS client properties (, dfs.encryption.key.provider.uri)
are need to be updated (single host updater startegy -> multiple host updater strategy)
3. stack advisor used wrong delimiter for the properties above. (based on:
The Ambari UI also updates these properties if new Ranger KMS server added, and also it replaces
',' with ';' (i found a story about the correct values on UI:
4. the patch contains fixes for handling suffix handling (it doesnt work with multiple host
topology updater, if the proerty string contains only one host):
- Use case with old code: "kms://http@%HOSTGROUP::group1%:2181/kms" -> (with multiple host
updater) "kms://http@host1:2181"
5. localhost' was not replaced in the multiple topology updater as well (despite that, it
was verified there) -> replace only if there is only one host for the specific component.


  ambari-server/src/main/resources/stacks/HDP/2.2/services/ a33be1e 
  ambari-server/src/test/python/stacks/2.2/common/ f5c0436 



Unit testing in progress..


Oliver Szabo

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message