question Re: Metadata Server Web UI in Atlas responds with 503 Service Unavailable in Archives of Support Questions (Read Only)

Metadata Server Web UI in Atlas responds with 503 Service Unavailable

menorah84 — Thu, 17 Nov 2016 16:01:34 GMT

Atlas is running but there is a warning sign (yellow) that says HTTP 503 response from Metadata Server Web UI. When I check the /var/log/atlas/application.log, I get:

2016-11-17 15:18:42,753 INFO  - [main:] ~ Server starting with TLS ? false on po
rt 21000 (Main:153)
2016-11-17 15:18:42,756 INFO  - [main:] ~ <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< (Mai
n:154)
2016-11-17 15:18:42,786 INFO  - [main:] ~ Logging initialized @446ms (log:186)
2016-11-17 15:18:42,888 INFO  - [main:] ~ jetty-9.2.12.v20150709 (Server:327)
2016-11-17 15:18:43,703 INFO  - [main:] ~ Loading Guice modules (GuiceServletConfig:59)
2016-11-17 15:18:44,050 INFO  - [main:] ~ Logged in user atlas (auth:SIMPLE) (LoginProcessor:80)
2016-11-17 15:18:44,343 INFO  - [main:] ~ Jersey loading from packages: org.apache.atlas.web.resources,org.apache.atlas.web.params (GuiceServletConfig:84)
2016-11-17 15:18:44,773 WARN  - [main:] ~ Failed startup of context o.e.j.w.WebAppContext@2fb860a{/,file:/usr/hdp/2.4.2.0-258/atlas/server/webapp/atlas/,STARTING}{/usr/hdp/current/atlas-server/server/webapp/atlas} (WebAppContext:514)
com.google.inject.CreationException: Unable to create injector, see the following errors:


1) Error in custom provider, java.lang.IllegalArgumentException: Could not instantiate implementation: com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager
  at org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModule.java:50)
  at org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModul
e.java:50)
  while locating com.google.inject.throwingproviders.ThrowingProviderBinder$Result annotated with @com.google.inject.internal.UniqueAnnotations$Internal(value=1)
Caused by: java.lang.IllegalArgumentException: Could not instantiate implementation: com.thinkaurelius.titan.diskstorage.berkeleyje.BerkeleyJEStoreManager
        at com.thinkaurelius.titan.util.system.ConfigurationUtil.instantiate(ConfigurationUtil.java:55)
        at com.thinkaurelius.titan.diskstorage.Backend.getImplementationClass(Backend.java:421)
        at com.thinkaurelius.titan.diskstorage.Backend.getStorageManager(Backend.java:361)
        at com.thinkaurelius.titan.graphdb.configuration.GraphDatabaseConfiguration.<init>(GraphDatabaseConfiguration.java:1275)
        at com.thinkaurelius.titan.core.TitanFactory.open(TitanFactory.java:93)
        at com.thinkaurelius.titan.core.TitanFactory.open(TitanFactory.java:73)
        at org.apache.atlas.repository.graph.TitanGraphProvider.getGraphInstance(TitanGraphProvider.java:111)
        at org.apache.atlas.repository.graph.TitanGraphProvider.get(TitanGraphProvider.java:142)

How do I resolve this? I am using Ambari v2.4.0.1 and HDP v2.4.2.

Re: Metadata Server Web UI in Atlas responds with 503 Service Unavailable

ckrishnakumar — Thu, 17 Nov 2016 23:15:41 GMT

it looks like the backend is pointing to BerklyDB. would be possible to share the entries in atlas-application.properties for the backend used?

Re: Metadata Server Web UI in Atlas responds with 503 Service Unavailable

apathan — Fri, 18 Nov 2016 10:22:47 GMT

@J. D. Bacolod

Below is the recommendation from the docs

If you are using Atlas on HDP-2.3 or 2.4; Do Not upgrade to Ambari-2.4.x until you are ready to upgrade to HDP-2.5 with the new version of Atlas.

https://docs.hortonworks.com/HDPDocuments/Ambari-2.4.0.1/bk_ambari-upgrade/content/upgrading_HDP_prerequisites.html

The issue with respect to incompatible versions. So, please plan to upgrade accordingly as per the instructions from above link. Hope this helps.

Re: Metadata Server Web UI in Atlas responds with 503 Service Unavailable

menorah84 — Fri, 18 Nov 2016 11:08:24 GMT

Here's what I have for /etc/atlas/conf/application.properties

atlas.enableTLS=false
atlas.graph.index.search.backend=elasticsearch
atlas.graph.index.search.directory=/var/lib/atlas/data/es
atlas.graph.index.search.elasticsearch.client-only=false
atlas.graph.index.search.elasticsearch.local-mode=true
atlas.graph.storage.backend=berkeleyje
atlas.graph.storage.directory=/var/lib/atlas/data/berkeley
atlas.lineage.hive.process.inputs.name=inputs
atlas.lineage.hive.process.outputs.name=outputs
atlas.lineage.hive.process.type.name=Process
atlas.lineage.hive.table.schema.query.hive_table=hive_table where name='%s'\, columns
atlas.lineage.hive.table.schema.query.Table=Table where name='%s'\, columns
atlas.lineage.hive.table.type.name=DataSet
atlas.notification.embedded=false
atlas.rest.address=http://<host>:21000
atlas.server.address.id1=<host>:21000
atlas.server.bind.address=<host>
atlas.server.ha.enabled=false
atlas.server.http.port=21000
atlas.server.https.port=21443
atlas.server.ids=id1

Unfortunately, I can't see a /var/lib/atlas existing. Should that path be created automatically by Ambari / HDP installation wizard?

Re: Metadata Server Web UI in Atlas responds with 503 Service Unavailable

anaik — Tue, 13 Dec 2016 02:30:15 GMT

@J. D. Bacolod This error might possibly be originating from the missing data folder. Can you try creating the folder manually and restart the server ? If it still doesn't help, can you capture the TRACE or DEBUG logs ?