Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 06:23
    Nican edited #6265
  • 05:36
    Nican edited #6265
  • 05:36
    Nican opened #6265
  • Nov 25 00:05
    to11mtm commented #6195
  • Nov 25 00:04
    to11mtm commented #6195
  • Nov 25 00:04
    to11mtm commented #6195
  • Nov 24 20:17
    Aaronontheweb labeled #6262
  • Nov 24 20:16
    Aaronontheweb edited #6262
  • Nov 24 20:16
    Aaronontheweb synchronize #6262
  • Nov 24 20:16
    Aaronontheweb labeled #6263
  • Nov 24 20:16

    Aaronontheweb on v1.4

    converted build system to .NET … (compare)

  • Nov 24 20:16
    Aaronontheweb closed #6263
  • Nov 24 20:15
    Aaronontheweb auto_merge_disabled #6263
  • Nov 24 19:33
    Aaronontheweb commented #6195
  • Nov 24 19:21

    Aaronontheweb on dotnet6-build-agent

    (compare)

  • Nov 24 19:21
    Aaronontheweb closed #6247
  • Nov 24 19:21
    Aaronontheweb commented #6247
  • Nov 24 19:21
    Aaronontheweb auto_merge_disabled #6247
  • Nov 24 19:16
    Aaronontheweb synchronize #6263
  • Nov 24 19:16

    Aaronontheweb on v1.4

    cleaned up duplicate System.Col… (compare)

Ralf
@Ralf1108
hi, when unit testing actors via Testkit... is it still required in latest version to tear down the test actor system?
or is this handled by the base class "Testkit"?
Marc Piechura
@marcpiechura
@Ralf1108 that's handled by the Teskit
Ralf
@Ralf1108
ok thx
but is it normal that after test completes there are so much debug log entries like
DeadLetter from [akka://test/user] to [akka://test/user]: <<DeathWatchNotification>: [akka://test/user/TestProbe_DetailPageVersion_9c57b66d-5cc9-4b73-8ad4-d4bdef0ad324], ExistenceConfirmed=True, AddressTerminated=False>
do I have to collect these DeathWatchNotifications by myself?
or can I suppress them?
Arjen Smits
@Danthar
@Ralf1108 its normal. What is happening is that as the ActorSystem is being shutdown. Various actors are sending DeathWatchNotifications (which is a system level message), to Actors that are already gone.
Thus the deadletter logs
nothing to worry about.
Ralf
@Ralf1108
is it possible to suppress them as they pollute the test log :-)
Arjen Smits
@Danthar
There is currently some work being done to suppress deadletter notifications for system messages, but it needs more work.
So not at this time
Ralf
@Ralf1108
ok good to know. thx!
Aaron Stannard
@Aaronontheweb
off-topic, but I just switched to using this yesterday: http://cmder.net/
much nicer commandline experience for Windows
John Nicholas
@MrTortoise
ive used conemu for a while it is v good, noticed that is based off it. v cool
Jordan S. Jones
@jordansjones
heh.. I use Git-bash
Artur Karbone
@ArturKarbone
Have anyone used app/web config transformations for HOCON? Any sample?
Aaron Stannard
@Aaronontheweb
I have
I just replace the entire HOCON section full stop
Artur Karbone
@ArturKarbone
Yeah I suspected that replace of the whole section required
cfjames
@cfjames
Question on Cluster Sharding: Can you have more than one instance of a given type of entity on a single Node? The only statement I could find of this issue was "One entity instance may live only at one node at the time" in the documentation, but I'm not really sure what that is supposed to mean.
Bartosz Sypytkowski
@Horusiath
@cfjames yes you can. This statement means, that if you have for example actor representing User with id=1, you may be sure that as long as cluster is not partitioned, no more than one actor representing that user will be present at the same time, keeping your user state consistent
cfjames
@cfjames
@Horusiath got it thanks.
Kris Schepers
@schepersk
Any example out there on how to use Cluster Sharding with Lighthouse?
Vagif Abilov
@object
Hello, I am moving my router configuration to HOCON, but I am using my own hash mapping function that I send to WithHashMapping. Does this disqualifiy router configuration in HOCON file?
Kris Schepers
@schepersk
When Lighthouse is running and a node where a Sharding Region starts, I see the following message in the Lighthouse logging: "Messge Register from akka.tcp://clustername@ip:port/user/sharding/typename to akka://clustername/user/sharding/typenameCoordinator/singleton/coordinator was not delivered"
Andrea Balducci
@andreabalducci
@cconstantin need some info for the MongoDb Persistence. Just aligned to akka 1.0.7 on my fork, now I've to implement AtomicWrites. It is possible to have a call to WriteMessagesAsync with AtomicWrites on more than one PersistenceId?
Thomas Lazar
@thomaslazar
ok. i seem to forget something. i have a topshelf service running an actorsystem and i added all the akka.remote stuff and put the config in the app.config and the logs show me the actorsystem gets started with that config. but it doesn't open up a port to listen to when i start the service in the debugger. do i still need something else?
Thomas Lazar
@thomaslazar
ok. my own fault and hocon comes again to bite me in the ass... i put the remote section unter the actor section because copy'n'pasta.
Bartosz Sypytkowski
@Horusiath
@schepersk you probably need to restrict your cluster sharding to nodes not being lighthouse. One of the available sharding settings is the role, which tells what role does a cluster node need to have in order to support cluster sharding - without it, shard region will assume, that all nodes are capable of sharding (while lighthouse is not)
@andreabalducci no, it's not possible, persistence id describes boundaries of write operations for persistence
Kris Schepers
@schepersk
@Horusiath Indeed, I was just about to try that when I saw it in the source code :-) Thanks!
@Horusiath So, does this also mean that you can restrict the type of a shard to a node role? Lets say you have a shard region for AR1 running on role ABC and you want to start a shard for AR2 on a completely different node with role XYZ..
Bartosz Sypytkowski
@Horusiath
each node can have multiple roles
you can have role like 'sharding-enabled' and simply refer to it from sharding settings
Kris Schepers
@schepersk
okay, but what about service1 in the cluster with 2 instances (nodes), hosting shards for its entities. Then service2 is ready to join the cluster with some instances (nodes). Each of these services have their own cluster sharding configuration. So my guess is that it should be possible to keep the entities from migrating to nodes where they don't "belong" ?
Bartosz Sypytkowski
@Horusiath
you can do the same again with roles
Kamil Wojciechowski
@aph5nt
hummm... one thing is wondering me... will akknet run on .net core now ?
Kris Schepers
@schepersk
@Horusiath I'm seeing these log entries.. Any thoughts?
Akka.Actor.LocalActorRef: Message WriteMessagesSuccessful from akka://bm2cluster/system/akka.persistence.journal.sql-server to akka://bm2cluster/user/sharding/LoonbonVerwerking/2/7afca3c0-e26c-4a97-89a5-4dd9883533b6 was not delivered. 8 dead letters encountered.
Akka.Actor.LocalActorRef: Message WriteMessageSuccess from akka://bm2cluster/temp/mb to akka://bm2cluster/user/sharding/LoonbonVerwerking/2/7afca3c0-e26c-4a97-89a5-4dd9883533b6 was not delivered. 9 dead letters encountered.
Maybe because they already got passivated before persistence could provide feedback?
Vagif Abilov
@object
SQL Server persistence plugin works in 1.0.7 if I build it from sources but when I use a version from NuGet I get TypeLoadException
{"Method 'DeleteBatchMessages' in type 'Akka.Persistence.SqlServer.Journal.SqlServerJournalQueryBuilder' from assembly 'Akka.Persistence.SqlServer, Version=1.0.6.3, Culture=neutral, PublicKeyToken=null' does not have an implementation.":"Akka.Persistence.SqlServer.Journal.SqlServerJournalQueryBuilder"}
Marc Piechura
@marcpiechura
@object you need Akka.Persistence.SqlServer, Version=1.0.7 for akka 1.0.7
Vagif Abilov
@object
@Silv3rcircl3 but where can I get it from? It's not on NuGet.
I see that none of NuGet packages for the actual persistence plugins has been updated to 1.0.7 on NuGEt.
Thomas Lazar
@thomaslazar
so i have a question. i have an actor that gets a message from a remote client. in this message is information about a class this actor should retrieve from the container and a method and a bunch of params that the actor should call as well as the return type. so i have this actor that retrieves the object form the container, checks if there's a method on that class that fits the description of the message and then tries to call it with Invoke(). so far so good. it is all working so far. i put this Invoke() call inside a try catch block because i basically want to tell the sender if something happened to while calling the method and basically return the thrown exception as a message back to sender. but when the invoked method itself throws a TargetInvocationException because of reasons it seems the actor just dies. and i get some disassociation messages in the log and stuff like that. it's like the try catch block inside the receive method is just not working. any hints?
Marc Piechura
@marcpiechura
@object indeed, then you can't use akka 1.0.7 with persistence until the plugin get's updated
@object there is a PR akkadotnet/Akka.Persistence.SqlServer#24 that updates the plugin, so you need to wait until this was merged and released