ON the yarn queues tab, I see: root (100%), default(0%), and llap(100%)..does this may changes had no effect?? ... View more

It works, thanks so much! ... View more

Indeed thank you, that solved the issue, I was just surprised that I needed to do all that, thought ambari would have set that up from the beginning. A follow up question.. When I run the query on druid directly, it returns in like 2 seconds..when I run the query on hive..it converts to map-reduce and takes 2+ minutes to run..any thoughts on why? when running it through hive..I'm guessing the query is not being passed down..and rather all the data is being streamed back to hive? ... View more

@Michael Bronson Just create the home directory as follows # su - hdfs $ hdfs dfs -mkdir /user/slider $ hdfs dfs -chown slider:hdfs /user/slider That should be enough .. good luck ... View more

abandoning this effort. was not getting anywhere as I think the ldaps in corp.example.com and machein hostname setup was causing all my issues., it is not a preferred setup anyhow I needed to correct so i renamed all cluster membre with corp.... ... View more

Hi @Jay Kumar SenSharma, I perform a fresh installation of the cluster hdp 2.6.5. I follow steps mentioned and it works now 🙂 Many Thanks for your help. Regards, ... View more

Thanks @Jay Kumar SenSharma for your help. Please see the output of the Ambari API call on browser . ambari-api-call-on-the-browser-output.txt http://$HOST_NAME:8080/api/v1/stacks/HDF/versions/3.3?fields=operating_systems/repositories/Repositories and CURL command on ambari server host . curl -ivL http://$HOST_NAME:8080/hdf/HDF/centos7/3.3.1.0-10/repodata/repomd.xml Please find the attached curl commend response .curl-uri-response.txt Can you please have a look on output files . Appreciated your help . -Vicky ... View more

@Yee Zee Please refer to the previously shared detailed steps to test this scenario. This works for any Abrupt Termination of the component (either due to host reboot or if somehow the process was killed abruptly). As mentioned earlier that Auto start of a component is based on its current state and "desired state". Which means if you stop a component using Ambari API Or using Ambari UI then you wont see the recovery because in that case the ambari DB will have the correct info. ... View more

Thanks Jay Kumar SenSharma i have resolved the above issue to changing the permissions. Now i am facing one more issue , its seems to looks its not pointing to right repo file .I am using local repository Could you hele me appreciated your help . Thanks in advances. -Vicky Traceback (most recent call last): File "/var/lib/ambari-agent/cache/stack-hooks/before-INSTALL/scripts/hook.py", line 37, in <module> BeforeInstallHook().execute() File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 352, in execute method(env) File "/var/lib/ambari-agent/cache/stack-hooks/before-INSTALL/scripts/hook.py", line 33, in hook install_packages() File "/var/lib/ambari-agent/cache/stack-hooks/before-INSTALL/scripts/shared_initialization.py", line 37, in install_packages retry_count=params.agent_stack_retry_count) File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line 166, in __init__ self.env.run() File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line 160, in run self.run_action(resource, action) File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line 124, in run_action provider_action() File "/usr/lib/ambari-agent/lib/resource_management/core/providers/packaging.py", line 30, in action_install self._pkg_manager.install_package(package_name, self.__create_context()) File "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/yum_manager.py", line 219, in install_package shell.repository_manager_executor(cmd, self.properties, context) File "/usr/lib/ambari-agent/lib/ambari_commons/shell.py", line 753, in repository_manager_executor raise RuntimeError(message) RuntimeError: Failed to execute command '/usr/bin/yum -y install hdf-select', exited with code '1', message: 'Repository HDP-UTILS-1.1.0.22 is listed more than once in the configuration One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid> 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true Cannot find a valid baseurl for repo: HDF-3.3-repo-151 ... View more