Member since
09-11-2015
269
Posts
281
Kudos Received
55
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
3157 | 03-15-2017 07:12 AM | |
1767 | 03-14-2017 07:08 PM | |
2192 | 03-14-2017 03:36 PM | |
1800 | 02-28-2017 04:32 PM | |
1292 | 02-28-2017 10:02 AM |
02-27-2017
08:13 AM
@Hitesh Rajpurohit can you please close this thread? as this is not an atlas issue and the actual hbase issue is tracked as a different question?
... View more
02-27-2017
07:23 AM
@Hitesh Rajpurohit
The logs you shared does not have any error or exception and it has very minimal information. Could you check the entire hbase logs and see if there is any exception? Also, I would recommend to ask this as a separate question because this is an Hbase issue, not related to Atlas. That way, more hbase folks would be notified and resolution will be quick. Please close this thread once asked as a different question.
... View more
02-25-2017
02:42 AM
@Hitesh Rajpurohit Then the problem is with hbase region server. So, could you please attach the region server and hbase master logs for debugging? Actually Atlas is dependent on Hbase for backend store, if hbase fails to comeup, atlas will also fail.
... View more
02-25-2017
02:39 AM
@Bilal Arshad This is just a warning message and it is not the actual exception. could you please check again!
... View more
02-24-2017
05:33 AM
Try restarting HBase region servers. If it does not help, please attach logs for master and region servers for further debugging.
... View more
02-24-2017
05:31 AM
Atlas logs are stored in application.log file which can be found at <ATLAS_HOME>/logs/application.log.
... View more
02-23-2017
12:50 PM
1 Kudo
@hanlim seok Looks like name node port (50070) is already in use. Stop any service running on 50070 and restart namenode. This should get the services started. java.net.BindException: Port in use: HlseokNamenode:50070 at org.apache.hadoop.http.HttpServer2.openListeners(HttpServer2.java:963) at org.apache.hadoop.http.HttpServer2.start(HttpServer2.java:900) at org.apache.hadoop.hdfs.server.namenode.NameNodeHttpServer.start(NameNodeHttpServer.java:170)
... View more
02-23-2017
12:41 PM
3 Kudos
@Veeru Muppalla
Ambari-Infra comes with solr instance. It is used by Atlas and Ranger for indexing and auditing respectively. So it is required to have solr instance running for Atlas and Ranger to work. From the logs you have attached, it looks like there are no live solr nodes. No live SolrServers available to handle this request
org.apache.solr.client.solrj.SolrServerException: No live SolrServers available to handle this request I would suggest to start the ambari infra component, which in-turn would bring up solr instance. Also, I can see that you have maintenance mode turned on ambari-infra component, any specific reason? This actually does not run the service check and you will not able to know its status. My recommendation is to turn-off the maintenance mode on ambari-infra and restart the service. Once this service is up and running - Atlas and Ranger should come up properly. Let me know if it works.
... View more
02-23-2017
12:18 PM
@Bilal Arshad Error 503 status signifies that the atlas service is not available/running. Please check the application log why its not running.
... View more
02-23-2017
09:53 AM
@Bilal Arshad The user with which you are starting the atlas does not seem to have permission to write to the application.log path. Please change the permissions accordingly. java.io.FileNotFoundException: /home/hduser/atlas/distro/target/apache-atlas-0.8-incubating-SNAPSHOT-bin/apache-atlas-0.8-incubating-SNAPSHOT/logs/application.log (Permission denied)
... View more