Skip to content
This repository has been archived by the owner on Feb 16, 2020. It is now read-only.

detect 2nd instance on same datastore #132

Closed
djmuk opened this issue Jan 5, 2014 · 3 comments
Closed

detect 2nd instance on same datastore #132

djmuk opened this issue Jan 5, 2014 · 3 comments

Comments

@djmuk
Copy link
Contributor

djmuk commented Jan 5, 2014

Not sure how easy / necessary this is but in testing I am finding it very easy to accidentally run a 2nd copy of Gekko against the same history which usually results in it being corrupted. This might also be easy for users to do if they launch gekko from a shortcut - not sure how easy it is to add some form of locking, although as Gekko doesn't have a clean exit path (have to use CTL-C) it would never be able to release the lock

@askmike
Copy link
Owner

askmike commented Jan 5, 2014

The current datastore is being replaced by our own, that should probably solve this issue as.

I'm keeping this issue open as a reminder until we shifted away from neDB.

@askmike
Copy link
Owner

askmike commented Jan 10, 2014

Not done with migrating to our own candleStore yet, but I do have an update which should (in theory) make it possible to run a couple of Gekkos listening to the same market:

read this.

askmike added a commit that referenced this issue Jan 11, 2014
@askmike
Copy link
Owner

askmike commented Jan 11, 2014

When you restart and mess up the database, instead of failing silently neDB now throws an error indicating the problem.

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

No branches or pull requests

2 participants