Akka.Persistence.Redis v1.4.16 - the "we removed Akka.Persistence.Query support" thread

[akkadotnet]

Akka.Persistence.Redis v1.4.16 - the "we removed Akka.Persistence.Query support" thread

[andyfurnival]

@Aaronontheweb I was trying to get your Cluster Sharding Viewer example working with Redis, as I wanted to understand why I'm getting occasional issues with an issue that was seen a long time, which causes the message "System.ArgumentException: Shard 98 is already allocated (Parameter 'e')" on Persistence Recovery.

I was hoping to interrogate Redis when the system is in a bad state, and try to deserialise the data and see what gets thrown up (and avoid all the boilerplate trying to go direct to redis to pull the raw data and try to deserialise it myself)

Given this notice above, am I right in thinking that any use of Persistent Query will simply not work for Redis? I'm not able to switch to ddata just yet, so its either Redis or I may need to look at an alternative plugin

[Aaronontheweb]

I was trying to get your Cluster Sharding Viewer example working with Redis

Which sample is this?

[andyfurnival]

https://github.com/Aaronontheweb/Cluster.Sharding.Viewer this one.

[Aaronontheweb]

Ah I see - good news though, this query:

https://github.com/Aaronontheweb/Cluster.Sharding.Viewer/blob/d19012d23ac1664608e8fbe27fddbebf5e549d14/src/Cluster.Sharding.Viewer/Program.cs#L22-L23

Is supported by Akka.Persistence.Redis.Query since it doesn't depend on tags.

Akka.Persistence.Redis/src/Akka.Persistence.Redis/Query/RedisReadJournal.cs

Lines 103 to 116 in 4aa8cd9

	public Source<EventEnvelope, NotUsed> CurrentEventsByPersistenceId(
	string persistenceId,
	long fromSequenceNr = 0L,
	long toSequenceNr = long.MaxValue)
	=> Source.ActorPublisher<EventEnvelope>(
	EventsByPersistenceIdPublisher.Props(
	persistenceId,
	fromSequenceNr,
	toSequenceNr,
	null,
	_maxBufferSize,
	_writeJournalPluginId))
	.MapMaterializedValue(_ => NotUsed.Instance)
	.Named("CurrentEventsByPersistenceId-" + persistenceId);

So does that viewer not run correctly with Redis right now?

[andyfurnival]

No, I can see query whilst monitoring redis which should return data (it does when called in redis-cli), but nothing ever returns in the console app. Might be serialisers. I’ll keep at it, now I know it should work