Am trying to deploy LIVY_SERVER through Ambari using blueprints, our cluster is running Ambari 184.108.40.206 and HDP 2.5.
The installation of LIVY_SERVER on the node works fine, however when Ambari comes to start the service it fails with the below error;
Traceback (most recent call last): File "/var/lib/ambari-agent/cache/common-services/SPARK/1.2.1/package/scripts/livy_server.py", line 145, in <module> LivyServer().execute() File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 280, in execute method(env) File "/var/lib/ambari-agent/cache/common-services/SPARK/1.2.1/package/scripts/livy_server.py", line 61, in start self.configure(env) File "/var/lib/ambari-agent/cache/common-services/SPARK/1.2.1/package/scripts/livy_server.py", line 51, in configure setup_livy(env, 'server', upgrade_type=upgrade_type, action = 'config') File "/var/lib/ambari-agent/cache/common-services/SPARK/1.2.1/package/scripts/setup_livy.py", line 48, in setup_livy mode=0644, File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 155, in __init__ self.env.run() File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 160, in run self.run_action(resource, action) File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 124, in run_action provider_action() File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", line 120, in action_create raise Fail("Applying %s failed, parent directory %s doesn't exist" % (self.resource, dirname)) resource_management.core.exceptions.Fail: Applying File['/usr/hdp/current/livy-server/conf/livy-env.sh'] failed, parent directory /usr/hdp/current/livy-server/conf doesn't exist
It seems under /usr/hdp/current/ there is a symbolic link for livy-client but not livy-server.
@Aaron Harris There should be both livy-client and livy-server directories both linking back to the /usr/hdp/<version>/livy dir. If you manually create the dir does it correct the issue? You could also run hdp-select to see if livy-server is connected to the correct hdp version. Hope this helps or you have resolved your issue.