Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Dec 07 11:49
    IgorFedchenko commented #4085
  • Dec 07 10:31
    IgorFedchenko commented #4085
  • Dec 07 08:36
    IgorFedchenko commented #4085
  • Dec 06 20:57
    IgorFedchenko commented #4085
  • Dec 06 20:32
    IgorFedchenko commented #4085
  • Dec 06 20:01
    IgorFedchenko commented #4085
  • Dec 06 19:55
    IgorFedchenko commented #4085
  • Dec 06 16:22
    Aaronontheweb labeled #3997
  • Dec 06 16:22
    Aaronontheweb closed #3997
  • Dec 06 16:20
    IgorFedchenko commented #3997
  • Dec 06 16:08
    IgorFedchenko commented #4085
  • Dec 06 15:50
    Aaronontheweb assigned #4085
  • Dec 06 15:50
    Aaronontheweb labeled #4085
  • Dec 06 15:50
    Aaronontheweb labeled #4085
  • Dec 06 15:49
    Aaronontheweb closed #4032
  • Dec 06 14:58
    IgorFedchenko commented #4032
  • Dec 06 14:57
    IgorFedchenko opened #4085
  • Dec 05 17:21
    Aaronontheweb synchronize #4079
  • Dec 05 17:20
    Aaronontheweb labeled #4084
  • Dec 05 17:20
    Aaronontheweb labeled #4084
Aaron Stannard
@Aaronontheweb
that looks like a bunch of marketing stuff
let me find the real deal
nathvi
@nathvi
lol
here you go
that's the original technical whitepaper
not some marketing BS for people who can't figure out if they need Dynamo or Oracle
Joshua Garnett
@joshgarnett
Aaron Stannard
@Aaronontheweb
the original Dynamo concepts I think were the idea of ring-based partitioning and using that to drive replicas too
and the usage of a gossip protocol was necessary for getting all of the topology information about which replicas were / were not available
"tunable consistency"
like, I think what was original about Dynamo wasn't any one idea
nathvi
@nathvi
Thanks!
Aaron Stannard
@Aaronontheweb
but the combination of all of them
Akka.NET's "ring-based partitioning" comes from consistent hashing routers and Cluster.Sharding's use of the same algos for shard placement
doesn't quite have the same opinionated design that Dynamo does since we're not a database - we're a multi-purpose framework
nathvi
@nathvi
Aaron Stannard
@Aaronontheweb
thanks! hope you liked it
nathvi
@nathvi
I did. Though, I'm not sure I understand this...
"I can’t understate ..." Should that be "I can't overstate"?
Aaron Stannard
@Aaronontheweb
probably
I just kind of rifle those posts out extemporaneously
nathvi
@nathvi
:)
Aaron Stannard
@Aaronontheweb
and I don't go back and revise them
which... is probably not a best practice
nathvi
@nathvi
lol,
I think open source software has had a huge part in pushing Microsoft to be more open
It's hard to compete with free
Looking to make my own company.
Onur Gumus
@OnurGumus
In a cluster, if a node is temporarily down and comes back alive after it is quarantined, it cannot rejoin to the cluster. What should I do for this case ?
Joshua Garnett
@joshgarnett
Restart the node
Onur Gumus
@OnurGumus
How can I detect that is quarantined?
Joshua Garnett
@joshgarnett
I’m pretty sure events are generated
Onur Gumus
@OnurGumus
Perhaps but can't find
hmm we have this Akka.Remote.QuarantinedEvent
@joshgarnett how do I restart a node without killing the process ?
Joshua Garnett
@joshgarnett
That’s what I mean
You have to restart the process
Of the node that was quarantined
Onur Gumus
@OnurGumus
Oh ok
Onur Gumus
@OnurGumus
@joshgarnett well you can actually just restart the system without killing the process
Joshua Garnett
@joshgarnett
Fair enough, in my experience if you were quarantined it was probably for a good reason and it’s makes sense to just do a full restart of the process.
Everyone’s use case is different though
Onur Gumus
@OnurGumus
I agree that is debatable
but it is an option.
Onur Gumus
@OnurGumus
From the following disassociation message, what can I deduce?
{"@t":"2018-03-23T11:13:46.3025809Z","@mt":"Association with remote system {0} has failed; address is now gated for {1} ms. Reason is: [{2}]","@l":"Warning","0":"akka.tcp://SmartGateSystem@localhost:9083","1":5000,"2":"Akka.Remote.EndpointDisassociatedException: Disassociated\r\n at Akka.Remote.EndpointWriter.PublishAndThrow(Exception reason, LogLevel level, Boolean needToThrow)\r\n at Akka.Remote.EndpointWriter.Unhandled(Object message)\r\n at Akka.Actor.ReceiveActor.ExecutePartialMessageHandler(Object message, PartialAction1 partialAction)\r\n at Akka.Actor.ReceiveActor.OnReceive(Object message)\r\n at Akka.Actor.UntypedActor.Receive(Object message)\r\n at Akka.Actor.ActorBase.AroundReceive(Receive receive, Object message)\r\n at Akka.Actor.ActorCell.ReceiveMessage(Object message)\r\n at Akka.Actor.ActorCell.ReceivedTerminated(Terminated t)\r\n at Akka.Actor.ActorCell.AutoReceiveMessage(Envelope envelope)\r\n at Akka.Actor.ActorCell.Invoke(Envelope envelope)\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at Akka.Actor.ActorCell.HandleFailed(Failed f)\r\n at Akka.Actor.ActorCell.SysMsgInvokeAll(EarliestFirstSystemMessageList messages, Int32 currentState)","Thread":"0014","LogSource":"[akka://SmartGateSystem/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FSmartGateSystem%40localhost%3A9083-21#899920873]","Timestamp":"2018-03-23T11:13:46.2955809Z","SourceContext":"akka://SmartGateSystem/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FSmartGateSystem%40localhost%3A9083-21","ApplicationSession":"bd4970e6-13cf-4d8b-b182-4cc438c736a4"}
`
Roman Golenok
@shersh

Hi guys, I'm running Lighthouse with configs

 remote {
            log-remote-lifecycle-events = DEBUG
            dot-netty.tcp {
              hostname = "127.0.0.1"
              port = 3333
            }
          }

But it's unreachable from non local clients.
if I change hostname to "0.0.0.0" I see errors like
dropping message for non-local recipient

So how I should change config for remote actor for using it's from outside of localhost?
AndreSteenbergen
@AndreSteenbergen
I am not that far that I can use multiple nodes with my own solution, but if I recall correct, you can also set a public host (it's actually in the lighthouse example) public-hostname = "POPULATE STATIC IP HERE"
I guess you will need to set that property as well.