Mailing-List: contact dev-help@atlas.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@atlas.apache.org
To: atlas <dev@atlas.incubator.apache.org>
MIME-Version: 1.0
Subject: Unable to start atlas on master
From: David Radley <david_radley@uk.ibm.com>
Date: Tue, 14 Nov 2017 10:55:00 +0000
Content-Type: multipart/alternative; boundary="=_alternative 003BF7AE802581D8_="
Message-Id: <OF4A7346F6.517E9D93-ON002581D8.003A7CE7-802581D8.003BF7E3@notes.na.collabserv.com>
archived-at: Tue, 14 Nov 2017 10:55:11 -0000

--=_alternative 003BF7AE802581D8_=
Content-Type: text/plain; charset="US-ASCII"

Hi all,
I have tried a few ways to build the latest atlas code from master;  all 
successfully build, but Atlas will not start. I wonder if anyone else is 
seeing this behavior. 

1) Prior to the recent changes, I was successfully running clean package 
-Pdist,berkeley-elasticsearch -DskipTests
This no longer works now the default has changed to Janus I get an error 
in the log com.sleepycat.je.DatabaseException not found

2) I have tried: 
clean package -Pdist,berkeley-elasticsearch -DskipTests 
-DGRAPH-PROVIDER=titan0
this also does not work - this looks like a regression - as the old titan0 
builds should continue to work the same as they did. 

3) I have followed the readme instructions and run 
$ export MAVEN_OPTS="-Xms2g -Xmx2g"
$ mvn clean install

# currently few tests might fail in some environments
# (timing issue?), the community is reviewing and updating
# such tests.
#
# if you see test failures, please run the following command:
   $ mvn clean -DskipTests install

$ mvn clean package -Pdist

This fails to start atlas

4) I run with HBase internal Solr errors - this fails with  errors in the 
log like this::

2017-11-13 16:51:36,612 ERROR - [pool-1-thread-3 - 
8eaf67c4-ba4b-4276-8ba9-7818ded1f9cf:] ~ Request to collection 
fulltext_index failed due to (400) 
org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: 
Error from server at 
http://9.20.103.142:9838/solr/fulltext_index_shard1_replica1: Exception 
writing document id 3a0 to the index; possible analysis error., retry? 0 
(CloudSolrClient:889)
2017-11-13 16:51:36,645 ERROR - [pool-1-thread-3 - 
8eaf67c4-ba4b-4276-8ba9-7818ded1f9cf:] ~ Request to collection 
fulltext_index failed due to (400) 
org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: 
Error from server at 
http://9.20.103.142:9838/solr/fulltext_index_shard1_replica1: Exception 
writing document id 3a0 to the index; possible analysis error., retry? 0 
(CloudSolrClient:889)
2017-11-13 16

This is issue is a blocker for me. I would which build options are 
expected to work and and which ones have been tested to work on master, 
  all the best, David. 


Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

--=_alternative 003BF7AE802581D8_=--