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

Gracefully exit when redis is not running #45

Open
wires opened this issue Jul 31, 2015 · 2 comments
Open

Gracefully exit when redis is not running #45

wires opened this issue Jul 31, 2015 · 2 comments

Comments

@wires
Copy link
Contributor

wires commented Jul 31, 2015

thing currently keeps running when cannot connect with redis

Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED
    at RedisClient.flush_and_error (/Users/wires/r/erfgoed-locatie/histograph-core/node_modules/redis/index.js:149:13)
    at RedisClient.on_error (/Users/wires/r/erfgoed-locatie/histograph-core/node_modules/redis/index.js:191:10)
    at Socket.<anonymous> (/Users/wires/r/erfgoed-locatie/histograph-core/node_modules/redis/index.js:106:14)
    at Socket.emit (events.js:107:17)
    at net.js:459:14
    at process._tickCallback (node.js:355:11)
@bertspaan
Copy link
Member

@wires what about some sort of histograph-db module which uses histograph-config and connects to Elasticsearch, Redis or Neo4j (or all of them), and exits on failure?

@sbocconi
Copy link

This issue from Trello is also related to this:

API onbereikbaar als redis down is

100% cpu tijd op API, omdat deze constant met redis probeert te connecten
API is dan non responsive

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants