These are chat archives for akkadotnet/akka.net

23rd
Sep 2016
Sergey Prytkov
@Rattenkrieg
Sep 23 2016 01:03
Hello guys, congrats with 1.1.2. But what is the status of pull #2277 and related issues? Is it fixed on Wire side?
Arsene Tochemey GANDOTE
@Tochemey
Sep 23 2016 06:59
@Horusiath Thank you for the answer.
Peter Bergman
@peter-bannerflow
Sep 23 2016 07:25
@Aaronontheweb About the Test.Scheduler issue, I've tried with .WithDispatcher(CallingThreadDispatcher.Id); but I still can't get the scheduled tell to fire. I've pretty much followed the example described in this article https://petabridge.com/blog/how-to-unit-test-akkadotnet-actors-akka-testkit/#how-do-i-test-scheduled-messages
Ronnie Overby
@ronnieoverby
Sep 23 2016 14:03
So, is there any good reason for this? After sending a poison pill to a broadcast group router, and receiving a Terminated message with that routers path, the router continues to route messages. Why?
output screenshot http://imgur.com/a/axeAG
Ronnie Overby
@ronnieoverby
Sep 23 2016 14:09
I wrote this test code to make sure that a poison pill wouldn't get forwarded by the router. I was happy to see that it didn't, but I can't understand why the router still functions.
Andrey Leskov
@andreyleskov
Sep 23 2016 15:12
Hi guys, congrats with 1.1.2 ! Every release is a step forward )
I'm trying to build a human-readable view of Akka.Persistence journal for production debug. I'm searching for possibility to subscribe to all persisted messages.
Now where is possibility to be notified only about some changes for persistence id, this functionality is provided by write journal:
Marc Piechura
@marcpiechura
Sep 23 2016 15:27
@andreyleskov sounds like a use case for persistence query http://doc.akka.io/docs/akka/current/scala/persistence-query.html module is ported but not the docs ;)
Andrey Leskov
@andreyleskov
Sep 23 2016 15:32
@Silv3rcircl3 I've read all docs for persisted query available at http://getakka.net/docs/persistence/persistence-query and some basics for Streams. It was initial idea that persistence queries and read journals are perfect tool for my goal.
But after playing with code it turned out we can have live event stream by persistence id or tag, but not for any persistence id. We can subscribe only to live stream of new and changed persistence id, that's why I've started to dig into the sources.
So we can be notified "hey, this id was added \ changed", but no event data will be provided. Workaround is to subscribe by each id, but I think overhead will be too big.
Andrey Leskov
@andreyleskov
Sep 23 2016 15:37
And what about using EventsByTag query with no tag specified ? ) http://doc.akka.io/docs/akka/current/scala/persistence-query.html#EventsByTag_and_CurrentEventsByTag
May be someone has experience?
BTW, is there any good article about using tags for aggregate roots? I've always used persistence Ids like 'AggregateRoot_xxxx-yyyy-xzzz-dddd' and was happy.
Bartosz Sypytkowski
@Horusiath
Sep 23 2016 15:40
@andreyleskov in general querying over all persistence ids is not a good idea - this is something not provided by default, as persistence queries are designed to tolerate partitions (so you can have events for persistence ids from 1 to 100 on one machine and from 101 to 200 on other)
if I'm correct event store also doesn't offer an ability to query over "all" streams
Andrey Leskov
@andreyleskov
Sep 23 2016 15:45
@Horusiath sure, querying all persistence id is not a good idea, I'm talking about be notified when a new message is saved by journal, regardless its persistence Id.
btw, SqlJournal current implementation queries for all persistence ids on startup ) Had a few problems with on on production. : https://github.com/akkadotnet/akka.net/blob/ecd0ede93c7fe7b888703fb54c03e2bcec39ef6f/src/contrib/persistence/Akka.Persistence.Sql.Common/Journal/QueryExecutor.cs#L159
Bartosz Sypytkowski
@Horusiath
Sep 23 2016 15:46
I suspected, this could be a problem in the future
just for curiosity, how many persistence ids do you have on production?
Sergey Prytkov
@Rattenkrieg
Sep 23 2016 15:47
Hello guys, congrats with 1.1.2. But what is the status of pull #2277 and related issues? Is it fixed on Wire side?
Bartosz Sypytkowski
@Horusiath
Sep 23 2016 15:48
strange, from what I know Wire should be able to serialize types marked as internal. @rogeralsing ?
Aaron Stannard
@Aaronontheweb
Sep 23 2016 15:49
@ronnieoverby good question
mind logging an issue for that?
Andrey Leskov
@andreyleskov
Sep 23 2016 15:51
@Horusiath ~ 350 000 unique ids and ~ 2 500 000 events in total
Problem was related to Azure sql db performance, we are far from theoretical limit )
Sergey Prytkov
@Rattenkrieg
Sep 23 2016 15:51
Wire now is 0.8.1, but I haven't found any release notes
this issue reported while Wire was at 0.8.0
Andrey Leskov
@andreyleskov
Sep 23 2016 15:58
@Horusiath @Silv3rcircl3 will such functionality be valuable for project? If yes I will create a PR.
Bartosz Sypytkowski
@Horusiath
Sep 23 2016 15:59
@andreyleskov I think, you can add it as an issue on github - this will be at least point to start a discussion
(also if I'm right, there might be already something similar available)
Roger Johansson
@rogeralsing
Sep 23 2016 16:44
There are tests in the Wire test suite that creates internal types, any specific details here
?
Alex Valuyskiy
@alexvaluyskiy
Sep 23 2016 17:17
@rogeralsing look at this PR akkadotnet/akka.net#2277
Roger Johansson
@rogeralsing
Sep 23 2016 17:20
Oooh, the array serializer fails on internal types... Didnt know that. Ill provide a fix asap
Ronnie Overby
@ronnieoverby
Sep 23 2016 20:30
@Aaronontheweb logged. Man. I'm on a role.
Aaron Stannard
@Aaronontheweb
Sep 23 2016 20:41
@ronnieoverby there's lots of stuff to test :p
stevemesser
@stevemesser
Sep 23 2016 23:42
See