Closed RobinJDCox closed 3 years ago
any update on this issue?
Hi! Is it fixed or not? Faced with the same issue using cluster sharding with redis plugin
@maxkornev whoops, we got Redis Sharding to work but I don't know about this. I don't think Akka.Persistence itself can support having multiple concurrent journal configs like this so I believe this is a won't-fix.
Enable DData for sharding if you want to offload sharding data from Akka.Persistence.
Whoops, didn't meant to close this again.
cc @Arkatufus can you investigate? I believe the blog post is wrong - not persistence.
The blog should be correct, we do have a HOCON setting to enable this.
The obvious example of this would be if you want to have your sharding persistence in a different key-space (or database) to the rest of your Journal/Snapshot persistence.
On reading the following from this blog about getting sharding working I started trying to separate my sharding persistence from my main business logic.
When running with Sql Server for my persistence, the example configuration from the blog I mentioned work fine. So I tried a similar pattern with this Redis but it seemed to be just using the default config (specifically using the same key-space).
Below is an example of the configuration I tried.
What I was hoping I'd be able to do is have my systems journal and snapshot data to be stored using key prefixes of
akka.persistence.journal
andakka.persistence.snapshot
respectively and my sharding data to be usingakka.persistence.sharding.journal
andakka.persistence.sharding.snapshot
Instead both the data from my system and all the sharding data is stored using these two key-prefixes -akka.persistence.journal
andakka.persistence.snapshot
Can we get this updated so that this is configurable in the same way as the
Akka.Persistence.SqlServer
package?