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
For the propagation of information, the system should possess a filtering capability.
On one hand, due to the update of Valkey, some commands are not in the old version, like EXPIREAT for 5.0, and thus if the version is not compatible, hybrid scheduling cannot be achieved.
On the other hand, this can enable the system to possess certain statistical capabilities.
At the same time, it is also closed-loop with the CommandFilter ability, and can do some control when synchronizing information externally
Description of the feature
Support an API in propagateNow, such as modulePropagateFilter, for processing argv. The following methods are supported:
modulePropagateFilters
RegisterPropagateFilter
UnregisterPropagateFilter
PropagateFilterArgsCount
PropagateFilterArgGet
PropagateFilterArgInsert
PropagateFilterArgReplace
PropagateFilterArgDelete
Alternatives you've considered
Use external components to synchronize, such as DTS.
Hardcoding, adaptation logic for version 5.0
Additional information
NA
The text was updated successfully, but these errors were encountered:
Interesting, but I want to understand the full picture. Do you want to attach a 5.0 replica to a new Valkey? There is another problem: It can't do full sync because it doesn't know the new RDB version.
Interesting, but I want to understand the full picture. Do you want to attach a 5.0 replica to a new Valkey? There is another problem: It can't do full sync because it doesn't know the new RDB version.
Sorry for the late reply. This is a good question. In order to support flexible grey release, of course, compatibility issues are also solved in the middle, but this is indeed a relatively safe operation for upgrading (otherwise you need to rely on DTS for data transfer). In fact, we have the ability to switch between different RDB VERSION. But I'm not sure if the community needs this function.
Secondly, making an interface in Propagate can have very flexible extensibility. On the one hand, Propagate can do some operation conversion, such as compatibility adaptation. Secondly, it can also encrypt the log securely. Finally, Propagate is used as an event trigger source to achieve many flexible functions.
The problem/use-case that the feature addresses
For the propagation of information, the system should possess a filtering capability.
On one hand, due to the update of Valkey, some commands are not in the old version, like
EXPIREAT
for 5.0, and thus if the version is not compatible, hybrid scheduling cannot be achieved.On the other hand, this can enable the system to possess certain statistical capabilities.
At the same time, it is also closed-loop with the CommandFilter ability, and can do some control when synchronizing information externally
Description of the feature
Support an API in propagateNow, such as modulePropagateFilter, for processing argv. The following methods are supported:
Alternatives you've considered
Additional information
NA
The text was updated successfully, but these errors were encountered: