Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wikibase dump out problem due to wdqs crashes #9

Open
NuriaQueralt opened this issue Jan 8, 2019 · 0 comments
Open

wikibase dump out problem due to wdqs crashes #9

NuriaQueralt opened this issue Jan 8, 2019 · 0 comments
Labels
bug Something isn't working

Comments

@NuriaQueralt
Copy link
Contributor

NuriaQueralt commented Jan 8, 2019

WDQS CRASHES

look at the wdqs log: $ docker-compose logs -f --tail 200 wdqs

show what is running in the container: $ docker ps

The dumping out of wikibase by Krusty::wd_to_neo4j.py makes wdqs crash when executed from aws. Consequently the dump out is unsuccessful. No problem when executed from our servers. Looking at the wdqs log it shows something about memory errors:

wdqs_1 | Caused by: com.bigdata.rwstore.sector.MemoryManagerClosedException: null

WDQS RE-START

solution 1: restart the query service via docker-composer

cd /home/ubuntu/wikibase
docker-compose restart wdqs
docker-compose restart wdqs-updater

solution 2 (harder crash): restart docker and then the query service via

docker-compose down
service docker restart
docker-compose up -d

THE PROBLEM

It seems that we are suffering from RAM problems. The docker-compose setup requires more than 2GB of available RAM to start. While being developed the dev machine has 4GB of RAM.'
according to: https://github.com/wmde/wikibase-docker/blob/master/README-compose.md

aws RAM:
$ free -mh
total used free shared buff/cache available
Mem: 7.8G 5.7G 589M 121M 1.5G 1.6G
Swap: 0B 0B 0B

our servers RAM:
$ free -mh
total used free shared buff/cache available
Mem: 62G 5.9G 9.3G 2.2M 47G 56G
Swap: 63G 0B 63G

Possible solutions:

  • limit neo4j ram usage in aws
  • run the dump out in another machine or on-demand platform
  • increase ram in aws
@NuriaQueralt NuriaQueralt added the bug Something isn't working label May 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant