Invalid database

[Håvard Ottestad]

Hi,

I realise I've been writing quite a few message lately.

I've had to restart stardog to maintain read performance, since it's still dipping after an hour or two. This time when I restarted stardog it wouldn't bring the database online again.

Following in the log:

INFO  2017-01-24 17:48:16,433 [main] com.complexible.stardog.StardogKernel:initDatabases(1944): Database testSesame will not be available because there was an error initializing the database: Cannot read header: 4104 != 5441571

INFO  2017-01-24 17:48:20,140 [main] com.complexible.stardog.StardogKernel:handleUnusableIndex(1999): Moving irreparable database testSesame to /home/stardog/data/.unusable/testSesame

I was strictly doing reads on the database.

Anything I can do to prevent this in the future, or repair the database?

Cheers,

Håvard

[Zachary Whitley]

No worries with all the messages. More information is better than less information. You can try repairing the database with "stardog-admin db repair" [1]. How much data are you trying to load? How much memory do you have allocated to stardog? How much total system memory do you have? Do you have swap enabled and if so what is your setting for vm.swappiness? Are you doing a bulk load or are you loading after db creation? Are you loading from the command line or through the Stardog API? I apologize if you've already answered some of those questions already.

[1] http://docs.stardog.com/man/db-repair.html

--
-- --
You received this message because you are subscribed to the C&P "Stardog" group.
To post to this group, send email to sta...@clarkparsia.com
To unsubscribe from this group, send email to
stardog+unsubscribe@clarkparsia.com
For more options, visit this group at
http://groups.google.com/a/clarkparsia.com/group/stardog?hl=en
---
You received this message because you are subscribed to the Google Groups "Stardog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to stardog+unsubscribe@clarkparsia.com.

[Håvard Ottestad]

Couldn't get db repair to work, it needs the database to be loaded by stardog it seems. And stardog won't load it.

When I restarted stardog it was doing a lot of read only queries, no writes at all!

The data in stardog had initially been bulk loaded, around 80 000 000 triples. Running with xmx8g off heap 2g. When I analyised the memory usage it only uses 90mb of off heap and around 4 gb og heap (xmx).