Member since
05-18-2017
5
Posts
0
Kudos Received
0
Solutions
04-10-2018
01:48 AM
Hi @Giovanni Ruotolo. Did you manage to fix the issue. I have precisely the same errors: 10 Apr 2018 13:35:50,364 ERROR [ambari-metrics-retrieval-service-thread-144064] URLStreamProvider:245 - Received HTTP 403 response from URL: http://isiloncluster:8082/jmx
10 Apr 2018 13:35:51,377 ERROR [ambari-metrics-retrieval-service-thread-144065] URLStreamProvider:245 - Received HTTP 403 response from URL: http://isiloncluster:8082/jmx
10 Apr 2018 13:35:51,377 ERROR [ambari-metrics-retrieval-service-thread-144070] URLStreamProvider:245 - Received HTTP 403 response from URL: http://isiloncluster:8082/jmx?get=Hadoop:service=NameNode,name=FSNamesystem::tag.HAState
... View more
03-20-2018
03:58 AM
There has been a recent release of v.2.3.0.0(March,18) though. Doesn't look like completely dead.
... View more
06-15-2017
03:04 AM
Hi @Jay SenSharma, Thank you for your helpful comment. It actually helped. I'am getting a different errors now, but a have a feeling they may relate to a storage. Btw, here is the output from host_version: ambari=# select * from ambari.host_version;
id | repo_version_id | host_id | state
----+-----------------+---------+---------
1 | 1 | 5 | CURRENT
2 | 2 | 51 | CURRENT
3 | 2 | 3 | CURRENT
4 | 2 | 1 | CURRENT
5 | 2 | 2 | CURRENT
6 | 2 | 4 | CURRENT
The host id=5 is our shared storage on EMC Isilon. All the other host IDs are nodes of our cluster. Do you think they should all have the same repo_version_id? I'm actually wondering why they don't. It is the first installation and not an upgrade. (you mentioned "upgrade" in one of your previous comments). Thanks, Igor
... View more
06-07-2017
02:01 AM
Hi @Jay SenSharma, Thank you for your reply. Output for the first two commands is the same across all node (in terms of components versions) [TEST] root@hdpc-t01:~
# hdp-select versions
2.4.0.0-169
[TEST] root@hdpc-t01:~
# hdp-select
accumulo-client - None
accumulo-gc - None
accumulo-master - None
accumulo-monitor - None
accumulo-tablet - None
accumulo-tracer - None
atlas-server - None
falcon-client - None
falcon-server - None
flume-server - None
hadoop-client - 2.4.0.0-169
hadoop-hdfs-datanode - 2.4.0.0-169
hadoop-hdfs-journalnode - 2.4.0.0-169
hadoop-hdfs-namenode - 2.4.0.0-169
hadoop-hdfs-nfs3 - 2.4.0.0-169
hadoop-hdfs-portmap - 2.4.0.0-169
hadoop-hdfs-secondarynamenode - 2.4.0.0-169
hadoop-httpfs - None
hadoop-mapreduce-historyserver - 2.4.0.0-169
hadoop-yarn-nodemanager - 2.4.0.0-169
hadoop-yarn-resourcemanager - 2.4.0.0-169
hadoop-yarn-timelineserver - 2.4.0.0-169
hbase-client - None
hbase-master - None
hbase-regionserver - None
hive-metastore - None
hive-server2 - None
hive-webhcat - None
kafka-broker - None
knox-server - None
mahout-client - None
oozie-client - None
oozie-server - None
phoenix-client - None
phoenix-server - None
ranger-admin - None
ranger-kms - None
ranger-usersync - None
slider-client - None
spark-client - 2.4.0.0-169
spark-historyserver - 2.4.0.0-169
spark-thriftserver - 2.4.0.0-169
sqoop-client - None
sqoop-server - None
storm-client - None
storm-nimbus - None
storm-slider-client - None
storm-supervisor - None
zeppelin-server - None
zookeeper-client - 2.4.0.0-169
zookeeper-server - 2.4.0.0-169
An output for select * from repo_version is attached (it was a bit bulky, so I attached as a separate file) select-from-repo-version-201706061643.xml A "cluster_version" looks like this: ambari=> SELECT * FROM cluster_version;
id | repo_version_id | cluster_id | state | start_time | end_time | user_name
----+-----------------+------------+---------+---------------+---------------+------------
1 | 1 | 2 | CURRENT | 1496204467640 | 1496204467652 | _anonymous
(1 row)
The "/etc/yum.repos.d/HDP.repo" contains this: [HDP-2.4]
name=HDP-2.4
baseurl=http://public-repo-1.hortonworks.com/HDP/centos6/2.x/updates/2.4.0.0
path=/
enabled=0
gpgcheck=0
Thanks for your help again and let me know if outputs are looking healthy or not. Thanks, Igor
... View more
06-03-2017
09:57 AM
Hi, I had cluster configured using Wizard. But all components are unhealthy. The same error across al components I see, when I try to start them up: ...
resource_management.core.exceptions.Fail:
Execution of 'conf-select set-conf-dir --package hadoop --stack-version 2.4.0.0
--conf-version 0' returned 1. 2.4.0.0 Incorrect stack version
... It is stated clear, that stack version is incorrect, but why? I have ambari of v.2.2.2 and HDP of v2.4. They should work fine together according to compatibility matrix. Please shed some light on why is the error and what direction to move.
... View more
Labels: