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.

Sign up for GitHub

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

Jump to bottom

Replace grains.id with qubesdb-read to support concurrent updates #710

Open
sssoleileraaa opened this issue Jun 9, 2021 · 1 comment
Open

Replace grains.id with qubesdb-read to support concurrent updates #710

sssoleileraaa opened this issue Jun 9, 2021 · 1 comment
Labels
needs discussion

Comments

@sssoleileraaa
Copy link
Contributor

Description

Follow-up issue for: #705

We were able to make a hot fix for #705 and now we need to decide, do we want to replace our usage of grains, specifically grains.id with qubesdb-read everywhere? Does the issue consistently go away when you turn off concurrency during updates, as @eloquence tested here: #705 (comment)? Is qubesdb-read required in order to reliably use concurrency? If so, perhaps we should increase concurrency from 2 to 4?
@eloquence eloquence added this to Near Term - SD Workstation in SecureDrop Team Board Jun 10, 2021
@sssoleileraaa sssoleileraaa removed this from Near Term - SD Workstation in SecureDrop Team Board Apr 26, 2022
@rocodes
Copy link
Contributor

rocodes commented Sep 14, 2022

Potentially relevant: we may instead be able to adjust the way grains are cached (partly dropping this link here to remind myself to investigate this more later)

@rocodes rocodes mentioned this issue Sep 15, 2022
Closed
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sssoleileraaa @rocodes