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

[Documentation] Can we turn off expiration? #107

Closed
pims opened this Issue Apr 2, 2019 · 1 comment

Comments

Projects
None yet
1 participant
@pims
Copy link

commented Apr 2, 2019

After reading the configuration documentation, it is unclear to me what

[store.fst.pool]

inactive_after (type: integer, allowed: seconds, default: 300) — Time after which a cached graph is considered inactive and can be closed (if it is not used, ie. re-activated)

and

[store.kv.pool]

inactive_after (type: integer, allowed: seconds, default: 1800) — Time after which a cached database is considered inactive and can be closed (if it is not used, ie. re-activated)

mean.
In my toy example, queries no longer return items after the inactive_after period which means, no searches succeed.

Is it possible to not expire those graphs?

@pims

This comment has been minimized.

Copy link
Author

commented Apr 2, 2019

It looks like the issue is on github.com/expectedsh/go-sonic/sonic and not sonic itself. Closing this as it is not as big of an issue anymore.

@pims pims closed this Apr 2, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.