You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In ProjectionManagement we have methods to pause and resume projections, across the cluster, if you know the ProjectionId up front. For projections feeding from events by slice queries, the slice range of each partition is a suffix of the projection id, and number of partitions may be dynamically scaled, so it can be a bit tricky to actually know the current specific projection ids up front.
For replication the projection id is completely made up behind the scenes from a static prefix, the entity type name, from replica id and to replica id, followed by the same slice range. So again, it is possible for a user to figure out all the projection ids and call ProjectionManagement.pause but it is tricky.
It would be good with an API that makes it possible to pause all partitions of a slice-range based projection, and (possibly another) API to pause all replication to a specific or all replicas.
User API could perhaps wildcard suffix based (RES_myentity* for all replication of my_entity, my_sliced_projection* for all partitions of a regular slice query projeciton) but note that we don't have a cluster-global registry of all running projection ids that we could match against in the current ProjectionManagement implementation.
The text was updated successfully, but these errors were encountered:
In
ProjectionManagement
we have methods to pause and resume projections, across the cluster, if you know theProjectionId
up front. For projections feeding from events by slice queries, the slice range of each partition is a suffix of the projection id, and number of partitions may be dynamically scaled, so it can be a bit tricky to actually know the current specific projection ids up front.For replication the projection id is completely made up behind the scenes from a static prefix, the entity type name, from replica id and to replica id, followed by the same slice range. So again, it is possible for a user to figure out all the projection ids and call
ProjectionManagement.pause
but it is tricky.It would be good with an API that makes it possible to pause all partitions of a slice-range based projection, and (possibly another) API to pause all replication to a specific or all replicas.
User API could perhaps wildcard suffix based (
RES_myentity*
for all replication ofmy_entity
,my_sliced_projection*
for all partitions of a regular slice query projeciton) but note that we don't have a cluster-global registry of all running projection ids that we could match against in the currentProjectionManagement
implementation.The text was updated successfully, but these errors were encountered: