Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 21:09
    Aaronontheweb commented #6065
  • 21:09
    Aaronontheweb auto_merge_enabled #6065
  • 21:09
    Aaronontheweb commented #6065
  • 21:03
    Arkatufus synchronize #6065
  • 20:57
    Arkatufus synchronize #6065
  • Aug 16 18:05
    Aaronontheweb synchronize #6065
  • Aug 16 18:05
    Aaronontheweb labeled #6065
  • Aug 16 18:05
    Aaronontheweb review_requested #6065
  • Aug 16 16:58
    Aaronontheweb commented #6063
  • Aug 16 16:58

    Aaronontheweb on dev

    [Cluster] Enable HeartbeatRespo… (compare)

  • Aug 16 16:58
    Aaronontheweb closed #6061
  • Aug 16 16:58
    Aaronontheweb closed #6063
  • Aug 16 14:51
    Arkatufus synchronize #6063
  • Aug 16 14:36
    Arkatufus synchronize #6063
  • Aug 16 14:10
    Arkatufus synchronize #6065
  • Aug 15 22:23
    Arkatufus synchronize #6065
  • Aug 15 20:56
    Arkatufus edited #6065
  • Aug 15 20:50
    Arkatufus opened #6065
  • Aug 15 18:25
    Arkatufus synchronize #6063
  • Aug 15 15:10
    Arkatufus synchronize #6063
Aaron Stannard
@Aaronontheweb
@schepersk you need to exclude Lighthouse from your shard regions in your configuration
it will never work
under any circumstances
because it doesn't run Akka.Cluster.Sharding or Akka.Persistence or Akka.Cluster.Tools
use the roles setting
Chris G. Stevens
@cgstevens
Are there any examples using Akka.Cluster.Tools ... I want to take my Cluster Monitor WinForms and be able to get the cluster info without having to part of the cluster.
Chris Constantin
@cconstantin
@andreabalducci what @Horusiath said :)
Aaron Stannard
@Aaronontheweb
@cgstevens there are some in the main repo
Bartosz Sypytkowski
@Horusiath
@schepersk your log suggest that your actor may be dead after persisting message inside the journal
ilhadad
@ilhadad

I am trying to run the cluster sharding example. Since I cannot compile the akka project I pulled the ClusterSharding.Node out into a clean solution. Installed all the references via Nuget. I am getting an error in the following line:

        public override string PersistenceId { get; } = Context.Parent.Path.Name + "/" + Context.Self.Path.Name;

The error is...

Akka.Persistence.UntypedPersistentActor.Context' is a 'property' but is used like a 'type'

What's missing?

Andreas Dirnberger
@Zetanova
Is the Ask valid in this sence or should i try to remove it in general?
var creditor = Context.ActorOf(PaymentCreditor.GetProps());
            service.Ask(AccountCommands.GetIdentity(state.AccountId))
                .PipeTo(creditor, success: m => PaymentProcessCommands.Credit(Id, m, state.Description, state.Amount));
Bartosz Sypytkowski
@Horusiath
@Zetanova you could use service.Tell(AccountCommands.GetIdentity(state.AccountId), creditor) and set message mapping on either sender or receiver side to have a valid value
this will set creditor as message sender
Andreas Dirnberger
@Zetanova
i am resolving one field of the command
of course the PaymentCreditor could do it to, but i would need to reduce the PaymentProcessCommands.Credit to AccountId-GUID
If i am sending the accountIdentity to the creditor before the credit command to set up the state, i would need to remove the account field of the credit command
Andreas Dirnberger
@Zetanova
Soem like a jumbo command generator pattern or actor initialize message pattern is missing me
Hyungho Ko
@hhko
Hi. @Horusiath Akka.NET 1.0.7 supports SupervisorStrategyConfigurator class for user guardian.
this is sample hocon.
      akka {
        actor {
          guardian-supervisor-strategy = "UserSupervisorExample.UserSupervisorStrategy"
        }
      }

namespace UserSupervisorExample
{
public class UserSupervisorStrategy : SupervisorStrategyConfigurator
{
public UserSupervisorStrategy()
{

    }

    public override SupervisorStrategy Create()
    {
        return new OneForOneStrategy((excep) =>
            {
                int x = 3;
                x = 6;

                return Directive.Restart;
            });
    }
}

}

however, Exception occurs in ActorSystem
Hyungho Ko
@hhko
blob
Marc Piechura
@marcpiechura
@hhko you need to provide the full qualified name, see the specs for an example
Hyungho Ko
@hhko
@Silv3rcircl3 thank you... I solve it. below
akka {
actor {
guardian-supervisor-strategy = "HelloWorldUserSupervisor.UserSupervisorStrategy, HelloWorldUserSupervisor"
}
}
i forget dll name. ^^;;
Andrea Balducci
@andreabalducci
@cconstantin @Horusiath if so I think JournalDbEngine (reference implementation) is buggy. should stop on first failure, now has a ContinueWhenAll so the stream can be corrupted rather than incomplete
Bartosz Sypytkowski
@Horusiath
@andreabalducci can you set an issue for that with some description?
Andrea Balducci
@andreabalducci
@Horusiath #1883 , I'm new to akka.net but have some background on EventSourcing / stream persistence. thank you for you help
Thomas Lazar
@thomaslazar
anyone got anything on my problem? i have a remote actor that i send a message to via a client. and as soon as that remote actor does anything that generates an exception that gets caught and handled in the remote actor the connection gets disassociated and the thing basically dies. what am i doing wrong here?
Bartosz Sypytkowski
@Horusiath
@thomaslazar can you provide some stack trace? It's unusual for random exception to cause disassociation
Thomas Lazar
@thomaslazar
cannot get any kind of relevant stacktrace. only what the log shows with the disassociation messages.
i will build a test solution and try if i get the same error there and if i do i'll up it on github
Bartosz Sypytkowski
@Horusiath
I know that the issue sometimes arises, when you have errors while trying to serialize/deserialize message
Andreas Dirnberger
@Zetanova
@Horusiath For the snapsot generation algo. there is beside event-count an other possibility. When each event has a timestamp and it is assumed that the application is pushing constantly events to the event-stream, then it is highly plausible that events in a short time frame are loaded faster then events over an longer timeframe. If the the events are over a long period >24h not snapshotted it can be done, even with only 2 events.
Thomas Lazar
@thomaslazar
@Horusiath it happens after i caught the exception. in the exception handler i basically just put that exception into a message and send it off to the sender and then exit the processing. and after the receive handler is left the connection dies.
but as i said i'll try to make a test program that "hopefully" has the same problem
Arjen Smits
@Danthar
You passing along a custom Exception class ? Could it be your Exception type is not serializable ?
Thomas Lazar
@thomaslazar
yeah. but nothing that shouldn't work. and in fact in not akka.remote tests it's working just fine.
Bartosz Sypytkowski
@Horusiath
@thomaslazar the more it points to serialization issue
Thomas Lazar
@thomaslazar
and i specifically have tests written that trigger said exceptions and the message returns just fine
and one exception that gets passed back is a TargetParameterCountException
and that doesn't work either
Thomas Lazar
@thomaslazar
ok guys. you were absolutely right. was a serialization issue.
switching to wire in my testsolution fixed the problem.
and i am stoopid as usual. was all there. nice and clean in the log file... stuff just didn't got output to the stdout
Arjen Smits
@Danthar
heh. No problem. It happens.
Kris Schepers
@schepersk

Question: I've got a sharded entity actor. It creates a child actor to perform some duty. When this child gets stopped by the entity actor, the following log entry appears:

Akka.Actor.LocalActorRef: Message DeathWatchNotification from akka://bm2cluster/user/sharding/LoonbonVerwerking/3/d8c52c1e-4843-4092-9cc4-43ec8f774737/lbvverrijking to akka://bm2cluster/user/sharding/LoonbonVerwerking/3/d8c52c1e-4843-4092-9cc4-43ec8f774737/lbvverrijking was not delivered. 5 dead letters encountered.

Before implementing sharding, this message didn't get logged.. Any idea's?

kariem-ali
@kariem-ali
Hi Guys. It seems that soft delete was removed form akka.persistence Eventsourced.DeleteMessages in 1.0.7. Is there any alternative?