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

chore: disable sqlite store on wakuv2.prod #53

Merged
merged 1 commit into from
Jun 23, 2022

Conversation

jm-clius
Copy link
Contributor

There is a known issue in v0.10 where certain store queries can slow down nodes: waku-org/nwaku#1017
A possible (at least partial) fix has been merged (waku-org/nwaku#1018) and deployed to wakuv2.test, but the SQLite store can be disable on prod in the meantime.

cc @kaiserd in case you'd rather have us keep this enabled but, say, with a shorter retention time. I think safest is to disable.

@jm-clius jm-clius requested a review from jakubgs June 23, 2022 16:43
Copy link
Contributor

@kaiserd kaiserd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I agree on disabling the sqlite store on the prod fleet for now.

Copy link
Member

@jakubgs jakubgs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok.

@jakubgs jakubgs merged commit 521b8b3 into master Jun 23, 2022
@jakubgs jakubgs deleted the chore/disable-sqlite-prod branch June 23, 2022 20:18
@jakubgs
Copy link
Member

jakubgs commented Jun 23, 2022

One not though. You added a nice explanation as to why you want this change in the PR description, but not in the commit.

I think this kind of info should also be included in the commit for the sake of easy access to history.

Fixed it: e563b766

@jakubgs
Copy link
Member

jakubgs commented Jun 23, 2022

Deployed.

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

Successfully merging this pull request may close these issues.

3 participants