-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Global db-cache invalidation on mutation #3155
Labels
Milestone
Comments
porunov
added a commit
to porunov/janusgraph
that referenced
this issue
Aug 26, 2022
Related to JanusGraph#3155 Signed-off-by: Oleksandr Porunov <[email protected]>
9 tasks
porunov
added a commit
to porunov/janusgraph
that referenced
this issue
Aug 26, 2022
Related to JanusGraph#3155 Signed-off-by: Oleksandr Porunov <[email protected]>
porunov
added a commit
to porunov/janusgraph
that referenced
this issue
Aug 26, 2022
Related to JanusGraph#3155 Signed-off-by: Oleksandr Porunov <[email protected]>
porunov
added a commit
to porunov/janusgraph
that referenced
this issue
Aug 31, 2022
Related to JanusGraph#3155 Signed-off-by: Oleksandr Porunov <[email protected]>
porunov
added a commit
to porunov/janusgraph
that referenced
this issue
Aug 31, 2022
Related to JanusGraph#3155 Signed-off-by: Oleksandr Porunov <[email protected]>
porunov
added a commit
to porunov/janusgraph
that referenced
this issue
Sep 1, 2022
Related to JanusGraph#3155 Signed-off-by: Oleksandr Porunov <[email protected]>
porunov
added a commit
to porunov/janusgraph
that referenced
this issue
Sep 2, 2022
Related to JanusGraph#3155 Signed-off-by: Oleksandr Porunov <[email protected]>
porunov
added a commit
to porunov/janusgraph
that referenced
this issue
Sep 22, 2022
Related to JanusGraph#3155 Signed-off-by: Oleksandr Porunov <[email protected]>
porunov
added a commit
that referenced
this issue
Oct 22, 2022
Related to #3155 Signed-off-by: Oleksandr Porunov <[email protected]>
porunov
added a commit
to porunov/janusgraph
that referenced
this issue
Oct 24, 2022
Fixes JanusGraph#3155 Signed-off-by: Oleksandr Porunov <[email protected]>
9 tasks
porunov
added a commit
to porunov/janusgraph
that referenced
this issue
Nov 7, 2022
Related JanusGraph#3155 JanusGraph#3263 JanusGraph#3264 Signed-off-by: Oleksandr Porunov <[email protected]>
9 tasks
porunov
added a commit
that referenced
this issue
Nov 7, 2022
Related #3155 #3263 #3264 Signed-off-by: Oleksandr Porunov <[email protected]>
porunov
added a commit
to porunov/janusgraph
that referenced
this issue
Feb 13, 2023
TODO: - Fix `buildCacheInvalidationChangeProcessor` to be able to invalidate updated vertices which are already removed by the time processor is started - Add parameter to JanusGraph which will allow automatically starting this log processor - Cover added logic with tests - Document global db-cache invalidation logic (like: lag time between transaction is committed and cache entry is evicted, log configuration for db-cache invalidation log processor, transactions usage for it to work) Fixes JanusGraph#3155 Signed-off-by: Oleksandr Porunov <[email protected]>
porunov
added a commit
to porunov/janusgraph
that referenced
this issue
Feb 13, 2023
TODO: - Fix `buildCacheInvalidationChangeProcessor` to be able to invalidate updated vertices which are already removed by the time processor is started - Add parameter to JanusGraph which will allow automatically starting this log processor - Cover added logic with tests - Document global db-cache invalidation logic (like: lag time between transaction is committed and cache entry is evicted, log configuration for db-cache invalidation log processor, transactions usage for it to work) Fixes JanusGraph#3155 Signed-off-by: Oleksandr Porunov <[email protected]>
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Partially discussed in
Invalidation
topic here: https://lists.lfaidata.foundation/g/janusgraph-dev/topic/discussion_janusgraph/93326202Currently we invalidate db-cache only in the next 3 scenarios:
cache.db-cache-time
).cache.db-cache-time
).I would propose adding a feature which adds a possibility to evict JanusGraph cache on all JanusGraph instances during mutation on any of the instances (something like
cache.db-cache-global-eviction = true
).This would be a good feature for situations when there are no many writes but many reads. Of course, if there are too many writes this would pressure other JanusGraph nodes which isn't good but then this feature shouldn't be used in such use-cases.
I didn't think on how to implement this feature but I guess maybe reusing JanusGraph messaging mechanism could be a good start.
The text was updated successfully, but these errors were encountered: