[Bigdata-developers] ServerStart timeout - SOLVED

[Jasper K. <jas...@gm...>]

Hello,

The question below is solved but as it was all written down maybe it might be useful for others…

The solution is: -Djetty.start.timeout=60

As can be found here: https://wiki.blazegraph.com/wiki/index.php/NanoSparqlServer


I have created a blaze graph database through the github code running the following command:

/ssd/jasper/BLAZEGRAPH_RELEASE_2_1_1/scripts/dataLoader.sh -verbose -durableQueues -namespace MicroDB MicroDB.properties ~/GZ/*ttl.gz

The property file that I used was as followed:

com.bigdata.namespace.kb.spo.com.bigdata.btree.BTree.branchingFactor=1024
com.bigdata.relation.container=MicroDB
com.bigdata.journal.AbstractJournal.bufferMode=DiskRW
com.bigdata.journal.AbstractJournal.file=MicroDB.jnl
com.bigdata.journal.AbstractJournal.initialExtent=209715200
com.bigdata.rdf.store.AbstractTripleStore.vocabularyClass=com.bigdata.rdf.vocab.DefaultBigdataVocabulary
com.bigdata.rdf.store.AbstractTripleStore.textIndex=false
com.bigdata.btree.BTree.branchingFactor=128
com.bigdata.namespace.kb.lex.com.bigdata.btree.BTree.branchingFactor=400
com.bigdata.rdf.store.AbstractTripleStore.axiomsClass=com.bigdata.rdf.axioms.NoAxioms
com.bigdata.service.AbstractTransactionService.minReleaseAge=1
com.bigdata.rdf.sail.truthMaintenance=false
com.bigdata.journal.AbstractJournal.maximumExtent=209715200
com.bigdata.rdf.sail.namespace=MicroDB
com.bigdata.relation.class=com.bigdata.rdf.store.LocalTripleStore
com.bigdata.rdf.store.AbstractTripleStore.quads=false
com.bigdata.relation.namespace=MicroDB
com.bigdata.btree.writeRetentionQueue.capacity=4000
com.bigdata.rdf.store.AbstractTripleStore.statementIdentifiers=false

After loading 4961 files all received the .good extension.

When trying to start the database of ±413 gigabytes using the following commands:


/ssd/jasper/BLAZEGRAPH_RELEASE_2_1_1/scripts/startBlazegraph.sh 9999 kb /ssd/jasper/MicroDB/MicroDB.properties

This is with a slightly modified startBlazegraph.sh script:

BASE_DIR=`dirname $0`
PORT=$1
NAMESPACE=$2
PROPERTIES_FILE=$3 
"$BASE_DIR"/prog.sh com.bigdata.rdf.sail.webapp.NanoSparqlServer $PORT $NAMESPACE $PROPERTIES_FILE

However the end result is:

WARN : NanoSparqlServer.java:517: Starting NSS
WARN : ServiceProviderHook.java:171: Running.
Server did not start.
FATAL: NanoSparqlServer.java:538: Server did not start.
ERROR: Banner.java:160: Uncaught exception in thread
java.util.concurrent.TimeoutException
	at com.bigdata.rdf.sail.webapp.NanoSparqlServer.awaitServerStart(NanoSparqlServer.java:528)
	at com.bigdata.rdf.sail.webapp.NanoSparqlServer.main(NanoSparqlServer.java:482)

I thought it could be due to the github version and thus tried the jar file from github and the jar file from source forge:

java -server -Xmx8g -Dbigdata.propertyFile=MicroDB.properties -jar blazegraph-jar-2.1.1.jar 
java -server -Xmx8g -Dbigdata.propertyFile=MicroDB.properties -jar blazegraph.jar

Unfortunately with the same result:

WARN : NanoSparqlServer.java:517: Starting NSS
WARN : ServiceProviderHook.java:171: Running.
Server did not start.
FATAL: NanoSparqlServer.java:538: Server did not start.
ERROR: Banner.java:160: Uncaught exception in thread
java.util.concurrent.TimeoutException
	at com.bigdata.rdf.sail.webapp.NanoSparqlServer.awaitServerStart(NanoSparqlServer.java:528)
	at com.bigdata.rdf.sail.webapp.StandaloneNanoSparqlServer.main(StandaloneNanoSparqlServer.java:150)

Any ideas on how to start the database as reloading it all again will take quite some time…

Thanks,

Jasper