Geo - Send a cache invalidation event via the log cursor whenever features are changed on the primary
requested to merge 5699-enabling-disabling-features-does-not-propagate-correctly-to-geo-secondaries into master
What does this MR do?
This MR introduces a new Geo event Geo::CacheInvalidationEvent that sends a cache invalidation event via the log cursor whenever features are changed on the Geo primary node.
What are the relevant issue numbers?
Closes #5699 (closed)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
Tests added for this feature/bug -
Conforms to the code review guidelines -
Conforms to the merge request performance guidelines -
Conforms to the style guides -
Conforms to the database guides -
EE specific content should be in the top level /eefolder -
For a paid feature, have we considered GitLab.com plans, how it works for groups, and is there a design for promoting it to users who aren't on the correct plan?
Edited by Douglas Barbosa Alexandre